From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org, pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: PlPython |
Date: | 2003-06-22 22:29:07 |
Message-ID: | 14454.1056320947@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 am inclined to rename plpython to plpythonu, by analogy to pltclu.
The advantage of doing so is that (a) the name change makes it somewhat
more obvious that there's a fundamental behavioral change, and (b)
assuming that the Python folk someday figure out a secure version of
RExec, we'd want to reinstitute the trusted version of plpython, but
perhaps not take away the untrusted one.
On the other hand, this would create headaches for people who are trying
to load dump files that declare plpython or contain plpython-language
functions. I can't think of any non-kluge solution to this (kluge
solutions would include putting special-case code into CREATE FUNCTION
to change 'plpython' to 'plpythonu' ...)
Comments?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-06-22 22:41:17 | Re: Schemas and access |
Previous Message | Bruce Momjian | 2003-06-22 21:59:29 | Re: interesting PHP/MySQL thread |
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-06-22 22:49:43 | Re: O_DIRECT in freebsd |
Previous Message | Bruce Momjian | 2003-06-22 22:28:15 | Re: O_DIRECT in freebsd |