Обсуждение: PID=2299350| 19| LISTEN| PGE-58P01:ERROR: could not access status of transaction 432906091
Hello,
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 ?
Kind regards
Tiamoh M
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
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
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.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
On Wed, 2025-01-29 at 13:42 -0500, tiamoh m wrote: > How is this possible? > Because I know pg_xact cannot be cleaned while a transaction is still active Perhaps this thread can explain it: https://www.postgresql.org/message-id/flat/VE1PR03MB531295B1BDCFE422441B15FD92499%40VE1PR03MB5312.eurprd03.prod.outlook.com#7e36d1fdca921b5292e92c7017984ffa Yours, Laurenz Albe