From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, MauMau <maumau307(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Ian Barwick <ian(at)2ndquadrant(dot)com>, Jim Mlodgenski <jimmy76(at)gmail(dot)com> |
Subject: | Re: pgaudit - an auditing extension for PostgreSQL |
Date: | 2015-01-27 23:54:29 |
Message-ID: | 54C82535.40606@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1/27/15 5:06 PM, Robert Haas wrote:
> On Tue, Jan 27, 2015 at 5:55 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> BTW, I know that at least earlier versions of EnterpriseDB's version of
>> Postgres (circa 2007) had an auditing feature. I never dealt with any
>> customers who were using it when I was there, but perhaps some other folks
>> could shed some light on what customers wanted to see an an auditing
>> feature... (I'm looking at you, Jimbo!)
>
> It's still there, but it's nothing like pgaudit. What I hear is that
> our customers are looking for something that has the capabilities of
> DBMS_FGA. I haven't researched either that or pgaudit enough to know
> how similar they are.
Do they really need the full capabilities of DBMS_FGA? At first glance, it looks even more sophisticated than anything that's been discussed so far. To wit (from http://docs.oracle.com/cd/B19306_01/appdev.102/b14258/d_fga.htm#CDEIECAG)
DBMS_FGA.ADD_POLICY(
object_schema VARCHAR2,
object_name VARCHAR2,
policy_name VARCHAR2,
audit_condition VARCHAR2,
audit_column VARCHAR2,
handler_schema VARCHAR2,
handler_module VARCHAR2,
enable BOOLEAN,
statement_types VARCHAR2,
audit_trail BINARY_INTEGER IN DEFAULT,
audit_column_opts BINARY_INTEGER IN DEFAULT);
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-01-27 23:58:14 | Re: Shortcoming in CLOBBER_FREED_MEMORY coverage: disk buffer pointers |
Previous Message | Jim Nasby | 2015-01-27 23:52:17 | Re: Parallel Seq Scan |