Re: plpython does not honour max-rows

Kieran McCusker <kieran.mccusker@gmail.com>

From: Kieran McCusker <kieran.mccusker@gmail.com>
To: daniel@yesql.se
Cc: pgsql-bugs@lists.postgresql.org
Date: 2023-05-02T11:37:00Z
Lists: pgsql-bugs
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?
Anyway it was surprising gotcha, but of course easy to code around.

Kieran

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

> > On 2 May 2023, at 12:30, Kieran McCusker <kieran.mccusker@gmail.com>
> wrote:
>
> > I came across this when developing a sampling function using
> plpy.execute that needs to be able to sample zero rows. What actually
> happens is that zero is ignored for max-rows and all rows are returned.
>
> A max_rows of less than or equal to zero is IIRC interpreted as "fetch all
> rows".  I think this works as intended, is it documented anywhere to work
> in
> another way?
>
> --
> 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.