Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Remove deprecation warnings when compiling PG ~13 with OpenSSL 3.0~
Date: 2023-06-21 07:16:38
Message-ID: 057B416A-15E8-4597-B06A-8AC8F3BA678B@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 21 Jun 2023, at 07:44, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2023-06-21 11:53:44 +0900, Michael Paquier wrote:

>> I have been annoyed by these in the past when doing backpatches, as
>> this creates some noise, and the only place where this counts is
>> sha2_openssl.c. Thoughts about doing something like the attached for
>> ~13?
>
> Wouldn't the proper fix be to backpatch 4d3db13621b?

Agreed, I'd be more inclined to go with OPENSSL_API_COMPAT. If we still get
warnings with that set then I feel those warrant special consideration rather
than a blanket suppression.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-06-21 07:18:45 Re: Consistent coding for the naming of LR workers
Previous Message Michael Paquier 2023-06-21 06:49:06 Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific