django-db-connection-pool
Database connection pool component library for Django
Decision gist · record as of 2026-08-14
Yes, if you run Django with a database that benefits from connection pooling (especially Oracle, PostgreSQL, or MySQL under load) and can tolerate the aging maintenance status. The package is stable and has no known vulnerabilities, but expect slower response to new issues. Not necessary for low-traffic or development-only projects where connection overhead is negligible.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Django and one of SQLAlchemy-compatible database drivers (mysql-connector-python, cx_Oracle, psycopg2, or JPype for JDBC).
- JDBC backend requires JAVA_HOME and CLASSPATH environment variables to be set.
- Low install friction; pure Python wheel.
License · maintenance · safety
permissive license (permissive) — MIT License permits commercial and private use, modification, and redistribution with minimal restrictions. Requires only that the license notice be included in copies or substantial portions of the software.
last release 2025-05-05 (466 days) · last repo commit 2025-05-05 · 248 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 199,818 downloads/mo, #9,700 on PyPI
Alternatives
Verify before relying
pip install django-db-connection-pool[mysql]
# In Django settings.py
DATABASES = {
'default': {
'ENGINE': 'dj_db_conn_pool.backends.mysql',
'POOL_OPTIONS': {
'POOL_SIZE': 10,
'MAX_OVERFLOW': 10
}
}
}- Performance impact of connection pooling on typical Django workloads compared to standard backends
- Compatibility with Django versions beyond the current release cycle
- Thread-safety guarantees under high concurrency in production deployments
What it is and what it does
django-db-connection-pool replaces Django's standard database backends with pooled alternatives that reuse connections across requests rather than creating new ones each time. It wraps SQLAlchemy's connection pool implementation and supports MySQL, Oracle, PostgreSQL, and JDBC-based databases (Oracle and OceanBase). The package is designed to work correctly in multiprocess environments like uWSGI, where each worker process maintains its own independent pool.
You configure it by changing your Django DATABASES ENGINE setting from the standard backend (e.g., `django.db.backends.mysql`) to the pooled equivalent (e.g., `dj_db_conn_pool.backends.mysql`), then optionally tune pool behavior via POOL_OPTIONS (pool size, overflow limit, connection recycling interval). The pool manages connection lifecycle automatically; you use Django's ORM and raw queries exactly as normal.
Use it for
- High-traffic Django applications where connection creation overhead becomes a bottleneck and connection reuse would reduce latency
- Multiprocess deployments (uWSGI, Gunicorn with multiple workers) where each process needs its own pool to avoid connection conflicts
- Projects using Oracle or PostgreSQL that benefit from tunable pool parameters like connection recycling for long-lived connections
- JDBC-based database access (Oracle via JDBC, OceanBase) when native Python drivers are unavailable or unsuitable
- Applications with bursty traffic patterns where MAX_OVERFLOW allows temporary connection spikes beyond the base pool size
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you run Django with a database that benefits from connection pooling (especially Oracle, PostgreSQL, or MySQL under load) and can tolerate the aging maintenance status.
The package is stable and has no known vulnerabilities, but expect slower response to new issues. Not necessary for low-traffic or development-only projects where connection overhead is negligible.
Install
django-db-connection-pool on PyPI
Before you install
Low install friction; pure Python wheel. Maintenance status is aging—last commit was 466 days ago, though the repository remains active and the package is marked Production/Stable. Suitable for established projects but may see delayed responses to new issues.
Requires Django and one of SQLAlchemy-compatible database drivers (mysql-connector-python, cx_Oracle, psycopg2, or JPype for JDBC). JDBC backend requires JAVA_HOME and CLASSPATH environment variables to be set.
License in practice
MIT License permits commercial and private use, modification, and redistribution with minimal restrictions. Requires only that the license notice be included in copies or substantial portions of the software.
Quickstart
pip install django-db-connection-pool[mysql]
# In Django settings.py
DATABASES = {
'default': {
'ENGINE': 'dj_db_conn_pool.backends.mysql',
'POOL_OPTIONS': {
'POOL_SIZE': 10,
'MAX_OVERFLOW': 10
}
}
}
Verify before relying
- Performance impact of connection pooling on typical Django workloads compared to standard backends
- Compatibility with Django versions beyond the current release cycle
- Thread-safety guarantees under high concurrency in production deployments
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.0 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 3 packagesDjangoSQLAlchemysqlparams |
| Maintenance | Aging 466 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 199,818 / month, #9,700 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableEnvironment :: Web EnvironmentFramework :: DjangoIntended Audience :: DevelopersLicense :: OSI Approved :: MIT LicenseOperating System :: OS IndependentProgramming Language :: Python :: 3Topic :: Software Development :: Libraries :: Python Modules |
Evidence: django_db_connection_pool-1.2.6-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “mysql oracle postgresql connection pool”
- django-db-connection-poolProvides connection pooling for Django database backends (MySQL,…
- sqlalchemy-jdbcapiSQLAlchemy dialect for JDBC and ODBC database connections with…
- databasesProvides async database access for PostgreSQL, MySQL, and SQLite…
Give your agent the search over MCP, or paste the wish link into any chat.
More Python Modules packages
Converts domain names between Unicode and ASCII-compatible encoding (Punycode) according to IDNA 2008 and Unicode Technical Standard 46, with security validation and broader script coverage than the standard library.
Install it if you work with internationalized domain names, need to validate domains, or use HTTP clients that depend on it transitively.
Setuptools is a Python build backend and package management tool that handles building, distributing, and installing Python packages, including support for C/C++ extension modules.
PyYAML parses and emits YAML 1.1 data format, enabling serialization and deserialization of configuration files and Python objects to and from human-readable YAML text.
Pydantic validates Python data structures against type hints, coercing and checking input at runtime to ensure it matches a declared schema.
Provides reusable metadata objects for use with PEP-593 `typing.Annotated` to express common constraints like bounds, collection sizes, and predicates on types.
Install it if you use or build libraries that need to express type constraints in a standardized, inspectable way—or if you want to annotate your own types with…
Provides runtime tools to inspect and introspect Python type annotations, enabling programmatic examination of type hints at execution time.
See also dj-database-url · sqlalchemy-jdbcapi · DBUtils · psycopg2-pool · psycopg-pool · django-db-geventpool · django-sequences · pondpond · databases · connection_pool