Andres Freund <andres@anarazel.de> writes:
> First question:
> Why do we currently use RTLD_GLOBAL loading extension libraries, but
> take pains ([1]) to make things work without RTLD_GLOBAL.
As mentioned in that very message, the point was better missing-symbol
error detection, not RTLD_GLOBAL/LOCAL per se.
> I think using RTLD_LOCAL on most machines would be a much better
> idea. I've not found proper explanations why GLOBAL is used. We started
> using it ages ago, with [2], but that commit contains no explanation,
> and a quick search didn't show up anything either. Peter?
https://www.postgresql.org/message-id/7142.1277772335@sss.pgh.pa.us
My position is the same as then: I'm happy to remove it if it doesn't
break things anywhere ... but it seems like it would cause problems for
plpython, unless their behavior has changed since 2001 which is
surely possible.
regards, tom lane