From: | Guillaume LELARGE <gleu(at)wanadoo(dot)fr> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Andrew Gould <andrewgould(at)yahoo(dot)com> |
Subject: | Re: capturing and storing query statement with rules |
Date: | 2003-06-24 22:40:28 |
Message-ID: | 200306242240.28986.gleu@wanadoo.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Le Mardi 24 Juin 2003 20:17, Andrew Gould a écrit :
> I would like to create a audit log of update and
> delete queries against a table. I want the log on the
> server side, since access will be done using various
> clients via ODBC. I would like to capture the user,
> current datetime and the query statement. My thought
> was to accomplish this by creating a rule that will
> insert the information into a log table.
>
To be server side, you need to use a trigger and a plpgsql function. On this
page you will find more informations on trigger related functions:
http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=plpgsql-trigger.html
Perhaps you can compare OLD and NEW rows to know which rows will be updated.
And you'll find at the end of the page how to get current user (current_user
keyword) and current datetime (function now).
> How can I captures the query statement so that I can
> place it in a insert query? Is there a variable in
> the server that holds the query statement as a string?
>
I don't think... or wasn't able to find something like this one in the
documentation.
Regards.
--
Guillaume <!-- http://absfr.tuxfamily.org/ -->.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-06-24 23:00:00 | Re: [GENERAL] Bug in metaphone (contrib/fuzzystrmatch) |
Previous Message | scott.marlowe | 2003-06-24 22:08:34 | Re: A creepy story about dates. How to prevent it? |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-06-24 23:22:31 | Re: [GENERAL] Many Pl/PgSQL parameters -> AllocSetAlloc(128)? |
Previous Message | Jonathan Bartlett | 2003-06-24 21:48:35 | Physical Database Configuration |