Hi Tom, > 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.
Sounds good. > 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. But since plpython is untrusted now this probably would not work anyway... > 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' ...) I think this would only make it more confusing. Changing plpython from trusted to untrusted is a big change, so some extra attention from the db-admin and users is good IMHO. Bye, Sander. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
