]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Allow type_func_name_keywords in even more places
authorStephen Frost <sfrost@snowman.net>
Wed, 22 Jan 2014 03:49:22 +0000 (22:49 -0500)
committerStephen Frost <sfrost@snowman.net>
Wed, 22 Jan 2014 04:01:40 +0000 (23:01 -0500)
commitf2eede9b584305472dd3fd58e1690766c378ab34
treea1d49fd6941cc851787d239bba980d5c34665e14
parente70c4282136e07ab3a0e57f3c811de80e4318d9f
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.
src/backend/parser/gram.y