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 1oCj37-0007EX-As for pgsql-committers@arkaria.postgresql.org; Sat, 16 Jul 2022 14:45:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oCj35-0001DL-8e for pgsql-committers@arkaria.postgresql.org; Sat, 16 Jul 2022 14:45:39 +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 1oCj35-0001Cp-1k for pgsql-committers@lists.postgresql.org; Sat, 16 Jul 2022 14:45:39 +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 1oCj2y-0004Sh-2L for pgsql-committers@lists.postgresql.org; Sat, 16 Jul 2022 14:45:38 +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 26GEjTfd3830067; Sat, 16 Jul 2022 10:45:29 -0400 From: Tom Lane To: Justin Pryzby cc: Peter Eisentraut , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Log details for client certificate failures In-reply-to: <3820525.1657979832@sss.pgh.pa.us> References: <20220716113752.GU18011@telsasoft.com> <48b78358-70d8-8de5-02ea-669c4051e4ba@enterprisedb.com> <20220716121723.GW18011@telsasoft.com> <3820525.1657979832@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sat, 16 Jul 2022 09:57:12 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3830065.1657982729.1@sss.pgh.pa.us> Date: Sat, 16 Jul 2022 10:45:29 -0400 Message-ID: <3830066.1657982729@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Justin Pryzby writes: >> It failed for me just now: https://cirrus-ci.com/task/6502388730167296 Looking at the cfbot, an annoyingly large percentage of current runs are being broken by this. I think we need to do this as a stopgap: > (2) abandon attempting to test this particular behavior. If somebody wants to think up a better answer later, great, but the current situation is completely not tolerable. regards, tom lane