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

2023-07-17 Thread Curt Kolovson
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 wrote: > > "David G

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

2023-07-17 Thread Curt Kolovson
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 wrote: > > "David G. Johnston" writes: >>> On Mon, Jul 17, 2023 at 4:53 PM Curt Kolovson w

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

2023-07-17 Thread Curt Kolovson
The actual results (shown below) are different than shown on this doc page. The reason is because the second parameter to the UDF that is passed to SPI_exec is the maximum number of rows to return, or 0 for no limit. It is not the maximum number of rows to process. In the case of "SELECT execq('INS