Connection management
Using your connections resourcefully
Connections
Every Compute Add-On has a pre-configured direct connection count and Supavisor pool size. This guide discusses ways to observe and manage them resourcefully.
Configuring Supavisor's pool size
You can change how many database connections Supavisor can manage by altering the pool size in the "Connection pooling configuration" section of the Database Settings:
The general rule is that if you are heavily using the PostgREST database API, you should be conscientious about raising your pool size past 40%. Otherwise, you can commit 80% to the pool. This leaves adequate room for the Authentication server and other utilities.
These numbers are generalizations and depends on other Supabase products that you use and the extent of their usage. The actual values depend on your peak connection usage. For instance, if you were only using 80 connections in a week period and your database max connections is set to 500, then realistically you could allocate the difference of 420 (minus a reasonable buffer) to service more demand.
Monitoring connections
Capturing historical usage
Supabase offers a Grafana Dashboard that records and visualizes over 200 project metrics, including connections. For setup instructions, check the metrics docs.
Its "Client Connections" graph displays connections for both Supavisor and Postgres
Observing live connections
pg_stat_activity is a special view that keeps track of processes being run by your database, including live connections. It's particularly useful for determining if idle clients are hogging connection slots.
Query to get all live connections:
_14SELECT_14 pg_stat_activity.pid as connection_id,_14 ssl,_14 datname as database,_14 usename as connected_role,_14 application_name,_14 client_addr as IP,_14 query,_14 query_start,_14 state,_14 backend_start_14FROM pg_stat_ssl_14JOIN pg_stat_activity_14ON pg_stat_ssl.pid = pg_stat_activity.pid;
Interpreting the query:
| Column | Description |
|---|---|
| connection_id | connection id |
| ssl | Indicates if SSL is in use |
| database | Name of the connected database (usually postgres) |
| usename | Role of the connected user |
| application_name | Name of the connecting application |
| client_addr | IP address of the connecting server |
| query | Last query executed by the connection |
| query_start | Time when the last query was executed |
| state | Querying state: active or idle |
| backend_start | Timestamp of the connection's establishment |
The usename can be used to identify the source:
| Role | API/Tool |
|---|---|
| supabase_admin | Used by Supabase to configure projects and for monitoring |
| authenticator | Data API (PostgREST) |
| supabase_auth_admin | Auth |
| supabase_storage_admin | Storage |
| supabase_realtime_admin | Realtime |
| supabase_replication_admin | Synchronizes Read Replicas |
| postgres | Supabase Dashboard and External Tools (e.g., Prisma, SQLAlchemy, PSQL...) |
| Custom roles defined by user | External Tools (e.g., Prisma, SQLAlchemy, PSQL...) |