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

From Laurenz Albe
Subject Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
Date
Msg-id 5a1a6a1da3478a949bc8ff186f314498182921d2.camel@cybertec.at
Whole thread Raw
In response to PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091  (tiamoh m <tiamohm25@gmail.com>)
Responses Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091
List 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



pgsql-admin by date:

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