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

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Radim Marek <radim(at)boringsql(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 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 08:41:03
Message-ID: AC1516B2-2E78-4C70-8A6E-2966F01A1058@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 26 May 2026, at 13:30, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
>
> Releasing MultiXactOffsetSLRULock around SimpleLruWriteAll() preserves
> the flush-before-physical-check rule while avoiding the self-deadlock.

I think we don't need to release lock, we just need to acquire it later, as it is done
in 17+ branches.

FWIW I'm working on buildfarm module that will recovery regress WAL from
REL_x_0 through replay by REL_x_STABLE.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-05-26 09:27:15 Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8
Previous Message Ayush Tiwari 2026-05-26 08:30:30 Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8