| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL deprectation warnings in Postgres 10-13 |
| Date: | 2022-04-07 11:38:27 |
| Message-ID: | 5A4FD772-EEEB-4C2C-8EB7-8F041577EE93@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> It seems easier to just disable deprecation warnings if you don't
>> want to see them.
>
> As far as my understanding goes, "just disable deprication warning" it
> is what commit 4d3db13621be64fbac2faf does.
But as stated above, there is no set of supported versions defined so there is
definitive value we can set for OPENSSL_API_COMPAT in the backbranches.
> Real fix would be rewrite corresponding parts of code so they wouldn't
> use deprecated API. (as it was done with sha2 code in PostgreSQL 14.
> which doesn't use openssl version of sha2 at all).
That wouldn't help for 10-13 since that's a change unlikely to be back ported
into a stable release.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2022-04-07 11:39:58 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Frédéric Yhuel | 2022-04-07 11:37:57 | Re: REINDEX blocks virtually any queries but some prepared queries. |