#24810: Reopen database connection automatically when no transaction is active
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Hugo Osvaldo Barrera):
I've been trying to address this with no luck.
My main problem is accurately reproducing this issue -- it seems to
happen from time to time in production for me. The DB connection seems to
die for some reason, and the next request fails with {{{InterfaceError}}}.
However, testing locally I tried to reproduce this by:
1. Start Django and Postgres.
2. Execute a Request (which does a DB call). It works!
3. Soft-exit Postgres
2. Execute a Request (which does a DB call). It still works! 😓
I tried as an alternative killing postgres in (3), but the result is the
same.
As per Sentry, I'm hitting this error a few hundred times a month, so I'd
really like to address this.
Any hints on how to accurately reproduce this?
--
Ticket URL: <https://code.djangoproject.com/ticket/24810#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f0214e877294a597016cd78e45cc8b4f%40djangoproject.com.
