Re: pg_class changes for group ownership

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_class changes for group ownership
Date: 2004-12-29 17:59:22
Message-ID: 11483.1104343162@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> Due to the fact that group system id's and user system id's can
> overlap, pg_class will need to change in order to accomedate group
> ownership. The things I've thought of so far, in order of preference:

I thought that the agreed-on direction for this was to merge users and
groups into a single kind of entity, or at least make sure that they
share a common unique identifier space. Then AclId is still sufficient
as an ownership indicator, and you don't need any of these kluges.
IIRC something of this sort is needed for improved compliance with the
SQL spec anyway --- see past discussions about "roles".

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2004-12-29 18:04:40 Re: pg_class changes for group ownership
Previous Message Rémi Zara 2004-12-29 17:58:23 Re: buildfarm NetBSD/m68k tsearch regression failure