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:59:37
Message-ID: aAAMKfepHe5lZWtC@ubby
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 16, 2025 at 03:53:53PM -0400, Ron Johnson wrote:
> On Wed, Apr 16, 2025 at 3:42 PM Nico Williams <nico(at)cryptonector(dot)com> wrote:
> > 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?

Yes, or use Debezium or the like which... do just that.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-04-16 20:04:10 Re: Fwd: Identify system databases
Previous Message Ron Johnson 2025-04-16 19:53:53 Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately