On 2026-May-05, Antonin Houska wrote: > However, I failed to notice that COMMIT record of > a transaction listed in the xl_running_xacts WAL record is not guaranteed to > follow the xl_running_xacts record in WAL. In other words, even if > xl_running_xacts is created before a COMMIT record of the contained > transaction, it may end up at higher LSN in WAL. So the cleanup I relied on > might not take place.
That's pretty bad news. > I've got no good idea how to fix that. Not sure I'm able to pursue the > "database-specific snapshots" feature now. It appears that the only reasonable course of action at this point is to revert 0d3dba38c777. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
