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 1kWQLs-0006sl-UN for pgsql-bugs@arkaria.postgresql.org; Sat, 24 Oct 2020 20:41:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kWQLq-0008La-Kd for pgsql-bugs@arkaria.postgresql.org; Sat, 24 Oct 2020 20:41:22 +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 1kWQLq-0008LS-Eh for pgsql-bugs@lists.postgresql.org; Sat, 24 Oct 2020 20:41:22 +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 1kWQLg-0005PA-I0 for pgsql-bugs@lists.postgresql.org; Sat, 24 Oct 2020 20:41:18 +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 09OKf9Wv390898; Sat, 24 Oct 2020 16:41:09 -0400 From: Tom Lane To: Alexander Lakhin cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16685: The ecpg thread/descriptor test fails sometimes on Windows In-reply-to: References: <16685-d6cd241872c101d3@postgresql.org> <367782.1603554604@sss.pgh.pa.us> <380144.1603558463@sss.pgh.pa.us> Comments: In-reply-to Alexander Lakhin message dated "Sat, 24 Oct 2020 21:00:00 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <390896.1603572069.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 24 Oct 2020 16:41:09 -0400 Message-ID: <390897.1603572069@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk BTW, I searched the buildfarm logs of ECPG failures to see if I could find anything related to this, and noticed that there were a fair number of Windows-machine failures in the thread/prep test. They don't all look quite alike, but this one is representative (and the most recent): sysname|dory snapshot|2019-04-02 11:20:25 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D pgsql.build/src/int= erfaces/ecpg/test/regression.diffs =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D diff -w -U3 c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecp= g/test/expected/thread-prep.stderr c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.b= uild/src/interfaces/ecpg/test/results/thread-prep.stderr --- c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/e= xpected/thread-prep.stderr 2018-04-20 16:03:08 -0400 +++ c:/pgbuildfarm/pgbuildroot/HEAD/pgsql.build/src/interfaces/ecpg/test/r= esults/thread-prep.stderr 2019-04-02 07:43:27 -0400 @@ -0,0 +1,84 @@ +SQL error: could not connect to database "ecpg1_regression" on line 48 +SQL error: the connection to the server was lost on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 ... quite a few repetitions of this ... +SQL error: the connection to the server was lost on line 52 +SQL error: invalid statement name "i" on line 53 +SQL error: invalid statement name "i" on line 55 +SQL error: connection "Connection: 1" does not exist on line 56 I suspect that this might arise from a pthread_once failure associated with the actual_connection_key variable. regards, tom lane