Version 2.0.8 of psycopg2 has been released, and it would be good to
get it packaged. One important thing it fixes is a double free in
one of the error handling, which quickly leads to segfaults.
+1. Just ran into this segfault. I'll probably have to fix it locally
sometime soon, but it would be really nice if a fix for it was
released in debian.
If 2.0.8 can't be pulled into testing at this point in the release
cycle, it seems at least fixing that segfault would be good.
This commit:
http://bazaar.launchpad.net/~psycopg/psycopg/2.0.x/revision/346.1.5
might be enough to fix that, but I don't know for sure.
From the NEWS file:
What's new in psycopg 2.0.8
---------------------------
* The connection object now has a get_backend_pid() method that
returns the current PostgreSQL connection backend process PID.
* The PostgreSQL large object API has been exposed through the
Cursor.lobject() method.
* Some fixes to ZPsycopgDA have been merged from the Debian package.
* A memory leak was fixed in Cursor.executemany().
* A double free was fixed in pq_complete_error(), that caused crashes
under some error conditions.
James
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
