Re: Improving some plpgsql error messages
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-20T16:16:33Z
Lists: pgsql-hackers
On Fri, Aug 20, 2021 at 8:50 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thoughts? Should I back-patch this into v14 where 2f48ede08 > came in, or just do it in HEAD? > I'd say back-patch in the interest of preventing probably quite a few emails from novices at plpgsql coding dealing with all the interplay between queries and variables and returning syntaxes. David J.
Commits
-
Improve error messages about misuse of SELECT INTO.
- 8f6a52196ace 14.0 landed
- 26ae66090398 15.0 landed
-
Avoid using a cursor in plpgsql's RETURN QUERY statement.
- 2f48ede080f4 14.0 cited