Re: [SQL] parsing audit table

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: "M(dot) D(dot)" <lists(at)turnkey(dot)bz>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [SQL] parsing audit table
Date: 2011-08-16 23:35:42
Message-ID: CAJKUy5hF-xcxaukOfNV7MT9AcuDdDXt2LFQ9LqmFYgYHbfhk9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-sql

On Tue, Aug 16, 2011 at 4:02 PM, M. D. <lists(at)turnkey(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message c k 2011-08-17 05:02:11 Re: Using Postgresql as application server
Previous Message Chris Travers 2011-08-16 23:14:14 Re: Using Postgresql as application server

Browse pgsql-sql by date

  From Date Subject
Next Message Igor Neyman 2011-08-17 20:26:59 Re: which is better: using OR clauses or UNION?
Previous Message M. D. 2011-08-16 21:48:43 Re: parsing audit table