How to Create PostgreSQL Advanced Edition Clusterspublic

Validated on 27 Apr 2026 • Last edited on 27 Apr 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.

DigitalOcean PostgreSQL Advanced Edition is the latest generation of Managed PostgreSQL, with a consensus-based HA manager for cluster coordination and a connection pooler for routing.

PostgreSQL Advanced Edition targets highly available workloads and supports vertical and horizontal scaling of database nodes as your workload grows.

High Availability Architecture

PostgreSQL Advanced Edition runs PostgreSQL on managed cluster nodes. A consensus-based HA manager runs on the nodes, tracks cluster membership, automatically elects the primary after failures, and coordinates failover.

PostgreSQL Advanced Edition uses a connection pooler to provide clients with a single, stable service endpoint. The pooler sits in front of the database nodes, tracks which are healthy, pools connections, and routes them to the current primary. When the HA manager moves the primary after a failover, it shifts routing so that the hostname and port can stay the same while the backing node changes.

During a failover, active connections to the former primary may be interrupted, but applications that reconnect to the same endpoint are routed to the new primary automatically.

Key Differences

The following table shows the key differences between PostgreSQL Standard and Advanced Edition clusters.

Feature PostgreSQL Advanced Edition PostgreSQL Standard Edition
Replication model Streaming replication with consensus-based leader election Primary–replica streaming replication
Failover Automatic leader election using consensus protocol; connection pooler detects the new primary and routes traffic to it without a DNS cutover wait Automatic primary promotion; same connection settings; some clients may still reach a former primary until DNS updates propagate (TTL)
Connection endpoint Connection pooler fronts the cluster; the backing node can change without the client changing parameters Same hostname and parameters; which node those names resolve to after failover depends on DNS timing (possible stale answers or unreachable database until propagation completes)
Topology HA-managed cluster with connection pooler Primary–replica
Node configurations 1-, 2-, or 3-node 1-, 2-, or 3-node
Best for Workloads that benefit from pooled, proxy-fronted endpoints and managed HA General-purpose managed PostgreSQL workloads

Overview

Pricing

The Control Panel shows the total monthly cost when you create a cluster. Storage is billed at the same rate regardless of edition. Advanced Edition compute is priced higher than comparable Standard Edition plans, and your total depends on your plan and storage configuration. Pricing may change before general availability.

Features

  • Vertical scaling: Resize nodes to a larger plan (more CPU, memory, or storage). The connection pooler manages traffic during the transition, reducing disruption.
  • Horizontal scaling: Add or remove database nodes to match workload demand.
  • Physical backups: Backups use physical backup and restore, which improves reliability and performance for large datasets.

Availability

PostgreSQL Advanced Edition is available in all regions.

Feedback and Support

PostgreSQL Advanced Edition is in public preview. Public previews receive full support. We expect but do not guarantee that public previews perform for production-level workloads.

Our terms of service govern your use of DigitalOcean and cover details of eligibility, content, use, payments and billing, and warranties.

Usage of Advanced Edition during public preview is also subject to the Managed Databases Advanced Edition preview terms.

Create a PostgreSQL Advanced Edition Cluster

To create a PostgreSQL Advanced Edition cluster, go to the Databases page, then click Create Database.

Choose a Database Engine

On the Create Database Cluster page, under Choose a database engine, select PostgreSQL, then choose a version. The database engine can’t be changed after creation.

The database engine selection portion of the database create page

Choose an Edition

Under Choose an edition, select Advanced Edition. The edition can’t be changed after creation.

The Choose an edition section of the databases create page

Choose a Database Configuration

In the Choose a database configuration section, select one of the following options:

  • General Purpose: Balanced vCPU-to-RAM ratio. Suitable for a broad range of workloads.
  • Storage-Optimized: Higher RAM-to-vCPU ratio with more storage and concurrent connections. Recommended for most database workloads.

Under Select a plan, choose an option. Each option shows its combined monthly cost and included resources, such as vCPUs and memory.

After creation, you can increase your cluster’s compute size at any time.

Choose a Storage Size

In the Choose a storage size section, you can increase storage using the up arrow or by entering a value in 10 GiB increments, up to the maximum shown under Storage range.

After creation, you can increase storage at any time.

In the Autoscale storage section, select Enable Storage Autoscaling to automatically increase storage when disk utilization on any node in the cluster reaches the specified threshold. The threshold is based on the worst-performing node in the cluster, not the average across nodes. Click Customize to set a custom threshold and storage increment. The system bills this increase as additional storage.

The storage autoscaling section

Autoscaling takes several minutes, depending on the cluster size. It runs without downtime, and you do not need to take any action.

Note
When autoscaling occurs, the specified storage increment is added to each node in the cluster, not distributed across the cluster. The total added storage is the increment multiplied by the number of nodes.

In the Maximize uptime for critical workloads section, you can add up to two standby nodes. Additional standby nodes increase cluster resilience by providing more promotion candidates during a failure.

Choose a Datacenter Region

In the Choose a datacenter region section, select a datacenter for your cluster.

The datacenter selection portion of the databases create page

The list shows the datacenters where you currently have the most resources, with the number of resources shown to the right as X resources. Hover over this text to see the specific resources in that datacenter.

For the best performance, create your database in the same datacenter as your other DigitalOcean resources. After creation, you can relocate your cluster to another datacenter.

Note
Each region has one or more datacenters, each with its own VPC network. Keeping resources in the same datacenter ensures they share the private networking interface, which reduces latency and prevents traffic from being routed over the public internet.

Finalize and Create

In the Finalize and Create section, enter a unique name for the cluster and select a project to add it to. After creation, you can move the cluster to another project, but its name can’t be changed.

The Finalize and Create section of the Create a database page

When finished, click Create Database Cluster.

Clusters typically take five minutes or more to provision, but you can complete important configuration tasks such as restricting inbound connections while you wait.

Limitations

  • Features, behavior, limits, and supported plans may change during the public preview.

  • Advanced Edition currently does not support the following features that are available in Standard:

    • Online data import tool
    • Read-only connections for standby nodes
    • Scale down cluster compute and storage
    • Migrate clusters to a different region

We can't find any results for your search.

Try using different keywords or simplifying your search terms.