#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: Rick.van.Hattem@… | Owner: aaugustin
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: database, postgres, | Needs documentation: 0
postgresql, connection, closed | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: closed => new
* resolution: fixed =>
Comment:
I'm reopening this ticket because I want to think about reopening the
connection automatically when no transaction is in progress.
There's probably a bunch of issues with that technique, like retrying a
query that failed.
But since "connection closed" errors are a problem many users struggle
with, it's worth making sure I haven't overlooked a solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:31>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/081.4e4f166a3273455fda91fd5af279a223%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
