Re: plpython does not honour max-rows
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kieran McCusker <kieran.mccusker@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>, pgsql-bugs@lists.postgresql.org
Date: 2023-05-02T14:02:30Z
Lists: pgsql-bugs
Kieran McCusker <kieran.mccusker@gmail.com> writes: > Without making too much of a fuss, wouldn't it be simpler to honour a > row-limit of zero rather than document that it doesn't work? plpy.execute is a thin wrapper around SPI_execute, which does document this point: If <parameter>count</parameter> is zero then the command is executed for all rows that it applies to. If <parameter>count</parameter> is greater than zero, then no more than <parameter>count</parameter> rows will be retrieved; execution stops when the count is reached, much like adding a <literal>LIMIT</literal> clause to the query. Since that's stood for a few decades now, changing it seems impossible from the backwards-compatibility standpoint. 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. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers.
- b00bae2e9103 13.11 landed
- 825828956ab3 12.15 landed
- 66ab2660e078 14.8 landed
- 6489875ce6b1 16.0 landed
- 23c7aa865b32 15.3 landed
- 0e0463fc590c 11.20 landed