| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Mike <ipso(at)snappymail(dot)ca>, Albert Cervera i Areny <albert(at)nan-tic(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Alpha 1 release notes |
| Date: | 2009-08-12 01:04:48 |
| Message-ID: | 603c8f070908111804t22a3909dm33c9dfe6d619f380@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 11, 2009 at 8:32 PM, Alvaro
Herrera<alvherre(at)commandprompt(dot)com> wrote:
> Mike wrote:
>
>> The thing that caused me the most trouble was that the "," wasn't very
>> noticeable sitting near the end of this line:
>>
>> EXPLAIN [ ( { ANALYZE boolean | VERBOSE boolean | COSTS boolean |
>> FORMAT { TEXT | XML | JSON } } [, ...] ) ] statement
>>
>> It may just be me, but I read that as the comma being optional, not
>> mandatory in circumstances where you want to specify more then one
>> option.
>
> It is you -- what's optional is having more than one option, but as soon
> as you have a second one, the comma is mandatory.
>
> I agree some examples would be useful.
Hmm, I thought we had some examples in there, but now that I look we
only have an example for COSTS OFF, not for FORMAT. That does seem
like an oversight.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-12 01:05:29 | Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY) |
| Previous Message | Robert Haas | 2009-08-12 01:02:54 | Re: dependencies for generated header files |