| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL deprectation warnings in Postgres 10-13 |
| Date: | 2022-04-06 13:01:42 |
| Message-ID: | 9a43c3c3-48a0-3ebb-400e-c24a3ce9c986@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06.04.22 11:55, Victor Wagner wrote:
> And found out that versions 10-13 produce a lot of warnings about
> deprecated OpenSSL functions.
>
> I've found discussion about this problem
>
> https://www.postgresql.org/message-id/flat/FEF81714-D479-4512-839B-C769D2605F8A%40yesql.se
>
> and commit 4d3db13621be64fbac2faf which fixes problem in the 14
> version and above. (it seems to me that declaring wish to use outdated
> API is ugly workaround, but anyway it works)
>
> But this commit seems not to be backpatched to versions 13-10.
As was discussed in that thread, we don't actually have precise
knowledge of what OpenSSL versions we support in versions before PG13.
So backpatching this could alter or break things that worked before.
It seems easier to just disable deprecation warnings if you don't want
to see them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-04-06 13:07:48 | logical replication of identity sequences |
| Previous Message | wangw.fnst@fujitsu.com | 2022-04-06 12:59:55 | RE: Logical replication timeout problem |