Joe Conway <[EMAIL PROTECTED]> writes:
> My reasoning at the time was that library preloading shouldn't prevent 
> the postmaster from starting, even if it is unsuccessful, but now I 
> wonder if that was a good idea.

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 guess.  Might as well make one in plpgsql too --- even if it
does nothing today, it might be useful in the future, so the
documentation ought to recommend "call 'plxxx_init' when preloading plxxx"
as a general thing.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html

Reply via email to