Rich Turner
Rich Turner
Some useful info in this article: https://www.cybertec-postgresql.com/en/tuning-autovacuum-postgresql/ I'm thinking we should just have something in PersistenceService init to configure these optimisations with an env variable to determine if the settings...
Discussed logging some metrics and/or long query logging in postgres itself, the query at the top of this issue gives a good insight into auto vacuum performance metrics but should...
Investigate timescaleDB table compression can we delete records that are compressed
TImescaleDB auto tune could this be used periodically?
@Miggets7 some more resources: https://www.depesz.com/2022/03/13/is-my-autovacuum-configured-properly/ https://www.reddit.com/r/PostgreSQL/comments/1dmvaco/monitor_bloated_tables/
Some really good info @Miggets7 so `pg_squeeze` would be an alternative to standard auto vacuum?
Some thoughts: ### Size Optimisation Add retention policy for timescaleDB `asset_datapoint` and `asset_predicted_datapoint` this should be done in the `postgres` docker image and the values should be configurable with env...
@Miggets7 let's discuss this when you are working next
The problem here is that there is no realm in the URL, we would need some way of parsing the realm in the URL either using existing queryparam mechanism e.g....
Maybe run this with the new master branch and we can get it merged without dealing with these conflicts