Re: SET ROLE documentation improvement
Yurii Rashkovskii <yrashk@gmail.com>
From: Yurii Rashkovskii <yrashk@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2023-09-26T15:33:25Z
Lists: pgsql-hackers
Attachments
- V2-0001-Minor-improvement-to-SET-ROLE-documentation.patch (application/octet-stream) patch 0001
On Mon, Sep 25, 2023 at 3:09 PM Nathan Bossart <nathandbossart@gmail.com> wrote: > On Fri, Sep 15, 2023 at 02:36:16PM -0700, Yurii Rashkovskii wrote: > > On Fri, Sep 15, 2023 at 1:47 PM Nathan Bossart <nathandbossart@gmail.com > > > > wrote: > >> I think another issue is that the aforementioned note doesn't mention > the > >> new SET option added in 3d14e17. > > > > How do you think we should word it in that note to make it useful? > > Maybe something like this: > > The current session user must have the SET option for the specified > role_name, either directly or indirectly via a chain of memberships > with the SET option. > This is a good start, indeed. I've amended my patch to include it. -- Y.
Commits
-
doc: Note exceptions for SET ROLE's effect on privilege checks.
- 953cf49e166a 17.0 landed
-
doc: Clarify requirements for SET ROLE.
- d82dc79ba03c 16.3 landed
- 3330a8d1b792 17.0 landed