| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Willi Mann <w(dot)mann(at)celonis(dot)de> |
| Subject: | Re: [PATCH] fix race condition in libpq (related to ssl connections) |
| Date: | 2023-11-22 01:58:15 |
| Message-ID: | CA+hUKGJch=dx+6XzGyJ-7WwgZWPpwiJpMtvO2U6tr1kB0+Yo6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 22, 2023 at 2:44 PM Michael Paquier <michael(at)paquier(dot)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."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-11-22 03:43:48 | Re: [HACKERS] Changing references of password encryption to hashing |
| Previous Message | Michael Paquier | 2023-11-22 01:48:25 | Re: [PATCH] fix race condition in libpq (related to ssl connections) |