On Tuesday 15 May 2001 13:09, Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> 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'm not sure it is any uglier than including the (to me) useless geometry
datatypes.
I would be happy to help get this working with plperl.
Another interesting idea is to allow the postmaster to 'preload' some of the
libraries. This would help cut down the startup cost of a new backend that
needed a widely used language.
--
Mark Hollomon
