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 TAA69202; Sat, 15 Apr 2000 19:29:29 -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 TAA03974; Sat, 15 Apr 2000 19:28:48 -0400 (EDT) From: Bruce Momjian Message-Id: <200004152328.TAA03974@candle.pha.pa.us> Subject: Re: Re: [HACKERS] SESSION_USER In-Reply-To: <17157.955839129@sss.pgh.pa.us> from Tom Lane at "Apr 15, 2000 06:52:09 pm" To: Tom Lane Date: Sat, 15 Apr 2000 19:28:47 -0400 (EDT) CC: Peter Eisentraut , 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/89 > Bruce Momjian 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 Updated. Thanks. -- 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