Re: plperl security - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl security
Date
Msg-id 4366.1089064685@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl security  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl security
Re: plperl security
List pgsql-hackers
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.

Recovering when you get an error is probably the trickiest part of this.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: plperl security
Next
From: Andrew Dunstan
Date:
Subject: Re: plperl security