Re: Database Design: Maintain Audit Trail of Changes - Mailing list pgsql-general

From Rich Shepard
Subject Re: Database Design: Maintain Audit Trail of Changes
Date
Msg-id alpine.LNX.2.00.1301030851140.5088@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Database Design: Maintain Audit Trail of Changes  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: Database Design: Maintain Audit Trail of Changes  (Bèrto ëd Sèra <berto.d.sera@gmail.com>)
List pgsql-general
On Thu, 3 Jan 2013, Adrian Klaver wrote:

> As a matter of course I include fields to record the timestamp and user for
> insert of records and last update of record on my tables.

Adrian,

   This is a useful addition to the application.

> For a relatively simple solution see this blog post I put up this summer:
> http://aklaver.org/wordpress/2012/06/23/postgres-and-hstore/
> I have since expanded that to include updates by using TG_OP to determine the
> operation being done on the table.
>
> There is also pg_audit
> :
> https://github.com/jcasanov/pg_audit

   Once again you came through with valuable advice and guidance.

Many thanks!

Rich



pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Database Design: Maintain Audit Trail of Changes
Next
From: Bèrto ëd Sèra
Date:
Subject: Re: Database Design: Maintain Audit Trail of Changes