On Thursday 13 February 2003 22:24, Joe Conway wrote:
Peter Eisentraut wrote:
Joe Conway writes:
So I wrote a quick hack to load and initialize the library on postmaster
startup.
On glibc systems you can probably do this using the environment variable
LD_PRELOAD. I guess others have a
Peter Eisentraut wrote:
Joe Conway writes:
So I wrote a quick hack to load and initialize the library on postmaster
startup.
On glibc systems you can probably do this using the environment variable
LD_PRELOAD. I guess others have a similar mechanism.
Hmmm. I could try that. But I found
Joe Conway writes:
So I wrote a quick hack to load and initialize the library on postmaster
startup.
On glibc systems you can probably do this using the environment variable
LD_PRELOAD. I guess others have a similar mechanism.
--
Peter Eisentraut [EMAIL PROTECTED]
While using PL/R in a web based application, I noticed that the library
load and initialization time is significant enough to be annoying. So I
wrote a quick hack to load and initialize the library on postmaster
startup. This way, the backends get a fully initialized copy of the
interpreter when
Joe Conway [EMAIL PROTECTED] writes:
2. It seems to me that other libraries such as those for PL/Tcl,
PL/Perl, etc may have the same issue. Is there any merit in
a GUC variable to allow libraries such as this to be loaded
and initialized at postmaster start? I'll generalize
Joe Conway [EMAIL PROTECTED] writes:
[ what about autoloading libraries into the postmaster? ]
I can see a couple possible downsides: (a) the library might have some
weird behavior across fork boundaries; (b) the additional memory space
that has to be duplicated into child processes will cost
