Re: OpenSSL 3.0.0 compatibility - Mailing list pgsql-hackers

From Robert Haas
Subject Re: OpenSSL 3.0.0 compatibility
Date
Msg-id CA+TgmobPs8_-5cYA55AepLQOnUjpfrc=KLhETxNmWuMF32j40g@mail.gmail.com
Whole thread Raw
In response to Re: OpenSSL 3.0.0 compatibility  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: OpenSSL 3.0.0 compatibility  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Tue, Jul 7, 2020 at 1:46 PM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> Trying to move this along, where would be a good place to define
> OPENSSL_API_COMPAT?  The only place that's shared between frontend and
> backend code is c.h.  The attached patch does it that way.

So, if we go this way, does that mean that we're not going to pursue
removing dependencies on the deprecated interfaces? I wonder if we
really ought to be doing that too, with preprocessor conditionals.
Otherwise, aren't we putting ourselves in an uncomfortable situation
when the deprecated stuff eventually goes away upstream?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit
Next
From: Juan José Santamaría Flecha
Date:
Subject: Re: TAP tests and symlinks on Windows