Error "could not access status of transaction" - version 14.21

From: Aaron Caskey-Demaret <aaron(dot)caskey-demaret(at)nshift(dot)com>
To: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Error "could not access status of transaction" - version 14.21
Date: 2026-02-19 14:47:18
Message-ID: AM7P192MB0771E47F1A21FD544623DF86A36BA@AM7P192MB0771.EURP192.PROD.OUTLOOK.COM
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

When replicating to version 14.21 from version 14.20 we encountered the following error:

2026-02-19 12:22:36.927 CET [4005-295] FATAL: could not access status of transaction 13690880
2026-02-19 12:22:36.927 CET [4005-296] DETAIL: Could not read from file "pg_multixact/offsets/00D0" at offset 237568: read too few bytes.
2026-02-19 12:22:36.927 CET [4005-297] CONTEXT: WAL redo at 27E6A/15BFDE98 for MultiXact/CREATE_ID: 13690879 offset 27490069 nmembers 2: 616733495 (keysh) 616733515 (keysh)
2026-02-19 12:22:37.928 CET [2582-6] LOG: startup process (PID 4005) exited with exit code 1
2026-02-19 12:22:37.928 CET [2582-7] LOG: terminating any other active server processes
2026-02-19 12:22:40.622 CET [2582-8] LOG: shutting down due to startup process failure
2026-02-19 12:22:44.994 CET [2582-9] LOG: database system is shut down

The server would restart, but the issue would crop up again within 30 mins (different offsets)

After rolling back to version 14.20 the environment is stable again.

I'm guessing this is the exact same issue as https://www.postgresql.org/message-id/CACV2tSw3VYS7d27ftO_cs%2BaF3M54%2BJwWBbqSGLcKoG9cvyb6EA%40mail.gmail.com I just wanted to log that the issue is affecting other versions as well.

Regards

Aaron Caskey-Demaret

Site Reliability Engineer

aaron(dot)caskey-demaret(at)nshift(dot)com

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Reshke 2026-02-19 17:34:29 Re: Error "could not access status of transaction" - version 14.21
Previous Message Vishal Prasanna 2026-02-19 13:43:10 [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change