Hi,
On 2022-08-29 23:18:23 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > Why do we continue to link the backend to ldap when we find ldap_r, given that
> > we know that it can cause problems for extension libraries using libpq?
>
> Uh ... if we know that, it's news to me.
Isn't that what the configure warning Peter mentioned upthread is about?
# PGAC_LDAP_SAFE
# --------------
# PostgreSQL sometimes loads libldap_r and plain libldap into the same
# process. Check for OpenLDAP versions known not to tolerate doing so; assume
# non-OpenLDAP implementations are safe. The dblink test suite exercises the
# hazardous interaction directly.
The patch applied as a result of this thread dealt with a different version of
the problem, with -lldap_r picking up a different library version than -lldap.
Leaving that aside it also doesn't seem like a great idea to have two
different copies of the nearly same library loaded for efficiency reasons, not
that it'll make a large difference...
Greetings,
Andres Freund
