Re: Proposal : REINDEX xxx VERBOSE - Mailing list pgsql-hackers

From Sawada Masahiko
Subject Re: Proposal : REINDEX xxx VERBOSE
Date
Msg-id CAD21AoAFbKPyO1jOLptzgTGvdGjaVAo6Bs3bcQP=fE3CGwh2+w@mail.gmail.com
Whole thread Raw
In response to Re: Proposal : REINDEX xxx VERBOSE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Proposal : REINDEX xxx VERBOSE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, May 1, 2015 at 1:38 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Apr 30, 2015 at 9:15 AM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
>> On Thu, Apr 30, 2015 at 8:39 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>> On Thu, Apr 30, 2015 at 6:37 AM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
>>>> Attached v10 patch is latest version patch.
>>>> The syntax is,
>>>> REINDEX { INDEX | ... } name [ WITH ] [ VERBOSE ]
>>>>
>>>> That is, WITH clause is optional.
>>>
>>> I thought we agreed on moving this earlier in the command:
>>>
>>> http://www.postgresql.org/message-id/18569.1423159294@sss.pgh.pa.us
>>>
>>
>> Oh, I see.
>> Attached patch is modified syntax as
>> REINDEX [VERBOSE] { INDEX | ... } name
>>
>> Thought?
>
> I thought what we agreed on was:
>
> REINDEX (flexible options) { INDEX | ... } name
>
> The argument wasn't about whether to use flexible options, but where
> in the command to put them.
>

VACUUM has both syntax: with parentheses and without parentheses.
I think we should have both syntax for REINDEX like VACUUM does
because it would be pain to put parentheses whenever we want to do
REINDEX.
Are the parentheses optional in REINDEX command?

And CLUSTER should have syntax like that in future?

Regards,

-------
Sawada Masahiko



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: disallow operator "=>" and use it for named parameters