> On 2 May 2023, at 22:39, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>>> On 2 May 2023, at 16:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 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.
>
> Ah, seems like we set to work on this at the same time :-(
Pretty impressive timing across timezones =)
> I thought that s/max-rows/limit/ would be a good idea,
I was actually thinking about that but backed off to not confuse things with
LIMIT.
> 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.
> I'm not especially concerned about the wording otherwise.
Neither am I, both are fine I think.
--
Daniel Gustafsson
