public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: tiamoh m <[email protected]>
To: [email protected]
Subject: Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR: could not access status of transaction 432906091
Date: Wed, 29 Jan 2025 06:40:07 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAPsGGUpE11R6S4Bts=D-aL_fnhNRfq5vLB_0nDiWStz4Dc7E-A@mail.gmail.com>
References: <CAPsGGUpE11R6S4Bts=D-aL_fnhNRfq5vLB_0nDiWStz4Dc7E-A@mail.gmail.com>
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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR: could not access status of transaction 432906091
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox