Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> I wonder whether people would like an option to statically link
>> libperl.a and/or libpython.a into the Postgres backend proper? That
>> would allow plperl/plpython to be used on platforms where this is an
>> issue, without having to make a nonstandard build of perl/python.
> Not unless you also link in plperl/plpython itself or mess with
> -whole-archive type linker flags.
The former is what I had in mind.
Yes, it's ugly and it bloats the binary, but people would presumably
only do this if they intended to use the language. So the bloat is
somewhat illusory. And it's less ugly than having to build a
nonstandard install of python or perl.
I could even see people doing this on platforms where they didn't have
to (because a non-PIC libpython or libperl could be included into a
shared library plpython or plperl). It should give a performance
advantage, which might be interesting to heavy users of those PLs.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
