I've moved this thread from pgsql-bugs to pgsql-hackers; here are
the original messages:
http://archives.postgresql.org/pgsql-bugs/2005-06/msg00105.phphttp://archives.postgresql.org/pgsql-bugs/2005-06/msg00107.php
As I mentioned in my followup to the bug report, a simple fix would
appear to be to check for a NULL return value from PyObject_Str()
before calling PyString_AsString() at the following location:
/* Lines 776-77 in plpython.c */ plrv_so = PyObject_Str(plrv); plrv_sc = PyString_AsString(plrv_so);
I was going to submit a patch, but I don't know enough about the
Python API or how Python and PostgreSQL handle Unicode to know
whether adding that simple check is the appropriate solution (I was
planning to raise an error if PyObject_Str() returned NULL). Can
anybody think of a better fix?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
