Yamakaky
Yamakaky
Idea: instead of copying the framebuffer, why not copy the textures currently used ? It would solve the synchronisation problem between two buffers. It may not be possible to batch...
Any development?
It could be a post-prod effect with opengl.
Maybe simply show the optimized `Ciphers` line in addition to the existing output? It would be easier to apply to the server conf, also.
Yes, see my schema just above. All timescaledb docs don't include primary keys, just time.
No, I just ended up adding an insert trigger on ltss to copy data to my hypertable. It would be better to have native support.
To add on my usecase: in my instance, I added `state_*` columns since it quickly became a pain to have casting with handling of invalid values at every query. For...
I understand your concern, however I don't think it's specific to my usecase. I assume most if not all ltss instances will need to cast to floats at some point...
That would work, at the cost of duplicate data between the aggregate and the main table. Data rate is pretty slow on my side so it should be fine.
You could also use [alpine linux](https://hub.docker.com/_/alpine/) as a base image, it would really slime down the size of the containers.