From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: configure openldap crash warning
Date: Mon, 09 May 2022 09:47:59 -0400
Message-ID: <3737934.1652104079@sss.pgh.pa.us> (raw)
In-Reply-To: <6f2a7259-812f-fc43-494b-22c85cc1490f@enterprisedb.com>
References: <fedacd7c-2a38-25c9-e7ff-dea549d0e979@enterprisedb.com>
<1832824.1651500238@sss.pgh.pa.us>
<f2393be8-2b92-1ee6-0812-324cf7660f24@enterprisedb.com>
<2358598.1651677372@sss.pgh.pa.us>
<6f2a7259-812f-fc43-494b-22c85cc1490f@enterprisedb.com>
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> Btw., I was a bit puzzled about all this talk about deprecation
> warnings, which I have not seen. I turns out that you only get those if
> you use the OS compiler, not a third-party gcc installation.
Ah-hah.
> So in terms of my original message, my installation is clearly niche.
> The possibly false-positive configure warning is a drop in the bucket
> compared to the deprecation warnings from the compiler. So it's
> probably okay to leave this as is and encourage users to use openldap.
OK. I will push the configure change once the release freeze lifts.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@enterprisedb.com
Subject: Re: configure openldap crash warning
In-Reply-To: <3737934.1652104079@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox