Re: testing plpython3u on 9.0beta2 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: testing plpython3u on 9.0beta2
Date
Msg-id 201006252344.47407.andres@anarazel.de
Whole thread Raw
In response to Re: testing plpython3u on 9.0beta2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: testing plpython3u on 9.0beta2  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wednesday 23 June 2010 16:30:54 Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > I can reproduce this, here.  The problem seems to be that plpython
> > only build either plpython2.so or plython3.so, but both languages
> > expect a call handler called plython_call_handler.  So once we load
> > the shared library for one language, the other language just grabs the
> > same call handler.
> 
> We had better fix that --- I can definitely foresee installations
> wanting to use both plpython2 and plpython3.  This'd require a change in
> the default contents of pg_pltemplate, though.  Does it seem important
> enough to bump catversion for?
Has anybody actually researched if it is safe to run python2 and python3 in 
the same address space? I wouldnt be surprised at all if that where 
problematic.

Andres


pgsql-hackers by date:

Previous
From: Pavel Baros
Date:
Subject: Re: GSoC - code of implementation of materialized views
Next
From: Peter Eisentraut
Date:
Subject: Re: testing plpython3u on 9.0beta2