Re: plperl security

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, plperlng-devel(at)pgfoundry(dot)org
Subject: Re: plperl security
Date: 2004-07-05 22:34:15
Message-ID: 40E9D767.7050806@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)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.
>
>
>
>

Ahh, ok. We already have a state var to remember the first part
(plperl_firstcall). Just need one new one I think.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Mascari 2004-07-05 22:40:51 Re: Recovery Features
Previous Message Oliver Jowett 2004-07-05 22:28:42 Re: subtransactions and FETCH behaviour (was Re: PREPARE