From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | acozens(at)pixelpower(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: reindex documentation |
Date: | 2025-05-17 12:44:09 |
Message-ID: | aCiEmbG52nk5iip7@paquier.xyz |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thu, May 15, 2025 at 06:12:54PM +0000, PG Doc comments form wrote:
> The following paragraph:
> "If the index marked INVALID is suffixed ccnew, then it corresponds to the
> transient index created during the concurrent operation, and the recommended
> recovery method is to drop it using DROP INDEX, then attempt REINDEX
> CONCURRENTLY again. If the invalid index is instead suffixed ccold, 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."
> It seems to me that the indexes are suffixed with _ccnew and _ccold not
> ccnew and ccold. Also, if _ccnew or _ccold indexes alread exist, an integer
> value starting from 1 will be added until a unique index is found - e.g.
> _ccnew1, _ccold1, _ccnew2 etc.
Right, following the rules defined internally by ChooseRelationName()
when creating the new/old indexes in the process. So this could be
added. Would you like to suggest a rewording of this sentence for the
extra number optionally appended to the suffix if a duplicated entry
exists?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Ge Yuxiang | 2025-05-19 05:03:02 | Ge Yuxiang added you to the postgresql group |
Previous Message | Paweł Szymczyk | 2025-05-15 21:12:05 | Re: Missing word |