We intended to do that very thing (read the earlier parts of the thread
between myself and Tom Lane)
Jeff
Guy Rouillier wrote:
Jeff Amiel wrote:
The issue is really propogating the authenticaion credentials to the
database itself.....it's our ON INSERT/ON UPDATE/ON DELETE triggers
that are doing the auditing and they need the user ID to accurately
log changes. In lieu of any other per-connection persistant data
option, this seems like the best bet.
I still don't like the idea of thousands of connections, most of which
will probably most of the time be doing nothing except consuming lots of
memory. You might want to explore creating a small wrapper around the
JBoss connection pool that uses SET SESSION AUTHORIZATION after
obtaining a connection. That way you can still have a small number of
pooled connections but have the real user id associated with the
connection.
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
