From: | Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: plpython does not honour max-rows |
Date: | 2023-05-02 11:51:06 |
Message-ID: | CAGgUQ6FMfBrCTeu7DLUmmsSVn0zu02mx7xZ39etb26pAqTrM+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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(at)yesql(dot)se> wrote:
> > On 2 May 2023, at 13:37, Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Vaclav Pink | 2023-05-02 12:00:18 | RE: BUG #17906: Segmentation fault and database crash during procedure call |
Previous Message | Daniel Gustafsson | 2023-05-02 11:48:46 | Re: plpython does not honour max-rows |