Re: plpython implementation - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: plpython implementation
Date
Msg-id 51D020D9.6060000@dunslane.net
Whole thread Raw
In response to plpython implementation  (Szymon Guz <mabewlun@gmail.com>)
Responses Re: plpython implementation  (Szymon Guz <mabewlun@gmail.com>)
List pgsql-hackers
On 06/30/2013 07:49 AM, Szymon Guz wrote:
> I'm reading through plperl and plpython implementations and I don't 
> understand the way they work.
>
> Comments for plperl say that there are two interpreters (trusted and 
> untrusted) for each user session, and they are stored in a hash.
>
> Plpython version looks quite different, there is no such global hash 
> with interpreters, there is just a pointer to an interpreter and one 
> global function _PG_init, which runs once (but per session, user, or 
> what?).
>
> I'm just wondering how a plpython implementation should look like. We 
> need another interpreter, but PG_init function is run once, should it 
> then create two interpreters on init, or should we let this function 
> do nothing and create a proper interpreter in the first call of 
> plpython(u) function for current session?
>
>


python does not any any sort of reliable sandbox, so there is no 
plpython, only plpythonu - hence only one interpreter per backend is needed.

cheers

andrew



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: plpython implementation
Next
From: Szymon Guz
Date:
Subject: Re: plpython implementation