#32305: Add an option to limit the number of connections to a database
-------------------------------------+-------------------------------------
     Reporter:  Barney Szabolcs      |                    Owner:  nobody
         Type:                       |                   Status:  new
  Cleanup/optimization               |
    Component:  Core (Other)         |                  Version:  3.0
     Severity:  Normal               |               Resolution:
     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
-------------------------------------+-------------------------------------
Description changed by Barney Szabolcs:

Old description:

> 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 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.
> (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.)

New description:

 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.)

--

-- 
Ticket URL: <https://code.djangoproject.com/ticket/32305#comment:1>
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.821d1ef17f0b4a0137f0a3ded0880e42%40djangoproject.com.

Reply via email to