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

From David E. Wheeler
Subject Re: Add on_perl_init and proper destruction to plperl [PATCH]
Date
Msg-id CBAA4731-0E52-4651-8366-172C3ADD7751@kineticode.com
Whole thread Raw
In response to Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Add on_perl_init and proper destruction to plperl [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers
On Jan 27, 2010, at 9:08 AM, Tom Lane wrote:

> This is exactly the claim that I have zero confidence in.  Quite
> frankly, the problem with Perl as an extension language is that Perl was
> never designed to be a subsystem: it feels free to mess around with the
> entire state of the process.  We've been burnt multiple times by that
> even with the limited use we make of Perl now, and these proposed
> additions are going to make it a lot worse IMO.

Can you provide an example? Such concerns are impossible to address without concrete examples.

Best,

David

pgsql-hackers by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: Re: C function accepting/returning cstring vs. text
Next
From: Tom Lane
Date:
Subject: Re: Add on_perl_init and proper destruction to plperl [PATCH]