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

On Tue, Nov 3, 2026 at 10:27 PM Jeevan Chalke
<jeevan(dot)chalke(at)enterprisedb(dot)com> wrote:
> If you think this is not needed, please feel free to ignore 0003.

Yes, let's leave 0003 out for now.

> 0002 removes "or use LIMIT 1" from the hint in both exec_stmt_execsql() and exec_stmt_dynexecute(), and updates the expected output accordingly.

On second thought, LIMIT 1 would be useful advice for many SELECT queries.
So, how about keeping it as a SELECT-specific example instead of removing it?

Make sure the query returns a single row, for example by using LIMIT
1 with SELECT.

> Attached is v3 with three patches:
> 0001: the too_many_rows check for EXECUTE ... INTO (same as v1)
> 0002: the hint change
> 0003: the documentation change

Thanks for updating the patches!

I think it's better to put the hint change first, so the too_many_rows patch
uses the revised hint from the start. So I revised the patches in that order.
Attached. 0001 updates the hint, and 0002 adds the too_many_rows check.

Barring any objections, I'm thinking to commit these to master.

> One more thing: I proposed this for master only, since it changes behavior for users who have too_many_rows in extra_errors, and I'd appreciate your view on that as well.

Agreed.

Regards,

--
Fujii Masao