Re: BUG #2096: bug in a SPI sample document - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #2096: bug in a SPI sample document
Date
Msg-id 200603030417.k234HX513657@candle.pha.pa.us
Whole thread Raw
In response to BUG #2096: bug in a SPI sample document  ("Yoshihisa Nakano" <nakano.yosihisa@jp.fujitsu.com>)
Responses Re: BUG #2096: bug in a SPI sample document
List pgsql-bugs
This documentation bug has been fixed.  We currently have:

    => 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:  1
    INSERT 0 1

Is the "INSERT 0 1" right?  I see an oid in your example, but that might
be because we no longer user oids by default.

---------------------------------------------------------------------------

Yoshihisa Nakano wrote:
>
> 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
>

--
  Bruce Momjian   http://candle.pha.pa.us
  SRA OSS, Inc.   http://www.sraoss.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2294: SPI_connect() fails in trigger when a Foreignkey constraint exists on same table as trigger.
Next
From: "Qingqing Zhou"
Date:
Subject: prepare-alter-exec issue