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

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Alex Hunsaker <badalex(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date: 2010-01-28 00:10:59
Message-ID: 90E97DB7-AC31-4CCA-B90A-336217A27D9A@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-28 00:15:57 Re: Add on_perl_init and proper destruction to plperl [PATCH]
Previous Message Tom Lane 2010-01-28 00:10:02 Re: Add on_perl_init and proper destruction to plperl [PATCH]