BUG #2352: Bug with Pl/Python
The following bug has been logged online:
Bug reference: 2352
Logged by: Rafael Jorge Sierra Goncales
Email address: rafaeljsg14@gmail.com
PostgreSQL version: 8.1.3
Operating system: NetBSD-3.0
Description: Bug with Pl/Python
Details:
I'm trying run this command:
=# CREATE LANGUAGE "plpythonu"
But it only throws a SIGABRT
I set all debug levels to the maximum (debug5), and I was compiled with the
option --enable-debug, when I run "gdb /postgresql-bin/postgres"
...
run -D path-database template1
...
postgres> CREATE LANG "plpythonu";
LOCATION: elog_node_display, print.c:86
STATEMENT: create language "plpythonu"
DEBUG: 00000: ProcessUtility
LOCATION: PortalRunUtility, pquery.c:952
STATEMENT: create language "plpythonu"
Program received signal SIGABRT, Aborted.
[Switching to LWP 1]
0x0000000201d2d15e in kill () from /usr/lib/libc.so.12
(gdb) backtrace
#0 0x0000000201d2d15e in kill () from /usr/lib/libc.so.12
Reading this, I can't found where is the problem, could this be a bug?
"Rafael Jorge Sierra Goncales" <rafaeljsg14@gmail.com> writes:
=# CREATE LANGUAGE "plpythonu"
Program received signal SIGABRT, Aborted.
This most likely indicates an Assert failure (did you build with
--enable-cassert?) There should be a TRAP message in the postmaster
log if so. Seeing that would be helpful.
I'm wondering if the problem comes from trying to load a wrong version
of the plpython shared library. You might want to check that you've got
a plpython.so that was built from the same PG version and same configure
options as the backend.
regards, tom lane