Re: OpenSSL 3.0.0 compatibility

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2020-07-19 14:29:54
Message-ID: 2aecde89-dd54-d154-6676-0aa71f22338b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-07-16 13:45, Michael Paquier wrote:
> On Thu, Jul 16, 2020 at 10:58:58AM +0200, Peter Eisentraut wrote:
>> if test "$with_openssl" = yes ; then
>> dnl Order matters!
>> + AC_DEFINE(OPENSSL_API_COMPAT, [10001],
>> + [Define to the OpenSSL API version in use. This avoids
>> deprecation warnings from newer OpenSSL versions.])
>> if test "$PORTNAME" != "win32"; then
>
> I think that you should additionally mention the version number
> directly in the description, so as when support for 1.0.1 gets removed
> it is possible to grep for it, and then adjust the number and the
> description.

Good point. I have committed it with that adjustment. Also, I had the
format of the version number wrong, so I changed that, too.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-19 14:43:49 Re: Default setting for enable_hashagg_disk
Previous Message James Coleman 2020-07-19 13:55:30 Re: Patch for nodeIncrementalSort comment correction.