summaryrefslogtreecommitdiff
path: root/src/backend/access/gin/ginbtree.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
commit611a4aba15f0e9ef8ef710454bd0ecb4f671eb39 (patch)
tree4feb9805b62786acf44e9ab6a820ee8d1e460710 /src/backend/access/gin/ginbtree.c
parente4865bbdc72a702d09c349116ad64d0b3d8c9add (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/access/gin/ginbtree.c')
0 files changed, 0 insertions, 0 deletions