| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: generic options for explain |
| Date: | 2009-05-24 14:25:55 |
| Message-ID: | 162867790905240725o19ed7c88le6fd836e931419bf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/5/24 Robert Haas <robertmhaas(at)gmail(dot)com>:
>>> EXPLAIN ('hash_detail', 'on') query...
>
> Oops, I should have written EXPLAIN (hash_detail 'on') query... can't
> follow my own syntax.
>
>> I am sorry - this is really strange syntax . Who will use this syntax?
>> For some parser is little bit better function call, than parametrized
>> statement. Some dificulties with options should be fixed with named
>> param (we are speaking about 8.5).
>>
>> select explain_xml("select ...", true as hash_detail, ...)
>
I prefere little bit different syntax for named params like param =
value, or param => value, but syntax with AS is one confirmed.
> See to me THAT is a really strange syntax, so I guess we need some more votes.
ok
>
> ...Robert
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Ali Rachid | 2009-05-24 14:46:54 | Oracle to Postgres : create type as object in Postgres |
| Previous Message | Robert Haas | 2009-05-24 14:21:44 | Re: generic options for explain |