Re: plpython does not honour max-rows

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 21:21:51
Message-ID: 2834901.1683062511@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 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!

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2023-05-02 21:23:39 Re: plpython does not honour max-rows
Previous Message Daniel Gustafsson 2023-05-02 20:50:17 Re: plpython does not honour max-rows