4 ms·
I hit this issue all the time and it is never easy or fast to fix once postgres stops accepting writes. If you have a write heavy postgres database, the autovac
by kuroyi 11y ago
I hit this issue all the time and it is never easy or fast to fix once postgres stops accepting writes. If you have a write heavy postgres database, the autovacuum settings are not sufficient. The entire database needs to be vacuumed aggressively.
- dinedal 11y ago> I hit this issue all the time Curious to know your problem space and context? User generated content? Sensor logs?
- kuroyi 11y agoEssentially a large volume of sensor data. Tons of inserts. Some updates in other tables.
- tokenizerrr 11y agoCould you elaborate on what settings you found insufficient?
- rosser 11y agoIf you have a write heavy postgres database, the autovacuum settings are not sufficient. Then you tune it to run more aggressively. There are configuration parameters specifically for this.