Request a Demo
Home   >   mailing lists

Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction" - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date
Msg-id 79171a15-1bb9-44ea-b2a9-1904f13364e6@iki.fi
Whole thread Raw
In response to Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"  (Kirill Reshke <reshkekirill@gmail.com>)
Responses Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
List pgsql-bugs
Tree view 
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

pgsql-bugs by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Next
From: Andrew Dunstan
Date:
Subject: Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.