Re: plpython does not honour max-rows

Kieran McCusker <kieran.mccusker@gmail.com>

From: Kieran McCusker <kieran.mccusker@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2023-05-02T11:51:06Z
Lists: pgsql-bugs
Without making too much of a fuss, wouldn't it be simpler to honour a
row-limit of zero rather than document that it doesn't work?

On Tue, 2 May 2023 at 12:48, Daniel Gustafsson <daniel@yesql.se> wrote:

> > On 2 May 2023, at 13:37, Kieran McCusker <kieran.mccusker@gmail.com>
> wrote:
>
> > Thanks for the quick response. Chapter 46.6.1 says that max-rows is an
> optional row limit. Unless I missed it there is nothing in the
> documentation about zero meaning all rows. Wouldn't it rather be like SQL
> LIMIT 0 meaning all rows?
>
> That does sound like something which we should document, the confusion is
> easy
> to see. Thanks for the report.
>
> FTR I think I misremembered in my earlier email, it's == 0 and not <= 0
> which
> implies to limit.
>
> --
> Daniel Gustafsson
>
>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Doc: clarify behavior of row-limit arguments in the PLs' SPI wrappers.