$ the-wire · showcase
DJANGO FIXES POSTGRESQL POOL OVERRIDE BUG
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
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].
Action items
References
- [1] Fixed PostgreSQL pool check callable override
- [2] PostgreSQL pool override fix details
- [3] 5.2.14 release notes typo fix
- [4] Django ASV ubuntu-latest results
