| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal : REINDEX xxx VERBOSE |
| Date: | 2015-02-05 18:01:34 |
| Message-ID: | 18569.1423159294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> We've got a mix of styles for extensible options right now:
That we do.
> So COPY puts the options at the very end, but EXPLAIN and VACUUM put
> them right after the command name. I prefer the latter style and
> would vote to adopt it here.
Meh. Options-at-the-end seems by far the most sensible style to me.
The options-right-after-the-keyword style is a mess, both logically
and from a parsing standpoint, and the only reason we have it at all
is historical artifact (ask Bruce about the origins of VACUUM ANALYZE
over a beer sometime).
Still, I can't help noticing that I'm being outvoted. I'll shut up now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2015-02-05 18:18:16 | Re: Possible problem with pgcrypto |
| Previous Message | Robert Haas | 2015-02-05 17:25:36 | Re: Proposal : REINDEX xxx VERBOSE |