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

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
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>
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date: 2026-02-16 16:01:54
Message-ID: 79171a15-1bb9-44ea-b2a9-1904f13364e6@iki.fi
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 16/02/2026 08:45, Kirill Reshke wrote:
> Patch LGTM.

Ok, thanks. I updated the comment to point out that 'latest_page_number'
is used for this backwards-compatibility hack, per Andrey's suggestion,
and committed.

I did some testing of this with the Sebastian's script, but Andrey if
you can verify with your TAP test, too, that'd be great.

> Lets wrap new minors with IT?

Yep, that's now planned for next week:
https://www.postgresql.org/message-id/177125656521.788.2734531836137629391%40wrigleys.postgresql.org

- Heikki

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Dunstan 2026-02-16 16:18:28 Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
Previous 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"