| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christian Maurer <c(dot)maurer(at)gmx(dot)at> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18312: libpq: PQsetdbLogin() not thread-safe |
| Date: | 2024-02-05 15:24:51 |
| Message-ID: | 117784.1707146691@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Christian Maurer <c(dot)maurer(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-02-05 16:04:12 | Re: BUG #18331: Why is the session lock (DEFAULT_LOCKMETHOD) not automatically released during process exit? |
| Previous Message | Alexander Korotkov | 2024-02-05 14:50:24 | Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction |