| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | SHARMILA JOTHIRAJAH <sharmi_jo(at)yahoo(dot)com> |
| Cc: | General postgres mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres auditing features |
| Date: | 2009-06-11 21:27:24 |
| Message-ID: | alpine.GSO.2.01.0906111723180.26947@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 11 Jun 2009, SHARMILA JOTHIRAJAH wrote:
> Does postgresql have any build-in auditing features like in Oracle's total-recall or fine grained auditing
There's nothing built-in, but it's not too difficult to build such
facilities yourself. I'm quite sure you could find someone who would be
hapy to build you a very extensive implementation of such a feature
customized for your application for less than an Oracle license costs.
Simple example right in the official docs:
http://www.postgresql.org/docs/8.3/static/plpgsql-trigger.html#PLPGSQL-TRIGGER-AUDIT-EXAMPLE
Project targeting this feature: http://pgfoundry.org/projects/tablelog/
Background information and other sample implementations:
http://it.toolbox.com/blogs/database-soup/simple-data-auditing-19014
http://www.go4expert.com/forums/showthread.php?t=7252
http://www.alberton.info/postgresql_table_audit.html
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-06-11 21:27:56 | Re: help with data recovery from injected UPDATE |
| Previous Message | Brandon Metcalf | 2009-06-11 20:56:34 | Re: listing relations |