aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/json.c
diff options
context:
space:
mode:
authorStephen Frost <sfrost@snowman.net>2014-01-21 22:49:22 -0500
committerStephen Frost <sfrost@snowman.net>2014-01-21 22:49:22 -0500
commit6c36f383df728866d7085c155cbe45ebc07b195f (patch)
treebd79088d2625c0f94522844db27fea45fe754509 /src/backend/utils/adt/json.c
parent69c7a9838c82bbfdd61301c697e3774e9543805e (diff)
downloadpostgresql-6c36f383df728866d7085c155cbe45ebc07b195f.tar.gz
postgresql-6c36f383df728866d7085c155cbe45ebc07b195f.zip
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.
Diffstat (limited to 'src/backend/utils/adt/json.c')
0 files changed, 0 insertions, 0 deletions