Re: "ccold" left by reindex concurrently are droppable?
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Date: 2020-08-20T05:17:13Z
Lists: pgsql-hackers
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
Commits
-
Revise REINDEX CONCURRENTLY recovery instructions
- da9ec328dda9 12.5 landed
- 2a9f042c4705 13.0 landed
- 0784c333728d 14.0 landed