1.19.1 — Emergency rollback of automatic PostgreSQL pooling

2026-08-25

django-mojo 1.19.1 stops automatically enabling psycopg connection pools in PostgreSQL deployments after the default caused process-local pool exhaustion in long-running ASGI, realtime, and job workers.

Fixed

• PostgreSQL aliases no longer receive a native psycopg pool unless the application explicitly configures DATABASE_POOL_OPTIONS or OPTIONS["pool"].
• Unconfigured deployments return to Django’s per-request connection behavior while retaining connection health checks.

Upgrade notes

• Redeploy or restart each application after upgrading so its Django settings are rebuilt without the implicit pool.
• Explicitly configured pools remain enabled and should be retained only where every database-using process is sized and monitored and all non-request execution paths return connections.