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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1rX5Fm-008hbz-VL
	for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Feb 2024 20:07:43 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1rX5Fm-00FegB-8I
	for pgsql-bugs@arkaria.postgresql.org; Mon, 05 Feb 2024 20:07:42 +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.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rX5Dt-00Fctc-Lm
	for pgsql-bugs@lists.postgresql.org; Mon, 05 Feb 2024 20:05:45 +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.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1rX5Dq-005dQ7-Md
	for pgsql-bugs@lists.postgresql.org; Mon, 05 Feb 2024 20:05:45 +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 415K5cnM265024;
	Mon, 5 Feb 2024 15:05:39 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Maurer <c.maurer@gmx.at>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe
In-reply-to: <117784.1707146691@sss.pgh.pa.us>
References: <18312-bbbabc8113592b78@postgresql.org>
 <trinity-bf4e8296-ed0b-48cd-8a8c-86135d8dd5d9-1706869306101@3c-app-gmx-bap04>
 <3154181.1706888936@sss.pgh.pa.us>
 <trinity-31b9e9ec-519e-4c85-8029-632609642c16-1706891244274@3c-app-gmx-bap32>
 <3222816.1706897982@sss.pgh.pa.us>
 <trinity-93690e67-61b3-42fb-b2fc-8f7db06d8110-1707137386572@3c-app-gmx-bap31>
 <117784.1707146691@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 05 Feb 2024 10:24:51 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <265022.1707163538.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 05 Feb 2024 15:05:38 -0500
Message-ID: <265023.1707163538@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/265023.1707163538%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Christian Maurer <c.maurer@gmx.at> writes:
>> Would it be possible, that the patch you are aiming to make can be incl=
uded 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.

For the archives' sake --- I've posted a patch for this at [1].

			regards, tom lane

[1] https://www.postgresql.org/message-id/264860.1707163416%40sss.pgh.pa.u=
s