Re: \c connects as another user instead I want in psql

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 19:53:25
Message-ID: 200105071953.f47JrPH25668@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> After thinking about that for awhile, I am inclined to change my
> previous position: we should not switch over to using the OIDs of
> pg_shadow rows as user identifiers. usesysid should continue to
> exist. Ditto for groups --- grosysid can't go away either.
>
> 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.

One thing on the TODO list is to allow people to soecify OID's on
INSERT. There is no reason we should disallow it, and it could come in
handy for fixing deleted rows.

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-05-07 19:54:24 Re: case insensitive unique index (part 2)
Previous Message Doug McNaught 2001-05-07 18:51:18 Re: Re: File system performance and pg_xlog (More info)