From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Subject: | Re: generic options for explain |
Date: | 2009-05-26 19:33:47 |
Message-ID: | 17367.1243366427@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, May 26, 2009 at 3:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> These are implementation details ;-). Let's get a definition that
>> everyone can sign off on, and then worry about what has to be done
>> to the code to make it happen.
> I'm actually not sure there's a whole lot to hash out... I was going
> to take a crack at writing some code.
I still haven't seen anything but formless handwaving as far as the "SQL
table" output format goes. For that matter, there's not much more than
handwaving behind the "XML" meme either. Show us a spec for the output
format, then think about code. (This was somewhere around slide ten
here: http://momjian.us/main/writings/pgsql/patch.pdf ;-))
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-05-26 20:22:20 | Re: generic options for explain |
Previous Message | Robert Haas | 2009-05-26 19:25:41 | Re: generic options for explain |