From: | KENAN ÇİFTÇİ <kciftci89(at)gmail(dot)com> |
---|---|
To: | vijay patil <vijay(dot)postgres(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |
Date: | 2025-04-15 11:14:03 |
Message-ID: | CAHsK0FqMEoZ_EL6bdHL=MO6irp3uXa5iC_T9jKuCgwRcOQ=Feg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2025-04-15 11:20:45 | Re: Help with PhD Dissertation |
Previous Message | vijay patil | 2025-04-15 10:44:03 | Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately |