Re: lippq client library and openssl initialization: PQinitOpenSSL() - Mailing list pgsql-general

From Daniel Gustafsson
Subject Re: lippq client library and openssl initialization: PQinitOpenSSL()
Date
Msg-id C3C3CD40-9F39-44DA-AFAA-AAD52002C3FA@yesql.se
Whole thread Raw
In response to Re: lippq client library and openssl initialization: PQinitOpenSSL()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: lippq client library and openssl initialization: PQinitOpenSSL()
List pgsql-general
> On 11 Sep 2022, at 23:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>> On 11 Sep 2022, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Don't believe so.  The HAVE_CRYPTO_LOCK stuff is all obsolete and
>>> not compiled if you built against 1.1.0.  The only thing left that
>>> will happen if you don't call PQinitOpenSSL is an extra call to
>>> OPENSSL_init_ssl, which should be harmless as far as I can see
>>> from the OpenSSL docs.
>
>> To the best of my knowledge, thats entirely correct.
>
> Should we document these functions as obsolete when using
> OpenSSL >= 1.1.0 ?

Given that 1.1.0+ is very common, it's probably not a bad idea to document them
as obsolete but harmless.  Unless you beat me to it I can propose a patch.

--
Daniel Gustafsson        https://vmware.com/




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()
Next
From: Peter Eisentraut
Date:
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()