Search Postgresql Archives

Re: Understanding EXPLAIN ANALYZE output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 09, 2005 at 11:36:22PM -0500, Tom Lane wrote:
> Michael Fuhr <mike@xxxxxxxx> 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/

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux