Re: PostgreSQL and OpenSSL 4.0.0

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL and OpenSSL 4.0.0
Date: 2026-05-27 00:06:01
Message-ID: ahY1aR4te1ffXkA2@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. For
v20, it sounds to me that cutting through the set of versions of
OpenSSL supported should make the situation much saner, even if the
range of changes seems to be limited due to the LibreSSL story.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2026-05-27 00:13:30 Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
Previous Message Amit Kapila 2026-05-26 23:39:34 Re: Bound memory usage during manual slot sync retries