Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091

From: tiamoh m <tiamohm25(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Date: 2025-01-29 18:42:16
Message-ID: CAPsGGUoOeXjhrdqm82MAWE1Huv1ZQW-j0cja_OaxHdeiQEB29w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello Laurenz

How is this possible?
Because I know pg_xact cannot be cleaned while a transaction is still
active

On Wed, Jan 29, 2025 at 12:40 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:

> On Tue, 2025-01-28 at 16:46 -0500, tiamoh m wrote:
> > I have been having this bizarre error in most of my postgresql clusters.
> >
> > I don't know if anyone has experienced this or has a solution ?
>
> That happens when you are using LISTEN and NOTIFY, but your transactions
> are so long that by the time the signal is delivered, the information
> about the transaction is already gone.
>
> Use shorter database transactions.
>
> Yours,
> Laurenz Albe
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2025-01-29 19:03:29 Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Previous Message tiamoh m 2025-01-29 15:12:37 Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091