| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | elein(at)varlena(dot)com |
| Cc: | Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, joconnor(at)cybermesa(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PlPython |
| Date: | 2003-06-30 21:32:18 |
| Message-ID: | 17718.1057008738@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
elein <elein(at)varlena(dot)com> writes:
> Sorry about the mixup earlier. But the "forbidden"
> modules part still needs to be tossed for the new doc.
Right. I already pulled section 43.4 --- see the updated docs at
http://developer.postgresql.org/docs/postgres/plpython.html
I've also commented out the paragraph about global data and function
arguments pending resolution of the question. Given the reference to
restricted execution objects in the original text, I would think that
the removal of rexec usage means that plpython functions can now get at
any global data. But I'm not a Python user and might be
misunderstanding the point.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Jacobs | 2003-06-30 21:36:36 | Re: PlPython |
| Previous Message | elein | 2003-06-30 21:14:09 | Re: PlPython |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Jacobs | 2003-06-30 21:36:36 | Re: PlPython |
| Previous Message | Tom Lane | 2003-06-30 21:27:38 | Re: [HACKERS] Missing array support |