Opened 3 years ago
Last modified 3 years ago
#32305 closed New feature
Add an option to limit the number of connections to a database — at Version 1
| Reported by: | Barney Szabolcs | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 3.0 |
| Severity: | Normal | Keywords: | db connection leak |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
With the introduction of threads in Django 3.0, somehow only changing from Django 2.2.x to Django 3.0 causes the number of connections to build up, with each request a new connection being added.
Probably this pile-up is because of some bug in one of the Django-related packages. However, it would be nice to have a safety feature in Django not to exceed a limit of database connections. It would make the whole system a lot more robust.
(At the moment it is not even worth to switch for some long term users who use a long list of packages along with Django because the db connection buildup has no straightforward solution, yet.)
Note:
See TracTickets
for help on using tickets.