Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] PlPython

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>,pgsql-hackers(at)postgreSQL(dot)org, pgsql-general(at)postgreSQL(dot)org
Subject: Re: [HACKERS] PlPython
Date: 2003-06-30 07:30:47
Message-ID: 1056958246.6907.1.camel@fuji.krosing.net (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Tom Lane kirjutas E, 30.06.2003 kell 06:39:
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> > Tom Lane kirjutas E, 30.06.2003 kell 01:21:
> >> Who's still using 1.5, I guess is the question?  And are they likely
> >> to be updating their PG installation when they're not updating Python?
> 
> > I guess that anyone who needs safe Restricted Execution will be using
> > 1.5 at least for that purpose until RExec is fixed in 2.x.
> 
> I don't find that real compelling ...
> 
> The bottom line is that this has to get done.  I have the time to
> convert plpython to untrusted status tomorrow.  I do not have the time,
> the infrastructure, nor the interest to build a conditional setup.
> Unless someone else wants to volunteer to make it happen in a timely
> fashion, untrusted is what it will be.

Fine with me.

Just don't put in any hacks to pretend it is trusted.

---------------
Hannu



In response to

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2003-06-30 07:48:02
Subject: Re: PlPython
Previous:From: Tom LaneDate: 2003-06-30 05:08:37
Subject: Re: PlPython

pgsql-general by date

Next:From: Hannu KrosingDate: 2003-06-30 07:48:02
Subject: Re: PlPython
Previous:From: Tom LaneDate: 2003-06-30 05:08:37
Subject: Re: PlPython

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group