Re: plperl security - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plperl security
Date
Msg-id 9643.1089065597@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl security  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl security
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> That would work.  You'd need two state flags instead of just one, but
>> that doesn't seem bad.

> 'splain please :-)

Maybe you weren't thinking of the same thing, but what I was imagining
was one state flag to remember that you'd created the interpreter (and
loaded the unsafe-func support into it), then a second one to remember
whether you've loaded the safe-func support.  There are various ways to
represent this of course, but the point is there need to be three
persistent states.
        regards, tom lane


pgsql-hackers by date:

Previous
From: elein
Date:
Subject: Re: strange bug in plperl
Next
From: Simon Riggs
Date:
Subject: Re: Recovery Features