1 | | 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. |
2 | | Probably this pile-up is because a bug in one of the django 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. |
| 1 | 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. |
| 2 | 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. |