• Managed Databases
• [postgresql.855c43f1f82e98a24a05998729b39a9937438c7f77af3dc0c22da5a5739f5eb7.svg]PostgreSQL
• Getting Started
  • Quickstart
• How-Tos
  • Create PostgreSQL Clusters
  • Create PostgreSQL Advanced Edition Clusters public
  • Connect to PostgreSQL Cluster
  • Secure PostgreSQL Clusters
  • Migrate Databases
  • Manage Users
    • Manage Users and Databases
    • Modify User Privileges
  • Monitor
    • Monitor PostgreSQL Performance
    • Set Up Monitoring Alerts
    • Forward Logs
    • Monitor with PMM 1-Click App
  • Scale Cluster
    • Resize Database Clusters
    • Add Standby Nodes
    • Add Read-Only Nodes
    • Manage Connection Pools
  • Manage Cluster
    • Schedule Automatic Updates
    • Tag Database Clusters
    • Relocate Database Clusters
    • Configure Custom CNAMEs
    • Fork Database Clusters
    • Restore from Backups
    • Upgrade PostgreSQL
    • Reconfigure Database Clusters
    • Migrate to Self-Managed PostgreSQL
    • Destroy Database Clusters
• Reference
  • API Reference
  • CLI Reference
  • MCP Reference
• Concepts
  • Best Practices
  • Migration Strategies
  • Shared Buffers
  • Shared Responsibility Model
• Details
  • Features
  • Pricing
  • Availability
  • Limits
  • Supported Extensions
  • Cluster Notifications
  • Service-Level Agreement
• Support

For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

PostgreSQL Limits

Last verified 18 Aug 2026

PostgreSQL is an open source, object-relational database built for extensibility, data integrity, and speed. Its concurrency support makes it fully ACID-compliant, and it supports dynamic loading and catalog-driven operations to let users customize its data types, functions, and more.

Managed Database Cluster Limits

• By default, you are limited to 10 clusters per account or team. If you reach this limit but need to create more database clusters, you can submit a request for a higher limit by clicking “Request Increase” on the window that shows when you attempt to create another cluster.

• You can only add standby nodes or reduce additional storage if the cluster’s storage size is greater than or equal to the latest backup’s size plus any data growth since then and a 20% buffer.

• You cannot delete the default database and user.

• VPC networks are only available to resources, accounts, and teams in the same region as the VPC network.

• You cannot migrate databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean using the online migration feature.

• You can only deploy standby nodes in the same region as your database cluster.

• You cannot reconfigure or resize a cluster while upgrading it.

• You cannot disable or customize automatic cluster notification emails.

• You currently cannot add IPv6 rules to a database cluster’s trusted sources.

• By default, database clusters only support up to 2,000 IP addresses as trusted sources. Different types of resources add varying numbers of IP addresses to your cluster. For example, Droplets typically have two IP addresses, one public and one private, both of which count towards the 2,000-address maximum. To add more than 2,000 IP addresses, contact support.

• Point-in-time-recovery (PITR) is limited to the last 7 days.

• When you restore from a backup, you must restore to a new node and re-add any read-only or standby nodes. See How to Restore from Backups for details.

PostgreSQL Limits

• Each cluster is limited to 3 nodes.

• You can’t choose a custom number of nodes. Node options depend on the selected edition, configuration, and high availability settings.

• Basic - Shared CPU plans aren’t available for Advanced Edition.

• Premium AMD (Disk: NVMe) is only available for Standard Edition clusters using Basic - Shared CPU.

• Standby nodes are supported for PostgreSQL clusters on most editions and configurations, except select 1 vCPU Shared CPU plans.

• PostgreSQL HNSW indexes are memory-bound. For datasets that outgrow RAM, use pgvectorscale’s StreamingDiskANN index, which supports disk-resident vector search. For more information, see Use pgvectorscale.

• Standard Edition supports PostgreSQL v14, v15, v16, v17, and v18. See the following table for EOL (End of Life) dates:

  PostgreSQL Version	EOL Date
  14	2026-11-12
  15	2027-11-12
  16	2028-11-09
  17	2029-11-08
  18	2030-11-08

• Advanced Edition supports PostgreSQL v16, v17, and v18. New Advanced Edition clusters default to v18. See How to Create PostgreSQL Advanced Edition Clusters.

• Advanced Edition clusters receive automatic resource usage email notifications for low disk space only. Standard Edition clusters receive all automatic cluster notifications. See Cluster Notifications.

• We only support selected PostgreSQL extensions. See Supported PostgreSQL Extensions for a comprehensive list.

• The number of available backend connections varies by plan size:

  Plan Size	Available Backend Connections
  1 GiB RAM	22
  2 GiB RAM	47
  4 GiB RAM	97
  8 GiB RAM	197
  16 GiB RAM	397
  32 GiB RAM	797
  64 GiB RAM	997
  128 GiB RAM	997
  160 GiB RAM	997
  192 GiB RAM	997
  256 GiB RAM	997

  For databases with high connection requirements, we recommend using connection pooling, backed by PgBouncer. Each database cluster supports 21 PgBouncer pools and up to 1,000 connections, depending on the plan size. If you need more pools or connections than this, contact support.

• To maintain cluster stability, users cannot access the superuser role. External monitoring tools such as Percona Monitoring and Management (PMM) can use predefined PostgreSQL roles instead; see Configure a PMM Monitoring User.

• You cannot migrate a cluster using the default postgres user.

• We do not currently support migrating managed database clusters on DigitalOcean to other managed database clusters on DigitalOcean using continuous migration. For example, you cannot migrate a managed database cluster from one DigitalOcean account to another. However, you can migrate with a dump.

Known Issues

Managed Database Cluster Known Issues

• You must use a third-party client to manage access control lists (ACLs). You can add users and databases from the DigitalOcean Control Panel.

• You can’t use DigitalOcean’s Cloud Firewalls with managed databases. Until support is available, you can restrict access to nodes by their incoming IPv4 addresses.

• Point-in-time-recovery (PITR) operations are limited to the last 7 days. The date picker doesn’t restrict you from choosing an earlier date; you receive an error if you try to recover from a date outside of the 7-day window.

PostgreSQL Known Issues

• Alerting on PostgreSQL metrics is not yet available.

• Additional storage can cause slight performance degradation in database clusters.

---