| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Michael Banck <mbanck(at)gmx(dot)net> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, j(dot)karremans(at)jk-consult(dot)nl, rmt(at)lists(dot)postgresql(dot)org, PostgreSQL mailing lists <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8) |
| Date: | 2026-06-25 10:14:46 |
| Message-ID: | 50D52121-30FF-4A2D-9230-0EFD953A2C36@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
> On 25 Jun 2026, at 14:30, Michael Banck <mbanck(at)gmx(dot)net> wrote:
>
> If either the standby gets updated to the
> latest minor release first, or if somebody does PITR from a primary on an
> earlier release to an instance with the latest minor release, the
> standby/PITR deadlocks and just sits there.
A bit of clarification. To trigger this bug WAL must be generated by 16.10
or prior and replay must be done by latest release (16.14). And the WAL
trace must contain sufficient number of MultiXacts.
So far we had 3 or 4 reports on pgsql-bugs and few in chats.
But yeah, restoration from an old backup is a typical use case.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-06-25 10:17:31 | Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8) |
| Previous Message | Michael Banck | 2026-06-25 09:30:32 | Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-06-25 10:17:31 | Re: Out-of-Cycle release? (was Re: BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8) |
| Previous Message | vignesh C | 2026-06-25 10:00:20 | Re: Include sequences in publications created by pg_createsubscriber |