From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: Andrey Klychkov <aaklychkov@mail.ru>,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: Re[2]:
In-reply-to: <20200528065948.GC3460@paquier.xyz>
References: <1590486572.205117372@f500.i.mail.ru>
 <cca87255-7dea-6aac-2e9a-35dfe3776122@2ndquadrant.com>
 <1590501239.839686286@f437.i.mail.ru> <17907.1590504619@sss.pgh.pa.us>
 <20200527074736.GG103662@paquier.xyz> <5816.1590581923@sss.pgh.pa.us>
 <20200528065948.GC3460@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Thu, 28 May 2020 15:59:48 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6213.1590671660.1@sss.pgh.pa.us>
Date: Thu, 28 May 2020 09:14:20 -0400
Message-ID: <6214.1590671660@sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> I don't think we should have any duplication between the REINDEX and
> reindexdb pages, and we have that in reindexdb:
> --concurrently
>     Use the CONCURRENTLY option. See REINDEX for further information.

> An idea would be to append to the second sentence something like
> "where all the caveats of this option are explained in details"?

+1, but I'd change the whole sentence.  Maybe

    Use the CONCURRENTLY option. See REINDEX, where all the caveats of
    this option are explained in detail.

			regards, tom lane