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 15:04:13 |
Message-ID: | 603c8f070906160804u196fff64h98d0e3f3b92f31b4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 16, 2009 at 10:59 AM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>
>
> Robert Haas wrote:
>>>
>>> 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.
>>
>>
>
> OK, I misread something you wrote, which prompted me to say that. Rereading
> it I realise my error. My apologies.
No problem, no apologies needed. I guess we do emit nodes like append
plans in the same order that they'd be emitted in text mode. Right
now we don't emit any additional information beyond putting them in
the same order, but I suppose that could be changed if needs be.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-06-16 15:05:42 | Re: Synch Rep: communication between backends and walsender |
Previous Message | Andrew Dunstan | 2009-06-16 14:59:32 | Re: machine-readable explain output |