From: Vik Fearing <vik.fearing@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Sergei Kornilov <sk@zsrv.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Craig Ringer <craig@2ndquadrant.com>
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0
Date: Sat, 19 Jan 2019 03:01:07 +0100
Message-ID: <a03a615c-3224-e54f-76ee-fddd6f524cbb@2ndquadrant.com> (raw)
In-Reply-To: <20190119013312.GC3306@paquier.xyz>
References: <201901161759.voovsk55ofe7@alvherre.pgsql>
<57479e55-ce26-5c00-2525-09e267c7224a@2ndquadrant.com>
<20190119013312.GC3306@paquier.xyz>
On 19/01/2019 02:33, Michael Paquier wrote:
> On Fri, Jan 18, 2019 at 07:58:06PM +0100, Vik Fearing wrote:
>> My vote is to have homogeneous syntax for all of this, and so put it in
>> parentheses, but we should also allow CREATE INDEX and DROP INDEX to use
>> parentheses for it, too.
>
> That would be a new thing as these variants don't exist yet, and WITH
> is for storage parameters. In my opinion, the long-term take on doing
> such things is that we are then able to reduce the number of reserved
> keywords in the grammar. Even if for the case of CONCURRENTLY we may
> see humans on Mars before this actually happens, this does not mean
> that we should not do it moving forward for other keywords in the
> grammar.
I'm not sure I understand your point.
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.
I never said anything about WITH.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
Attachments:
[application/pgp-signature] signature.asc (832B, ../a03a615c-3224-e54f-76ee-fddd6f524cbb@2ndquadrant.com/2-signature.asc)
download
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: vik.fearing@2ndquadrant.com, michael@paquier.xyz, alvherre@2ndquadrant.com, sk@zsrv.org, peter.eisentraut@2ndquadrant.com, michael.paquier@gmail.com, andreas@proxel.se, sfrost@snowman.net, craig@2ndquadrant.com
Subject: Re: [HACKERS] REINDEX CONCURRENTLY 2.0
In-Reply-To: <a03a615c-3224-e54f-76ee-fddd6f524cbb@2ndquadrant.com>
* 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