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 | 93b2bbede91b32d12d9e444e576be2efff6942b5 (patch) | |
| tree | dfb4f1bfb7b3375b29ed712428c56d2094793a8d /src/tutorial | |
| parent | fcaf29d87a6ca08188fa9fe1ebba90c9654df006 (diff) | |
| download | postgresql-93b2bbede91b32d12d9e444e576be2efff6942b5.tar.gz postgresql-93b2bbede91b32d12d9e444e576be2efff6942b5.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 'src/tutorial')
0 files changed, 0 insertions, 0 deletions