|
Home > Archive > PostgreSQL Bugs > December 2005 > BUG #2096: bug in a SPI sample document
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BUG #2096: bug in a SPI sample document
|
|
| Yoshihisa Nakano 2005-12-07, 7:25 am |
|
The following bug has been logged online:
Bug reference: 2096
Logged by: Yoshihisa Nakano
Email address: nakano.yosihisa@jp.fujitsu.com
PostgreSQL version: 8.1.0
Operating system: RedHat Enterprise Linux ES 3.0
Description: bug in a SPI sample document
Details:
There is a difference between the result of the SPI
example in the doc and the actual result of that.
Doc 40.5 Examples
=> SELECT * FROM a;
x
---
1 -- no rows in a (0) + 1
(1 row)
=> INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
INFO: EXECQ: 0
INSERT 167713 1
I tried this example, but INFO showed 1, not 0. I
think the value of INFO in doc is wrong, because the
value of row is 1 at this time.
This bug seems to exist also in 7.3.x, 7.4.x and 8.0.x.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Tom Lane 2005-12-07, 11:24 am |
| "Yoshihisa Nakano" <nakano.yosihisa@jp.fujitsu.com> writes:
> => INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
> INFO: EXECQ: 0
> INSERT 167713 1
> I tried this example, but INFO showed 1, not 0.
Yeah ... the INSERT won't show an OID by default anymore, either.
Fixed; thanks for the report!
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
|
|
|
|
|