Performance / Article
How savepoints quietly throttled our Postgres queue
The article describes a Postgres-backed escalation queue that used SAVEPOINT subtransactions and SKIP LOCKED, then suffered MultiXact LWLock contention under load. It reports that separating claiming from ticking, removing subtransactions, and reducing claim scans improved peak escalation throughput by 3.5x.
Read the originalWhy it’s in the collection
Offers concrete diagnosis and mitigation patterns for Postgres queue contention, including MultiXact waits, HOT updates, and fillfactor.
THE CONVERSATION
Found on Hacker News 2
Links lead to the original story or comment where this resource appeared. Titles identify the surrounding discussion.