Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Ron <ronljohnsonjr@gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2025-04-16T19:53:53Z
Lists: pgsql-general
On Wed, Apr 16, 2025 at 3:42 PM Nico Williams <nico@cryptonector.com> wrote: > 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. > Decode the logical replication stream? -- Death to <Redacted>, and butter sauce. Don't boil me, I'm still alive. <Redacted> lobster!