On Feb 13, 2010, at 6:32 AM, Andrew Dunstan wrote:

> My feeling is if we provide something we are responsible for it, documented or not. Undocumented features with security implications raise big red flags in my head. Maybe the difference in perspective comes from working on a database as opposed to working on a language.

I'm confused. Doesn't on_plperl_init already give us this? Isn't any of the stuff loaded by that GUC then available from inside the PLPerl Safe compartment?

Best,

David

In response to

• Re: Package namespace and Safe init cleanup for plperl [PATCH] at 2010-02-13 14:32:31 from Andrew Dunstan

Responses

• Re: Package namespace and Safe init cleanup for plperl [PATCH] at 2010-02-13 22:46:05 from Andrew Dunstan

pgsql-hackers by date

Next:	From: Andrew Dunstan	Date: 2010-02-13 22:46:05
	Subject: Re: Package namespace and Safe init cleanup for plperl [PATCH]
Previous:	From: David E. Wheeler	Date: 2010-02-13 22:25:48
	Subject: Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl