Horton

Re: Sanding down some edge cases for PL/pgSQL reserved words

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org, Jan Behrens <jbe-mlist@magnetkern.de>
Date: 2025-06-30T21:08:37Z
Lists: pgsql-hackers 
Pavel Stehule <pavel.stehule@gmail.com> writes:
> Looks so nobody has any motivation to do some deeper changes to reduce
> prohibition of reserved words. It is true, so in the real world it is not
> an issue.

Certainly anyone who's annoyed is free to do more work here.

> All tests passed without problems. I'll mark this patch as ready for commit.
> Maybe the usage of unreserved words as variables or field names can be
> tested a little bit more. See patch 0003

Pushed with the test case as you suggested.  Thanks for reviewing!

			regards, tom lane

Commits

  1. Improve error report for PL/pgSQL reserved word used as a field name.

  2. De-reserve keywords EXECUTE and STRICT in PL/pgSQL.