Re: pgsql: Add pg_audit, an auditing extension
От | Thom Brown |
---|---|
Тема | Re: pgsql: Add pg_audit, an auditing extension |
Дата | |
Msg-id | CAA-aLv4EOZ8TmWQHnzq=AF-ybDm83RqjtGOoQFQ+NLub75t-Rg@mail.gmail.com обсуждение исходный текст |
Ответ на | pgsql: Add pg_audit, an auditing extension (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: pgsql: Add pg_audit, an auditing extension
Re: pgsql: Add pg_audit, an auditing extension |
Список | pgsql-committers |
On 14 May 2015 at 15:36, Stephen Frost <sfrost@snowman.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
В списке pgsql-committers по дате отправления: