#30441: Persistent connections not reused on request.
-------------------------------------+-------------------------------------
Reporter: cryptogun | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mahdi Zareie):
* status: new => closed
* resolution: => invalid
Comment:
I reproduce the problem using the example source code you have provided
when I used development server, it said `django.db.utils.OperationalError:
FATAL: sorry, too many clients already`.
But I failed in reproducing the same error when I tried the same scenario
using gunicorn, according to documentation:
> The development server creates a new thread for each request it handles,
negating the effect of persistent connections. Don’t enable them during
development.
so I think it's not a bug, it's the expected behavior if you are using
development server.
--
Ticket URL: <https://code.djangoproject.com/ticket/30441#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.5c04ce4fa36e4f59d636a7bff29f2e2b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
