pgsql: Revise REINDEX CONCURRENTLY recovery instructions

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Revise REINDEX CONCURRENTLY recovery instructions
Date: 2020-08-20 17:52:20
Message-ID: E1k8ojc-0002Uo-Qu@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revise REINDEX CONCURRENTLY recovery instructions

When the leftover invalid index is "ccold", there's no need to re-run
the command. Reword the instructions to make that explicit.

Backpatch to 12, where REINDEX CONCURRENTLY appeared.

Author: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Reviewed-by: Michael Paquier <michael(at)paquier(dot)xyz>
Reviewed-by: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Discussion: https://postgr.es/m/20200819211312.GA15497@alvherre.pgsql

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/da9ec328dda9625725ae8210ad6e6599ab876206

Modified Files
--------------
doc/src/sgml/ref/reindex.sgml | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2020-08-20 20:05:16 pgsql: Revert "Make vacuum a bit more verbose to debug BF failure."
Previous Message Andres Freund 2020-08-20 01:35:58 Re: pgsql: Fix race condition in snapshot caching when 2PC is used.