Skip site navigation (1) Skip section navigation (2)

machine-readable explain output v4

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: machine-readable explain output v4
Date: 2009-07-30 03:05:48
Message-ID: 603c8f070907292005t495c515dv5759e71666bcb2e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
OK, here's the updated version of my machine-readable explain output
patch.  This needed heavy updating as a result of the changes that Tom
asked me to make to the explain options patch, and the further changes
he made himself.  In addition to any regressions I may have introduced
during the rebasing process, there is one definite problem here: in
the previous version of this patch, explain (format xml) returned XML
data; now, it's back to text.

The reason for this regression is that Tom asked me to change
ExplainStmt to just carry a list of nodes and to do all the parsing in
ExplainQuery.  Unfortunately, the TupleDesc is constructed by
ExplainResultDesc() which can't trivially be changed to take an
ExplainState, because UtilityTupleDescriptor() also wants to call it.
We could possibly fix this by a hack similar to the one we already
added to GetCommandLogLevel(), but I haven't done that here.

...Robert

Attachment: explain_format-v4.patch
Description: text/x-diff (74.0 KB)

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-07-30 03:16:30
Subject: Re: RFD: Don't force plpgsql IN parameters to constant
Previous:From: Tom LaneDate: 2009-07-30 02:57:09
Subject: Re: RFD: Don't force plpgsql IN parameters to constant

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group