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