From: | "Dischner, Anton" <Anton(dot)Dischner(at)med(dot)uni-muenchen(dot)de> |
---|---|
To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Cawley <cj_cawley(at)yahoo(dot)com> |
Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | AW: What do you do with a long running rollback |
Date: | 2021-11-29 10:10:57 |
Message-ID: | ed80d5c2840c432099df8a6f56b40d8a@MITMB5.helios.med.uni-muenchen.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Hi Tom,
do you see heavy disk activity?
best,
A
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Gesendet: Freitag, 26. November 2021 19:42
An: Chris Cawley <cj_cawley(at)yahoo(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Betreff: Re: What do you do with a long running rollback
Chris Cawley <cj_cawley(at)yahoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Gaurav Anand | 2021-11-29 12:35:39 | Re: PGXN installation failure for Postgres Image of PostgreSQL 12 and 13 versions. |
Previous Message | Ron | 2021-11-29 09:02:43 | Re: PGXN installation failure for Postgres Image of PostgreSQL 12 and 13 versions. |
From | Date | Subject | |
---|---|---|---|
Next Message | Paul van Rixel | 2021-11-29 11:12:11 | split postgresql logfile |
Previous Message | Wicher | 2021-11-29 09:23:15 | DDL tools for working with views in dependency order? |