Thanks for the support. It looks like the transaction cleared off over the weekend.
Chris
On Monday, November 29, 2021, 05:13:28 AM EST, Dischner, Anton <anton.dischner@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Tom,
do you see heavy disk activity?
best,
A
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@xxxxxxxxxxxxx>
Gesendet: Freitag, 26. November 2021 19:42
An: Chris Cawley <cj_cawley@xxxxxxxxx>
Cc: pgsql-admin@xxxxxxxxxxxxxxxxxxxx
Betreff: Re: What do you do with a long running rollback
Chris Cawley <cj_cawley@xxxxxxxxx> writes:
> It's been like that for several days already.
Really? Rollback is O(1) in Postgres.
I could possibly believe that it's blocked on a lock, but even that would be a bug, because transaction abort should never try to take any new locks.
A perhaps-more-plausible theory is that you've enabled synchronous commit but your replica is failing to ack the transmission of the abort's WAL record.
What are you looking at exactly?
regards, tom lane
do you see heavy disk activity?
best,
A
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@xxxxxxxxxxxxx>
Gesendet: Freitag, 26. November 2021 19:42
An: Chris Cawley <cj_cawley@xxxxxxxxx>
Cc: pgsql-admin@xxxxxxxxxxxxxxxxxxxx
Betreff: Re: What do you do with a long running rollback
Chris Cawley <cj_cawley@xxxxxxxxx> writes:
> It's been like that for several days already.
Really? Rollback is O(1) in Postgres.
I could possibly believe that it's blocked on a lock, but even that would be a bug, because transaction abort should never try to take any new locks.
A perhaps-more-plausible theory is that you've enabled synchronous commit but your replica is failing to ack the transmission of the abort's WAL record.
What are you looking at exactly?
regards, tom lane
