| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "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:53:53 |
| Message-ID: | CANzqJaCTCJHZtiL6Y48Bp7si+MasnrV95+y0jgGxtm4yMH83gA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 16, 2025 at 3:42 PM Nico Williams <nico(at)cryptonector(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2025-04-16 19:59:37 | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
| Previous Message | Nico Williams | 2025-04-16 19:42:54 | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |