| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal : REINDEX xxx VERBOSE |
| Date: | 2015-02-03 23:08:32 |
| Message-ID: | 2030.1423004912@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> writes:
> On 2/3/15 9:20 AM, Tom Lane wrote:
>> 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).
Well, I really really don't like the first of those. IMO the command name
is "REINDEX INDEX" etc, so sticking something in the middle of that is
bogus.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabrízio de Royes Mello | 2015-02-03 23:09:38 | Re: Proposal : REINDEX xxx VERBOSE |
| Previous Message | Heikki Linnakangas | 2015-02-03 22:47:03 | Re: [COMMITTERS] pgsql: Process 'die' interrupts while reading/writing from the client s |