Re: Database Design: Maintain Audit Trail of Changes

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Database Design: Maintain Audit Trail of Changes
Date: 2013-01-03 16:52:39
Message-ID: alpine.LNX.2.00.1301030851140.5088@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bèrto ëd Sèra 2013-01-03 17:01:40 Re: Database Design: Maintain Audit Trail of Changes
Previous Message Rich Shepard 2013-01-03 16:50:58 Re: Database Design: Maintain Audit Trail of Changes