Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Azure Cosmos DB for PostgreSQL is on a retirement path and no longer recommended for new projects. Instead, use one of these two services:
For PostgreSQL workloads: use the Elastic Clusters feature of Azure Database For PostgreSQL to use the horizontal scale-out and distributed PostgreSQL features contained within the open source Citus extension. For migration guidance, see migrate to Azure Database for PostgreSQL with Elastic Cluster.
For NoSQL workloads, use Azure Cosmos DB for NoSQL for a distributed database solution that includes a 99.999% availability service level agreement (SLA), instant autoscale, and automatic failover across multiple regions.
Azure Cosmos DB for PostgreSQL allows you to stop compute on all nodes in a cluster. Compute billing is paused when cluster is stopped and continues when computer is started again.
Note
Billing for provisioned storage on all cluster nodes continues when cluster's compute is stopped.
Managing compute state on cluster nodes
You can stop compute on a cluster for as long as you need.
You can perform management operations such as compute or storage scaling, adding a worker node, or updating networking settings only on clusters with started compute.
If cluster has high availability (HA) enabled, compute start and stop operations would start and stop compute on all primary and standby nodes in the cluster. You can start and stop compute on the primary cluster and any of its read replicas independently.
Next steps
- Learn how to start and stop cluster compute in Azure Cosmos DB for PostgreSQL
- Learn about pricing options in Azure Cosmos DB for PostgreSQL