From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: configure openldap crash warning
In-reply-to: <20220830030817.hgokyi6lyx5zb3hy@awork3.anarazel.de>
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> <2360302.1651678212@sss.pgh.pa.us>
 <2957308.1651860043@sss.pgh.pa.us>
 <20220830030817.hgokyi6lyx5zb3hy@awork3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Mon, 29 Aug 2022 20:08:17 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3494041.1661829503.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Aug 2022 23:18:23 -0400
Message-ID: <3494042.1661829503@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3494042.1661829503%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Why do we continue to link the backend to ldap when we find ldap_r, give=
n that
> we know that it can cause problems for extension libraries using libpq?

Uh ... if we know that, it's news to me.

I think we might've avoided ldap_r for fear of pulling libpthread into
the backend; per recent discussion, it's not clear that avoiding that
is possible anyway.  But you didn't make a case for changing this.

			regards, tom lane