Re: parsing audit table - Mailing list pgsql-sql

From Jaime Casanova
Subject Re: parsing audit table
Date
Msg-id CAJKUy5hF-xcxaukOfNV7MT9AcuDdDXt2LFQ9LqmFYgYHbfhk9Q@mail.gmail.com
Whole thread Raw
In response to parsing audit table  ("M. D." <lists@turnkey.bz>)
Responses Re: [ADMIN] parsing audit table  (Jan Eskilsson <janeskil1525@gmail.com>)
List pgsql-sql
On Tue, Aug 16, 2011 at 4:02 PM, M. D. <lists@turnkey.bz> wrote:
> Hi everyone,
>
> I'm a bit lazy, or actually in a bit of a crunch.  I added an audit
> recording a few months ago, but never really used it much, but today I'm
> seeing a bunch of suspicious activity by one user.  Does someone have any
> function to quickly parse this data?
>

that's not exactly auditable information :D

i made this one for that: https://github.com/jcasanov/pg_audit

it has two versions one using hstore in which you will see in old
"column=>old_data" and in new "column=>new_data" seems better and i
guess you can use hstore functions on it
(http://www.postgresql.org/docs/9.0/static/hstore.html)

The other one uses arrays to store column names, old values, new
values, still more parseable

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación

pgsql-sql by date:

Previous
From: "M. D."
Date:
Subject: parsing audit table
Next
From: "Igor Neyman"
Date:
Subject: Re: which is better: using OR clauses or UNION?