From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Coleman <jtc331@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: David Johnston <david.g.johnston@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Date: Wed, 13 Jan 2021 18:49:25 -0500
Message-ID: <1342637.1610581765@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAaqYe9Qzx5wcL1qPVPe5wOPxnyFgsXv4dSyrpPY-PUpWmiM_w@mail.gmail.com>
References: <20210113211604.GA16584@alvherre.pgsql>
<1337019.1610573371@sss.pgh.pa.us>
<CAAaqYe_gm=JFna+BACJhY49UWef2pNRLfQ+GV7AqyLVcWdtT6Q@mail.gmail.com>
<1338243.1610575228@sss.pgh.pa.us>
<CAAaqYe9Qzx5wcL1qPVPe5wOPxnyFgsXv4dSyrpPY-PUpWmiM_w@mail.gmail.com>
James Coleman <jtc331@gmail.com> writes:
> On Wed, Jan 13, 2021 at 5:00 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> [ raised eyebrow ] Surely REINDEX and VACUUM can't run on the same
>> table at the same time.
> + Like any long-running transaction, <command>CREATE INDEX</command> on a
> + table can affect which tuples can be removed by concurrent
> + <command>VACUUM</command> on any other table.
> The "on a table" is the table on which the REINDEX/CREATE INDEX is
> occurring. The "any other table" is where VACUUM might run.
I still think it'd be just as clear without the auxiliary clauses,
say
+ Like any long-running transaction, <command>CREATE INDEX</command>
+ can affect which tuples can be removed by concurrent
+ <command>VACUUM</command> operations.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, jtc331@gmail.com, alvherre@alvh.no-ip.org, michael@paquier.xyz, david.g.johnston@gmail.com, pgsql-hackers@lists.postgresql.org, andres@anarazel.de
Subject: Re: [DOC] Document concurrent index builds waiting on each other
In-Reply-To: <1342637.1610581765@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox