| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com> |
| Cc: | joconnor(at)cybermesa(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PlPython |
| Date: | 2003-06-30 18:11:26 |
| Message-ID: | 16159.1056996686@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Jacobs | 2003-06-30 19:02:06 | Re: PlPython |
| Previous Message | Tom Lane | 2003-06-30 16:57:38 | Re: Possible parsing problem? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Jacobs | 2003-06-30 19:02:06 | Re: PlPython |
| Previous Message | greg | 2003-06-30 17:31:27 | Datetime patch |