#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):
Hi André, I think this might be intended behavior. You need to close
connections. During a request cycle Django does it for you. But stuff like
celery etc also have to manually close connections. I assume your code was
working before without the pool? What was the configuration then?
Especially did you have persistent connections enabled? If yes I think
you'd see the same behavior there.
--
Ticket URL: <https://code.djangoproject.com/ticket/35672#comment:12>
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/01070191654a5b58-fead1c39-64e3-4233-9327-a16c576fda53-000000%40eu-central-1.amazonses.com.
