pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedAW: What do you do with a long running rollback
2+ messages / 2 participants
[nested] [flat]
* AW: What do you do with a long running rollback
@ 2021-11-29 10:10 Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
2021-11-29 13:22 ` Re: AW: What do you do with a long running rollback Chris Cawley <cj_cawley@yahoo.com>
0 siblings, 1 reply; 2+ messages in thread
From: Dischner, Anton @ 2021-11-29 10:10 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Chris Cawley <cj_cawley@yahoo.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Hi Tom,
do you see heavy disk activity?
best,
A
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@sss.pgh.pa.us>
Gesendet: Freitag, 26. November 2021 19:42
An: Chris Cawley <cj_cawley@yahoo.com>
Cc: pgsql-admin@lists.postgresql.org
Betreff: Re: What do you do with a long running rollback
Chris Cawley <cj_cawley@yahoo.com> 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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: AW: What do you do with a long running rollback
2021-11-29 10:10 AW: What do you do with a long running rollback Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
@ 2021-11-29 13:22 ` Chris Cawley <cj_cawley@yahoo.com>
0 siblings, 0 replies; 2+ messages in thread
From: Chris Cawley @ 2021-11-29 13:22 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
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@med.uni-muenchen.de> wrote:
Hi Tom,
do you see heavy disk activity?
best,
A
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl@sss.pgh.pa.us>
Gesendet: Freitag, 26. November 2021 19:42
An: Chris Cawley <cj_cawley@yahoo.com>
Cc: pgsql-admin@lists.postgresql.org
Betreff: Re: What do you do with a long running rollback
Chris Cawley <cj_cawley@yahoo.com> 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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-11-29 13:22 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-11-29 10:10 AW: What do you do with a long running rollback Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
2021-11-29 13:22 ` Chris Cawley <cj_cawley@yahoo.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox