Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Andrei Varashen <voroshen(dot)av(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18804: LISTEN on channel fails with "could not access status of transaction"
Date: 2025-06-10 14:44:42
Message-ID: 9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)org> wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference:      18804
> > Logged by:          Andrei Varashen
> > Email address:      voroshen(dot)av(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-06-10 18:00:01 BUG #18953: Planner fails to build plan for complex query with LATERAL references
Previous Message Michael Paquier 2025-06-10 11:14:40 Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements