Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation
Heikki Linnakangas <hlinnaka@iki.fi>
From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2026-03-22T12:29:08Z
Lists: pgsql-hackers
On 17/03/2026 17:07, Ayush Tiwari wrote: > On Tue, 17 Mar 2026 at 03:40, Heikki Linnakangas <hlinnaka@iki.fi > <mailto:hlinnaka@iki.fi>> wrote: > >> Hmm, although why did I not apply commit 817f74600d to 'master', only >> backbranches? The bug that it fixed was related to minor version >> upgrade, and thus it was not needed on 'master', but the code change >> would nevertheless make a lot of sense on 'master' too. > > Agreed, once 817f74600d is on master the standby would honestly evaluate > the SimpleLruTruncate wraparound backstop instead of bypassing it. I now committed that change to master too. - Heikki
Commits
-
Don't reset 'latest_page_number' when replaying multixid truncation
- 516310ed4dba 19 (unreleased) landed
- 817f74600d0d 18.3 cited
-
Set next multixid's offset when creating a new multixid
- 8ba61bc06386 17.8 cited