Django connection guide

Django PostgreSQL Connection Settings

Translate a PostgreSQL URI into Django DATABASES settings and keep SSL options in the right place.

Use the connection value generated by Django, keep it in an environment variable, and test it before changing application code. The URI shape below is a template, not a credential to paste unchanged.

URI scheme
postgresql://
Default PostgreSQL port
5432
Credential handling
Environment variable or secret manager
First test
python manage.py dbshell

Connection string template

postgresql://USER:PASSWORD@HOST:5432/DB_NAME?sslmode=require

Replace every uppercase placeholder. Percent-encode reserved characters in URI usernames and passwords.

Environment variable

DATABASE_URL="postgresql://USER:PASSWORD@HOST:5432/DB_NAME?sslmode=require"

Where to get the Django values

Django accepts explicit NAME, USER, PASSWORD, HOST, and PORT settings. Projects that prefer one DATABASE_URL commonly parse it with a small configuration package; the built-in setting is still a mapping.

The failure mode worth checking first

Django's CONN_MAX_AGE controls persistent connections. Long-lived connections can exhaust a small hosted database, while a transaction pooler may require server-side cursors to be disabled.

Test the connection

Run a cheap read-only command before migrations or application startup. That separates network, TLS, and authentication errors from framework configuration problems.

Connection check

python manage.py dbshell

Open it in PostgresGUI

Paste the PostgreSQL URI into PostgresGUI or enter the same host, port, database, user, password, and SSL mode as separate fields. A desktop connection is useful for checking the visible schemas and role permissions before debugging the application layer.

Questions that come up

Should the connection string be committed to Git?

No. Commit an example with placeholders and load the real value from an environment variable or secret manager.

Why does a password with @ or # break the URI?

Those characters have meaning inside a URL. Percent-encode the username and password, or use a structured connection API instead of assembling a URL by hand.

Do I need sslmode=require?

Most hosted PostgreSQL services require TLS. For strict certificate and hostname verification, use sslmode=verify-full with the provider's trusted root certificate when the client supports it.

Keep going