Re: privileges oddity - Mailing list pgsql-general

From Scott Ribe
Subject Re: privileges oddity
Date
Msg-id 997A0678-B203-432F-AF7D-7ADB6415C28A@elevated-dev.com
Whole thread Raw
In response to Re: privileges oddity  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: privileges oddity
Re: privileges oddity
List pgsql-general
> On Aug 7, 2020, at 1:08 PM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>
> "Using this command, it is possible to either add privileges or restrict one's privileges. If the session user role
hasthe INHERIT attribute, then it automatically has all the privileges of every role that it could SET ROLE to; in this
caseSET ROLE effectively drops all the privileges assigned directly to the session user and to the other roles it is a
memberof, leaving only the privileges available to the named role. On the other hand, if the session user role has the
NOINHERITattribute, SET ROLE drops the privileges assigned directly to the session user and instead acquires the
privilegesavailable to the named role. 
> "

So it would only have removed privs if I had used set role in the session, which I am not.





pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: privileges oddity
Next
From: Tom Lane
Date:
Subject: Re: privileges oddity