postgrespro.git / summary / log / commit / refs

commit    9b60c4b979bce060495e2b05ba01d1cc6bffdd2d
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Sun May 31 01:48:21 2020 +0000

    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 f6c3d9538b..026fd018d9 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>


[parent: 92f9468657f0]