| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: machine-readable explain output v4 |
| Date: | 2009-08-10 01:43:22 |
| Message-ID: | 200908100343.23128.andres@anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-08-10 01:47:59 | Re: machine-readable explain output v4 |
| Previous Message | Tom Lane | 2009-08-10 01:36:14 | Re: Issues for named/mixed function notation patch |