Backport python-psycopg2 2.0.7 to hardy?
Bug #238537 reported by
Roel van Os
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hardy Backports |
Won't Fix
|
Undecided
|
Unassigned | ||
psycopg2 (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: python-psycopg2
I'm using python-psycopg2 to develop a database-driven GUI application (using SQLAlchemy).
I've had some crash issues that seem to be related to python-psycopg2 when making database connections. glibc complains about corrupted memory just before crashing, which seems to indicate some malloc/free problems. In psycopg2's changelog I found that some changes have been made to malloc/free usage for version 2.0.7. I tested with python-psycopg2 2.0.7 from intrepid: the crashes no longer happen.
Could python-psycopg2 2.0.7 be backported to hardy?
Ubuntu 8.04
python-psycopg2 2.0.6-3
Changed in psycopg2 (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in hardy-backports: | |
status: | New → Won't Fix |
To post a comment you must log in.
I forgot to mention: I'm using the 32 bit version of Ubuntu.