Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


If 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.


> I hit this issue all the time

Curious to know your problem space and context? User generated content? Sensor logs?


Essentially a large volume of sensor data. Tons of inserts. Some updates in other tables.


Could you elaborate on what settings you found insufficient?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: