From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Add pg_audit, an auditing extension |
Date: | 2015-05-14 16:37:39 |
Message-ID: | CAA-aLv4EOZ8TmWQHnzq=AF-ybDm83RqjtGOoQFQ+NLub75t-Rg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 14 May 2015 at 15:36, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Add pg_audit, an auditing extension
>
> This extension provides detailed logging classes, ability to control
> logging at a per-object level, and includes fully-qualified object
> names for logged statements (DML and DDL) in independent fields of the
> log output.
>
> Authors: Ian Barwick, Abhijit Menon-Sen, David Steele
> Reviews by: Robert Haas, Tatsuo Ishii, Sawada Masahiko, Fujii Masao,
> Simon Riggs
>
> Discussion with: Josh Berkus, Jaime Casanova, Peter Eisentraut,
> David Fetter, Yeb Havinga, Alvaro Herrera, Petr Jelinek, Tom Lane,
> MauMau, Bruce Momjian, Jim Nasby, Michael Paquier,
> Fabrízio de Royes Mello, Neil Tiffin
A quick glance shows a parameter called pg_audit.log_statement_once,
which isn't mentioned in the docs. Also, pg_audit.log_level isn't in
the logs, but seems to offer a superset of functionality to
pg_audit.log_notice, which doesn't appear as a valid config parameter.
Is this expected? Are the doc updates supposed to upcoming anyway?
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-14 16:40:48 | Re: pgsql: Add pg_audit, an auditing extension |
Previous Message | Stephen Frost | 2015-05-14 16:35:51 | Re: pgsql: Add pg_audit, an auditing extension |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-14 16:40:48 | Re: pgsql: Add pg_audit, an auditing extension |
Previous Message | Stephen Frost | 2015-05-14 16:35:51 | Re: pgsql: Add pg_audit, an auditing extension |