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

From Andres Freund
Subject Re: machine-readable explain output v4
Date
Msg-id 200908100343.23128.andres@anarazel.de
Whole thread Raw
In response to Re: machine-readable explain output v4  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: machine-readable explain output v4  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Monday 10 August 2009 03:34:36 Robert Haas wrote:
> On Sun, Aug 9, 2009 at 9:32 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> > Andres Freund <andres@anarazel.de> writes:
> >> Adding the notion of opening a 'empty' Group together with X_OPENCLOSE
> >> or handling of X_OPENING|X_CLOSING would allow to handle empty tags like
> >> in ExplainOneUtility (<Notify />).
> >
> > Yeah, I was just wondering what to do with the <Notify /> code.  I'm
> > not sure if it's worth trying to fold it into the OpenGroup/CloseGroup
> > code --- it might be easier to have an ExplainEmptyGroup or something
> > like that.
>
> Well there's no rule that says you can't emit it as
>
> <Notify>
> </Notify>
That wont work nicely with json output.

Andres


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Issues for named/mixed function notation patch
Next
From: Andrew Dunstan
Date:
Subject: Re: machine-readable explain output v4