Thread: plpython.so
On two different machines I've built pg 7.4 --with-python. When I createlang plpythonu db I get this error: createlang: language installation failed: ERROR: could not load library "/usr/local/pgsql/lib/plpython.so": /usr/local/pgsql/lib/plpython.so:undefined symbol: PyDict_Copy PyDict_Copy is a python standard call since forever. nm shows it is not defined. nm also shows some glib.c functions not defined. build --with-python and createlang works fine on some other machines. What is the problem here? Some python module I'm missing? Help! --elein elein@varlena.com
elein@varlena.com (elein) writes:
> When I createlang plpythonu db I get this error:
> createlang: language installation failed: ERROR: could not load library "/usr/local/pgsql/lib/plpython.so":
/usr/local/pgsql/lib/plpython.so:undefined symbol: PyDict_Copy
> build --with-python and createlang works fine on some other machines.
What are the exact platforms on which it works or doesn't work for you?
Are they exactly the same Python versions?
regards, tom lane
Debian--works (mine) Fedora--doesn't work (not mine) RedHat--doesn't work (not mine) Is it possible that there is a problem with glibc? If so, what does one do about that? --elein On Wed, Feb 02, 2005 at 01:25:03PM -0500, Tom Lane wrote: > elein@varlena.com (elein) writes: > > When I createlang plpythonu db I get this error: > > createlang: language installation failed: ERROR: could not load library "/usr/local/pgsql/lib/plpython.so": /usr/local/pgsql/lib/plpython.so:undefined symbol: PyDict_Copy > > > build --with-python and createlang works fine on some other machines. > > What are the exact platforms on which it works or doesn't work for you? > Are they exactly the same Python versions? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >
elein@varlena.com (elein) writes:
> Debian--works (mine)
> Fedora--doesn't work (not mine)
> RedHat--doesn't work (not mine)
[ blink ] plpython works for me on Fedora Core 3, using
python-2.3.4-11. Anyone else see a problem with it?
regards, tom lane
Fedora as listed below is really, RedHat Enterprice Linux ES 2.1 I'm not sure about the second failing system. --elein On Wed, Feb 02, 2005 at 10:32:06AM -0800, elein wrote: > Debian--works (mine) > Fedora--doesn't work (not mine) > RedHat--doesn't work (not mine) > > Is it possible that there is a problem with glibc? > If so, what does one do about that? > > --elein > > On Wed, Feb 02, 2005 at 01:25:03PM -0500, Tom Lane wrote: > > elein@varlena.com (elein) writes: > > > When I createlang plpythonu db I get this error: > > > createlang: language installation failed: ERROR: could not load library "/usr/local/pgsql/lib/plpython.so": /usr/local/pgsql/lib/plpython.so:undefined symbol: PyDict_Copy > > > > > build --with-python and createlang works fine on some other machines. > > > > What are the exact platforms on which it works or doesn't work for you? > > Are they exactly the same Python versions? > > > > regards, tom lane > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 8: explain analyze is your friend > > > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >
elein@varlena.com (elein) writes:
> Fedora as listed below is really, RedHat Enterprice Linux ES 2.1
ES 2.1 is pretty old; I'd not be at all surprised if it has a very
obsolete python version.
regards, tom lane
It did have an old python and we updated it to python 2.1 and the problem still occurs. Is there a documented minimum python version required? --elein On Wed, Feb 02, 2005 at 04:16:03PM -0500, Tom Lane wrote: > elein@varlena.com (elein) writes: > > Fedora as listed below is really, RedHat Enterprice Linux ES 2.1 > > ES 2.1 is pretty old; I'd not be at all surprised if it has a very > obsolete python version. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >
On Wed, 2005-02-02 at 16:26, elein wrote: > It did have an old python and we updated it to > python 2.1 and the problem still occurs. > > Is there a documented minimum python version required? > > --elein > > On Wed, Feb 02, 2005 at 04:16:03PM -0500, Tom Lane wrote: > > elein@varlena.com (elein) writes: > > > Fedora as listed below is really, RedHat Enterprice Linux ES 2.1 > > > > ES 2.1 is pretty old; I'd not be at all surprised if it has a very > > obsolete python version. Are you sure you're not missing some -devel library or something like that?
Installation of a new version of python (2.1) did the trick. The apparent failure of 2.1 was because 1.x remains on the system and I had to convince configure to ignore it. (PYTHON=python2) Thank you all. --elein On Wed, Feb 02, 2005 at 05:01:21PM -0600, Scott Marlowe wrote: > On Wed, 2005-02-02 at 16:26, elein wrote: > > It did have an old python and we updated it to > > python 2.1 and the problem still occurs. > > > > Is there a documented minimum python version required? > > > > --elein > > > > On Wed, Feb 02, 2005 at 04:16:03PM -0500, Tom Lane wrote: > > > elein@varlena.com (elein) writes: > > > > Fedora as listed below is really, RedHat Enterprice Linux ES 2.1 > > > > > > ES 2.1 is pretty old; I'd not be at all surprised if it has a very > > > obsolete python version. > > > Are you sure you're not missing some -devel library or something like > that? > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match >