#15802: Django stops functioning when the database (PostgreSQL) closes the
connection
-------------------------------------+-------------------------------------
Reporter: Rick.van.Hattem@… | Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) | Resolution: fixed
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: assigned => closed
* resolution: => fixed
Comment:
- connection.close() was made idempotent in Django, regardless of whether
this gets fixed or not in pyscopg2.
- Django should not provide automatic reconnection within a request
because that can break transaction integrity.
- The problem of long running processes is covered by #17887.
The fix seems to work and the discussion after the ticket was reopened
didn't bring up any actionnable item.
--
Ticket URL: <https://code.djangoproject.com/ticket/15802#comment:25>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
