| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add pg_audit, an auditing extension |
| Date: | 2015-05-14 16:45:20 |
| Message-ID: | 20150514164520.GE30322@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Thom,
* Thom Brown (thom(at)linux(dot)com) wrote:
> On 14 May 2015 at 15:36, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Add pg_audit, an auditing extension
>
> 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?
Actually, I see them both in pgaudit.sgml in master..?
Is there somewhere else they're missing from?
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-05-14 16:59:28 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
| Previous Message | Stephen Frost | 2015-05-14 16:43:30 | Re: pgsql: Add pg_audit, an auditing extension |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-05-14 16:53:01 | Changes to backup.sgml |
| Previous Message | Andrew Dunstan | 2015-05-14 16:43:48 | Re: trust authentication behavior |