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

Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will
Date: 2010-07-07 21:05:55
Message-ID: 1278536755.4130.0.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On tis, 2010-07-06 at 18:15 -0400, Tom Lane wrote:
> At this point it seems clear to me that we've not adequately thought
> through the implications of having two python versions in one
> application namespace, and I'm not sure the Python people have either.
> I think we need to do something to block that from happening, at least
> until we have a plausible way to make it work.

How about this?


Attachment: plpython-version-check.patch
Description: text/x-patch (1.3 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2010-07-07 21:14:06
Subject: Re: Why is vacuum_defer_cleanup_age PGC_USERSET?
Previous:From: Robert HaasDate: 2010-07-07 20:44:10
Subject: Re: t_self as system column

pgsql-committers by date

Next:From: Tom LaneDate: 2010-07-07 21:31:52
Subject: Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will
Previous:From: Tom LaneDate: 2010-07-07 15:13:21
Subject: pgsql: Adjust mbutils.c so it won't get broken by future pgindent runs.

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