Message-ID: <9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel@cybertec.at>
Subject: Re: BUG #18804: LISTEN on channel fails with "could not access
 status of transaction"
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Andrei Varashen <voroshen.av@gmail.com>, pgsql-bugs@lists.postgresql.org
Date: Tue, 10 Jun 2025 16:44:42 +0200
In-Reply-To: 
 <CAKe6vCZwCouvLPz9Djv5i2ePEf+JMJUODZDqgCbRtFfoZbRdPw@mail.gmail.com>
References: <18804-bccbbde5e77a68c2@postgresql.org>
	 <CAKe6vCZwCouvLPz9Djv5i2ePEf+JMJUODZDqgCbRtFfoZbRdPw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/9ca962e107aaad0bed399dc5ae47a761b8a61c95.camel%40cybertec.at>
Precedence: bulk

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 respo=
nse
>=20
> On Tue, Feb 11, 2025 at 5:27=E2=80=AFPM PG Bug reporting form <noreply@po=
stgresql.org> wrote:
> > The following bug has been logged on the website:
> >=20
> > Bug reference:=C2=A0 =C2=A0 =C2=A0 18804
> > Logged by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Andrei Varashen
> > Email address:=C2=A0 =C2=A0 =C2=A0 voroshen.av@gmail.com
> > PostgreSQL version: 16.3
> > Operating system:=C2=A0 =C2=A0Debian GNU/Linux 12 (bookworm)
> > Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0=20
> >=20
> > Hi there,=20
> >=20
> > I've encountered the error while trying to register a listener with the
> > LISTEN channel_name statement in my production database:
> >=20
> > 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%40postgre=
sql.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