diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-11-19 14:21:41 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-11-19 14:21:41 -0500 |
| commit | 787b3fd33fb3089bf80d49ef9948a6ec85005d04 (patch) | |
| tree | 189faaece2e8ed8c262929bd0ec49eb9d08047c5 /contrib/btree_gist/btree_text.c | |
| parent | 7f338369ca624ca6c2e4f579623274c88d325bce (diff) | |
| download | postgresql-787b3fd33fb3089bf80d49ef9948a6ec85005d04.tar.gz postgresql-787b3fd33fb3089bf80d49ef9948a6ec85005d04.zip | |
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 'contrib/btree_gist/btree_text.c')
0 files changed, 0 insertions, 0 deletions