public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andreas Karlsson <[email protected]>
To: Thom Brown <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?
Date: Thu, 29 Jun 2023 13:04:25 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA-aLv4BZZSGpQVnEmY6oQQzBwFFF9ogMh5LXvx5Q_Wa10p=Rg@mail.gmail.com>
References: <CAA-aLv4BZZSGpQVnEmY6oQQzBwFFF9ogMh5LXvx5Q_Wa10p=Rg@mail.gmail.com>
On 6/29/23 11:13, Thom Brown wrote:
> I get the feeling that this is deliberate, and perhaps an attempt to
> mitigate locking issues, or some other explanation, but the rationale
> isn't immediately apparent to me if this is the case.
I have always assumed the reason is that there might be other
transactions using the index so if we are going to drop it on rollback
we might get stuck forever waiting for an exclusive lock on the index.
How do you get around that? Rollback being stuck waiting forever is
certainly not a nice behavior.
Andreas
view thread (2+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox