Re: PostgreSQL and OpenSSL 4.0.0 - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: PostgreSQL and OpenSSL 4.0.0
Date
Msg-id 65C5DC15-DE27-4D36-8AEE-A854C23B3834@yesql.se
Whole thread
In response to Re: PostgreSQL and OpenSSL 4.0.0  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PostgreSQL and OpenSSL 4.0.0
Re: PostgreSQL and OpenSSL 4.0.0
Re: PostgreSQL and OpenSSL 4.0.0
List pgsql-hackers
> On 17 Apr 2026, at 23:50, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Apr 16, 2026 at 03:32:54PM +0200, Daniel Gustafsson wrote:
>> The attached patch, while not pretty, allows libpq and sslinfo to build without
>> warnings on OpenSSL 1.1.1 through 4.0.0 as well as on LibreSSL (and there is
>> quite some variability in constness across all these API versions).
>
> Thanks for that.  That is super fast.
>
> This is likely going to require a backpatch at some point, right?
> What's the impact of the blast in branches where we need to support
> OpenSSL down to 1.0.1, which is the minimum version in REL_14_STABLE?

Indeed, we probably want to backpatch this at some point since OpenSSL 4 is
equally likely to be used regardless of which branch users compile.  Whether we
want to apply this already before 19 goes beta I'll leave for the RMT to
decide.

For 14 through master the attached compiles without warnings and tests green on
all the supported versions of OpenSSL and LibreSSL.  That being said, I'm not
sure that we want to go all the way to 14 since if something does break, we
can't really go around fixing it - I think amending the docs in 14 stating that
OpenSSL 3.6 is the highest supported version is a better solution.

--
Daniel Gustafsson


Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Postgresql 18 Linux (all flavors) - with installation, create new instance/main database
Next
From: Tom Lane
Date:
Subject: Re: Broken build on macOS (Universal / Intel): cpuid instruction not available