Re: [PATCH] fix race condition in libpq (related to ssl connections)

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Willi Mann <w.mann@celonis.de>
Date: 2023-11-22T01:58:15Z
Lists: pgsql-hackers
On Wed, Nov 22, 2023 at 2:44 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Tue, Nov 21, 2023 at 12:14:16PM +0300, Aleksander Alekseev wrote:
> > I wonder if we should just document that libpq is thread safe as of PG
> > v??? and deprecate PQisthreadsafe() at some point. Currently the
> > documentation gives an impression that the library may or may not be
> > thread safe depending on the circumstances.
>
> Because --disable-thread-safe has been removed recently in
> 68a4b58eca03.  The routine could be marked as deprecated on top of
> saying that it always returns 1 for 17~.

See also commit ce0b0fa3 "Doc: Adjust libpq docs about thread safety."



Commits

  1. Fix race condition with BIO methods initialization in libpq with threads

  2. Doc: Adjust libpq docs about thread safety.