On Fri, Dec 04, 2009 at 02:05:28PM -0500, Tom Lane wrote: > Robert Haas <robertmh...@gmail.com> writes: > > So, do we look for another way to provide the functionality besides > > having a GUC, or is the functionality itself bad? > > I don't think we want random Perl code running inside the postmaster, > no matter what the API to cause it is. I might hold my nose for "on > load" code if it can only run in backends, though I still say that > it's a badly designed concept because of the uncertainty about who > will run what when.
Robert's comparison with mod_perl is very apt. Preloading code gives dramatic performance gains in production situations where there's a significant codebase and connections are frequent. The docs for plperl.on_perl_init could include a section relating to it's use with shared_preload_libraries. That could document any issues and caveats you feel are important. Tim. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
