Re: machine-readable explain output v4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: machine-readable explain output v4
Date: 2009-08-10 01:32:08
Message-ID: 6877.1249867928@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-08-10 01:34:36 Re: machine-readable explain output v4
Previous Message Robert Haas 2009-08-10 01:23:33 Re: Issues for named/mixed function notation patch