From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Clark C(dot) Evans" <cce(at)clarkevans(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: COMMENT ON [GROUP/USER] |
Date: | 2004-03-08 19:36:01 |
Message-ID: | 200403081936.i28Ja1C20944@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Clark C. Evans" <cce(at)clarkevans(dot)com> writes:
> > It would be wonderful to be able to create comments
> > on users and groups. In particular, I need a place
> > to store the user's name. Yes, I could make a user
> > table, but that seems overkill as all of the other
> > aspects of a user are already in the metadata.
>
> This seems like a good idea, but I'd recommend leaving it as a TODO
> until after we finish the planned revisions for SQL role support.
> (Peter E. has made noises about working on that, but I dunno what
> his timeframe for it is.) In particular, it's not clear that there
> will still be a hard and fast separation between "users" and "groups"
> after that happens, so it seems premature to wire such an assumption
> into the syntax.
>
> Another small problem that would have to be faced is that users and
> groups don't have OIDs. We could physically get away with a type-cheat
> of storing their integer IDs into pg_description instead, but I'm worried
> that would create issues of its own.
Another problem is that pg_description is per-database, while
pg_user/group are global for all databases.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-03-08 19:41:06 | Re: raising the default default_statistics_target |
Previous Message | Tom Lane | 2004-03-08 19:25:06 | Re: COMMENT ON [GROUP/USER] |