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 1rX0qA-008IjT-R3 for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Feb 2024 15:24:59 +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 1rX0q9-00E4l1-Il for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Feb 2024 15:24:57 +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 1rX0q9-00E4iQ-AC for pgsql-bugs@lists.postgresql.org; Mon, 05 Feb 2024 15:24:57 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rX0q6-005D7D-Tm for pgsql-bugs@lists.postgresql.org; Mon, 05 Feb 2024 15:24:56 +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 415FOpao117785; Mon, 5 Feb 2024 10:24:51 -0500 From: Tom Lane To: Christian Maurer cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe In-reply-to: References: <18312-bbbabc8113592b78@postgresql.org> <3154181.1706888936@sss.pgh.pa.us> <3222816.1706897982@sss.pgh.pa.us> Comments: In-reply-to Christian Maurer message dated "Mon, 05 Feb 2024 13:49:46 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <117783.1707146691.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 05 Feb 2024 10:24:51 -0500 Message-ID: <117784.1707146691@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Christian Maurer writes: > I could apply your patch and compile libpq on Windows 10. > =C2=A0 > The parallel connect issues are gone now > * in the minimal example and > * also in our regression test which showed the issue in the first place. Great, thanks for the confirmation. > Would it be possible, that the patch you are aiming to make can be inclu= ded in version 16.2? I'm afraid we're a few days too late for that --- even if I had a finished patch, the release freeze started two days ago. It'll be in the May releases, instead. regards, tom lane