diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2020-09-17 11:39:28 +0200 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2020-09-17 11:40:08 +0200 |
commit | 45b9805706fdc726906fc9187c9a7b38c559755c (patch) | |
tree | ef61233750b2bb15746a08f7001d927196f5c965 /contrib/postgres_fdw/postgres_fdw.c | |
parent | 16fa9b2b30a357b4aea982bd878ec2e5e002dbcc (diff) | |
download | postgresql-45b9805706fdc726906fc9187c9a7b38c559755c.tar.gz postgresql-45b9805706fdc726906fc9187c9a7b38c559755c.zip |
Allow CURRENT_ROLE where CURRENT_USER is accepted
In the particular case of GRANTED BY, this is specified in the SQL
standard. Since in PostgreSQL, CURRENT_ROLE is equivalent to
CURRENT_USER, and CURRENT_USER is already supported here, adding
CURRENT_ROLE is trivial. The other cases are PostgreSQL extensions,
but for the same reason it also makes sense there.
Reviewed-by: Vik Fearing <vik@postgresfriends.org>
Reviewed-by: Asif Rehman <asifr.rehman@gmail.com>
Reviewed-by: Alvaro Herrera <alvherre@2ndquadrant.com>
Discussion: https://www.postgresql.org/message-id/flat/f2feac44-b4c5-f38f-3699-2851d6a76dc9%402ndquadrant.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions