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: | Jan Wieck <JanWieck(at)yahoo(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: \c connects as another user instead I want in psql |
Date: | 2001-05-07 18:40:33 |
Message-ID: | 200105071840.f47IeXN19882@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I think the original motivation for wanting to eliminate these columns
> was that we need usesysid and grosysid to be distinct (can't use the
> same ID for both a user and a group). Using OIDs as IDs would fix
> that, but it's overkill. Wouldn't it be sufficient to use an
> installation-wide sequence object to assign new IDs for new users and
> groups? We have no such animals at the present, but I see no reason
> why we couldn't make one.
Updated TODO to show both options:
* Add unique indexes to pg_shadow.usename and pg_shadow.usesysid or
switch to pg_shadow.oid as user id
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-05-07 18:48:11 | Re: NOCREATETABLE patch (was: Re: Please, help!(about Postgres)) |
Previous Message | Bruce Momjian | 2001-05-07 18:38:50 | Re: Re: XFS File systems and PostgreSQL |