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 1s6XPc-000ByU-VI for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 15:16:26 +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 1s6XPd-001R1H-3c for pgsql-general@arkaria.postgresql.org; Mon, 13 May 2024 15:16:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6XOL-001L1D-4I for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 15:15:05 +0000 Received: from mail-oo1-xc33.google.com ([2607:f8b0:4864:20::c33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s6XOH-000110-6Y for pgsql-general@lists.postgresql.org; Mon, 13 May 2024 15:15:02 +0000 Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-5aa1bf6cb40so3275485eaf.1 for ; Mon, 13 May 2024 08:15:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715613300; x=1716218100; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=LjBuXnFKBFGYr6FJXI8HaHuHJjirz7V1vnCWmbIOVis=; b=nmv3/aJG9JBps5eepibWSWBuTEfakJZqxBhp+aFlupzLFFiGpzyWvhLGL3Kziy49ic JNpXi2MpZnZYT2FOtawQO2QUHvxB+VKp1ZxpSAaJneMIDU+fw9NBn9a0hjR7ln7XJr7g zMNvhcOgxdRDlrNMOSVK7pHkHgGw9fX8dXPun9KZvqsLKEP7IlbNV2ujMN8riYzB0FXS yBl6ryA4FFWFrTjw6l2m2t4yF62iY06588HBofgWNa3d2g46qQvWxVV/AP7A0yTuJ66z M3aSwQyeOsPQA/+FQHzMRBkHqTix9sRXhrotBus3J78xyNhpzqvWX1D4MTFZQ5uIAuXL NiWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715613300; x=1716218100; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=LjBuXnFKBFGYr6FJXI8HaHuHJjirz7V1vnCWmbIOVis=; b=Td3blUdZLCnh7uno0nFr27E0YEjhxHWRo4whvlrsfYz0p9Iz5vpxwaOKb6yVywp3sh BTCmafMQ2RCuecl3FWqG28Ny6EkNk3RoioRwCV4xU3bip5FHzEwVi3avvIm8OWSrL4t+ TX6ze5PwUPj3bih1flKS2mUxIVaUcTfEEzZS14w9Z+u4SCDIVK1ytCVS2EkmlnQoBjgU rzMQqWEuWkQdmKt4QGacBgrdj7NaYIXkEOrTES14Gw7HdBtNXPJqAZz8uCgm6u9yyuUM Bn+hlr/RokaTuPeP9qyUFYq78vcFIVVP5+QjK5cO+IUOw4XlOcCrL5icMBlCIrxf8jB8 P9Iw== X-Forwarded-Encrypted: i=1; AJvYcCW+qwn8H7v77nMVg00eCcTswMWToV48I/addUvWZbv+H267LGjm3rMWNd96aLQ+qg8jJluVK33idcitrnlP6H+7sXvKsJ+W4eHJpgVPMr/ekIk7 X-Gm-Message-State: AOJu0YxAjKGXM7/JcK3JTuTNPFKtqYLyTkLNoCsC2oZBSKXiR2U/rxUX UVZgbklG1ejnYMXk2U/Sy4PFX/ARnna1bVxXqzNh9QmRRBF4O1mqxNu/lOrOmBT7bkglBG/h1lO PWB3iJsaGD0vMMPdK0phfBabYY7g= X-Google-Smtp-Source: AGHT+IF2kaVrTrKfYO6/d/LlNKoG2qUAlyfpMbKOyndifJ15kZWhweHzIG7IYIjg59OiLN5iaKL2qx87W2F/w7laSCw= X-Received: by 2002:a4a:5141:0:b0:5b2:3782:7844 with SMTP id 006d021491bc7-5b28196150fmr10072274eaf.5.1715613300645; Mon, 13 May 2024 08:15:00 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:c4e:0:b0:52b:9175:545a with HTTP; Mon, 13 May 2024 08:14:59 -0700 (PDT) In-Reply-To: References: <740639.1715610369@sss.pgh.pa.us> From: "David G. Johnston" Date: Mon, 13 May 2024 08:14:59 -0700 Message-ID: Subject: Re: how to completely turn off statement error logging To: "Zwettler Markus (OIZ)" Cc: Tom Lane , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000005b674306185759ed" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005b674306185759ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, May 13, 2024, Zwettler Markus (OIZ) wrote: > > > but I do not want to suppress errors that are related to infrastructure > problems, i.e. "could not open file..." > > The server doesn=E2=80=99t classify the errors it emits into scope, =E2=80= =9Capplication errors=E2=80=9D and =E2=80=9Dinfrastructure errors=E2=80=9D, or otherwise. = The only classification is severity. It does include an SQL Error Code that you could, in post-processing, act on. David J. --0000000000005b674306185759ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, May 13, 2024, Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch> wrote:

but I do not want to suppress errors that are related to infrastructure pro= blems, i.e. "could not open file..."


The server doesn=E2=80=99t classify the er= rors it emits into scope, =E2=80=9Capplication errors=E2=80=9D and =E2=80= =9Dinfrastructure errors=E2=80=9D, or otherwise.=C2=A0 The only classificat= ion is severity.

It does include an SQL Error Code= that you could, in post-processing, act on.

David= J.

--0000000000005b674306185759ed--