Re: generic options for explain - Mailing list pgsql-hackers

From Greg Smith
Subject Re: generic options for explain
Date
Msg-id alpine.GSO.2.01.0905241756210.10282@westnet.com
Whole thread Raw
In response to Re: generic options for explain  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: generic options for explain  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: generic options for explain  (Robert Haas <robertmhaas@gmail.com>)
List 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@gregsmith.com http://www.gregsmith.com Baltimore, MD


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pull raw text of a message by message-id
Next
From: Alvaro Herrera
Date:
Subject: Re: [pgsql-www] pull raw text of a message by message-id