Re: plpython? (Was: Re: Damn triggers and NEW)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jay O'Connor" <joconnor(at)cybermesa(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: plpython? (Was: Re: Damn triggers and NEW)
Date: 2003-06-18 14:32:33
Message-ID: 21390.1055946753@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jay O'Connor" <joconnor(at)cybermesa(dot)com> writes:
> At 06:42 AM 06/18/2003 +0200, you wrote:
>> We could change plpython to an untrusted language
>> if someone cares enough to develop a patch to remove the use of
>> rexec. Otherwise I fear we'll have to pull it.

> When you say "have to pull it" does that mean dropping plpython completely?

Yes. I can't see that we have any other alternative. The existing
plpython won't work at all with newer Python installations, and while
it'd still work with older ones, it has exactly the same security holes
that prompted the Python folk to pull rexec. That means it's foolish
to pretend that it can still be considered a trusted language. So
I feel we cannot just leave it sit there. Either somebody does the
legwork to convert it into an untrusted language that doesn't use rexec,
or it goes. And I don't think any of the core team has the time to do
that legwork. If there's no plpython user with the commitment to fix
it, it's history :-(. Any volunteers out there?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2003-06-18 14:40:37 Re: plpython? (Was: Re: Damn triggers and NEW)
Previous Message Carlos Oliva 2003-06-18 14:29:11 Re: How to convert Oracle database to Postgresql.