| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | PostgreSQL and OpenSSL 4.0.0 |
| Date: | 2026-04-16 13:32:54 |
| Message-ID: | 066B07BB-85FA-487C-BE8C-40F791CFC3C4@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
With OpenSSL 4.0.0 shipping GA a few days ago I tried compiling PostgreSQL
against it and run the tests. Unsurpisingly the test pass just fine and it
compiles without error since they aren't removing any API's we use (they are
deprecating more APIs we use, more on that in later threads). There are
however a number of warnings since they changed constness on a number of API's.
Sadly, just adopting const cause similar warnings on OpenSSL 1.1.1 and LibreSSL
so we need to do uglier tricks with casting away constness.
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).
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-ssl-Declare-variables-const-as-per-OpenSSL-4-API-upd.patch | application/octet-stream | 6.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-04-16 14:06:25 | Re: Use XLogRecPtrIsValid() instead of negated XLogRecPtrIsInvalid |
| Previous Message | Chengpeng Yan | 2026-04-16 13:01:38 | [PATCH] Fix hashed ScalarArrayOp semantics for NULL LHS with non-strict comparators |