Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
| От | Ron Johnson |
|---|---|
| Тема | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
| Дата | |
| Msg-id | CANzqJaCTCJHZtiL6Y48Bp7si+MasnrV95+y0jgGxtm4yMH83gA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately (Nico Williams <nico@cryptonector.com>) |
| Ответы |
Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
|
| Список | 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!
В списке pgsql-general по дате отправления: