Postgres Pro
Downloads
Home   >   mailing lists

Re: Package namespace and Safe init cleanup for plperl [PATCH] - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Package namespace and Safe init cleanup for plperl [PATCH]
Date
Msg-id E8D769F2-26BF-4F01-9688-A2C2C921B287@kineticode.com
Whole thread Raw
In response to Re: Package namespace and Safe init cleanup for plperl [PATCH]  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Package namespace and Safe init cleanup for plperl [PATCH]
List pgsql-hackers
Tree view 
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
securityimplications raise big red flags in my head. Maybe the difference in perspective comes from working on a
databaseas 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
frominside the PLPerl Safe compartment? 

Best,

David

pgsql-hackers by date:

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