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

From: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(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 03:34:11
Message-ID: CAM2+6=UDP=P0LkWgQtmB33X-82iGC_wu2bUdiDWPkjth2SQzQQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2026 at 7:38 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:

> 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!
>

Thank you, Fujii-san.

> Regards,
>
> --
> Fujii Masao
>

--
*Jeevan Chalke*
*Senior Principal Engineer, Engineering Manager*
*Product Development*

enterprisedb.com <https://www.enterprisedb.com>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-11-16 04:04:32 Re: Index drops during phase 1 of REINDEX CONCURRENTLY
Previous Message David Rowley 2026-11-16 03:27:03 Re: Incremental Sort crash on a rescan that becomes bounded