Re: plpython does not honour max-rows
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Kieran McCusker <kieran.mccusker@gmail.com>,
pgsql-bugs@lists.postgresql.org
Date: 2023-05-02T21:21:51Z
Lists: pgsql-bugs
Daniel Gustafsson <daniel@yesql.se> writes: > On 2 May 2023, at 22:39, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> mainly because >> plperl's spi_exec_prepared uses that name as a caller-exposed hash key. > But I didn't realize that, and in light of that I agree that limit is better. OK, let's do it like that then. >> I'm not especially concerned about the wording otherwise. > Neither am I, both are fine I think. I'll compare and merge the two patches and push. Thanks for looking at it! 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