From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: generic options for explain |
Date: | 2009-05-24 22:05:09 |
Message-ID: | alpine.GSO.2.01.0905241756210.10282@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 24 May 2009, Pavel Stehule wrote:
> we should have a secondary function explain_query(query_string,
> option) that returns setof some.
+1. The incremental approach here should first be adding functions that
actually do the work required. Then, if there's a set of those that look
to be extremely useful, maybe at that point it's worth talking about how
to integrate them into the parser. Starting with the parser changes
rather than the parts that actually do the work is backwards. If you do
it the other way around, at all times you have a patch that actually
provides immediate useful value were it to be committed.
Something that returns a setof can also be easily used to implement the
"dump EXPLAIN to a table" feature Josh Tolley brought up (which is another
common request in this area).
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-05-24 22:13:16 | Re: [HACKERS] pull raw text of a message by message-id |
Previous Message | Tom Lane | 2009-05-24 22:02:58 | Re: [HACKERS] pull raw text of a message by message-id |