RepoJournal
Django

@django

Python's batteries-included web framework

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

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].

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

FAQ

What changed in Django on May 1, 2026?
Django patched a critical PostgreSQL connection pool bug that was silently breaking custom health-check configurations .
What should Django teams do about it?
Pull the PostgreSQL pool override fix into your next deploy if you're using custom health-check callables • Review your PostgreSQL OPTIONS["pool"] configuration if you've had unexplained connection timeouts

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.