From c0d2c7be44ff186ed302247af1d16ba12b21f367 Mon Sep 17 00:00:00 2001 From: Jelte Fennema Date: Wed, 29 Jun 2022 11:27:19 +0200 Subject: [PATCH] Remove warnings on PG13 + OpenSSL 3.0 OpenSSL 3.0 has marked some functions that we use as deprecated, but we want to continue support OpenSSL 1.0.1 for the time being too. This indicates that to OpenSSL 3.0, so it doesn't show warnings. (cherry picked from commit 58e8da8339a4540dff4baf589ab6efc506ac2e6b) --- src/backend/distributed/utils/enable_ssl.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/src/backend/distributed/utils/enable_ssl.c b/src/backend/distributed/utils/enable_ssl.c index a6a8dc065..704670b9e 100644 --- a/src/backend/distributed/utils/enable_ssl.c +++ b/src/backend/distributed/utils/enable_ssl.c @@ -8,6 +8,19 @@ *------------------------------------------------------------------------- */ + +/* + * Make sure that functions marked as deprecated in OpenSSL 3.0 don't trigger + * deprecation warnings by indicating that we're using the OpenSSL 1.0.1 + * compatibile API. Postgres does this by already in PG14, so we should not do + * it otherwise we get warnings about redefining this value. + */ +#if PG_VERSION_NUM < PG_VERSION_14 +#ifndef OPENSSL_API_COMPAT +#define OPENSSL_API_COMPAT 0x1000100L +#endif +#endif + #include "postgres.h" #include "distributed/connection_management.h"