pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Дилян Палаузов <dilyan.palauzov@aegee.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: No libldap_r in OpenLDAP 2.5 - use LDAP_API_FEATURE_X_OPENLDAP_REENTRANT from ldap_features.h
Date: Wed, 25 Aug 2021 10:07:40 +0300
Message-ID: <3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org> (raw)
In-Reply-To: <520273.1629872978@sss.pgh.pa.us>
References: <20210825052142.Horde.fX47Irhz5YmXoRVbIbyYUJm@webmail.aegee.org>
	<520273.1629872978@sss.pgh.pa.us>

Hello Tom,

on my system I have installed first OpenLDAP 2.4, and then in addition
OpenLDAP 2.5.  The problem is, that postgresql (daemon) links with
libldap-2.5, and libpq links with libldap_r-2.4 . So any executable
(e.g. php) which links with both libldap and libpq, loads at the end at
the same time libldap-2.5 andl libldap_r-2.4 - two different versions.
This is not good.

When libldap( 2.5) is reentrant, and when libldap_r-2.4 is present,
libldap_r-2.4 shall not be used for linking.

Greetings
  Дилян


On Wed, 2021-08-25 at 02:29 -0400, Tom Lane wrote:
> Dilyan Palauzov <Dilyan.Palauzov@aegee.org> writes:
> > The current postgres/configure.ac logic is: if libldap_r is
> > availabe,  
> > then use it, otherwise use libldap.
> 
> Right.
> 
> > I propose, instead of looking for the presence of libldap_r, to
> > check  
> > the feature macro, and if libldap is reentrant, not to use
> > libldap_r .
> 
> Why?  This seems more fragile (i.e., it adds an assumption that the
> visible header file matches the available libraries), and if there is
> a concrete benefit, you did not say what that is.
> 
>                         regards, tom lane






view thread (8+ messages)  latest in thread

Message-ID: <3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org>
Permalink:  ../3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org/
Also on:    postgresql.org/message-id/3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org

 · 

reply

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-bugs@postgresql.org
  Cc: dilyan.palauzov@aegee.org, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
  Subject: Re: No libldap_r in OpenLDAP 2.5 - use LDAP_API_FEATURE_X_OPENLDAP_REENTRANT from ldap_features.h
  In-Reply-To: <3894d2a91d141b0fe454da01b3b7faad6fa9d07a.camel@aegee.org>

* 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