Connection limits per plan for Aiven for PostgreSQL®

Find the default max_connections value for each Aiven for PostgreSQL® plan, and learn how to change it for your service.

By default, Aiven for PostgreSQL® instances limit the number of allowed connections to make sure that the database is able to serve them all.

`max_connections` defaults

Default values of the max_connections setting vary according to the service plan:

Plan	Max connections
Developer	15
Free	20
Hobbyist	25
Startup/Business/Premium-4	100
Startup/Business/Premium-8	200
Startup/Business/Premium-16	400
Startup/Business/Premium-32	800
Startup/Business/Premium-64 and above	1000

note

Aiven can utilize any number of the connections for managing the service.

Aiven for PostgreSQL doesn't apply a fixed per-GiB connection formula (for example, 100 connections per GiB of RAM). The plan-based defaults in the preceding table are the only default values, and there's no separate max_connection_limit setting. max_connections is the only parameter that controls the total number of connections for your service.

tip

During a connection-exhaustion incident, use an AI assistant connected to Aiven MCP to check current connection usage against the configured limit. For example:

Show the current connection count on my-pg-service, grouped by role and state, and compare the total with max_connections.

Increase or decrease `max_connections`

To increase or decrease the number of allowed connections for your service, set the max_connections parameter, which accepts a value from 25 to 60000.

note

Changing max_connections causes a service restart. If your service has a read replica, increase the replica's value first. After that change is applied, increase the primary service's value.

Console
CLI
Terraform
API

Log in to Aiven Console, and go to your organization > project > Aiven for PostgreSQL service.
On the Overview page of your service, select Service settings from the sidebar.
On the Service settings page, go to the Advanced configuration section, and select Configure.
Select Add configuration options, add the max_connections parameter, set the value, and select Save configuration.

Run the service update command:

avn service update SERVICE_NAME -c pg.max_connections=VALUE

Set max_connections in the pg_user_config.pg block of the aiven_pg resource:

resource "aiven_pg" "example" {
  # ...
  pg_user_config {
    pg {
      max_connections = 1000
    }
  }
}

Call the ServiceUpdate endpoint:

curl --request PUT \
  --url https://api.aiven.io/v1/project/PROJECT_NAME/service/SERVICE_NAME \
  -H 'Authorization: Bearer BEARER_TOKEN' \
  -H 'content-type: application/json' \
  --data '{
      "user_config": {
          "pg": {
              "max_connections": 1000
          }
      }
  }'

Use connection pooling

When several clients or client threads are connecting to the database, Aiven recommends using connection pooling to limit the number of actual backend connections. Connection pooling is available in all Aiven for PostgreSQL Startup, Business, and Premium plans, and can be configured in the console.

max_connections defaults​

Increase or decrease max_connections​

Use connection pooling​

`max_connections` defaults

Increase or decrease `max_connections`

Use connection pooling