| From: | Nathan Bossart <nathan(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: doc: Clarify requirements for SET ROLE. |
| Date: | 2024-03-24 20:28:57 |
| Message-ID: | E1roUSf-005TTg-3J@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
doc: Clarify requirements for SET ROLE.
Since commit 3d14e171e9, SET ROLE has required the current session
user to have membership with the SET option in the target role, but
the SET ROLE documentation only mentions the membership
requirement. This commit adds this important detail to the SET
ROLE page.
Reviewed-by: Robert Haas
Discussion: https://postgr.es/m/CA%2BRLCQysHtME0znk2KUMJN343ksboSRQSU-hCnOjesX6VK300Q%40mail.gmail.com
Backpatch-through: 16
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d82dc79ba03c783fa41be768c1bf13cb8200a340
Modified Files
--------------
doc/src/sgml/ref/set_role.sgml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2024-03-24 23:40:22 | pgsql: Fix convert_case(), introduced in 5c40364dd6. |
| Previous Message | Tom Lane | 2024-03-24 18:30:40 | pgsql: Allow more cases to pass the unsafe-use-of-new-enum-value restri |