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 Andrey Borodin
Subject Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date
Msg-id ACB73592-44AB-40EB-85F6-19A00184D29F@yandex-team.ru
Whole thread Raw
In response to Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"  (Andrey Borodin <x4mmm@yandex-team.ru>)
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 14 Feb 2026, at 21:18, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
> Perhaps, we also can bump latest_page_number forward?
This is not a good idea, we don't want "most accurate latest_page_number", we need precise number at any point after
StartupMultiXact().

Wiping write by XLOG_MULTIXACT_TRUNCATE_ID seems correct to me everywhere 14-18.

I'd also suggest updating comment:

* this is not critical data, since we use it only to avoid swapping out
* the latest page.

It's absolutely critical now.


Best regards, Andrey Borodin.

pgsql-bugs by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Next
From: Thomas Munro
Date:
Subject: Re: BUG #19406: substring(text) fails on valid UTF-8 toasted value in PostgreSQL 15.16