Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html - Mailing list pgsql-docs

From Curt Kolovson
Subject Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html
Date
Msg-id 672A5662-FB6C-454B-AD82-BDC30474E47C@gmail.com
Whole thread Raw
In response to Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
Tom is correct. It appears that nobody tested this example, which by the way seems unnecessarily complicated.

Sent from my iPhone

> On Jul 17, 2023, at 6:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>>> On Mon, Jul 17, 2023 at 4:53 PM Curt Kolovson <ckolovson@gmail.com> wrote:
>>> The actual results (shown below) are different than shown on this doc
>>> page.
>
>> SPI_exec sees "INSERT 0 2" as the command tag from the SQL command you
>> passed and so 2 is the output of the execq function call.
>> No INFO messages appear because you did not include a returning clause.
>> The 1 you passed to the call is immaterial if the query you supply doesn't
>> produce a result set.
>
> I think his point is that this example does not behave as the
> documentation claims.  Which it does not, according to my
> tests here.  I find this a bit disturbing --- did we intentionally
> change the behavior of SPI_exec somewhere along the line?
>
>            regards, tom lane



pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html
Next
From: "David G. Johnston"
Date:
Subject: Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html