Re: PlPython

From: "Sander Steffann" <steffann(at)nederland(dot)net>
To: "Kevin Jacobs" <jacobs(at)penguin(dot)theopalgroup(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>, <pgsql-general(at)postgreSQL(dot)org>
Subject: Re: PlPython
Date: 2003-06-23 08:32:12
Message-ID: 006201c33961$f20f8460$c801a8c0@office.computel.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jaka Erjavec 2003-06-23 09:12:20 to_timestamp function
Previous Message Thomas Kellerer 2003-06-23 08:21:04 Re: Urgent : Postgresql Client for linux

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Huxton 2003-06-23 09:11:40 Re: what is the meaning of "schema"?
Previous Message Tatsuo Ishii 2003-06-23 08:17:25 Re: [HACKERS] again: Bug #943: Server-Encoding from EUC_TW