RepoJournal
Django

@django

Python's batteries-included web framework

Keep up with Django in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Python Full archive →

The Wire · Showcase

DJANGO FIXES POSTGRESQL POOL OVERRIDE BUG

By RepoJournal · Filed · About Django

Django patched a critical PostgreSQL connection pool bug that was silently breaking custom health-check configurations [ref:2].

The fix resolves ticket #37075, where users setting a custom `check` callable in `OPTIONS["pool"]` hit a TypeError because Django's PostgreSQL backend was hardcoding `check=` and then unpacking user options on top, causing a conflict [1] [2]. The patch now uses `setdefault()` to let user callables take precedence and copies `pool_options` before modification to avoid mutating your settings dict—a subtle but essential safeguard for production deployments. This is the kind of bug that silently breaks connection health checks in ways that only surface under load. A typo fix landed in the 5.2.14 release notes [3]. Build infrastructure continues monitoring across ubuntu-latest [4].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Fixed PostgreSQL pool check callable override
  2. [2] PostgreSQL pool override fix details
  3. [3] 5.2.14 release notes typo fix
  4. [4] Django ASV ubuntu-latest results

Quick answers

What shipped in Django on May 1, 2026?
Django patched a critical PostgreSQL connection pool bug that was silently breaking custom health-check configurations [ref:2]. In total, 3 commits and 1 pull requests landed.

More from @django

Daily updates, in your inbox

Follow Django

Keep up with Django in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?