Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for PostgreSQL
  • Getting started
    • Resource relationships
    • Planning a cluster topology
    • High availability clusters
    • Networking in Managed Service for PostgreSQL
    • Quotas and limits
    • Storage in Managed Service for PostgreSQL
    • Backups
    • Assigning roles
    • Managing connections
    • Replication
    • Maintenance
    • Supported clients
    • PostgreSQL settings
    • Indexes
    • SQL command limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Number and placement of cluster hosts
  • Replication settings
  • Maintenance settings
  • Other settings
  1. Concepts
  2. High availability clusters

High availability of a Managed Service for PostgreSQL cluster

Written by
Yandex Cloud
Updated at December 22, 2025
  • Number and placement of cluster hosts
  • Replication settings
  • Maintenance settings
  • Other settings

High availability of a Managed Service for PostgreSQL cluster depends on the number and placement of its hosts, replication settings, and other cluster parameters.

Number and placement of cluster hostsNumber and placement of cluster hosts

A cluster may consist of one or more hosts.

A single-host cluster does not provide high availability. If the master host VM fails, your cluster will be unavailable for reading and writing until the VM recovers completely. Single-host clusters are not covered by the Service level agreement (SLA).

Warning

We do not recommend creating a single-host cluster.

A cluster with two hosts located in different availability zones is considered highly available and is subject to the SLA. This option is suitable for medium-sized applications in a production environment. The default cluster configuration offered in the management console includes two hosts.

A cluster with three or more hosts located in three different availability zones is considered highly available and is subject to the SLA. Such clusters are suitable for production environments subject to high availability and performance requirements.

For more information, see Planning cluster topology.

Replication settingsReplication settings

High availability is achieved through replication and master failover, which work as follows:

  • Clusters uses streaming replication. Each replica host receives a replication stream from another host, typically the master. Managed Service for PostgreSQL manages replication streams in the cluster automatically, but you can manage them manually if you need to. When you set the replication source manually, the replicas will have a number of limitations.
  • The cluster uses automatic master selection and failover in case the current master fails.
  • If you use public access for the host, you must also enable it for the replicas, otherwise the cluster will become unavailable following master failover.

Warning

Using a special FQDN simplifies application development, but your cluster will be unavailabile during master failover. To quickly switch to a new master, you need to implement monitoring of master replacement on the application side.

Maintenance settingsMaintenance settings

During maintenance, a cluster with two or more hosts may not be available for writes until the master automatically fails over. A single host cluster is completely unavailable during maintenance. Therefore, consider the expected load on your cluster when selecting the maintenance day and hour.

When updating a PostgreSQL version, a cluster with three or more hosts is unavailable for writes but has at least one readable replica. A cluster with one or two hosts is completely unavailable during PostgreSQL version updates. Consider the expected load on your cluster when planning updates.

Other settingsOther settings

The following settings may also affect cluster availability:

  • Backup settings.
  • Storage disk type you selected.
  • Host classes.
  • Connection pooler's operation mode and settings.
  • Quotas and limits.
  • Write-ahead log (WAL) settings.

Was the article helpful?

Previous
Planning a cluster topology
Next
Networking in Managed Service for PostgreSQL
© 2025 Direct Cursus Technology L.L.C.