Re: plpython implementation

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Szymon Guz <mabewlun(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpython implementation
Date: 2013-06-30 12:13:13
Message-ID: 51D020D9.6060000@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Szymon Guz 2013-06-30 12:18:07 Re: plpython implementation
Previous Message Martijn van Oosterhout 2013-06-30 12:05:41 Re: plpython implementation