pgsql: Allow type_func_name_keywords in even more places - Mailing list pgsql-committers

From Stephen Frost
Subject pgsql: Allow type_func_name_keywords in even more places
Date
Msg-id E1W5p1T-0004bp-VZ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Allow type_func_name_keywords in even more places

A while back, 2c92edad48796119c83d7dbe6c33425d1924626d allowed
type_func_name_keywords to be used in more places, including role
identifiers.  Unfortunately, that commit missed out on cases where
name_list was used for lists-of-roles, eg: for DROP ROLE.  This
resulted in the unfortunate situation that you could CREATE a role
with a type_func_name_keywords-allowed identifier, but not DROP it
(directly- ALTER could be used to rename it to something which
could be DROP'd).

This extends allowing type_func_name_keywords to places where role
lists can be used.

Back-patch to 9.0, as 2c92edad48796119c83d7dbe6c33425d1924626d was.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/f2eede9b584305472dd3fd58e1690766c378ab34

Modified Files
--------------
src/backend/parser/gram.y |   48 +++++++++++++++++++++++++--------------------
1 file changed, 27 insertions(+), 21 deletions(-)


pgsql-committers by date:

Previous
From: Stephen Frost
Date:
Subject: pgsql: Allow type_func_name_keywords in even more places
Next
From: Stephen Frost
Date:
Subject: pgsql: Allow type_func_name_keywords in even more places