On tis, 2010-07-13 at 20:28 -0500, Chris wrote:
> So if I have to explicitly set the python interpretor, how would you
> ever have a plpython2u and plpython3u function in the same DB
> (regardless of the fact that they can't run in the same session)? The
> manual implies you could have them both i
>
>
> You'd have to build the two plpython.so's in separate compile operations.
>
>regards, tom lane
>
I hadn't thought of that. Tried it and it does work. Thanks.
--
Chris Spotts
rfu...@gmail.com
Chris writes:
> So if I have to explicitly set the python interpretor, how would you ever
> have a plpython2u and plpython3u function in the same DB (regardless of the
> fact that they can't run in the same session)?
You'd have to build the two plpython.so's in separate compile operations.
So if I have to explicitly set the python interpretor, how would you ever
have a plpython2u and plpython3u function in the same DB (regardless of the
fact that they can't run in the same session)? The manual implies you could
have them both installed since it says that there's a per session
limita
On tis, 2010-07-13 at 15:38 -0500, Chris wrote:
> I'm testing beta 3 and ran across a PL/Python3u bug again.
> This time it won't let me install it at all.
> Kubuntu 10.04
>
> ./configure --with-pgport=5433 --with-python --with-ossp-uuid
> --with-libxml
> --with-libxslt --with-perl --prefix=/usr/l
I'm testing beta 3 and ran across a PL/Python3u bug again.
This time it won't let me install it at all.
Kubuntu 10.04
./configure --with-pgport=5433 --with-python --with-ossp-uuid --with-libxml
--with-libxslt --with-perl --prefix=/usr/local/pgsqlb3
make
make check
sudo make install
All work fine.
