It works with ActivePython 3.2.2.3, but not ActivePython 2.7.2.5.
------------------ Original ------------------
From: "Raghavendra"<raghavendra.rao@xxxxxxxxxxxxxxxx>;
Date: Jul 11, 2013
To: "guxiaobo1982"<guxiaobo1982@xxxxxx>;
Cc: "Jov"<amutu@xxxxxxxxx>; "Michael Paquier"<michael.paquier@xxxxxxxxx>; "pgsql-general"<pgsql-general@xxxxxxxxxxxxxx>; "Asif Naeem"<asif.naeem@xxxxxxxxxxxxxxxx>;
Subject: Re: Reply: [GENERAL] »Ø¸´£º [GENERAL] Can't create plpython language
I am using PostgreSQL 9.3 beta 2[postgres@lix Multicorn-master]$ psqlpsql (9.3beta2)Type "help" for help.postgres=#It does not work with ActivePython3.2(ActivePython-3.2.2.3-linux-x86_64.tar.gz), Which version of PostgreSQL are you running?
Sorry for being late on this email. I overlooked the version you were pointing. I didn't test on PG 9.3Beta, I did on PG 9.2 after looking your error showing PG 9.2.4
[postgres@lix PostgreSQL]$ psql
Password:
psql (9.2.4)
Type "help" for help.
postgres=# create language plpython2u;
ERROR: could not access file "$libdir/plpython2": No such file or directory
postgres=# create language plpython3u;
ERROR: could not access file "$libdir/plpython3": No such file or directory
Later, I began testing it with PG 9.3beta and encountered same error message as you have shared here.
Did some analysis and finally succeeded to create language plpython3u with AP-3.2, however with not many tweaks in compilation.(Steps might be arguing. Pardon me).
Despite the fact that I have ActivePython-3.2 on my system, source compilation was looking for shared library. Hence compiled explicitly with shared_libpython=yes.
Pre-Steps: (Assuming you have ActivePython 3.2)
cd /opt/ActivePython-3.2/bin/
cp python3.2-config python-config
cp python3. python
Test:
export PATH=/opt/ActivePython-3.2/bin:$PATH
# which python
/opt/ActivePython-3.2/bin/python
# which python-config
/opt/ActivePython-3.2/bin/python-config
/opt/ActivePython-3.2/bin/python
# which python-config
/opt/ActivePython-3.2/bin/python-config
Steps:
1. Install PG 9.3 beta with below steps:
export PATH=/opt/ActivePython-3.2/bin:$PATH
./configure --prefix=/usr/local/pg93b3 --with-python
make shared_libpython=yes
make shared_libpython=yes install
2. After installation you should see below files in your PG installation Path:
[root@localhost pg93b3]# pwd
/usr/local/pg93b3
[root@localhost pg93b3]# find . | grep python
./lib/postgresql/plpython3.so
./share/postgresql/extension/plpython3u--unpackaged--1.0.sql
./share/postgresql/extension/plpython3u--1.0.sql
./share/postgresql/extension/plpython3u.control
3. Now, create new cluster using INITDB
4. Before starting the cluster set the PYTHONHOME, PYTHONPATH, LD_LIBRARY_PATH
export PYTHONHOME=/opt/ActivePython-3.2/
export PYTHONPATH=/opt/ActivePython-3.2/bin:$PATH
export LD_LIBRARY_PATH=/opt/ActivePython-3.2/lib:$LD_LIBRARY_PATH
5. Start the cluster and create the language:
/usr/local/pg93b3/bin/pg_ctl -D /usr/local/pg93b3/data/ start
-bash-4.1$ psql -p 4444
psql (9.3beta1)
Type "help" for help.
postgres=# create language plpython3u;
CREATE LANGUAGE
psql (9.3beta1)
Type "help" for help.
postgres=# create language plpython3u;
CREATE LANGUAGE
Out of my analysis on the issue, Asif Naeem from our Dev group shared his valuable thoughts to conclude this. Thanks Asif.
Question still in mind, Why plpython depends on Shared Libraries (.so) ?