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

From Tom Lane
Subject Re: lippq client library and openssl initialization: PQinitOpenSSL()
Date
Msg-id 1206133.1662932104@sss.pgh.pa.us
Whole thread Raw
In response to Re: lippq client library and openssl initialization: PQinitOpenSSL()  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: lippq client library and openssl initialization: PQinitOpenSSL()
List pgsql-general
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 ?

            regards, tom lane



pgsql-general by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()
Next
From: Daniel Gustafsson
Date:
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()