Re: lippq client library and openssl initialization: PQinitOpenSSL()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Sebastien Flaesch <sebastien.flaesch@4js.com>,
"pgsql-general@lists.postgresql.org"
<pgsql-general@lists.postgresql.org>
Date: 2022-09-12T13:47:51Z
Lists: pgsql-general
Daniel Gustafsson <daniel@yesql.se> writes: > On 12 Sep 2022, at 13:21, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: >> AFAICT, RHEL 7 ships with an older version. I think that's still pretty widespread. > Fair enough. That doesn't however IMO prevent us from adding a note that 1.1.0 > and onwards are different. The attached keeps the strong wording of the main > para, but adds a note after the related functions. Personally I'd put this up front, more like have been initialized by your application, so that <application>libpq</application> will not also initialize those libraries. + However, this is unnecessary when using OpenSSL 1.1.0 or later, + as duplicate initializations are no longer problematic. </para> If you do use wording that specifically mentions PQinitOpenSSL, it should also mention PQinitSSL, just for clarity. regards, tom lane
Commits
-
doc: PQinitOpenSSL and PQinitSSL are obsolete in OpenSSL 1.1.0+
- ea7894d33d17 11.20 landed
- e76fbcf796d6 12.15 landed
- 36f49be80856 13.11 landed
- e9884e992186 14.8 landed
- de575c78e14c 15.3 landed
- 928e05ddfd40 16.0 landed