Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> 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?

Yeah, I was going to suggest something involving
find_rendezvous_variable to let the two versions of plpython check for
each other.  But doesn't the error need to be elog(FATAL)?  If you just
elog(ERROR) then the conflicting version of python.so is already loaded
and able to cause problems.  elog(FATAL) isn't very desirable maybe
but it beats crashing.

Minor grammatical nit: I think "session has previously used" would read
better in the errdetail.

			regards, tom lane

In response to

• Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will at 2010-07-07 21:05:55 from Peter Eisentraut

Responses

• Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will at 2010-07-08 18:40:51 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Josh Berkus	Date: 2010-07-07 22:44:08
	Subject: Re: Proposal for 9.1: WAL streaming from WAL buffers
Previous:	From: Josh Berkus	Date: 2010-07-07 21:14:06
	Subject: Re: Why is vacuum_defer_cleanup_age PGC_USERSET?

pgsql-committers by date

Next:	From: Josh Berkus	Date: 2010-07-07 22:48:23
	Subject: Re: Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes.
Previous:	From: Peter Eisentraut	Date: 2010-07-07 21:05:55
	Subject: Re: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will