public inbox for [email protected]
help / color / mirror / Atom feedFrom: Michael Banck <[email protected]>
To: Sebastian Webber <[email protected]>
Cc: [email protected]
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
Date: Sat, 14 Feb 2026 10:05:02 +0100
Message-ID: <[email protected];lightning.p46.dedyn.io> (raw)
In-Reply-To: <CACV2tSw3VYS7d27ftO_cs+aF3M54+JwWBbqSGLcKoG9cvyb6EA@mail.gmail.com>
References: <CACV2tSw3VYS7d27ftO_cs+aF3M54+JwWBbqSGLcKoG9cvyb6EA@mail.gmail.com>
Hi,
On Fri, Feb 13, 2026 at 05:31:18PM -0300, Sebastian Webber wrote:
> Description
> -----------
>
> A PostgreSQL 17.8 standby crashes during WAL replay when streaming
> from a 17.5 primary. The crash occurs after replaying a
> MultiXact/TRUNCATE_ID record followed by a MultiXact/CREATE_ID
> record.
Ouch.
For the record, somebody else (Jacob Bunk Nielsen) reported the same(?) issue
independently on Slack:
|We are running a PostgreSQL 17.7 primary with a number of physical replicas. We upgraded some of the replicas from 17.5 to 17.8 earlier today, and now 4 of them consistently die after a short time with errors like:
|
|Feb 13 13:36:01 srv2 postgres[13068]: [12-1] 2026-02-13 13:36:01 UTC::@:[13068]: FATAL: could not access status of transaction 155428864
|Feb 13 13:36:01 srv2 postgres[13068]: [12-2] 2026-02-13 13:36:01 UTC::@:[13068]: DETAIL: Could not read from file "pg_multixact/offsets/0943" at offset 172032: read too few bytes.
|Feb 13 13:36:01 srv2 postgres[13068]: [12-3] 2026-02-13 13:36:01 UTC::@:[13068]: CONTEXT: WAL redo at 9F79/27144740 for MultiXact/CREATE_ID: 155428863 offset 1359592572 nmembers 2: 448728610 (keysh) 448728612 (keysh)
|
|Did we hit a bug in the newly released 17.8?
Sebastian, as it looks like you are able to reproduce it - are you maybe in a
position to bisect from 17.5 to 17.8 to see which commit is responsible for this?
Michael
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: 17.8 standby crashes during WAL replay from 17.5 primary: "could not access status of transaction"
In-Reply-To: <[email protected];lightning.p46.dedyn.io>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox