| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | torcher999(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15281: Set role does not affect superuser privleges |
| Date: | 2018-07-16 22:12:50 |
| Message-ID: | 9786.1531779170@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> On 07/16/2018 04:55 PM, PG Bug reporting form wrote:
>> Here are the two scenarios I tested:
>> 1) as a session_user: superuser and current_user: non-superuser I can edit
>> others' tables
>> 2) as a session_user: non-superuser and current_user: superuser I cannot
>> edit others' tables
> It's usually a good idea to provide exact scripts / output so that
> people can reproduce the issue easily. For me it behaves like this:
> ...
> So, correct in both cases. I'm not on Windows, but I don't see why would
> it behave differently there.
Tomas' test left out the "GRANT user0 to user1" bit, but I can't
reproduce the behavior as described either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-07-16 23:26:41 | Re: BUG #15281: Set role does not affect superuser privleges |
| Previous Message | Tomas Vondra | 2018-07-16 21:48:43 | Re: BUG #15281: Set role does not affect superuser privleges |