Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
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
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Selecting the disk type during cluster creation
  • Disk space management
  • Recovering a cluster from read-only mode
  • Automatic increase of storage size
  1. Concepts
  2. Storage in Managed Service for PostgreSQL

Storage in Managed Service for PostgreSQL

Written by
Yandex Cloud
Updated at March 28, 2025
  • Selecting the disk type during cluster creation
  • Disk space management
    • Recovering a cluster from read-only mode
    • Automatic increase of storage size

Managed Service for PostgreSQL allows you to use network and local storage drives for database clusters. Network drives are based on network blocks, which are virtual disks in the Yandex Cloud infrastructure. Local disks are physically located on the database host servers.

When creating a cluster, you can select the following disk types for data storage:

  • Network HDDs (network-hdd): Most cost-effective option for clusters that do not require high read/write performance.

  • Network SSDs (network-ssd): Balanced solution. Such disks are slower than local SSD storage, but, unlike local disks, they ensure data integrity if Yandex Cloud hardware fails.

  • Non-replicated SSD (network-ssd-nonreplicated): Network disks with enhanced performance achieved by eliminating redundancy.

    You can increase the size of such disks only in increments of 93 GB.

  • Ultra high-speed network SSDs with three replicas (network-ssd-io-m3): Network disks with the same performance characteristics as non-replicated ones. This disk type provides redundancy.

    You can increase the size of such disks only in increments of 93 GB.

    Access to high-performance SSDs is available on request. Contact support or your account manager.

  • Local SSDs (local-ssd): Disks with the best performance.

    The size of such a storage can be increased:

    • For Intel Broadwell and Intel Cascade Lake: Only in 100 GB increments.
    • For Intel Ice Lake: In 368 GB increments only.

    Note

    For clusters with hosts residing in the ru-central1-d availability zone, local SSD storage is not available if using the Intel Cascade Lake platform.

Selecting the disk type during cluster creationSelecting the disk type during cluster creation

The number of hosts you can create together with a PostgreSQL cluster depends on the selected disk type:

  • You can create a cluster only with three or more hosts when using the following disk types:

    • Local SSDs (local-ssd)
    • Non-replicated SSDs (network-ssd-nonreplicated)

    This cluster will be fault-tolerant.

    Local SSD storage has an effect on how much a cluster will cost: you pay for it even if it is stopped. For more information, see Pricing policy.

  • You can add any number of hosts within the current quota when using the following disk types:

    • Network HDDs (network-hdd)
    • Network SSDs (network-ssd) * Ultra high-speed network SSDs with three replicas (network-ssd-io-m3)

For more information about limits on the number of hosts per cluster, see Quotas and limits.

Disk space managementDisk space management

When the storage is more than 97% full, the host automatically switches to read-only mode. All DBs get the DEFAULT_TRANSACTION_READ_ONLY = TRUE setting through the ALTER DATABASE query.

In this mode, the INSERT, DELETE, or UPDATE queries result in an error.

You can monitor storage utilization on cluster hosts by setting up alerts in Yandex Monitoring:

Recovering a cluster from read-only modeRecovering a cluster from read-only mode

Use one of these methods:

  • Increase the storage capacity to exceed the threshold value. Managed Service for PostgreSQL will then disable read-only mode automatically.

  • Disable read-only mode manually and free up storage space by deleting some data.

    Alert

    When doing so, make sure the amount of free disk space never reaches zero. Otherwise, since the fail-safe mechanism is disabled, PostgreSQL will crash and the cluster will stop operating.

Automatic increase of storage sizeAutomatic increase of storage size

Automatic storage size increase prevents situations where the disk runs out of free space and hosts switch to read-only mode. The storage size increases upon reaching the specified threshold percentage of the total capacity. There are two thresholds:

  • Scheduled increase threshold: When reached, the storage size increases during the next maintenance window.
  • Immediate increase threshold: When reached, the storage size increases immediately.

You can use either one or both thresholds. If you set both, make sure the immediate increase threshold is higher than the scheduled one.

If the specified threshold is reached, the storage size increases differently depending on disk type:

  • For network HDDs and SSDs, by the higher of the two values: 20 GB or 20% of the current disk size.

  • For non-replicated SSDs and ultra high-speed network SSDs with three replicas, by 93 GB.

  • For local SSDs:

    • In an Intel Broadwell or Intel Cascade Lake cluster, by 100 GB.
    • Intel Ice Lake cluster, by 368 GB.

If the threshold is reached again, the storage size will be automatically increased until it reaches the specified maximum. After that, you can specify a new maximum storage size manually.

You can configure automatic increase of storage size when creating or updating a cluster. If you set the scheduled increase threshold, you also need to configure the maintenance window schedule.

Warning

  • You cannot decrease the storage size.
  • While resizing the storage, cluster hosts will be unavailable.

Was the article helpful?

Previous
Quotas and limits
Next
Backups
© 2025 Direct Cursus Technology L.L.C.