#13870: psycopg2 backend never terminates isolating transactions
---------------------------------------------------+------------------------
Reporter: patrys | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by davidr):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I ran into to this problem from Django 1.0 and ended up using the
following workaround to explicitly close the connection after the model
was used.
{{{
from django.db import connection
connection.close()
}}}
In my case there was a shared table lock which ended up being held by the
process using the model classes (because of the uncommited transaction)
which in turn caused a deadlock as another process requiring an exclusive
lock on the table would block forever.
--
Ticket URL: <http://code.djangoproject.com/ticket/13870#comment:1>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
