Re: PlPython - Mailing list pgsql-general

From Tom Lane
Subject Re: PlPython
Date
Msg-id 16159.1056996686@sss.pgh.pa.us
Whole thread Raw
In response to Re: PlPython  (Kevin Jacobs <jacobs@penguin.theopalgroup.com>)
Responses Re: PlPython  (elein <elein@varlena.com>)
Re: PlPython  (Kevin Jacobs <jacobs@penguin.theopalgroup.com>)
List pgsql-general
Kevin Jacobs <jacobs@penguin.theopalgroup.com> writes:
> Attached is a patch that removes all of the RExec code from plpython from
> the current PostgreSQL CVS.  In addition, plpython needs to be changed to an
> untrusted language in createlang.

I'm working on the latter and cleaning up the documentation.  How does
your patch affect this statement in the plpython documentation?

   Each function gets its own restricted execution object in the
   Python interpreter, so that global data and function arguments from
   <function>myfunc</function> are not available to
   <function>myfunc2</function>.  The exception is the data in the
   <varname>GD</varname> dictionary, as mentioned above.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible parsing problem?
Next
From: elein
Date:
Subject: Re: PlPython