Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction" - Mailing list pgsql-bugs

From Laurenz Albe
Subject Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Date
Msg-id 9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel@cybertec.at
Whole thread Raw
In response to Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"  (Andrei Varashen <voroshen.av@gmail.com>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Andrei Varashen
Date:
Subject: Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Next
From: PG Bug reporting form
Date:
Subject: BUG #18953: Planner fails to build plan for complex query with LATERAL references