#32305: Add an option to limit the number of connections to a database
-------------------------------------+-------------------------------------
Reporter: Barney Szabolcs | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: db connection leak | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
* component: Core (Other) => Database layer (models, ORM)
* type: Cleanup/optimization => New feature
Comment:
Hi Barney.
> 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.
This is something worth looking at if you can demonstrate it with a
minimal project. There really shouldn't be a regression here.
In general I think tracking connections isn't in scope for Django itself.
We'd suggest using a connection pool (e.g. PgBouncer) for your database,
or similar approaches.
--
Ticket URL: <https://code.djangoproject.com/ticket/32305#comment:2>
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/074.fd53acb301bdaf7bf91a6a4e030910cd%40djangoproject.com.
