Postgres Pro
Downloads
Home   >   mailing lists

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

From tiamoh m
Subject Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Date
Msg-id CAPsGGUrKHYNduUFKx9_3AoTt87kpOs_pWr6coviCw52kSkRtpQ@mail.gmail.com
Whole thread Raw
In response to Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin
Tree view
Thank you very much Laurenz Albe

On Wed, Jan 29, 2025 at 12:40 AM Laurenz Albe <laurenz.albe@cybertec.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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Next
From: Laurenz Albe
Date:
Subject: Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091