Re: Add on_perl_init and proper destruction to plperl [PATCH]
От | Tom Lane |
---|---|
Тема | Re: Add on_perl_init and proper destruction to plperl [PATCH] |
Дата | |
Msg-id | 10270.1264615736@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Add on_perl_init and proper destruction to plperl [PATCH] ("David E. Wheeler" <david@kineticode.com>) |
Ответы |
Re: Add on_perl_init and proper destruction to plperl [PATCH]
Re: Add on_perl_init and proper destruction to plperl [PATCH] |
Список | 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
В списке pgsql-hackers по дате отправления: