Re: privileges oddity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: privileges oddity
Date: 2020-08-07 19:32:03
Message-ID: 2795205.1596828723@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Scott Ribe <scott_ribe(at)elevated-dev(dot)com> writes:
> So it would only have removed privs if I had used set role in the session, which I am not.

Yes, you are. It looks like what you actually issued is

ALTER USER akanzler SET role confidential_read_only;

but that would have the effect that subsequent session starts would
automatically do "SET ROLE confidential_read_only".

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-08-07 19:40:09 Re: privileges oddity
Previous Message Scott Ribe 2020-08-07 19:27:26 Re: privileges oddity