Post

incident.io/blog/how-sav... wrote about Postgres internals for a long while

incident.ioHow savepoints quietly throttled our Postgres queue | Blog | incident.ioOur on-call ticker runs on a Postgres-backed queue. Under load test it slowed to a crawl, and adding workers only made it worse. The culprit was a savepoint per tick, minting a MultiXact on every lock...

7/10/26, 9:00 pm3 reposts11 likes

The Projekt

@wearetheprojekt.bsky.social

A savepoint per tick minting a MultiXact on every lock is nasty because pg_stat_activity looks totally normal. mxid_age(datminmxid) climbing is often the first number that gives it away.