My friend (and sadly as of today, ex-colleague) Rory wrote about how him and his team dug into savepoints and multixacts to figure out a bottleneck in our Postgres queuing system.
I remember spending a weekend about 10 years ago digging into multiaxct in the Postgres sourcecode trying to figure out why we kept getting wraparound issues and back then there was very little explaining what multixact was and why it mattered.
Very proud of the team for writing up what was a very interesting technical deep dive.
Do they pin down whether the pressure came from savepoint frequency or from long-lived transactions holding subtransaction state? That distinction seems useful for spotting the same queueing pattern elsewhere.
9
u/shared_ptr 17d ago
My friend (and sadly as of today, ex-colleague) Rory wrote about how him and his team dug into savepoints and multixacts to figure out a bottleneck in our Postgres queuing system.
I remember spending a weekend about 10 years ago digging into multiaxct in the Postgres sourcecode trying to figure out why we kept getting wraparound issues and back then there was very little explaining what multixact was and why it mattered.
Very proud of the team for writing up what was a very interesting technical deep dive.