Horton

Re: lippq client library and openssl initialization: PQinitOpenSSL()

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>, "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2022-09-11T21:35:04Z
Lists: 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

Commits

  1. doc: PQinitOpenSSL and PQinitSSL are obsolete in OpenSSL 1.1.0+