| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Auditing and Postgres 7.3 |
| Date: | 2002-01-23 15:54:35 |
| Message-ID: | 200201231544.g0NFicS04407@neuromancer.ctlno.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I've been thinking implementing auditing for Postgres 7.3 and wanted to
> see if anyone had any thoughts about it.
< snip >
> So what would an audit trail consist of?
>
> timestamp
> query type
> query
> query result (successful|unsuccessful)
> audit object oid
We have implemented an audit trail at the application level several times for
several different projects. While what you have described in this thread is
more aimed at debugging, what we have used it for is to see who changed what
value to what when. We can show the complete history of all the values for
parts of our schema, and who changed them when. Very useful for a number of
situation. This I would be a nice feature to have the database manage.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8Tty+8BXvT14W9HARAoFVAJ9fMHF9q0QhcRQSdmmGbTZX3P1vyACgkquy
WU0WElwZoF6LOP9yNgIvf1c=
=RazC
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-23 16:02:33 | Re: Add OR REPLACE clauses to non-FUNCTION object creation in PostgreSQL 7.3 |
| Previous Message | Tom Lane | 2002-01-23 15:44:34 | Re: RFD: schemas and different kinds of Postgres objects |