pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Curt Kolovson <ckolovson@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html
Date: Mon, 17 Jul 2023 19:45:24 -0700
Message-ID: <9F566B71-42A3-4502-85CA-076BA8C5BDD5@gmail.com> (raw)
In-Reply-To: <4124246.1689647806@sss.pgh.pa.us>
References: <4124246.1689647806@sss.pgh.pa.us>

I’d vote for showing both (with RETURNING and without), since without it the second argument to SPI_exec has no effect in this example, which may not be obvious. That seems to be one of the subtle points illustrated by this example. 

> On Jul 17, 2023, at 7:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>>> On Mon, Jul 17, 2023 at 6:22 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 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?
> 
>> Appears to be a documentation fix oversight back in v9.0
>> https://github.com/postgres/postgres/commit/2ddc600f8f0252a0864e85d5cc1eeb3b9687d7e9
> 
> Ah, thanks for the pointer.  I'd just been trying to bisect where
> between 8.4 and 9.0 it changed, but failed because early-9.0 versions
> don't build at all with current bison :-(
> 
> Anyway, given that the example needs updating, how should we do that
> exactly?  Is it worth demonstrating both the behavior with RETURNING
> and that without?  If not, which one to show?
> 
>            regards, tom lane





view thread (10+ messages)  latest in thread

Message-ID: <9F566B71-42A3-4502-85CA-076BA8C5BDD5@gmail.com>
Permalink:  ../9F566B71-42A3-4502-85CA-076BA8C5BDD5@gmail.com/
Also on:    postgresql.org/message-id/9F566B71-42A3-4502-85CA-076BA8C5BDD5@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: ckolovson@gmail.com, tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Bug in documentation: https://www.postgresql.org/docs/current/spi-examples.html
  In-Reply-To: <9F566B71-42A3-4502-85CA-076BA8C5BDD5@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox