From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: superusers are members of all roles? |
Date: | 2011-04-07 15:26:29 |
Message-ID: | 4D9DD7A5.6080904@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/07/2011 11:01 AM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> I thought about that. What I'd like to know is how many people actually
>> want and use and expect the current behaviour. If it's more than a
>> handful (which I seriously doubt) then that's probably the way to go.
>> Otherwise it seems more trouble than it's worth.
> Well, the point here is that "is_member_of" is currently considered
> to be a kind of privilege test, and of course superusers should
> automatically pass every privilege test. If you want it to not act
> that way in some circumstances, we need a fairly clear theory as to
> which circumstances it should act which way in.
>
>
Personally, other things being equal I would expect things to operate
similarly to Unix groups, where root can do just about anything but is
only actually a member of a small number of groups:
[root(at)emma ~]# groups
root bin daemon sys adm disk wheel
I bet most DBAs and SAs would expect the same.
The HBA file is the most obvious context in which this actually matters,
and off hand I can't think of another.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Selena Deckelmann | 2011-04-07 15:54:55 | Re: GSoC Proposal - Caching query results in pgpool-II |
Previous Message | Kevin Grittner | 2011-04-07 15:21:21 | Re: SSI bug? |