From: Nathaniel Smith <nate@summersault.com>
To: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Data audit trail techniques in postgresql
Date: Thu, 27 Aug 2009 12:28:31 -0400
Message-ID: <20090827122831.7a780cdb@gibson.summersault.com> (raw)
Howdy,
(cross-posted to the pg.sql and pg.general lists)
I'm looking to set up an audit trail system--ie, logging every
INSERT/UPDATE/DELETE on a given table and tracking how the data
changes over time. I know I could do it by hand using triggers, but was
hoping to save a little time using something prepackaged.
I installed and tested the two-year untouched
http://pgfoundry.org/projects/audittrail2/ --the only auditing tool on
pgFoundry with a release--and found that, while it works well, it's
still marked as beta and has an obvious bug in it when used in 8.3.7.
What do others use to accomplish this? Do most pg users just write
triggers by hand? Or is there some nice auditing module that Google
just isn't revealing to me?
Thanks.
Nathaniel Smith
Web Application Developer
Summersault, LLC.
710 E. Main St., Suite 200
Richmond, IN 47374
www.summersault.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: nate@summersault.com, pgsql-general@postgresql.org
Subject: Re: Data audit trail techniques in postgresql
In-Reply-To: <20090827122831.7a780cdb@gibson.summersault.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox