Re: PostgreSQL and OpenSSL 4.0.0

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-29 20:05:56
Message-ID: E90EBB9D-9528-45CD-923D-8E201A302C2E@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 May 2026, at 12:47, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> On 27 May 2026, at 02:06, Michael Paquier <michael(at)paquier(dot)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.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zakariyah Ali 2026-05-29 20:07:31 [PATCH v1] Fix doubled-word typos and punctuation in code comments
Previous Message Ayush Tiwari 2026-05-29 19:43:28 Re: pg_stash_advice: dump file with overlong stash name crashes worker in a restart loop