On Wed, 2006-04-12 at 14:38 -0500, Jim C. Nasby wrote:
> On Wed, Apr 12, 2006 at 09:45:41AM -0700, Mischa Sandberg wrote:
> > Jim C. Nasby wrote:
> > >On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
> > >
> > >><NestedLoop cost="1.06..40.43" rows="5" width="244">
> > >> <JoinFilter publicTenk1Unique2="int4_tbl.f1">
> > >> <HashAggregate cost="1.06..1.11" rows="5" width="4"/>
> > >> </JoinFilter>
> > >></NestedLoop>
> > >
> > >
> > >Well, the downside is that such a format means explain output is now
> > >twice as long. But I'd love to see something like that as an option. I'd
> > >also still like to see an SQL-parseable version as well, since I think
> > >there's applications for that.
> [...]
We can get the best of both worlds.
For instance, EXPLAIN and EXPLAIN ANALYZE with the usual output; but
also EXPLAIN XML and EXPLAIN ANALYZE XML with an XML syntax to be
used by programs.
I have a patch for this behavior, but unfortunately this is not
updated. It was made by the time that postgresql 8.0 was beta
without any chance to get feedback (everybody were fixing bugs).
The strategy was quite simple. It was implemented inside on
explain.c; with an extra parameter. So, if any change could
happen in the normal output of explain, it could be easier to
update the XML one.
Get it updated should not be so much hours of work. At this
moment I do not have that time :-(
--
Germán Poó-Caamaño
http://www.ubiobio.cl/~gpoo/
Concepción - Chile