Foremost, its interesting, why your replies populate as distinct thread rather than of continuing one. (I may be incorrect, are you choosing "forward" option while replying, no ?). Request to hold the continuity of the post instead of different chunks for each reply. :)
Problem with ActivePython-2.7.2.5 is
No. It compiles well with this version too.
This time I have not tweaked ActivePython binary files like I did for AP 3.2, I have just enabled Active Python 2.7 in my path while compiling source.
export PATH=/opt/ActivePython-2.7/bin:$PATH
./configure --prefix=/usr/local/pg93b2 --with-python
make shared_libpython=yes
make shared_libpython=yes install
export PYTHONHOME=/opt/ActivePython-2.7/
export PYTHONPATH=/opt/ActivePython-2.7/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/pg93b2/lib
export LD_LIBRARY_PATH=/opt/ActivePython-2.7/lib:$LD_LIBRARY_PATH
-bash-4.1$ ./psql -p 4444
psql (9.3beta2)
Type "help" for help.
postgres=#
postgres=# create language plpython2u;
CREATE LANGUAGE
By chance if you have missed this part of the PG documentation reading, then please go through it, it has clear instructions of how you enable Plpython2 or Plpython3. In particular, the tip section
"Tip: The built variant depends on which Python version was found during the installation or which version was explicitly set using the PYTHON environment variable; see Section 15.4. To make both variants of PL/Python available in one installation, the source tree has to be configured and built twice."
[postgres@lix stado]$ psqlpsql (9.3beta2)Type "help" for help.postgres=# create language plpython2u;ERROR: could not load library "/opt/PostgreSQL/93b2src/lib/postgresql/plpython2.so": /opt/PostgreSQL/93b2src/lib/postgresql/plpython2.so: undefined symbol: PyObject_Bytes
Not certain on the error. Retake the test with above steps you should succeed.
with environment variables asexport PGDATA=/opt/PostgreSQL/pgdata/93b2srcexport PYTHONHOME=/opt/ActivePython-2.7export PYTHONPATH=/opt/ActivePython-2.7/binexport PATH=/opt/PostgreSQL/93b2src/bin:$PYTHONHOME/bin:$PATHexport LD_LIBRARY_PATH=$PYTHONHOME/lib:$LD_LIBRARY_PATH------------------ Original ------------------Sender: "Raghavendra"<raghavendra.rao@xxxxxxxxxxxxxxxx>;Send time: Tuesday, Jul 16, 2013 4:53 PMTo: "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: 回复： Can't create plpython languageOn Mon, Jul 15, 2013 at 7:10 PM, guxiaobo1982 <guxiaobo1982@xxxxxx> wrote:
It works with ActivePython 3.2.2.3,Thanks for notifying.but not ActivePython 2.7.2.5.No idea... :), I tried AP 3.2 with PG 9.2 & PG 9.3B it went fine for me.------------------ Original ------------------From: "Raghavendra"<raghavendra.rao@xxxxxxxxxxxxxxxx>;Date: Jul 11, 2013To: "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: 回复： Can't create plpython languageOn Wed, Jul 10, 2013 at 7:36 AM, guxiaobo1982 <guxiaobo1982@xxxxxx> wrote:
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 directoryLater, 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-configcp python3. pythonTest: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-configSteps:1. Install PG 9.3 beta with below steps:export PATH=/opt/ActivePython-3.2/bin:$PATH./configure --prefix=/usr/local/pg93b3 --with-pythonmake shared_libpython=yesmake shared_libpython=yes install2. 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.control3. Now, create new cluster using INITDB4. Before starting the cluster set the PYTHONHOME, PYTHONPATH, LD_LIBRARY_PATHexport PYTHONHOME=/opt/ActivePython-3.2/export PYTHONPATH=/opt/ActivePython-3.2/bin:$PATHexport LD_LIBRARY_PATH=/opt/ActivePython-3.2/lib:$LD_LIBRARY_PATH5. 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 LANGUAGEOut 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) ?
