From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 11:55:29 |
Message-ID: | B6FABD15-33C3-4C0B-AEEF-BD250F431B22@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 12 Sep 2022, at 13:21, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> On 11.09.22 23:43, Daniel Gustafsson wrote:
>>> On 11 Sep 2022, at 23:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> 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.
>
> 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.
--
Daniel Gustafsson https://vmware.com/
Attachment | Content-Type | Size |
---|---|---|
pqinitopenssl.diff | application/octet-stream | 533 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Watzinger, Alexander | 2022-09-12 12:22:38 | Re: Support for dates before 4713 BC |
Previous Message | Peter Eisentraut | 2022-09-12 11:21:57 | Re: lippq client library and openssl initialization: PQinitOpenSSL() |