Re: PL/pgSQL: apply the too_many_rows extra check to EXECUTE ... INTO

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PL/pgSQL: apply the too_many_rows extra check to EXECUTE ... INTO
Date: 2026-11-16 00:46:09
Message-ID: CAHGQGwFdv0UxJ-YCZ6zbYED6BZu+f1EO95gKAteab+Dz_kiPUA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2026 at 1:50 AM Jeevan Chalke
<jeevan(dot)chalke(at)enterprisedb(dot)com> wrote:
> Just one small observation on the 0002 commit message: it does not mention that EXECUTE ... INTO STRICT errors also gain the hint now (the three existing stricttest cases in plpgsql.out change accordingly). You may want to add a sentence about that.

OK, I'll add "Also add a hint to errors reported when EXECUTE ... INTO
STRICT returns multiple rows." to the commit message for the 0002 patch.
After one more CI run with both patches, I'll commit them.

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-11-16 00:59:08 Re: DOCS - CREATE PUBLICATION wording re 'ONLY' for partitioned tables.
Previous Message Manu 2026-11-16 00:34:35 Re: UNDO with FILEOPS, and the FLUX table AM