From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Groups and roles |
Date: | 2003-06-18 18:53:50 |
Message-ID: | Pine.LNX.4.44.0306181732270.2501-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> Hm. That seems to be another reason to unify usesysid and grosysid into
> a single unique something-id. Which probably implies unifying pg_shadow
> and pg_group into one table.
Maybe this is too radical, but why not merge "user" and "group" into one
animal? Both exist to bear privileges. The only difference is that
groups can contain other bearers of privileges, but then a user is just a
special case with zero members. Once you allow groups to have the
possibilities that users currently have (createdb privilege, object
ownership), there is no difference left. Of course, one such "animal"
would be the session user and interact with pg_hba.conf, but that is just
an ID, which may as well be a group.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-06-18 18:57:31 | Escape sequences in string literals insufficient? |
Previous Message | Peter Eisentraut | 2003-06-18 18:52:25 | Re: Groups and roles |