Re: Alpha 1 release notes - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Alpha 1 release notes
Date
Msg-id 603c8f070908111804t22a3909dm33c9dfe6d619f380@mail.gmail.com
Whole thread Raw
In response to Re: Alpha 1 release notes  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Alpha 1 release notes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Aug 11, 2009 at 8:32 PM, Alvaro
Herrera<alvherre@commandprompt.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: dependencies for generated header files
Next
From: Tom Lane
Date:
Subject: Re: pgindent timing (was Re: [COMMITTERS] pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY)