#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: | Owner: Honza_Kral
Rick.van.Hattem@… | Status: reopened
Type: Bug | Component: Database layer
Milestone: | (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 Honza_Kral):
Replying to [comment:10 dekkers]:
> ...
>
> The problem is again that self.connection isn't None, but it isn't
usable either, and we will loop over this error again and again. The
attached patch will catch the exception and call close(), so that we can
continue with creating a new connection.
>
> ...
And does it occur then at every request or just once? If just once I
consider that fine - we wouldn't want to hide the fact that something bad
happened to the connection from the user.
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:11>
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.
