Re: PostgreSQL and OpenSSL 4.0.0

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-06-12T13:15:11Z
Lists: pgsql-hackers
> On 29 May 2026, at 22:05, Daniel Gustafsson <daniel@yesql.se> wrote:
> 
>> On 27 May 2026, at 12:47, Daniel Gustafsson <daniel@yesql.se> wrote:
>> 
>>> On 27 May 2026, at 02:06, Michael Paquier <michael@paquier.xyz> wrote:
>>> 
>>> On Tue, May 26, 2026 at 10:16:40AM +0200, Daniel Gustafsson wrote:
>>>> I have plans for fixing this in v20 but for 14-19 there isn't much we can do
>>>> except unconstifying.
>>> 
>>> Indeed, no objections regarding that for the stable branches.
>> 
>> Thanks for confirming.  I am currently re-testing all the combinations of stable
>> postgres branches and supported OpenSSL and LibreSSL versions.
> 
> While I had hoped to get it done sooner (sickness altered my plans), I just
> pushed this to master ahead of the beta1 deadline, and once it's been through
> some rounds of buildfarm compiles I'll backpatch to the stable branches.

I've now pushed this to all supported branches after recompiling and retesting
all the backbranches against all the versions of OpenSSL and LibreSSL we
support.

--
Daniel Gustafsson




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix compilation with OpenSSL 4