Re: distinguishing different database connections - Mailing list pgsql-sql

From Stephan Szabo
Subject Re: distinguishing different database connections
Date
Msg-id Pine.BSF.4.21.0106221138530.9504-100000@megazone23.bigpanda.com
Whole thread Raw
In response to distinguishing different database connections  (Markus Wagner <wagner@imsd.uni-mainz.de>)
List pgsql-sql
How about creating a temporary table with the data?  That'll be persistant
for the session.

On Fri, 22 Jun 2001, Markus Wagner wrote:

> Hi,
> 
> can I access information on the current connection from within a trigger
> function?
> I need to identify different server connections somehow. Something like
> a "connection id" would be enough.
> 
> The background:
> 
> When a user starts a frontend application (NT, Access) he starts a new
> connection to our Linux database server. But for all users the "postgres
> user" is the same, since the ODBC connection is hard linked into the
> application. The problem is that we need the NT user name within our
> trigger (C) functions.
> 
> The idea:
> Let's execute a function "logon" whenever an instance of the application
> is started. This function will get the NT user name as a parameter. It
> will recognize the current connection id and it would store the pair
> (connection id, NT user name) in a table. Then, whenever some trigger
> needs to know the user name (for logging actions), it could lookup the
> user name with the current connection id.



pgsql-sql by date:

Previous
From: pierre@kahuna.versions.com
Date:
Subject: timestamp conversion to unisgned long?
Next
From: "Josh Berkus"
Date:
Subject: Re: View performance question