Re: machine-readable explain output

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: machine-readable explain output
Date: 2009-06-16 14:31:29
Message-ID: 603c8f070906160731i46060f6dj2921a0534ab76f3d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2009 at 9:45 AM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
> Robert Haas wrote:
>>
>> 3. We have existing precedent for this design pattern in, e.g.
>> table_to_xml
>>
>> http://www.postgresql.org/docs/current/interactive/functions-xml.html
>
> Tables are flat, explain output is not.
>
> If there is a relationship between the items then that needs to be expressed
> in the XML structure, either by use of child nodes or attributes. Relying on
> the sequence of nodes, if that's what you're doing, is not a good idea, and

I'm not doing that. Period, full stop. The discussion was only about
attributes vs. child nodes.

> Anyway, I think what this discussion points out is that we actually need a
> formal XML Schema for this output.

Well, I don't know how to write one, and am not terribly interested in
learning. Perhaps someone else would be interested?

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-06-16 14:32:32 Re: machine-readable explain output
Previous Message Andres Freund 2009-06-16 14:30:46 Re: machine-readable explain output