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

From Robert Haas
Subject Re: machine-readable explain output
Date
Msg-id 603c8f070906160732o16cbc855u692d9865fc3d1357@mail.gmail.com
Whole thread Raw
In response to Re: machine-readable explain output  (Andres Freund <andres@anarazel.de>)
Responses Re: machine-readable explain output
List pgsql-hackers
On Tue, Jun 16, 2009 at 10:30 AM, Andres Freund<andres@anarazel.de> wrote:
> How would you model something like:
> <plans>
>  <plan> ... </plan>
>  <plan> ... </plan>
>  ...
> </plans>
> otherwise?
>
> There are potentially unlimited number of child nodes - AppendNode for
> example can have any number of them. Sure, you can give each <plan> node a
> 'offset=' id, but that doesn't buy much.
> I don't see how that could be much improved by using child-nodes (or even
> worse attributes).

Note that even in this case we DON'T rely on the ordering of the
nodes.  The inner <plan> nodes have child nodes which contain their
relationship to the parent.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: machine-readable explain output
Next
From: Greg Stark
Date:
Subject: Re: Synch Rep: communication between backends and walsender