Tom Lane wrote:
As coded, this will cause pltcl to try to execute the unknown-module
load on every pltcl function call :-(. You really need two bits of
state if you are going to have separate postmaster-time and backend-time
initialization.
Hmmm, I see your point :(. Sorry about that!
Will fix an
Tom Lane wrote:
It seems entirely sensible to me for the postmaster to choke on invalid
settings in postgresql.conf. Better than failing to mention the problem
at all, anyway.
2) do you want a patch that exports plperl_init_all() (and I guess
similar init functions in pltcl and plpython)?
Yeah, I
Joe Conway <[EMAIL PROTECTED]> writes:
> Attached is a patch that:
> 1) fixes the behavior of preload_libraries
> 2) adds an exported xxx_init() function to plperl, pltcl, plpython, and
> plpgsql
> 3) updates the documentation for the changes
As coded, this will cause pltcl to try to execute t
