Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation
Date: 2026-03-22 12:29:08
Message-ID: e541ee5d-6515-4623-88c9-81d8d3fa2c63@iki.fi
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17/03/2026 17:07, Ayush Tiwari wrote:
> On Tue, 17 Mar 2026 at 03:40, Heikki Linnakangas <hlinnaka(at)iki(dot)fi
> <mailto:hlinnaka(at)iki(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-03-22 12:39:58 Re: Avoid use of TopMemoryContext for resource owner cleanup in portals
Previous Message Andrew Dunstan 2026-03-22 11:24:56 Re: pg_waldump: support decoding of WAL inside tarfile