Re: Add on_perl_init and proper destruction to plperl [PATCH]

On Jan 27, 2010, at 4:10 PM, Tom Lane wrote:

> 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.

Is that not the case with plperlu already?

Best,

David