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 02:08:16
Message-ID: CAHGQGwE2mN1qj_m8hQx2nHWnd10RHWZdRFqzhQGzX9dXL2OfJQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2026 at 9:46 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> 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.

I've pushed the patches. Thanks!

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Chao Li 2026-11-16 01:44:07 Re: extension_control_path: ignore empty elements and deduplicate directories