summaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/misc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-11-19 14:21:42 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-11-19 14:21:42 -0500
commitde8c2d38fddc4be2a4cd0c5108b428daa5cc781e (patch)
treeb99212f6e729293b3b6edd3daf65191c66e69cb0 /src/backend/utils/adt/misc.c
parentecb533af623738f49a8bd748e688c7f02c1c0f9f (diff)
Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA.
The existing text stated that "Default privileges that are specified per-schema are added to whatever the global default privileges are for the particular object type". However, that bare-bones observation is not quite clear enough, as demonstrated by the complaint in bug #16124. Flesh it out by stating explicitly that you can't revoke built-in default privileges this way, and by providing an example to drive the point home. Back-patch to all supported branches, since it's been like this from the beginning. Discussion: https://postgr.es/m/16124-423d8ee4358421bc@postgresql.org
Diffstat (limited to 'src/backend/utils/adt/misc.c')
0 files changed, 0 insertions, 0 deletions