Re: Add on_perl_init and proper destruction to plperl [PATCH] - Mailing list pgsql-hackers

"David E. Wheeler" <david@kineticode.com> writes:
> On Jan 27, 2010, at 3:11 PM, Tom Lane wrote:
>> ...  Anything that Perl does to libc
>> state, open file handles, etc etc carries a high risk of breaking the
>> backend.

> As could any other code that executes then, including C libraries installed from pgFoundry and loaded by a DBA.

Absolutely.  The difference here is in who is going to be expected to
try to deal with any problems.  When somebody says "if I do this in
plperlu, my database crashes!  Postgres sux!" it's not going to help to
say "that's a Perl bug", even if an independent observer might agree.
It's going to be *our* problem, and I don't see any reason to expect
a shred of help from the Perl side.
        regards, tom lane