Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4H1CtA90892 for ; Wed, 16 May 2001 21:12:56 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4H1CiR08127; Wed, 16 May 2001 21:12:44 -0400 (EDT) To: Jonathan Bartlett cc: pgsql-sql@postgresql.org Subject: Re: Setting session global variables In-reply-to: References: Comments: In-reply-to Jonathan Bartlett message dated "Thu, 17 May 2001 00:43:45 -0000" Date: Wed, 16 May 2001 21:12:44 -0400 Message-ID: <8124.990061964@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/178 X-Sequence-Number: 2995 Jonathan Bartlett writes: > However, the only way I can see to implement this is to have session > global variables. Is there a way to fake session global variables with a > table? Any comments would be appreciated. You could do it with temp tables: the same temp table name would refer to a different table in each session. (You realize, of course, that CURRENT_USER already exists per SQL spec. I assume you just meant that you'd like to have things *like* CURRENT_USER, but defined by yourself...) regards, tom lane