Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA94528; Sat, 15 Apr 2000 14:52:08 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id OAA02648; Sat, 15 Apr 2000 14:50:35 -0400 (EDT) From: Bruce Momjian Message-Id: <200004151850.OAA02648@candle.pha.pa.us> Subject: Re: Re: [HACKERS] SESSION_USER In-Reply-To: from Peter Eisentraut at "Apr 15, 2000 08:53:01 pm" To: Peter Eisentraut Date: Sat, 15 Apr 2000 14:50:35 -0400 (EDT) CC: Tom Lane , PostgreSQL-development , PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200004/86 [Charset ISO-8859-1 unsupported, filtering to ASCII...] > Tom Lane writes: > > > Looking at the spec, we do seem to be missing SYSTEM_USER out of the > > four variants the spec mentions. However, considering that we map > > them all to the same thing anyway, I can't get too excited about it. > > 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. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026