From 38be24228dcdde935e6090ac4d7f85ceea58d914 Mon Sep 17 00:00:00 2001
From: Michael Paquier <michael@paquier.xyz>
Date: Sun, 31 May 2020 10:48:28 +0900
Subject: [PATCH] Doc: Mention about caveats of --concurrently on reindexdb
 page

The documentation of REINDEX includes a complete description of
CONCURRENTLY and its advantages as well as its disadvantages, but
reindexdb was not really clear about all that.

From discussion with Tom Lane, based on a report from Andrey Klychkov.

Discussion: https://postgr.es/m/1590486572.205117372@f500.i.mail.ru
Backpatch-through: 12
---
 doc/src/sgml/ref/reindexdb.sgml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/reindexdb.sgml b/doc/src/sgml/ref/reindexdb.sgml
index 860c579a3f0..3403fb91afc 100644
--- a/doc/src/sgml/ref/reindexdb.sgml
+++ b/doc/src/sgml/ref/reindexdb.sgml
@@ -122,8 +122,9 @@ PostgreSQL documentation
       <term><option>--concurrently</option></term>
       <listitem>
        <para>
-        Use the <literal>CONCURRENTLY</literal> option.  See <xref
-        linkend="sql-reindex"/> for further information.
+        Use the <literal>CONCURRENTLY</literal> option.  See
+        <xref linkend="sql-reindex"/>, where all the caveats of this option
+        are explained in detail.
        </para>
       </listitem>
      </varlistentry>