From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: De-reserve keywords EXECUTE and STRICT in PL/pgSQL.
Date: Mon, 30 Jun 2025 21:06:46 +0000
Message-ID: <E1uWLiA-0045jb-1C@gemulon.postgresql.org> (raw)
De-reserve keywords EXECUTE and STRICT in PL/pgSQL.
On close inspection, there does not seem to be a strong reason
why these should be fully-reserved keywords. I guess they just
escaped consideration in previous attempts to minimize PL/pgSQL's
list of reserved words.
Author: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Pavel Stehule <pavel.stehule@gmail.com>
Discussion: https://postgr.es/m/2185258.1745617445@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/999f172ded2bae7efbd8bf1dd6f823095395493f
Modified Files
--------------
src/pl/plpgsql/src/expected/plpgsql_misc.out | 14 ++++++++++++++
src/pl/plpgsql/src/pl_gram.y | 13 +++++++++----
src/pl/plpgsql/src/pl_reserved_kwlist.h | 2 --
src/pl/plpgsql/src/pl_scanner.c | 2 +-
src/pl/plpgsql/src/pl_unreserved_kwlist.h | 2 ++
src/pl/plpgsql/src/sql/plpgsql_misc.sql | 13 +++++++++++++
6 files changed, 39 insertions(+), 7 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: De-reserve keywords EXECUTE and STRICT in PL/pgSQL.
In-Reply-To: <E1uWLiA-0045jb-1C@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox