Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81nU-0002MR-AH for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 15:13:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n81nT-0006B4-5u for pgsql-committers@arkaria.postgresql.org; Thu, 13 Jan 2022 15:13:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81nS-0006AU-Uq for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 15:13:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81nQ-0004kT-EM for pgsql-committers@lists.postgresql.org; Thu, 13 Jan 2022 15:13:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 20DFDkR83151376; Thu, 13 Jan 2022 10:13:46 -0500 From: Tom Lane To: Simon Riggs cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Include permissive/enforcing state in sepgsql log messages. In-reply-to: References: Comments: In-reply-to Simon Riggs message dated "Thu, 13 Jan 2022 13:03:15 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3151374.1642086826.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Jan 2022 10:13:46 -0500 Message-ID: <3151375.1642086826@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Simon Riggs writes: > Is that a bug fix to be backpatched, or a new/changed feature to be docu= mented? It'd be the latter, if sepgsql had any documentation about the content of its log messages. But AFAICS it doesn't (and I'm not volunteering to add that). regards, tom lane