From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Ian Barwick <ian(at)2ndquadrant(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgaudit - an auditing extension for PostgreSQL |
Date: | 2014-06-23 10:15:39 |
Message-ID: | CAHGQGwF8Y+ckO_uLnFhE4jasx0dHNyHFZ6jR21PEt9YQr2CK6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 2, 2014 at 3:19 PM, Ian Barwick <ian(at)2ndquadrant(dot)com> wrote:
> Hi
>
> Here is an initial version of an auditing extension for Postgres to
> generate log output suitable for compiling a comprehensive audit trail
> of database operations.
You added this into CF, but its patch has not been posted yet. Are you planning
to make a patch?
> Planned future improvements include:
>
> 1. Additional logging facilities, including to a separate audit
> log file and to syslog, and potentially logging to a table
> (possibly via a bgworker process). Currently output is simply
> emitted to the server log via ereport().
>
> 2. To implement per-object auditing configuration, it would be nice to use
> extensible reloptions (or an equivalent mechanism)
Is it possible to implement these outside PostgreSQL by using hooks?
If not, it might be better to implement audit feature in core from the
beginning.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-06-23 10:48:07 | Re: idle_in_transaction_timeout |
Previous Message | Andres Freund | 2014-06-23 10:15:01 | Use a signal to trigger a memory context dump? |