Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately - Mailing list pgsql-general

From Nico Williams
Subject Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Date
Msg-id aAAIPiQ7kwW3sU1M@ubby
Whole thread Raw
In response to Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
List 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
-- 



pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Next
From: Ron Johnson
Date:
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately