| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:34:04 |
| Message-ID: | F0A43D83-EA33-4909-A002-1C401ACE1049@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 2 May 2023, at 16:02, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Since that's stood for a few decades now, changing it seems impossible
> from the backwards-compatibility standpoint.
Agreed, that's a non-starter.
> However, it does seem
> appropriate to repeat that material in the wrapper's documentation.
>
> 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.
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| max_rows.diff | application/octet-stream | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-05-02 20:35:45 | Re: plpython does not honour max-rows |
| Previous Message | PG Bug reporting form | 2023-05-02 16:58:42 | BUG #17915: sha256sum check failure on postgress 14 rhel-7-x86_64 repository |