pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: clarify behavior of ALTER DEFAULT PRIVILEGES ... IN SCHEMA.
Date: 2019-11-19 19:22:02
Message-ID: E1iX94c-00019F-8F@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/787b3fd33fb3089bf80d49ef9948a6ec85005d04

Modified Files
--------------
doc/src/sgml/ref/alter_default_privileges.sgml | 30 ++++++++++++++++++++------
1 file changed, 23 insertions(+), 7 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2019-11-19 19:43:51 pgsql: Doc: clarify use of RECURSIVE in WITH.
Previous Message Thomas Munro 2019-11-19 02:57:58 pgsql: Allow invisible PROMPT2 in psql.