Re: [HACKERS] REINDEX CONCURRENTLY 2.0 - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Date
Msg-id CAFj8pRAGwmj++9+nEPArMtbPFTTM2MBBM-iEiQPRmauhhSVujw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] REINDEX CONCURRENTLY 2.0  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


st 23. 1. 2019 19:17 odesílatel Robert Haas <robertmhaas@gmail.com> napsal:
On Fri, Jan 18, 2019 at 9:01 PM Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
> I don't want a situation like this:
>     CREATE INDEX CONCURRENTLY ...
>     DROP INDEX CONCURRENTLY ...
>     REINDEX INDEX (CONCURRENTLY) ...
>
> All three should be the same, and my suggestion is to add the
> parenthesized version to CREATE and DROP and not add the unparenthesized
> version to REINDEX.

+1 for all three being the same.  I could see allowing only the
unparenthesized format for all three, or allowing both forms for all
three, but I think having only one form for each and having them not
agree will be too confusing.

+1

Pavel


--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Next
From: Tom Lane
Date:
Subject: Re: ArchiveEntry optional arguments refactoring