| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | hf1122x(at)protecting(dot)net, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Understanding EXPLAIN ANALYZE output |
| Date: | 2005-02-11 00:34:07 |
| Message-ID: | 4585.1108082047@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> I've been wondering about that. A while ago the change was made from
> outputting a NOTICE with the EXPLAIN output to returning a resultset.
> If you could agree on what columns to return it might not be so hard
> for the EXPLAIN to return full tuples...
The major stumbling block to that is that a table is inherently
unordered, so you'd have to devise a labeling scheme to allow the
node-tree structure to be represented properly. And without WITH or
CONNECT BY, it'd be a bit of a PITA for an application to decipher the
labeling scheme again ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-02-11 00:39:15 | Re: Fwd: Unending recursive gmake during install? |
| Previous Message | David Fetter | 2005-02-11 00:01:13 | Re: Understanding EXPLAIN ANALYZE output |