Re: plperl vs. plperlu - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: plperl vs. plperlu
Date
Msg-id 40F0136B.6040800@Yahoo.com
Whole thread Raw
In response to Re: plperl vs. plperlu  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 7/10/2004 9:05 AM, Andrew Dunstan wrote:

> If trusted, the function is located inside a perl Safe container, a 
> mechanism designed for just this purpose. Try doing something forbidden 
> inside a trusted function (like opening a file) and you will see the error.

As if I would know perl :-)

But yes, I see that it does it in create_sub() now ... thanks for the 
clearification.


Jan

> 
> cheers
> 
> andrew
> 
> Jan Wieck wrote:
> 
>> while playing with the OSCON CD's, I noticed that the current version 
>> of plperl installs the same function handler for both, plperl and 
>> plperlu. I was wondering how it implements the important security 
>> difference or, in case it is not handled and both are in fact the 
>> same, who ignored this IMHO important difference in the naming 
>> convention of procedural languages.
>>
>>
>> Jan
>>


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #1118: Misleading Commit message
Next
From: Tom Lane
Date:
Subject: Re: User Quota Implementation