RE: PostgreSQL ld.so.1 problem (solaris)

On Wed, 19 Jul 2000, Carlos Villegas wrote:

> Hi,

Hello

> working. The problem is that some symbols used by plpgsql.so are
> defined in the postgres executable. However, when loading the
> library dynamically using the dlopen function, the
> caller symbols are not available to the shared object.

Yes, that's sort of what I (with the help of nm) was thinking too.

> Fortunately, there is a flag to export the caller symbols
> (in this case postgres) to the shared library. I got
> it from the man page of dlopen!

The Solaris 2.5.1 manpage only lists 3 RTLD_ flags but the dlfcn.h lists a
lot more ...


> The patch at the end should do the job.

It doesn't for me. I still get this in the create_function_2 regression
test.

LOAD '/export/tmp/postgresql-7.0.2/src/test/regress/input/../regress.so';
ERROR:  Load of file
/export/tmp/postgresql-7.0.2/src/test/regress/input/../regress.so failed:
ld.so.1: /home/postgres/bin/postmaster: fatal: relocation error:  file
/export/tmp/postgresql-7.0.2/src/test/regress/input/../regress.so: symbol
CurrentMemoryContext: referenced symbol not found

Maybe this is a solaris 2.5.1/2.6 difference? Maybe there is a reason that
flag isn't mentioned in the manpage ...

I have tried to make very sure that there are no traces of the old
postgres binaries and libraries on the system, so I don't think that is it
(unless you need to do something silly like reboot to replace a .so on
solaris).


Oh, well. It was never that important to me. Thanks for sending the patch,
it does look right but for some reason it doesn't seem to work. If someone
has other patches or want to guess things I may have done wrong I'll
gladly test that.

/Urban