Re: OpenSSL 3.0.0 compatibility

> On 29 Jun 2022, at 11:02, Jelte Fennema <postgres(at)jeltef(dot)nl> wrote:
>
> 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?

See upthread in ef5c7896-20cb-843f-e91e-0ee5f7fd932e(at)enterprisedb(dot)com, below is
the relevant portion:

>> 13 and older will, when compiled against OpenSSL 3.0.0, produce a fair amount
>> of compiler warnings on usage of depreceted functionality but there is really
>> anything we can do as suppressing that is beyond the scope of a backpatchable
>> fix IMHO.
>
> Right, that's just a matter of adjusting the compiler warnings.
>
> Earlier in this thread, I had suggested backpatching the OPENSSL_API_COMPAT definition to PG13, but now I'm thinking I wouldn't bother, since that still wouldn't help with anything older.

--
Daniel Gustafsson https://vmware.com/