ghaverla@freenet.edmonton.ab.ca writes:
> Is this normal, that it is the same in 2 modules, but not
> the third?
Looks normal enough to me --- that's just from the linker merging
modules together.
My bet is that you are chasing the wrong idea. I doubt there's anything
special about CurrentMemoryContext; probably it just happens to be the
first symbol the linker tries (and fails) to link while loading your
shared object file. I'd be looking at issues like whether you have
things configured for dynamic shared-object linking at all. For
example, on HPUX it's necessary to use a special linker switch (-E,
I think) while linking the main "postgres" executable, or else its
global symbols won't be set up to be accessible by dynamically loaded
objects. Dunno if there's a similar incantation needed on your
platform, but that seems like the sort of issue to be looking at.
regards, tom lane