| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Fetter <david(at)fetter(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 05:10:45 |
| Message-ID: | 20050210051045.GA59116@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 09, 2005 at 11:36:22PM -0500, Tom Lane wrote:
> Michael Fuhr <mike(at)fuhr(dot)org> writes:
> > I started looking at this earlier. Is it even possible to get
> > EXPLAIN output via SPI (and thus the PLs' interfaces to SPI)?
>
> Hmm ... my first reaction was "sure", but:
[snip]
> ERROR: cannot open non-SELECT query as cursor
That's what I saw when I started playing with this. I wasn't sure
if I was overlooking something or if SPI really didn't allow it.
> (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?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-02-10 05:53:39 | Re: pg_affected Change Request |
| Previous Message | Michael Fuhr | 2005-02-10 05:01:41 | Re: a SELECT FOR UPDATE question |