Dave Pooser <dave-pg@xxxxxxxxxxxxxxx> writes: > On 7/2/11 8:50 PM, "Tom Lane" <tgl@xxxxxxxxxxxxx> wrote: >> Most likely what is happening is that one of the other libraries called >> by the postmaster is pulling in libldap_r --- a bit of research with ldd >> should confirm or deny that. If so, you could probably fix things by >> hacking LDAP_LIBS_BE in the configured src/Makefile.global to pull >> in libldap_r not libldap. > That worked perfectly-- thanks so much for your help! > Do you think this is a Solaris bug, or a Postgres bug, or is this a "works > as designed but sysadmin is an idiot" situation? If it's the first, I > might as well file a bug with Oracle, not that I expect them to be in any > hurry to improve compatibility with a rival DB. Hard to tell. If we'd seen more cases like this, I'd be wondering how to teach configure to look to see which version of libldap was in use by other libraries the postmaster needs. But this is the first such report that I can recall, so I'm inclined to think it might be a misconfigured library. (On my Linux box, for example, a fully-featured postmaster links only to libldap not libldap_r, which is the behavior we were expecting.) Did you identify what it was that was linked to libldap_r? regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
