Re: [HACKERS] loading libraries on Postmaster startup

2003-05-29 Thread Darko Prenosil
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

Re: [HACKERS] loading libraries on Postmaster startup

2003-02-13 Thread Joe Conway
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

Re: [HACKERS] loading libraries on Postmaster startup

2003-02-13 Thread Peter Eisentraut
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]

Re: [HACKERS] loading libraries on Postmaster startup

2003-02-12 Thread Greg Stark
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

Re: [HACKERS] loading libraries on Postmaster startup

2003-02-12 Thread Tom Lane
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