From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Wittel <gwittel(at)proofpoint(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Odd PL/PgSQL Error -- relation "X" does not exist when using index expression |
Date: | 2007-02-18 01:47:57 |
Message-ID: | 200702180147.l1I1lv207144@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Michael Fuhr wrote:
> On Thu, Feb 08, 2007 at 10:32:25AM -0500, Tom Lane wrote:
> > My advice is not to try to execute multiple commands in the same EXECUTE
> > string --- if we were going to do anything to "fix" this, I think it
> > would be along the lines of enforcing that advice. Trying to make the
> > world safe for it doesn't sound productive.
>
> The SPI_execute() documentation does mention that multiple commands
> are allowed:
>
> http://www.postgresql.org/docs/8.2/interactive/spi-spi-execute.html
>
> "You may pass multiple commands in one string. SPI_execute returns
> the result for the command executed last. The count limit applies
> to each command separately, but it is not applied to hidden commands
> generated by rules.
>
> "When read_only is false, SPI_execute increments the command counter
> and computes a new snapshot before executing each command in the
> string."
>
> Should that documentation be modified?
Done, and attached.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/diff | text/x-diff | 998 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Karthikeyan Sundaram | 2007-02-18 08:15:01 | How to analyse the indexes in postgres? |
Previous Message | Louis-David Mitterrand | 2007-02-17 18:40:00 | Re: sub-limiting a query |