#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: Rick.van.Hattem@… | Owner:
Type: Bug | Honza_Kral
Component: Database layer | Status: reopened
(models, ORM) | Version: 1.3
Severity: Normal | Resolution:
Keywords: database, postgres, | Triage Stage: Accepted
postgresql, connection, closed | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by dekkers):
The problem that is solved by my patch is that the connection is closed by
the DB without Django knowing it (this happens when you for example
restart the DB). Django tries to use self.connection and doesn't handle
the exception. You could change the psycopg2 behaviour to automatically
reconnect, but that might hide other problems, so I don't think that's a
good idea.
I currently run Django 1.3.1 with both patches applied without any
problems.
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:15>
Django <https://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.
