Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately

From: Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately
Date: 2025-04-16 09:10:22
Message-ID: 54b3d612-363e-4c05-8a08-a7563c7d52f1@cloud.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 <vijay(dot)postgres(at)gmail(dot)com>
> 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
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Anton Shepelev 2025-04-16 09:27:49 Cannot turn track_counts on
Previous Message Dominique Devienne 2025-04-16 08:09:11 Re: Fwd: Identify system databases