| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Understanding EXPLAIN ANALYZE output |
| Date: | 2005-02-10 20:53:06 |
| Message-ID: | 20050210205306.GL22824@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 10, 2005 at 03:38:05PM -0500, Tom Lane wrote:
> Michael Fuhr <mike(at)fuhr(dot)org> writes:
> > On Wed, Feb 09, 2005 at 11:36:22PM -0500, Tom Lane wrote:
> >> (And no, EXECUTE doesn't help.) This seems like an oversight.
> >> We already have some understanding in the backend that certain
> >> utility commands return query results; the SPI code should be
> >> letting those results be scanned as if they were ordinary SELECT
> >> results.
>
> > Any suggestions for the meantime?
>
> Update to CVS tip ;-)
I'd be delighted to, but I'm not sure how to see to it that EXPLAIN
gets the CMD_SELECT flag. What all files need to change to effect
this? Or have I drastically misunderstood what's involved?
Cheers,
D
--
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F.O'Connell | 2005-02-10 21:13:59 | Profiling ERROR Conditions |
| Previous Message | Tom Lane | 2005-02-10 20:38:05 | Re: Understanding EXPLAIN ANALYZE output |