Ants Aasma wrote: > I had to make oracle_fdw work with PostgreSQL compiled using > --with-ldap. The issue there is that Oracle's client library has the > delightful property of linking against a ldap library they bundle that > has symbol conflicts with OpenLDAP. At PostgreSQL startup libldap is > loaded, so when libclntsh.so (the Oracle client) is loaded it gets > bound to OpenLDAP symbols, and unsurprisingly crashes with a segfault > when those functions get used. > > glibc-2.3.4+ has a flag called RTLD_DEEPBIND for dlopen that prefers > symbols loaded by the library to those provided by the caller. Using > this flag fixes my issue, PostgreSQL gets the ldap functions from > libldap, Oracle client gets them from whatever it links to. Both work > fine.
I am aware of the problem, but this solution is new to me. My workaround so far has been to load OpenLDAP with the LD_PRELOAD environment variable on PostgreSQL start. But then you get a crash when Oracle uses LDAP functionality (directory naming). > Attached is a patch that enables this flag on Linux when available. > This specific case could also be fixed by rewriting oracle_fdw to use > dlopen for libclntsh.so and pass this flag, but I think it would be > better to enable it for all PostgreSQL loaded extension modules. I'll consider changing oracle_fdw in that fashion, even if that will only remedy the problem on Linux. I think that this patch is a good idea though. Yours, Laurenz Albe -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
