Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id SAA20556;
	Sat, 15 Apr 2000 18:53:09 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id SAA17160;
	Sat, 15 Apr 2000 18:52:10 -0400 (EDT)
To: Bruce Momjian <pgman@candle.pha.pa.us>
cc: Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL-documentation <docs@postgresql.org>
Subject: Re: Re: [HACKERS] SESSION_USER 
In-reply-to: <200004151850.OAA02648@candle.pha.pa.us> 
References: <200004151850.OAA02648@candle.pha.pa.us>
Comments: In-reply-to Bruce Momjian <pgman@candle.pha.pa.us>
	message dated "Sat, 15 Apr 2000 14:50:35 -0400"
Date: Sat, 15 Apr 2000 18:52:09 -0400
Message-ID: <17157.955839129@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200004/88

Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> SYSTEM_USER is the operating system user that connected to the database
>> system. This is obviously not generally applicable in the environment
>> PostgreSQL runs in, nor is there a universal and reliable way to get this
>> information, so I suggest we don't bother about it. Mapping it to
>> [CURRENT_]USER would certainly be wrong.

> Well, we do already map it.  I just documented it.

No we don't!

regression=# select system_user;
ERROR:  Attribute 'system_user' not found

			regards, tom lane