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

From: Ian Lance Taylor <ian(at)airs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: \c connects as another user instead I want in psql
Date: 2001-05-03 18:05:17
Message-ID: siy9se8g0y.fsf@daffy.airs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> No. I'm not sure whether or not I believe the comment about Unix
> accounts; Postgres does not care about Unix accounts, and never has
> to my knowledge. But it has always used the usesysid as owner
> identification for database objects (tables etc). If two different
> users have the same usesysid then they are both the owner of these
> objects; moreover they are interchangeable for permissions checks, too.
> This is not a situation that has any practical use AFAICS.

On Unix it is reasonable to have multiple users with the same user ID.
You do this when they play the same role, but it is useful to
distinguish them for logging purposes. They have different passwords,
of course, and logging code uses getlogin() to get the login name they
used.

I can imagine something similar within Postgres, using triggers to
record log information when changes are made.

Whether this is a feature worth having, I don't know. But there is at
least one practical use.

Ian

---------------------------(end of broadcast)---------------------------
TIP 924: Good news from afar can bring you a welcome visitor.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message bpalmer 2001-05-03 18:20:50 Re: Re: New Linux xfs/reiser file systems
Previous Message Bruce Momjian 2001-05-03 17:17:58 Final stamp for 7.1.1