| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | hf1122x(at)protecting(dot)net |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Understanding EXPLAIN ANALYZE output |
| Date: | 2005-02-10 23:06:45 |
| Message-ID: | 20050210230645.GE19117@svana.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 10, 2005 at 11:38:47PM +0100, Harald Fuchs wrote:
> But I think it should be the other way round: EXPLAIN ANALYZE should
> return its output in table form, and there should be a function to
> convert that table into what EXPLAIN ANALYZE outputs now.
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...
Backward compatability is a problem though...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-02-10 23:24:13 | Re: Understanding EXPLAIN ANALYZE output |
| Previous Message | Michael Fuhr | 2005-02-10 23:03:54 | Re: Understanding EXPLAIN ANALYZE output |