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

From Tom Lane
Subject Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date
Msg-id 17378.1264637757@sss.pgh.pa.us
Whole thread Raw
In response to Re: Add on_perl_init and proper destruction to plperl [PATCH]  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: Add on_perl_init and proper destruction to plperl [PATCH]
List pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes:
> 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?

Sure.  Which is why I'm resisting expanding our exposure to it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Next
From: "David E. Wheeler"
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]