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.96) (envelope-from ) id 1wKd2H-001CGm-2j for pgsql-hackers@arkaria.postgresql.org; Wed, 06 May 2026 14:15:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wKd2G-00HML5-1p for pgsql-hackers@arkaria.postgresql.org; Wed, 06 May 2026 14:15:36 +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.96) (envelope-from ) id 1wKd2G-00HMKx-0u for pgsql-hackers@lists.postgresql.org; Wed, 06 May 2026 14:15:36 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wKd2E-00000000pne-0wN3 for pgsql-hackers@lists.postgresql.org; Wed, 06 May 2026 14:15:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 646EFWnf768824; Wed, 6 May 2026 10:15:32 -0400 From: Tom Lane To: Tomas Vondra cc: PostgreSQL Hackers Subject: Re: occasional ECPG failures on dikkop (FreeBSD) In-reply-to: <9fc5913c-d47c-4e00-88ee-6ceb2e7fcf4b@vondra.me> References: <07a279bd-dcd4-4e6a-a5bb-2bc184f6017d@vondra.me> <767885.1778076033@sss.pgh.pa.us> <9fc5913c-d47c-4e00-88ee-6ceb2e7fcf4b@vondra.me> Comments: In-reply-to Tomas Vondra message dated "Wed, 06 May 2026 16:11:25 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <768822.1778076932.1@sss.pgh.pa.us> Date: Wed, 06 May 2026 10:15:32 -0400 Message-ID: <768823.1778076932@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tomas Vondra writes: > Ah, I haven't noticed the last couple messagess, mentioning dikkop. Not > sure if it's the same issue - I guess we'll have to wait if the failures > go away once it gets fixed. > Still, it seems like a long-standing issue. It's curious dikkop started > failing only very recently, after the OS upgrade. Yeah. Given that these are threading tests, I'm suspecting some change in thread scheduling behavior in this latest FBSD release, which somehow made it easier to hit a pre-existing issue. regards, tom lane