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.0905242248100.8633@westnet.com
Whole thread Raw
In response to Re: generic options for explain  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 24 May 2009, Tom Lane wrote:

> A serious problem with EXPLAIN via a function returning set, or with
> putting the result into a table, is that set results are logically
> unordered, just as table contents are.

Fair enough; I think Pavel and myself were presuming an implied "line 
number" in the output there that, as you point out, doesn't actually 
exist.  The actual implementation detail there doesn't really change the 
spirit of what I was trying to suggest though:  that this feature should 
get designed starting with the expected output and how to generate it, 
then work backwards towards how you pass it parameters.

On that topic, I though Tom Raney was the latest to update code for the 
XML output at least.  Code and a presentation going over everything is at 
http://web.cecs.pdx.edu/~raneyt/gsoc/ and there's a video at 
http://www.postgresqlconference.org/2008/west/talks/

A note about that got sent to this list at one point but I don't see any 
follow-up: 
http://archives.postgresql.org/pgsql-hackers/2008-06/msg00802.php

Anybody have a better idea of what happened with that project than me?

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: generic options for explain
Next
From: Andrew McNamara
Date:
Subject: No sanity checking performed on binary TIME parameters.