#35672: Using database connection pooling, threads do not return the connection
-------------------------------------+-------------------------------------
Reporter: André S. Hansen | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Florian Apolloner):
Addendum to the comment before: The behavior before should have been the
same with and without persistent connections. Though I might have an idea
why you might not have seen this before (I am just guessing though, I
don't know the details of our thread local implementations out of my
head). Before thread ids might have gotten reused, so while you were
leaking connections as well other requests might have spawned with the
same thread id. Now with the pool it is very important that you close the
connection at the end of your code to return it.
--
Ticket URL: <https://code.djangoproject.com/ticket/35672#comment:13>
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/01070191655b5797-7cf67168-7d70-425b-a671-9f19223ebd41-000000%40eu-central-1.amazonses.com.
