[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Proposal : REINDEX xxx VERBOSE
From:       Robert Haas <robertmhaas () gmail ! com>
Date:       2015-04-30 16:38:11
Message-ID: CA+TgmoYe977Zh3iYowTSRTqWrUHR-1Dddi7Nz7C29RTzknz9xw () mail ! gmail ! com
[Download RAW message or body]

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.

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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread]