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-02T21:23:39Z
Lists: pgsql-bugs 
> On 2 May 2023, at 23:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> 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!

+1, sounds like a good plan.

--
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.