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

From Robert Haas
Subject Re: testing plpython3u on 9.0beta2
Date
Msg-id AANLkTimvEiKEXlI0b9ckK0IBkL-1eL5zC09dAQcTnKXs@mail.gmail.com
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
List pgsql-hackers
On Wed, Jun 23, 2010 at 10:30 AM, Tom Lane <tgl@sss.pgh.pa.us> 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?

Yeah, I think so.  As for using both plpython2 and plpython3, it looks
to me like right now you can only use one or the other.  I think if
you somehow manage to install both, you're really just getting the
same one twice (I have not tested this, however).

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: testing plpython3u on 9.0beta2
Next
From: Leonardo F
Date:
Subject: access method: are disk pages mandatory?