| 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 21:23:39 |
| Message-ID: | 2D9214C9-4223-46A3-A234-1366763882B9@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 2 May 2023, at 23:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 2 May 2023, at 22:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-05-03 05:19:07 | BUG #17916: Expression IN list translates to unqualified operator |
| Previous Message | Tom Lane | 2023-05-02 21:21:51 | Re: plpython does not honour max-rows |