diff options
author | Michael Paquier <michael@paquier.xyz> | 2025-05-20 14:39:14 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2025-05-20 14:39:14 +0900 |
commit | 009e8a85d32aaea7aa19505fc9023dcb9a80e255 (patch) | |
tree | f257999853cceef2804281872e2ffd2f0d97cfaf | |
parent | 72fe74ca533375fa04264f976d4c4971c6804dce (diff) |
doc: Clarify use of _ccnew and _ccold in REINDEX CONCURRENTLY
Invalid indexes are suffixed with "_ccnew" or "_ccold". The
documentation missed to mention the initial underscore.
ChooseRelationName() may also append an extra number if indexes with a
similar name already exist; let's add a note about that too.
Author: Alec Cozens <acozens@pixelpower.com>
Discussion: https://postgr.es/m/174733277404.1455388.11471370288789479593@wrigleys.postgresql.org
Backpatch-through: 13
-rw-r--r-- | doc/src/sgml/ref/reindex.sgml | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index 336ca24b312..6b7f6f4eab8 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -451,14 +451,17 @@ Indexes: </programlisting> If the index marked <literal>INVALID</literal> is suffixed - <literal>ccnew</literal>, then it corresponds to the transient + <literal>_ccnew</literal>, then it corresponds to the transient index created during the concurrent operation, and the recommended recovery method is to drop it using <literal>DROP INDEX</literal>, then attempt <command>REINDEX CONCURRENTLY</command> again. - If the invalid index is instead suffixed <literal>ccold</literal>, + If the invalid index is instead suffixed <literal>_ccold</literal>, it corresponds to the original index which could not be dropped; the recommended recovery method is to just drop said index, since the rebuild proper has been successful. + A nonzero number may be appended to the suffix of the invalid index + names to keep them unique, like <literal>_ccnew1</literal>, + <literal>_ccold2</literal>, etc. </para> <para> |