Re: Auditing idea

From: "Chris Hutchinson" <chris(at)hutchinsonsoftware(dot)com>
To: "Felipe Schnack" <felipes(at)ritterdosreis(dot)br>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Auditing idea
Date: 2003-08-08 03:04:34
Message-ID: IDEOKBCDGGIDOBADNGAPCEGDEAAA.chris@hutchinsonsoftware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Felipe,

This article might be of interest. It implements exactly the functionality
you describe:
http://philip.greenspun.com/internet-application-workbook/examples-content-m
anagement/audit-acs-doc

Regards,
Chris

> Hey all! I had an idea to implement a very simple (IMHO) auditing
mechanism for an application I'm developing, and thought > some people here
could give some hints, opinions, etc about it.
> I was thinking about implementing update and delete triggers for all my
tables that I want to be audited, and these
> triggers would create automatically the auditing message for me.
Basically, the update triggers would store the row values
> in the OLD and NEW rows, and the delete trigger would store the values in
the OLD row.
> What you guys think of this idea? To me seems simple and good enough.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Neil Zanella 2003-08-08 04:28:52 PostgreSQL and ACID properties support
Previous Message Chris Webster 2003-08-07 23:44:05 postmaster(s) have high load average