James Coleman <jtc...@gmail.com> writes: > On Wed, Jan 13, 2021 at 5:00 PM Tom Lane <t...@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