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 1ruB93-003BdJ-Hk for pgsql-admin@arkaria.postgresql.org; Tue, 09 Apr 2024 13:04:14 +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 1ruB92-004qLv-It for pgsql-admin@arkaria.postgresql.org; Tue, 09 Apr 2024 13:04: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 1ruB92-004qLn-5b for pgsql-admin@lists.postgresql.org; Tue, 09 Apr 2024 13:04:12 +0000 Received: from mail-qv1-xf32.google.com ([2607:f8b0:4864:20::f32]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ruB8z-0001OP-BX for pgsql-admin@lists.postgresql.org; Tue, 09 Apr 2024 13:04:11 +0000 Received: by mail-qv1-xf32.google.com with SMTP id 6a1803df08f44-69b137d09e3so14701656d6.1 for ; Tue, 09 Apr 2024 06:04:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712667847; x=1713272647; 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=iFlJlxe5aRyLo90nTRsqOBHkE3oSOZbYVWQWHLzyvgU=; b=HxmdNSTDZJzX1rvQ7q8qOnNmngQvfDN6bzkQ3pQLLWtfk7UQJYcWU5YhZM6GW/QlBz Sj2XWhWQPKbNrMBYRFx2ZrQjJhOcU3o9ScU8f5BanoOj2Dorkc1KX+Q0kcIqLMCm2nTn XnEJOqr0DfhkWrZQ0Uoy7s0vxrH8+fQb7VhEHXHVYPrRu4i5ae3sjayjXWN773ClnWpN vKyrOJX/wNtec8E2zpfAWAL0Mtf6jRDPCth2dEnlS2bK5WwZ3tmr8ZKrFuQSbAGoNdYs 5meZ8CGHCP+KDCLxAjYOvmDXJdsxT2EKdFfUMtJNp9tqx35xMX1N9kqwaWa3ZPVKdSAf a0TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712667847; x=1713272647; 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=iFlJlxe5aRyLo90nTRsqOBHkE3oSOZbYVWQWHLzyvgU=; b=nKA5Hda4vI4l1YMNDnXLCV/ugmyX1baKLeFhw3d8n11Iy5jPno0Dv7+9u1qsLTrpE+ VIcZgrYGyBwO3/3GS2bYTZAjzyi0urEorKT/xGVMtsTQVoe4+5vyd1HQOWzzDwAjjj1h F0aGj81oq0MlbxouSL2hmkkv0tDuIG+c/UMZFqONEiZW9Dnc0LrW7bbH5vbAJOnITLZR P4t8bmsE2vvK8+ZEgtoNB3xJTL+nZqxDWAaW4RScmM4576Y8rsVfP3sMsFk2A+MygskI P5BOrlhOZy7paw3YSsmDAG5FtBHFaZAiQEN56AxuzmgAovgwKyZoKhJPvJEhasyJpUXM SOsg== X-Gm-Message-State: AOJu0Yw1uI2zIdJrhm8NbFrJaVamrV0gcTvAgm/S8gVZoT6Km/zYfykG 3C1GfqbL084XgyijNxXkggqZzl6pLfOgtDYw/qTlvc45jF6IPu6QSRKrWZGl90SthAD7zZ8DEEL UpjUwAdmHPv0tL2vhFEscqUTbS1e0aDhuc8WQF/0SFu5oG5c8w03RYWpUeLg0gwk3OC1Itcznlq 4= X-Google-Smtp-Source: AGHT+IFrU2sl5E1k+mmzS6yDbFvY/ecud8NjMgLUqDJdc0sYgoXpgCJ4E80O0U4a+lPI82zZEuyAeuxX5zA+d9gVK2d0stBUvgm1nmPX X-Received: by 2002:a05:6214:1c8c:b0:696:a03c:6bb3 with SMTP id ib12-20020a0562141c8c00b00696a03c6bb3mr13032767qvb.39.1712667847256; Tue, 09 Apr 2024 06:04:07 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tejaswi K T Date: Tue, 9 Apr 2024 15:03:56 +0200 Message-ID: Subject: Re: Auditing in Postgres To: Scott Ribe Cc: pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000a772450615a98e6c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a772450615a98e6c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =F0=9F=91=8D Tejaswi K T reacted via Gmail On Tue, Apr 9, 2024 at 2:15=E2=80=AFPM Scott Ribe wrote: > > Do we have similar commands in pgaudit , which captures only failed DML > and not the successful ones. > > Not in pgaudit. Just in the standard PG config, in the logging section, > you can choose if/how errors are logged. Not at the granularity of your > example, but you can log all errors, then in your monitoring filter and > classify them. --000000000000a772450615a98e6c Content-Type: text/vnd.google.email-reaction+json; charset="UTF-8" Content-Transfer-Encoding: quoted-printable { "emoji": "=F0=9F=91=8D", "version": 1 } --000000000000a772450615a98e6c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

=F0=9F=91=8D<= /p>

Tejaswi K T reacted via Gmail

=

= On Tue, Apr 9, 2024 at 2:15=E2=80=AFPM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> Do we have similar commands in pgaud= it , which captures only failed DML and not the successful ones.

Not in pgaudit. Just in the standard PG config, in the logging section, you= can choose if/how errors are logged. Not at the granularity of your exampl= e, but you can log all errors, then in your monitoring filter and classify = them.
--000000000000a772450615a98e6c--