From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Andrei Varashen <voroshen.av@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Date: Tue, 10 Jun 2025 16:44:42 +0200
Message-ID: <9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel@cybertec.at> (raw)
In-Reply-To: <CAKe6vCZwCouvLPz9Djv5i2ePEf+JMJUODZDqgCbRtFfoZbRdPw@mail.gmail.com>
References: <18804-bccbbde5e77a68c2@postgresql.org>
<CAKe6vCZwCouvLPz9Djv5i2ePEf+JMJUODZDqgCbRtFfoZbRdPw@mail.gmail.com>
On Tue, 2025-06-10 at 12:02 +0200, Andrei Varashen wrote:
> Hi! Just kind reminder about bug report. I'm still waiting for some response
>
> On Tue, Feb 11, 2025 at 5:27 PM PG Bug reporting form <noreply@postgresql.org> wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 18804
> > Logged by: Andrei Varashen
> > Email address: voroshen.av@gmail.com
> > PostgreSQL version: 16.3
> > Operating system: Debian GNU/Linux 12 (bookworm)
> > Description:
> >
> > Hi there,
> >
> > I've encountered the error while trying to register a listener with the
> > LISTEN channel_name statement in my production database:
> >
> > STATEMENT: LISTEN river_leadership
> > ERROR: could not access status of transaction 2048841894
> > DETAIL: Could not open file "pg_xact/07A1": No such file or directory.
This is a duplicate of bug 16961:
https://www.postgresql.org/message-id/flat/16961-25f29f95b3604a8a%40postgresql.org
As far as I know, the problem happens when you are hold transactions
open for a very long time, so don't do that.
A restart of the database will fix the immediate problem.
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, voroshen.av@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
In-Reply-To: <9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel@cybertec.at>
* 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