Resource relationships in Managed Service for PostgreSQL
The main entity used in Managed Service for PostgreSQL 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 Nebius AI 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.
-
The cost of a single-host cluster is lower, but it does not guarantee fault tolerance.
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 PostgreSQL host classes.
To manage connections and balance the cluster load, the service architecture features a built-in 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.