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>
Cc: 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 19:03:29
Message-ID: 9397b80e7a5258eaf4e68f3b93a7a921f7ca194c.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message srinivasan s 2025-01-30 08:47:56 Partition management - best practices and avoid long access exclusive lock during partition creation
Previous Message tiamoh m 2025-01-29 18:42:16 Re: PID=2299350| 19| LISTEN| PGE-58P01:ERROR:  could not access status of transaction 432906091