Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe
Date
Msg-id 117784.1707146691@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe  (Christian Maurer <c.maurer@gmx.at>)
Responses Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
Christian Maurer <c.maurer@gmx.at> writes:
> I could apply your patch and compile libpq on Windows 10.
>  
> 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 included 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

pgsql-bugs by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
Next
From: Tom Lane
Date:
Subject: Re: BUG #18331: Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released during process exit?