Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Date: 2025-04-16 19:42:54
Message-ID: aAAIPiQ7kwW3sU1M@ubby
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 16, 2025 at 02:43:59PM -0400, Ron Johnson wrote:
> You'll have to bring that up with the PgAudit maintainer. Note, though,
> that the purpose of PgAudit is not "recreate the database from audit logs";
> it's "what Auditors care about". In my experience, auditors do not care
> about COMMIT and ROLLBACK statements.

I would care about what happened. To know what happened I'd have to see
either only audit logs for committed transactions, or also see the
COMMIT and ROLLBACK statements.

Nico
--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-04-16 19:53:53 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Previous Message Ron Johnson 2025-04-16 19:34:15 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately