[Django] #36745: native support for database connection pooling in Django.

5 views
Skip to first unread message

Django

unread,
Nov 19, 2025, 6:15:41 AM11/19/25
to django-...@googlegroups.com
#36745: native support for database connection pooling in Django.
-------------------------------------+-------------------------------------
Reporter: Pravin | Owner: Pravin
Type: New | Status: assigned
feature |
Component: Database | Version: 5.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In Django, {{{CONN_MAX_AGE }}} helps with persistent connections, but it
doesn’t provide true connection pooling like you’d get with
{{{SQLAlchemy}}} in {{{FastAPI}}} or similar frameworks.

In contrast, SQLAlchemy gives you:
- Configurable pool sizes
- Queueing and timeout behavior
- Recycle/reconnect logic
- Pool health insights

This makes a huge performance difference for apps with high concurrency,
short-lived processes (e.g. in serverless), or async workflows.
--
Ticket URL: <https://code.djangoproject.com/ticket/36745>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Nov 19, 2025, 9:21:35 AM11/19/25
to django-...@googlegroups.com
#36745: native support for database connection pooling in Django.
-------------------------------------+-------------------------------------
Reporter: Pravin | Owner: Pravin
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):

* resolution: => worksforme
* status: assigned => closed

Comment:

Connection pooling for postgres was added in 5.1, and for oracle in 5.2.
Both allow configuring pool sizes, and likely other options as well. I'm
not sure what else you are proposing to add here. New features should be
discussed first at django/new-features. Please be as specific as you can
with your proposal, and take into account what already exists.
--
Ticket URL: <https://code.djangoproject.com/ticket/36745#comment:1>
Reply all
Reply to author
Forward
0 new messages