Re: Add on_perl_init and proper destruction to plperl [PATCH]
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@kineticode.com>
Cc: Tim Bunce <Tim.Bunce@pobox.com>, Alex Hunsaker <badalex@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@postgresql.org
Date: 2010-01-27T18:08:56Z
Lists: pgsql-hackers
"David E. Wheeler" <david@kineticode.com> writes: > 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. Two examples that I can find in a quick review of our CVS history: perl stomping on the process's setlocale state, and perl stomping on the stdio state (Windows only). regards, tom lane