Just monitor it and you’re done. I’ve delivered and maintained hundreds of pg instances and never faced this issue. There is so much literature about it that at some point no one even slightly skilled will face it.
This is just anecdote, colliding with documented database behavior, who is not an issue on Oracle, SQL Server, or IBM DB2.
PostgreSQL explicitly documents xid wraparound as a failure mode that can lead to catastrophic data loss and says vacuuming is required to prevent it. Near exhaustion, it will refuse commands.
Getting AI vibes from this article? It is strangely repetitive and meandering. Also tell-tale "It's not X, it's Y" and sort of unspecific mostly.
Also, why would you have billions of open transactions? That is the implication I got from the article as someone who doesn't know anything about Postgres.
(I use SQLite and perhaps I have Stockholm syndrome, but I like how it pushes you towards a design with small transactions, ideally entirely database-side.)
I meant "obvious to anyone putting PostgreSQL in production that they have to put specific monitoring in place for this, and palliative measures"
The database shutting itself down and refusing to come back up until a full vacuum or vacuum freeze is performed, which means days of downtime, yes, that's pretty obvious indeed.
tl;dr: autovacuum was seen to be active during an earlier incident, assumed to be at fault, and was disabled. It was never re-enabled. The long-term implications of disabling autovacuum were not actively considered.
TL;DR: Devs didn't know what they were doing and turned off autovacuum and eventually it broke, then the author decided to have an AI slop out an article about the incident which may or may not have actually occurred.
