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

From Jim Nasby
Subject Re: Proposal : REINDEX xxx VERBOSE
Date
Msg-id 54D14B1B.1090305@BlueTreble.com
Whole thread Raw
In response to Re: Proposal : REINDEX xxx VERBOSE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal : REINDEX xxx VERBOSE  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal : REINDEX xxx VERBOSE  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-hackers
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).
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Redesigning checkpoint_segments
Next
From: Jim Nasby
Date:
Subject: Re: Fwd: [GENERAL] 4B row limit for CLOB tables