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 1u4dpW-005BCt-HW for pgsql-general@arkaria.postgresql.org; Tue, 15 Apr 2025 10:47:50 +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 1u4dpU-007tXe-Qe for pgsql-general@arkaria.postgresql.org; Tue, 15 Apr 2025 10:47:49 +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 1u4dmE-007oaH-19 for pgsql-general@lists.postgresql.org; Tue, 15 Apr 2025 10:44:26 +0000 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u4dmB-000CMm-26 for pgsql-general@lists.postgresql.org; Tue, 15 Apr 2025 10:44:26 +0000 Received: by mail-lj1-x22f.google.com with SMTP id 38308e7fff4ca-30eef9ce7feso54483001fa.0 for ; Tue, 15 Apr 2025 03:44:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744713862; x=1745318662; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=kPhM5Hc2kKho1N2d29Keq8H8fWSu0E/BL8v8xW8Jw54=; b=FXsCKky6KWdL8m/jNVM7Opkznzn0MYczOpnE1BpVo1spkxvzJFH6HbA+4UUgoBEC79 ud3DXT7auVtUhnTGhEHapfJGHunoK3P/9xqKyUfguv6KGQsRPZNK8KI9Y+AHfPfIkgWj 4MEiilhYMxMUWH519tThEsDH0AooU7KaRYi7w0oNk+exvKUcng3kDmF3IMk7VsDbwf2d Y+AhGRWT1QUDdaHQN4a4cUnG3HojJUcVBAucihg+MkgirOkZ5kLUFOnz/ZHsTzSAi26g 7KhqKRxynxaM9b6s6B+nyO1gTmUFyOdu09VSrl708O7ECqb9Owtmnde43+rT0YWVbksK 4kug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744713862; x=1745318662; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=kPhM5Hc2kKho1N2d29Keq8H8fWSu0E/BL8v8xW8Jw54=; b=u43nPIycc1QgB2ASZI7W8cAsoaHyZFMH2Bztf7h9Z+JLv66d6+N8teC/1P+1GyH2F/ jFOlNgXWyLMEEHJQTKTYiiPMF3uysx4blCwVM0YsUuAjKlSO0MNIQcCtU7kABrlFTxqc nctPFIPRDkdKS7a93wnELh/t4KBlKaJjp2lKAxfl9U48/nLxAwO0qzeWQjYSFN8L8HwQ shc6vaQWjMtOr0A9DINs5TGFQyNihgWeOeA5H62Bly49yEHUlrPsF0aLA7bl0hSpDRp2 wScmRILP0axZECjtrHwbGtF1YzbafdJeNMw0saSYHZnwc0IAF20wAkMj7p+WinOsPUn/ 33FQ== X-Gm-Message-State: AOJu0YxaLGqzi6C/PfmG4sM+LSegHsqdUlfGU9+olCSVHXcqjDs79CI4 2xZkpJ9e93HNfbIToF4ieN35bkaWkJIkC/pDGgg5t5qnNxLfwna5YgXFvW5NR7pKsXBpNs0fKSa 6AseOOeWv8lb7hQo1G+f5g2P2Fp7XHb7g X-Gm-Gg: ASbGnct0bxuMth7S8PDLmQBfXXOTEnxE+AbihKMPmJoyiBzH6bWYi6V/G7JX1LQtrk4 pyj1Iya3ktJPfHH6DynijLFlZhNYUtA6GsZi0MdQmbe+M/P3jR6MMFnFT7UAjY3L6g+sd1wTcNc 7cRCueolgbA9K6wGODyXmAiuQlTwNe/T5C9WhB6VwSa8NPngXnuROLrMWBeS2criR7UQ== X-Google-Smtp-Source: AGHT+IFsdUDHyvfiQwmkt/T3bhetVFnrfQg3jhIV5fTWsQYnm4SU2eltP4dlaxdWfqE5zzeWatpNVNtMY7jqP025av4= X-Received: by 2002:a05:651c:1146:b0:309:23ea:5919 with SMTP id 38308e7fff4ca-31049a8005dmr44123191fa.31.1744713861995; Tue, 15 Apr 2025 03:44:21 -0700 (PDT) MIME-Version: 1.0 From: vijay patil Date: Tue, 15 Apr 2025 16:14:03 +0530 X-Gm-Features: ATxdqUEYdxynA2WfbMfA-Dk6hyQTs27F3-ZzQeMq3LykQXcfLcLZJDOqFUkIHbs Message-ID: Subject: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000faa3b30632ced98f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000faa3b30632ced98f Content-Type: text/plain; charset="UTF-8" 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 --000000000000faa3b30632ced98f Content-Type: text/html; charset="UTF-8"

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

--000000000000faa3b30632ced98f--