AW: What do you do with a long running rollback
От | Dischner, Anton |
---|---|
Тема | AW: What do you do with a long running rollback |
Дата | |
Msg-id | ed80d5c2840c432099df8a6f56b40d8a@MITMB5.helios.med.uni-muenchen.de обсуждение исходный текст |
Ответ на | Re: What do you do with a long running rollback (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: AW: What do you do with a long running rollback
|
Список | pgsql-admin |
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 nevertry 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 transmissionof the abort's WAL record. What are you looking at exactly? regards, tom lane
В списке pgsql-admin по дате отправления: