lobject (conn) can segfault with bad parameter
Reported by Psycopg website | November 26th, 2013 @ 06:38 PM
Submitted by: Voicu Hodrea
attempting to create an lobject but giving a wrong parameter (something which is not a connection object) will segfault python
Comments and changes to this ticket
Hmm, I tested what happens when doing psycopg2.extensions.cursor(<not a conn object>) and the result is weird - the cursor object is created and it lets you do operations but fails in unexpected ways - the query fails with the exception "cursor already closed" which is not very descriptive IMHO.
- State changed from open to resolved
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.