From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Cawley <cj_cawley@yahoo.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: What do you do with a long running rollback
Date: Fri, 26 Nov 2021 13:42:16 -0500
Message-ID: <440098.1637952136@sss.pgh.pa.us> (raw)
In-Reply-To: <1977259621.1023368.1637951601701@mail.yahoo.com>
References: <1977259621.1023368.1637951601701.ref@mail.yahoo.com>
<1977259621.1023368.1637951601701@mail.yahoo.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, cj_cawley@yahoo.com, pgsql-admin@lists.postgresql.org
Subject: Re: What do you do with a long running rollback
In-Reply-To: <440098.1637952136@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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