From: Rob Sargent <robjsargent@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Nathaniel Smith <nate@summersault.com>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Data audit trail techniques in postgresql
Date: Thu, 27 Aug 2009 12:31:23 -0600
Message-ID: <4A96D0FB.5010609@gmail.com> (raw)
In-Reply-To: <20090827173617.GK11213@alvh.no-ip.org>
References: <20090827122831.7a780cdb@gibson.summersault.com>
<20090827173617.GK11213@alvh.no-ip.org>
tablelog doesn't appear any more lively than the OPs audittrail2.
Alvaro Herrera wrote:
> Nathaniel Smith wrote:
>
>
>> 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?
>>
>
> I think tablelog (to be found in pgfoundry too) is the most commonly
> used audit module.
>
>
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: robjsargent@gmail.com, alvherre@commandprompt.com, nate@summersault.com, pgsql-general@postgresql.org
Subject: Re: [SQL] Data audit trail techniques in postgresql
In-Reply-To: <4A96D0FB.5010609@gmail.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