How do persistent connections interact with PostgreSQL connection pools in Django deployments?

In the Django deployment checklist, persistent database connections are recommended for production environments

• Deployment checklist | Django documentation | Django

I am curious about the interaction between persistent connections and PostgreSQL connection pools

• Django 5.1 release notes | Django documentation | Django

If a connection pool is used, are persistent connections still necessary and how do these two features work together?

Additionally, we are planning a transition to ASGI this year and noted that persistent connections have a known issue with ASGI

• #33497 (Database persistent connections do not work with ASGI in 4.0) – Django

Our PostgreSQL database is running in a separate container on the same host as our Django backend, with Django communicating over TCP via an internal Docker network. Are there any recommendations on whether to use persistent connections or a connection pool in this setup?