aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/geo_spgist.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2023-01-16 10:35:29 -0500
committerRobert Haas <rhaas@postgresql.org>2023-01-16 10:35:29 -0500
commit3cdf7502f85c9e61913e05519f88580f008b8453 (patch)
tree6e77f0aa9c1cb8004572dae91f6391838d481846 /src/backend/utils/adt/geo_spgist.c
parent20428d344a2964de6aaef9984fcd472f3c65d115 (diff)
downloadpostgresql-3cdf7502f85c9e61913e05519f88580f008b8453.tar.gz
postgresql-3cdf7502f85c9e61913e05519f88580f008b8453.zip
More documentation update for GRANT ... WITH SET OPTION.
Update the reference pages for various ALTER commands that mentioned that you must be a member of role that will be the new owner to instead say that you must be able to SET ROLE to the new owner. Update ddl.sgml's generate statement on this topic along similar lines. Likewise, update CREATE SCHEMA and CREATE DATABASE, which have options to specify who will own the new objects, to say that you must be able to SET ROLE to the role that will own them. Finally, update the documentation for the GRANT statement itself with some general principles about how the SET option works and how it can be used. Patch by me, reviewed (but not fully endorsed) by Noah Misch. Discussion: http://postgr.es/m/CA+TgmoZk6VB3DQ83+DO5P_HP=M9PQAh1yj-KgeV30uKefVaWDg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/geo_spgist.c')
0 files changed, 0 insertions, 0 deletions