From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Subject: Re: "ccold" left by reindex concurrently are droppable?
Date: Thu, 20 Aug 2020 14:17:13 +0900
Message-ID: <20200820051713.GA3730@paquier.xyz> (raw)
In-Reply-To: <20200819211312.GA15497@alvherre.pgsql>
References: <20200819211312.GA15497@alvherre.pgsql>
On Wed, Aug 19, 2020 at 05:13:12PM -0400, Alvaro Herrera wrote:
> In other words I propose to reword this paragraph as follows:
>
> If the transient index created during the concurrent operation is
> suffixed <literal>ccnew</literal>, the recommended recovery method
> is to drop the invalid index using <literal>DROP INDEX</literal>,
> and try to perform <command>REINDEX CONCURRENTLY</command> again.
> If the transient index is instead suffixed <literal>ccold</literal>,
> it corresponds to the original index which we failed to drop;
> the recommended recovery method is to just drop said index, since the
> rebuild proper has been successful.
Yes, that's an improvement. It would be better to backpatch that. So
+1 from me.
> (The original talks about "the concurrent index", which seems somewhat
> sloppy thinking. I used the term "transient index" instead.)
Using transient to refer to an index aimed at being ephemeral sounds
fine to me in this context.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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-hackers@postgresql.org
Cc: michael@paquier.xyz, alvherre@alvh.no-ip.org, pgsql-hackers@lists.postgresql.org, peter.eisentraut@2ndquadrant.com
Subject: Re: "ccold" left by reindex concurrently are droppable?
In-Reply-To: <20200820051713.GA3730@paquier.xyz>
* 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