From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | aalasso(at)gmail(dot)com |
Subject: | Misleading sentence about default privileges |
Date: | 2021-06-17 09:07:11 |
Message-ID: | 162392083110.690.13436519749099977740@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/sql-alterdefaultprivileges.html
Description:
In the docs
(https://www.postgresql.org/docs/10/sql-alterdefaultprivileges.html) it
states:
> You can change default privileges only for objects that will be created by
yourself or by roles that you are a member of.
Yet, altering the default privileges `for role`'s that I am a member of
(i.e. `target_role` in docs), does not affect privileges granted on objects
created by other members of said role.
Seeing as separating Users (roles with log-in privilege) from Roles
(containing concrete grants, unable to log in) seems a common, and
recommendable pattern, I believe the statement is quite misleading.
For an example of expected behaviour, see this Stack Overflow question:
https://stackoverflow.com/questions/56237907/why-doesnt-alter-default-privileges-work-as-expected
The only scenario I can think of where the statement makes sense seems quite
foreign to me:
Scenario: I, say `role_a`, have log-in, and am also a member of another
Role, say `role_b`, which also has login. Only objects created directly by
`role_b` (i.e. not any of its members) are affected.
I suggest adding something like the following to the documentation:
" Note that only object created directly by _*target_role*_ , i.e. not any
of its members, will have privileges granted. "
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2021-06-17 14:56:52 | Re: Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM |
Previous Message | Shinya11.Kato | 2021-06-16 05:22:41 | change float4 to floating point about type of autovacuum_vacuum_insert_scale_factor |