From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Coleman <jtc331@gmail.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Michael Paquier <michael@paquier.xyz>,
        David Johnston <david.g.johnston@gmail.com>,
        PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>,
        Andres Freund <andres@anarazel.de>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
In-reply-to: 
 <CAAaqYe_gm=JFna+BACJhY49UWef2pNRLfQ+GV7AqyLVcWdtT6Q@mail.gmail.com>
References: <20210113211604.GA16584@alvherre.pgsql>
 <1337019.1610573371@sss.pgh.pa.us>
 <CAAaqYe_gm=JFna+BACJhY49UWef2pNRLfQ+GV7AqyLVcWdtT6Q@mail.gmail.com>
Comments: In-reply-to James Coleman <jtc331@gmail.com>
	message dated "Wed, 13 Jan 2021 16:48:37 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1338242.1610575228.1@sss.pgh.pa.us>
Date: Wed, 13 Jan 2021 17:00:28 -0500
Message-ID: <1338243.1610575228@sss.pgh.pa.us>
Precedence: bulk

James Coleman <jtc331@gmail.com> writes:
> On Wed, Jan 13, 2021 at 4:29 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> but the antecedent of "a table" is a bit unclear; people might
>> wonder if it means the table being reindexed.

> It does mean the table being reindexed; the last phrase says "any
> table" meaning "any other table".

[ raised eyebrow ]  Surely REINDEX and VACUUM can't run on the same
table at the same time.

			regards, tom lane