public inbox for [email protected]
help / color / mirror / Atom feedFrom: Achilleas Mantzios - cloud <[email protected]>
To: [email protected]
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Date: Wed, 16 Apr 2025 10:10:22 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHsK0FqMEoZ_EL6bdHL=MO6irp3uXa5iC_T9jKuCgwRcOQ=Feg@mail.gmail.com>
References: <CAD5k+7zxAmkoOeVq61gqg1xWu8egSjcRtAT=rrAF=ihxUjdTMQ@mail.gmail.com>
<CAHsK0FqMEoZ_EL6bdHL=MO6irp3uXa5iC_T9jKuCgwRcOQ=Feg@mail.gmail.com>
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 do you alleviate that ?
>
> yours,
>
> Kenan Çiftçi
>
> On Tue, Apr 15, 2025 at 1:44 PM vijay patil <[email protected]>
> wrote:
>
> 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
> detailed auditing capabilities and is compatible with our
> setup.
>
> 2.
>
> *Can we store the audit information separately from PostgreSQL
> logs if we decide to use |pgaudit|?*
>
> *
>
> We would prefer to keep the audit logs in a separate file
> or location for easier management and analysis.
>
>
> We appreciate any help or suggestions!
>
>
> Thanks
>
> Vijay
>
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox