| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: plpython does not honour max-rows |
| Date: | 2023-05-02 20:39:15 |
| Message-ID: | 2830145.1683059955@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 2 May 2023, at 16:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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 :-(
I thought that s/max-rows/limit/ would be a good idea, mainly because
plperl's spi_exec_prepared uses that name as a caller-exposed hash key.
I'm not especially concerned about the wording otherwise.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-05-02 20:50:17 | Re: plpython does not honour max-rows |
| Previous Message | Tom Lane | 2023-05-02 20:35:45 | Re: plpython does not honour max-rows |