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 17:03:43 |
Message-ID: | CAA-aLv5BiEG_YS6itCfCGTQXOS7H4E-4T5MKNRYjGRDYtiqs_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 14 May 2015 at 17:45, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> 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?
Ah, my apologies. I can see from the file date that pgaudit.html is
dated 2 weeks ago, so I'm looking at an old copy. Not sure what
happened there as all other files were newer. In any case, I've
rebuilt and see neither of those issues I reported exist anymore.
Sorry for the noise.
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-14 17:04:59 | Re: pgsql: Add pg_audit, an auditing extension |
Previous Message | Andrew Dunstan | 2015-05-14 16:59:28 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-14 17:04:59 | Re: pgsql: Add pg_audit, an auditing extension |
Previous Message | Andrew Dunstan | 2015-05-14 16:59:28 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |