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 1u4eFB-005I4A-Ur for pgsql-general@arkaria.postgresql.org; Tue, 15 Apr 2025 11:14:22 +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 1u4eF9-008JJ5-3e for pgsql-general@arkaria.postgresql.org; Tue, 15 Apr 2025 11:14:19 +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 1u4eF8-008JIx-Nz for pgsql-general@lists.postgresql.org; Tue, 15 Apr 2025 11:14:19 +0000 Received: from mail-pj1-x102e.google.com ([2607:f8b0:4864:20::102e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u4eF5-000Ca7-2J for pgsql-general@lists.postgresql.org; Tue, 15 Apr 2025 11:14:18 +0000 Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-30828fc17adso3511034a91.1 for ; Tue, 15 Apr 2025 04:14:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744715654; x=1745320454; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=g8bBVTaZL3KN8fbokqvRUlxGHQHQ1tIOiQqCvs1+kH4=; b=DFj1T4LrXsNDhwRfFuEGwc27U70xFG6yIo/PGm18oBU9FarDeO+lk6rC27qf06P/9C HvAvskgr4n93LS+D7JqWQMRvPLGBRkM78LiG5ruQYcEKi4oZ097V2ZluWu+wBZM0CDVY odOI4dK8gvBEqRrgDW7eYQ7JQUlP9clIZnM5vGAPWE9a1fexXf2ghJ6cIjKoW+aIAADY +Jj0wxhXlaEiPjfxPYxGP2aAP9fnedJDmbR0a1Ct7WAQKsGuWzUH/s0zdysXCTyQoJYZ 1upxqJPmvQ6tWQUQGl/rZqH9Mnrbmy6+fON3C9IsxzhuryVPkjUwT8qd71p1ElAJFAUK 9cQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744715654; x=1745320454; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=g8bBVTaZL3KN8fbokqvRUlxGHQHQ1tIOiQqCvs1+kH4=; b=l5XCVIcZzfFtpZA6otKpXPEbCORve3dVrH5cUxSbeAx0CF5iSLmDqfZ+UbZ0tvoUGa EsRRIbl71tuWTKnJVFjjM1iu0R+0DnFyAdOuMIFindlJLb4Mn1KFyNdccfZoAkb/CIL9 8qUr2btjpli4RCQ7zpkTr12Fh/tJbdlBY59zkb4rxpJKOHCuXJO1mGmMNLvodsAwapJe D94hzasE8JWWUWak1gXWVLK6X708H8AK9+nKCiQfxVBp6QeFXjZ8HlpxFRPWXxdsU6JA LOhkYn9yXw8lAZF3BpD7cnFjmE7KljNxOUKSXpUgs+BBsmf86j4ieZvuervnBwbH4792 xRXw== X-Gm-Message-State: AOJu0Yy20J3Vh/hUUIdUniZAUr9oD9x83oGLwvMnvhO6vPed43MSaWMp u16h0Cmhe17qD58J1xgy80Rqo8fnNxp1lCyLNU24ulJFXdi/wsejh9ahfaAFsaww0aa73JQ5PPZ 1InyH40OAf3j2ieBTGEg6T+qNLi0= X-Gm-Gg: ASbGnct0DikqX4W8w2zqlTUfCoQO+cKzxfHkP7hqbLQEaTPoVEL56Yghgped0wC5F2Y C1mFxaUf2QYALB1LhO3lWFwnb7YZ/fjnfO+OZEoDBXE+pTrkEIaw3G0bPm2AYfc3wNhkzbeqCHa xJ2AbwjTn6fL29/1Y1u2YMuA== X-Google-Smtp-Source: AGHT+IFFdq0rXZbXzp8QJd9nxdzcTJhNcaiJWDv+CoqGuaNIwowOO2DGk/GN22Cp0PpHU+JKlFumKIHg7V1EOdEEi/w= X-Received: by 2002:a17:90b:5211:b0:2ff:5714:6a with SMTP id 98e67ed59e1d1-30823643fd3mr23148879a91.19.1744715654232; Tue, 15 Apr 2025 04:14:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?S0VOQU4gw4fEsEZUw4fEsA==?= Date: Tue, 15 Apr 2025 14:14:03 +0300 X-Gm-Features: ATxdqUFYQ6mX9knkdi47S6OYUuvwOH0hVWwDbwvst_MxixuLqo_oN18hGfyLsyw Message-ID: Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately To: vijay patil Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ce03990632cf44e4" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ce03990632cf44e4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, You can use pgaudit and pgauditlogtofile extension ( https://github.com/fmbiete/pgauditlogtofile) together to write audit logs in a separate file. yours, Kenan =C3=87ift=C3=A7i On Tue, Apr 15, 2025 at 1:44=E2=80=AFPM 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 > --000000000000ce03990632cf44e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

You can use pgaudit and pgauditlogt= ofile extension (ht= tps://github.com/fmbiete/pgauditlogtofile) together=C2=A0to write audit= logs in a separate=C2=A0file.=C2=A0

yours,
<= div>
Kenan =C3=87ift=C3=A7i

On Tue= , Apr 15, 2025 at 1:44=E2=80=AFPM vijay patil <vijay.postgres@gmail.com> wrote:

Hi All,

We are exploring auditing solutions for our PostgreSQL d= atabase and are considering using pgaudit for this purpose. Ho= wever, 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 lo= gs if we decide to use pgaudit?

    • We would prefer to keep the audit logs in a separate file or location fo= r easier management and analysis.


We appreciate any help or suggestions!


Thanks

Vij= ay

--000000000000ce03990632cf44e4--