Horton
Menu

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

Heikki Linnakangas <hlinnaka@iki.fi>

View thread
From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: Sebastian Webber <sebastian@swebber.me>, pgsql-bugs@lists.postgresql.org, Andrey Borodin <amborodin@acm.org>, Álvaro Herrera <alvherre@kurilemu.de>, Dmitry Yurichev <dsy.075@yandex.ru>, Chao Li <li.evan.chao@gmail.com>, Ivan Bykov <i.bykov@modernsys.ru>
Date: 2026-02-16T16:01:54Z
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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Don't reset 'latest_page_number' when replaying multixid truncation

  2. Set next multixid's offset when creating a new multixid

  3. Rework the way multixact truncations work.