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-29 22:56:27 |
Message-ID: | 1056927387.1816.118.camel@fuji.krosing.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane kirjutas E, 30.06.2003 kell 01:21:
> Hannu Krosing <hannu(at)tm(dot)ee> writes:
> > The version with patch which removes RExec (as Python 2.x is not
> > supporting it ) is the right thoing to do FOR PYTHON 2.X, but there is
> > no reason to remove safe execution when using python 1.5.x.
>
> 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?
Python is designed such that one can install and use different versions
in parallel - for example the deafult directopries for libraries are
/usr/lib/python1.5/ and /usr/lib/python2.2/ if you have installed python
1.5.x and 2.2.x, also executables are python2, python2.2 and python1.5,
with plain python being a link to one of these.
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.
------------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2003-06-30 01:52:52 | Re: libpq.so.2 and postgresql-libs-7.3.3 RPM |
Previous Message | Tom Lane | 2003-06-29 22:25:20 | Re: PG crash on simple query |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2003-06-29 23:11:53 | pgsql-hackers@postgresql.org |
Previous Message | Joe Conway | 2003-06-29 22:32:11 | Re: [HACKERS] Missing array support |