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 Raw
In response to Re: Proposal : REINDEX xxx VERBOSE  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra"><br />On Tue, Feb 3, 2015 at 8:26 PM, Jim Nasby <<a
href="mailto:Jim.Nasby@bluetreble.com">Jim.Nasby@bluetreble.com</a>>wrote:<br />><br />> On 2/3/15 9:20 AM,
TomLane wrote:<br />>>><br />>>> >i.g., I will add following syntax format,<br />>>>
>REINDEX( { INDEX | TABLE | SCHEMA | SYSTEM | DATABASE } , [VERBOSE] )<br />>>> >name [FORCE];<br
/>>><br/>>> Well, the object type is not an optional part of the command.  It's<br />>> *necessary*. 
Iwas thinking more like<br />>><br />>> REINDEX { INDEX | TABLE | etc } name [ ( option [, option ...] )
]<br/>><br />><br />> 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).<br />> <br /><br /></div><div
class="gmail_extra">Makessense... +1<br /></div><div class="gmail_extra"><br /></div><div
class="gmail_extra">Regards,<br/></div><div class="gmail_extra"><br />--<br />Fabrízio de Royes Mello<br
/>Consultoria/CoachingPostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>

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