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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: tiamoh m <tiamohm25(at)gmail(dot)com>, 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 05:40:07
Message-ID: 5a1a6a1da3478a949bc8ff186f314498182921d2.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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 tiamoh m 2025-01-29 15:12:37 Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Previous Message tiamoh m 2025-01-28 21:46:20 PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091