Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, Radim Marek <radim(at)boringsql(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
Date: 2026-05-26 12:28:02
Message-ID: d52502b3-48cf-4eb4-a966-a0a46a4637de@iki.fi
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 26/05/2026 12:33, Andrey Borodin wrote:
>> On 26 May 2026, at 14:27, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>>
>> Hmm, okay. I am not sure what you mean here, could you demonstrate
>> your idea with a patch later?
>
> Something like attached, not tested yet, working on an automated test.

Yeah, that looks correct to me. It moves the locking on v16 to where it
happens on v17 and v18. I don't see any reason to hold the lock in the
earlier parts of RecordNewMultiXact() in v16.

- Heikki

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-05-26 14:44:38 BUG #19493: Assertion failure in pg_plan_advice with EXISTS subquery and DO_NOT_SCAN advice
Previous Message Nikita Malakhov 2026-05-26 11:17:45 Re: BUG #19458: OOM killer in jsonb_path_exists_opr (@?) with malformed JSONPath containing non-existent variables