Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation
Date
Msg-id e541ee5d-6515-4623-88c9-81d8d3fa2c63@iki.fi
Whole thread Raw
In response to Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation  (Ayush Tiwari <ayushtiwari.slg01@gmail.com>)
List 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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_waldump: support decoding of WAL inside tarfile
Next
From: Heikki Linnakangas
Date:
Subject: Re: Avoid use of TopMemoryContext for resource owner cleanup in portals