On Wed, Apr 16, 2025 at 03:53:53PM -0400, Ron Johnson wrote:
> On Wed, Apr 16, 2025 at 3:42 PM Nico Williams 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
On Wed, Apr 16, 2025 at 3:42 PM Nico Williams 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 Auditor
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 CO
On Wed, Apr 16, 2025 at 3:15 PM Achilleas Mantzios <
a.mantz...@cloud.gatewaynet.com> wrote:
> On 16/4/25 21:43, 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 "w
On 16/4/25 21:43, 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 statement
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.
On Wed, Apr 16, 2025 at 1:35 PM Achill
On 16/4/25 15:36, Ron Johnson wrote:
pgaudit is statement-level, not transaction-level; that's its nature.
This is the same as log_statement.
ok, but log_statement prints ROLLBACKs/COMMITs, but pgaudit not.
On Wed, Apr 16, 2025 at 5:10 AM Achilleas Mantzios - cloud
wrote:
On 4/15/2
pgaudit is statement-level, not transaction-level; that's its nature. This
is the same as log_statement.
On Wed, Apr 16, 2025 at 5:10 AM Achilleas Mantzios - cloud <
a.mantz...@cloud.gatewaynet.com> wrote:
> On 4/15/25 12:14, KENAN ÇİFTÇİ wrote:
>
> Hi,
>
> You can use pgaudit and pgauditlogtofi
On 4/15/25 12:14, KENAN ÇİFTÇİ wrote:
Hi,
You can use pgaudit and pgauditlogtofile extension
(https://github.com/fmbiete/pgauditlogtofile) together to write audit
logs in a separate file.
One issue we have with pgaudit is that it prints AUDIT records even if
the xaction gets rollbacked, how
Hi Kenan,
Thanks for the quick response.
Thanks
Vijay
On Tue, Apr 15, 2025 at 4:44 PM KENAN ÇİFTÇİ wrote:
> Hi,
>
> You can use pgaudit and pgauditlogtofile extension (
> https://github.com/fmbiete/pgauditlogtofile) together to write audit logs
> in a separate file.
>
> yours,
>
> Kenan Çiftçi
Hi All,
We are exploring auditing solutions for our PostgreSQL database and are
considering using pgaudit for this purpose. However, we have a few
questions:
1.
*What is the best tool for auditing PostgreSQL databases?*
-
We are specifically looking for a solution that offers det
Hi,
You can use pgaudit and pgauditlogtofile extension (
https://github.com/fmbiete/pgauditlogtofile) together to write audit logs
in a separate file.
yours,
Kenan Çiftçi
On Tue, Apr 15, 2025 at 1:44 PM vijay patil
wrote:
> Hi All,
>
> We are exploring auditing solutions for our PostgreSQL da
12 matches
Mail list logo
