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 1u58pr-00CtEg-W5 for pgsql-general@arkaria.postgresql.org; Wed, 16 Apr 2025 19:54:16 +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 1u58po-004OtB-2x for pgsql-general@arkaria.postgresql.org; Wed, 16 Apr 2025 19:54:12 +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 1u58pn-004OqL-NI for pgsql-general@lists.postgresql.org; Wed, 16 Apr 2025 19:54:12 +0000 Received: from mail-oi1-x233.google.com ([2607:f8b0:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u58pi-000RnP-10 for pgsql-general@lists.postgresql.org; Wed, 16 Apr 2025 19:54:12 +0000 Received: by mail-oi1-x233.google.com with SMTP id 5614622812f47-3feaedb531dso1618032b6e.3 for ; Wed, 16 Apr 2025 12:54:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744833245; x=1745438045; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=mzwLqW9rMa8ZP1MF8YL7gKQAWQuZb9dqkW80X8umpK4=; b=Ab7NITq5bvrinAjVW/Ac4GTrZNx0hH2edqA8rMsukqEW81OZtWWpjUOYLzXqMulRwd NysqIrZL2iKiwUsaiUzu/Ckml5AG3bhKqWJdvmZySUrgP5ykPJ3Ln9Mrs9u4XS9o2eQM KTEj1WS23PxJY9W2X4MyaWqYaYj/3XgQ+7eCvqidS99f3uR671w5tHptUxK4D3wGymWk 00op3oSD1G6nP2N1PutqsXidVmZJGfDYZjc+AY4KMaIQKToEhgFsmM1rjmtS3z2kEKsf bUnQN/JlH6s47USlx0G3Xe2ZfuMwAGmAr5FNSI0z7oESyZydafFpXdF87MlMtxPjACIT +1gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744833245; x=1745438045; h=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=mzwLqW9rMa8ZP1MF8YL7gKQAWQuZb9dqkW80X8umpK4=; b=T30Dlht2YW/1b4iROo9xCzSdn9zJ3weVKWF5+lf9vBcbbtHBWCQz+KZRy6IuKrBN0X WPfs3MHRWEmEq7lwXjmkx6fK+j+Oj7AoBQgxL+s7/heIXK2UUMod2HZEFcd+YTKSgipv BOJjuxm+2VuGhwKaK4xYUCvJzXmYzy73F1078LZblCF2u5/JFP57IFwHxIOwexJrh2zf 2MRII4MOb1I4O+ohj/D6rdtOilDGqZChKgrGCJ2eJCnDJF8TkVS4EF8u6iJNe7pEOCtH UcRAkiir9XtSBiQq7mIUm/N9HYAQPdqSwdy77aLSq+MtG2AthyBbLXRt9JO9snikCMKf YgJQ== X-Gm-Message-State: AOJu0YxT/09tZYKi8bz+6xZQIbpbr7krYy/fpvkzsgd6GW1L1rjTV5nW by/ET3slXcnaqlCZGCZ8Xb3VC7eoTkAglvRvRxsoNg+BVnpUvj0dVMsnVSqGytKXauDGVs7BEBO G8ZfSM5sflA6Nmy2pBMFyBeMovpE6CQZF X-Gm-Gg: ASbGncvmwglYf0+1EFZ1VQhAsR3+cfQQn8s0Dx0U/R8aN5gYDKKejGT/zoXM0rTEoFb DqkaBWR9OdFwZrPCgX9l3kxQAvAozkikhqf56k0nLoZi+lpKmnpnYMxeNALEQNeit8iuz611mM3 lpIhbyzi9Sy2tZ3/CYLVl+x4Q= X-Google-Smtp-Source: AGHT+IF3Vp8+5v6ecTv5hwuzHJ2YK88DwXF6s5ObLHhAZEjv+owYSaDzACkglAoumVhrY1sV6Ya8TBPSbiTL6/25eV4= X-Received: by 2002:a05:6808:17a4:b0:3f8:9781:3cc9 with SMTP id 5614622812f47-400b01ecdbamr2128540b6e.21.1744833245129; Wed, 16 Apr 2025 12:54:05 -0700 (PDT) MIME-Version: 1.0 References: <54b3d612-363e-4c05-8a08-a7563c7d52f1@cloud.gatewaynet.com> In-Reply-To: From: Ron Johnson Date: Wed, 16 Apr 2025 15:53:53 -0400 X-Gm-Features: ATxdqUFhOm5ITS9evv6wCjiEwPV5sMxlB3rzPD5X2Ark3FYn9A9pNogkVF3eX5o Message-ID: Subject: Re: Best Tool for PostgreSQL Auditing and Storing Audit Logs Separately To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000c4b6f60632eaa51c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c4b6f60632eaa51c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Apr 16, 2025 at 3:42=E2=80=AFPM Nico Williams wrote: > On Wed, Apr 16, 2025 at 02:43:59PM -0400, Ron Johnson wrote: > > You'll have to bring that up with the PgAudit maintainer. Note, though= , > > that the purpose of PgAudit is not "recreate the database from audit > logs"; > > it's "what Auditors care about". In my experience, auditors do not car= e > > about COMMIT and ROLLBACK statements. > > I would care about what happened. To know what happened I'd have to see > either only audit logs for committed transactions, or also see the > COMMIT and ROLLBACK statements. > Decode the logical replication stream? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000c4b6f60632eaa51c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Apr 16, 2025 at 3:42=E2=80=AFPM N= ico Williams <nico@cryptonector= .com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Apr 16, 2025 at 02= :43:59PM -0400, Ron Johnson wrote:
> You'll have to bring that up with the PgAudit maintainer.=C2=A0 No= te, though,
> that the purpose of PgAudit is not "recreate the database from au= dit logs";
> it's "what Auditors care about".=C2=A0 In my experience,= auditors do not care
> about COMMIT and ROLLBACK statements.

I would care about what happened.=C2=A0 To know what happened I'd have = to see
either only audit logs for committed transactions, or also see the
COMMIT and ROLLBACK statements.

Decode = the logical replication stream?

--
Death to <Redacted>, and butter sauce.
Don&#= 39;t boil me, I'm still alive.
<Redacted> lobster!
--000000000000c4b6f60632eaa51c--