Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Sebastian Webber <sebastian(at)swebber(dot)me>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Andrey Borodin <amborodin(at)acm(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Dmitry Yurichev <dsy(dot)075(at)yandex(dot)ru>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Ivan Bykov <i(dot)bykov(at)modernsys(dot)ru>, Kirill Reshke <reshkekirill(at)gmail(dot)com>
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date: 2026-02-15 18:11:32
Message-ID: 029A0108-DB58-4A62-A8DF-A8E6FBF9E4B2@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 14 Feb 2026, at 22:41, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> Wiping write by XLOG_MULTIXACT_TRUNCATE_ID seems correct to me everywhere 14-18.

FWIW I've tried to create a TAP-reproducer, but it's tricky in controlled environment.
But I've created a TAP that triggers near-wraparound truncation:

2026-02-15 23:05:57.716 +05 [73950] DEBUG: replaying multixact truncation: offsets [1, 2147483648), offsets segments [0, 8000), members [1, 3), members segments [0, 0)
2026-02-15 23:05:57.716 +05 [73950] CONTEXT: WAL redo at 0/309CD70 for MultiXact/TRUNCATE_ID: offsets [1, 2147483648), members [1, 3)
2026-02-15 23:05:57.716 +05 [73950] DEBUG: MultiXactId wrap limit is 4294967295, limited by database with OID 1
2026-02-15 23:05:57.716 +05 [73950] CONTEXT: WAL redo at 0/309CD70 for MultiXact/TRUNCATE_ID: offsets [1, 2147483648), members [1, 3)
2026-02-15 23:05:57.716 +05 [73950] LOG: file "pg_multixact/offsets/8000" doesn't exist, reading as zeroes

And I observe no problems with applied "0001-Don-t-reset-latest_page_number-when-replaying-multix.patch"

Best regards, Andrey Borodin.

Attachment Content-Type Size
0001-Test-Multixact-truncation-near-araparound.patch application/octet-stream 13.5 KB
unknown_filename text/plain 2 bytes

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Reshke 2026-02-16 06:45:29 Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Previous Message Tom Lane 2026-02-15 15:10:33 Re: BUG #19410: Cannot ser client_encoding