Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for PostgreSQL
  • Getting started
    • Resource relationships
    • Planning a cluster topology
    • 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
  1. Concepts
  2. Resource relationships

Resource relationships in Managed Service for PostgreSQL

Written by
Yandex Cloud
Updated at March 20, 2024

The main entity used in the Managed Service for PostgreSQL service is a database cluster.

Each cluster consists of one or more database hosts, which are virtual machines with DBMS servers deployed on them. Cluster hosts may reside in different availability zones. You can learn more about Yandex Cloud availability zones here.

  • A cluster with multiple hosts features automatic failover: one of the replica hosts becomes master if the current master host is down.

    A replica that has an explicitly specified replication thread source cannot take the master role. To learn more, see Replication.

  • The cost of a single-host cluster is lower, but it does not guarantee fault tolerance.

  • The minimum number of hosts in a cluster depends on the selected disk type.

A cluster's computing capacity depends on its host class, which is the virtual machine template used to deploy the cluster's hosts. For a list of available host classes and their specs, see Host classes.

To manage connections and balance the cluster load, the service architecture features the Odyssey connection pooler. For more information, see Managing connections.

A cluster created in a folder can be accessed by all VMs connected to the same cloud network. For more information about networking, see the Virtual Private Cloud documentation.

Alert

The service can automatically access the system and diagnostic information of your databases to build monitoring charts and maintain your cluster health. The service never queries or uses the data you saved to the database.

Was the article helpful?

Previous
Asynchronously replicating data from PostgreSQL to ClickHouse®
Next
Active host classes
Yandex project
© 2025 Yandex.Cloud LLC