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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()
Date: 2022-09-12 13:47:51
Message-ID: 1606993.1662990471@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 12 Sep 2022, at 13:21, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2022-09-12 14:11:11 Re: Resolving host to IP address
Previous Message Julien Rouhaud 2022-09-12 13:31:21 Re: unable to install pldebugger