Re:Transaction ID Wraparound in Postgres
by kuroyi on Thursday July 23, 2015 @01:35PM
(#9937248)
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.
[ Parent
| on HN ]
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.
Re:Transaction ID Wraparound in Postgres
by tokenizerrr on Thursday July 23, 2015 @04:22PM
(#9938252)
Could you elaborate on what settings you found insufficient?