Skip to main content

Add a DB connection pool using gevent to django

Project description

travis pypi version pypi license

Another DB pool using gevent for PostgreSQL DB.

Need Django 1.5.x or newer (check settings for django >= 1.6)

Python 3 is supported, but if gevent is not installed successfully it will use eventlet.


django-db-geventpool requires psycopg2:

Patch psycopg2

Before using the pool, psycopg2 must be patched with psycogreen, if you are using gunicorn webserver, a good place is the post_fork() function at the config file:

from psycogreen.gevent import patch_psycopg     # use this if you use gevent workers
from psycogreen.eventlet import patch_psycopg   # use this if you use eventlet workers

def post_fork(server, worker):
    patch_psycopg()"Made Psycopg2 Green")


  • Set ENGINE in your database settings to:
    • ‘django_db_geventpool.backends.postgresql_psycopg2’
    • For postgis: ‘django_db_geventpool.backends.postgis’
  • Add MAX_CONNS to OPTIONS to set the maximun number of connections allowed to database (default=4)
  • If using django 1.6 or newer, add ‘CONN_MAX_AGE’: 0 to settings to disable default django persistent connection feature. And read below note if you are manually spawning greenlets
# for django 1.5.x
    'default': {
        'ENGINE': 'django_db_geventpool.backends.postgresql_psycopg2',
        'NAME': 'db',           # Or path to database file if using sqlite3.
        'USER': 'postgres',                      # Not used with sqlite3.
        'PASSWORD': 'postgres',                  # Not used with sqlite3.
        'HOST': '',                      # Set to empty string for localhost. Not used with sqlite3.
        'PORT': '',                      # Set to empty string for default. Not used with sqlite3.
        'OPTIONS': {
            'MAX_CONNS': 20

# for django 1.6 and newer version, CONN_MAX_AGE must be set to 0, or connections will never go back to the pool
    'default': {
        'ENGINE': 'django_db_geventpool.backends.postgresql_psycopg2',
        'NAME': 'db',
        'USER': 'postgres',
        'PASSWORD': 'postgres',
        'HOST': '',
        'PORT': '',
        'ATOMIC_REQUESTS': False,
        'CONN_MAX_AGE': 0,
        'OPTIONS': {
            'MAX_CONNS': 20

Using Django 1.6+ ORM when not serving requests

If you are using django 1.6+ with celery (or other), or have code that manually spawn greenlets it will not be sufficient to set CONN_MAX_AGE to 0. Django only checks for long-live connections when finishing a request - So if you manually spawn a greenlet (or have a task spawning one) its connections will not get cleaned up and will live until timeout. In production this can cause quite some open connections and while developing it can hamper your tests cases.

To solve it make sure that each greenlet either sends the django.core.signals.request_finished signal or calls django.db.close_old_connections() right before it ends

The decorator method is preferred, but the other alternatives are also valid.

from django_db_geventpool.utils import close_connection

def greenlet_worker()


from django.core.signals import request_finished
def greenlet_worker():


from django.db import close_old_connections
def greenlet_worker():

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for django-db-geventpool, version 3.2.0
Filename, size File type Python version Upload date Hashes
Filename, size django_db_geventpool-3.2.0-py3-none-any.whl (13.0 kB) File type Wheel Python version py3 Upload date Hashes View hashes
Filename, size django-db-geventpool-3.2.0.tar.gz (10.1 kB) File type Source Python version None Upload date Hashes View hashes

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page