From: Matheus Alcantara <matheusssilv97@gmail.com>
To: Smolkin Grigory <smallkeen@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: clog segment truncation
Date: Mon, 10 Nov 2025 10:05:26 -0300
Message-ID: <DE51BYNX23R4.171OIQ4ZKTK1A@gmail.com> (raw)
In-Reply-To: <CAMp+ueZkG+HTWd0tajG4nDU_Vk51+wkngtuq7XjOjEBEW7t8Gw@mail.gmail.com>
References: <CAMp+ueZkG+HTWd0tajG4nDU_Vk51+wkngtuq7XjOjEBEW7t8Gw@mail.gmail.com>
On Mon Nov 10, 2025 at 9:29 AM -03, Smolkin Grigory wrote:
> Hello, hackers!
>
> I`m currently investigating the case of one of our PostgreSQL instance
> having started issuing error messages about missing clog segment:
> ERROR: could not access status of transaction 1550558894
> DETAIL: Could not open file "pg_xact/05C6": No such file or directory.
>
Is this error happening with the LISTEN/NOTIFY? There is a discussion
going on [1] that aims to fix this issue for the LISTEN/NOTIFY.
[1] https://www.postgresql.org/message-id/CAK98qZ3wZLE-RZJN_Y%2BTFjiTRPPFPBwNBpBi5K5CU8hUHkzDpw%40mail.g...
--
Matheus Alcantara
EDB: http://www.enterprisedb.com
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: pgsql-bugs@postgresql.org
Cc: matheusssilv97@gmail.com, smallkeen@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: clog segment truncation
In-Reply-To: <DE51BYNX23R4.171OIQ4ZKTK1A@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox