Re: plpython does not honour max-rows - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: plpython does not honour max-rows
Date
Msg-id 2D9214C9-4223-46A3-A234-1366763882B9@yesql.se
Whole thread Raw
In response to Re: plpython does not honour max-rows  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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




pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpython does not honour max-rows
Next
From: PG Bug reporting form
Date:
Subject: BUG #17916: Expression IN list translates to unqualified operator