| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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: | Re: What do you do with a long running rollback |
| Date: | 2021-11-26 18:42:16 |
| Message-ID: | 440098.1637952136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
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 | Tom Lane | 2021-11-26 19:44:29 | Re: What do you do with a long running rollback |
| Previous Message | Chris Cawley | 2021-11-26 18:33:21 | What do you do with a long running rollback |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaozhong SHI | 2021-11-26 19:08:24 | Merge into does not work |
| Previous Message | Chris Cawley | 2021-11-26 18:33:21 | What do you do with a long running rollback |