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

From Michael Paquier
Subject Re: PostgreSQL and OpenSSL 4.0.0
Date
Msg-id ahU3irfvsoO5Ul9S@paquier.xyz
Whole thread
In response to Re: DOCS: Describe some missing parameters on CREATE/ALTER PUBLICATION pages  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: PostgreSQL and OpenSSL 4.0.0
List pgsql-hackers
On Tue, May 19, 2026 at 02:18:08PM -0700, Daniel Gustafsson wrote:
> > On 8 May 2026, at 00:21, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > I think the changes are straightforward enough that we can go ahead with them.
> > I'll re-test and re-post a new patchset for all branches once the minors ship.
>
> Attached are rebased versions of this patchset for v14-master.

I have a question here.  Most of the changes relate to the use of const
where the OpenSSL APIs require these to be so, but why is this a new
requirement for 4.0?  I can see that for most of the upstream
routines, the const changes are much older, like in 8cc86b81ac20 for
X509_NAME_get_text_by_NID() applying down to branch openssl-3.0.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: Support EXCEPT for ALL SEQUENCES publications
Next
From: jian he
Date:
Subject: Re: Fix bug of CHECK constraint enforceability recursion