Horton
Menu

Re: plpython does not honour max-rows

Daniel Gustafsson <daniel@yesql.se>

View thread
From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kieran McCusker <kieran.mccusker@gmail.com>, pgsql-bugs@lists.postgresql.org
Date: 2023-05-02T20:34:04Z
Lists: pgsql-bugs

Attachments

> On 2 May 2023, at 16:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Since that's stood for a few decades now, changing it seems impossible
> from the backwards-compatibility standpoint.

Agreed, that's a non-starter.

> However, it does seem
> appropriate to repeat that material in the wrapper's documentation.
> 
> I wonder whether the similar plperl and pltcl wrappers are also
> documentation-shy here.

It seems like they are all a bit thin on explaining this.  The attached diff
copies the wording (which unsurprisingly is pretty good IMO) into the
plperl/python/tcl documentation.

--
Daniel Gustafsson

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers.