| From: | Jelte Fennema <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | daniel(at)yesql(dot)se |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2022-06-29 09:02:56 |
| Message-ID: | CAGECzQSNs7LrSBRiEQU9ds08J6zjupz-OB0KEoCr5yLAV3m2Vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 29 Jun 2022 at 10:55, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> These have now been pushed to 14 through to 10 ahead of next week releases
I upgraded my OS to Ubuntu 22.04 and it seems that "Define
OPENSSL_API_COMPAT" commit was never backported
(4d3db13621be64fbac2faf7c01c4879d20885c1b). I now get various
deprecation warnings when compiling PG13 on Ubuntu 22.04, because of
OpenSSL 3.0. Was this simply forgotten, or is there a reason why it
wasn't backported?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Geier | 2022-06-29 09:03:51 | Re: Lazy JIT IR code generation to increase JIT speed with partitions |
| Previous Message | Yugo NAGATA | 2022-06-29 08:29:50 | Re: Prevent writes on large objects in read-only transactions |