Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u4ynq-00ALWu-Ek for pgsql-general@arkaria.postgresql.org; Wed, 16 Apr 2025 09:11:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u4ymo-00AHrw-Sg for pgsql-general@arkaria.postgresql.org; Wed, 16 Apr 2025 09:10:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u4ymo-00AHro-HH for pgsql-general@lists.postgresql.org; Wed, 16 Apr 2025 09:10:27 +0000 Received: from cloud.gatewaynet.com ([185.90.37.94]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u4yml-000Mm6-2F for pgsql-general@lists.postgresql.org; Wed, 16 Apr 2025 09:10:26 +0000 Content-Type: multipart/alternative; boundary="------------JWGrlAvPNfqJ6Ij2blGJHS4y" Message-ID: <54b3d612-363e-4c05-8a08-a7563c7d52f1@cloud.gatewaynet.com> Date: Wed, 16 Apr 2025 10:10:22 +0100 MIME-Version: 1.0 Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately To: pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Achilleas Mantzios - cloud In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------JWGrlAvPNfqJ6Ij2blGJHS4y Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 > --------------JWGrlAvPNfqJ6Ij2blGJHS4y Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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.postgres@gmail.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

--------------JWGrlAvPNfqJ6Ij2blGJHS4y--