Re: machine-readable explain output - Mailing list pgsql-hackers

From Robert Haas
Subject Re: machine-readable explain output
Date
Msg-id 603c8f070906141004l39a08b73j942496136df47268@mail.gmail.com
Whole thread Raw
In response to Re: machine-readable explain output  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: machine-readable explain output  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Sun, Jun 14, 2009 at 1:02 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Sun, Jun 14, 2009 at 11:28 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>>> However, using BuildTupleFromCStrings is wasteful/stupid for *both*
>>> text and xml output, so it seems like getting rid of it is the thing
>>> to do here.
>
>> Makes sense.  However, if we just make that change in do_tup_output(),
>> then we'll break the ability to use that function for non-text
>> datatypes.
>
> I'd envision it taking Datums, so it doesn't really matter.  However,
> as you say, specializing it to text only wouldn't be much of a loss.

I like the Datum option, so I'll work up a patch for that, unless you
want to just do it and spare me the trouble.  :-)

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: machine-readable explain output
Next
From: "Erik Rijkers"
Date:
Subject: 8.4 release notes "Recursive Joins"