| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Nathaniel Smith <nate(at)summersault(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [SQL] Data audit trail techniques in postgresql |
| Date: | 2009-08-27 18:31:23 |
| Message-ID: | 4A96D0FB.5010609@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
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.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2009-08-27 18:36:45 | Re: Select data for current week only |
| Previous Message | BlackMage | 2009-08-27 18:09:36 | Select data for current week only |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-08-27 19:32:15 | Re: [SQL] Data audit trail techniques in postgresql |
| Previous Message | Alvaro Herrera | 2009-08-27 17:36:17 | Re: Data audit trail techniques in postgresql |