On 1 February 2012 22:29, Christian Ramseyer <rc@xxxxxxxxxxx> wrote: > Hello list > > I'm trying to build a little trigger-based auditing for various web > applications. They have many users in the application layer, but they > all use the same Postgres DB and DB user. > > So I need some kind of session storage to save this application level > username for usage in my triggers, which AFAIK doesn't exist in > Postgres. Googling suggested to use a temporary table to achieve > something similar. > > Question 1: Is this really the right approach to implement this, or are > there other solutions, e.g. setting application_name to user@application > and using this in the triggers or similar workarounds? > There's an example in the manual of another way to keep session-specific data: http://www.postgresql.org/docs/current/static/plperl-global.html You can do similar things in other procedural languages too, just not in PL/pgSQL. Regards, Dean -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
