From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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 15:57:13 |
Message-ID: | 4A196E59.9020409@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas wrote:
>>> 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, ...)
>>
>
> See to me THAT is a really strange syntax, so I guess we need some more votes.
>
>
>
Both of these seem both odd an unnecessary. Why not just have a setting
called, say, explain_format which governs the output?
set explain_format = 'xml, verbose';
explain select * from foo;
No new function or syntax would be required.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2009-05-24 16:02:22 | Re: [PATCH] cleanup hashindex for pg_migrator hashindex compat mode (for 8.4) |
Previous Message | Alvaro Herrera | 2009-05-24 15:34:09 | Re: pull raw text of a message by message-id |