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

From Fabrízio de Royes Mello
Subject Re: Proposal : REINDEX xxx VERBOSE
Date
Msg-id CAFcNs+q5EysbpNjgPeuqedHUhL_jkv_=Dnu-6zur3Sp35ccGvg@mail.gmail.com
Whole thread
In response to Re: Proposal : REINDEX xxx VERBOSE  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers

On Tue, Feb 3, 2015 at 8:26 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
>
> On 2/3/15 9:20 AM, Tom Lane wrote:
>>>
>>> >i.g., I will add following syntax format,
>>> >REINDEX ( { INDEX | TABLE | SCHEMA | SYSTEM | DATABASE } , [VERBOSE] )
>>> >name [FORCE];
>>
>> Well, the object type is not an optional part of the command.  It's
>> *necessary*.  I was thinking more like
>>
>> REINDEX { INDEX | TABLE | etc } name [ ( option [, option ...] ) ]
>
>
> VACUUM puts the options before the table name, so ISTM it'd be best to keep that with REINDEX. Either REINDEX (options) {INDEX | ...} or REINDEX {INDEX | ...} (options).
>

Makes sense... +1

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposal : REINDEX xxx VERBOSE
Next
From: Andres Freund
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Process 'die' interrupts while reading/writing from the client s