Re: plperl security - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: plperl security
Date
Msg-id 40E9D029.7010608@dunslane.net
Whole thread Raw
In response to Re: plperl security  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plperl security  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew@dunslane.net> writes:
>  
>
>>The thing is that unlike TCL we have one interpreter for both trusted 
>>and untrusted cases.
>>    
>>
>
>  
>
>>My thinking is to factor out all the code that only applies to trusted 
>>cases from the interpreter init code, and only call it if we try to 
>>compile a trusted function and it hasn't been run yet. Does that seem 
>>reasonable?
>>    
>>
>
>That would work.  You'd need two state flags instead of just one, but
>that doesn't seem bad.
>  
>

2?

'splain please :-)

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plperl security
Next
From: elein
Date:
Subject: Re: strange bug in plperl