Storage in Managed Service for PostgreSQL

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 HDD storage (network-hdd): Most cost-effective option for clusters that do not require high read/write performance.

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

• Non-replicated SSD storage (network-ssd-nonreplicated): Network SSD storage with enhanced performance but without redundancy.

  The storage size can only be increased in 93 GB increments.

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

  The size of such storage can be increased:

  • For Intel Broadwell and Intel Cascade Lake: In 100 GB increments only.
  • 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:

• With local SSDs (local-ssd) or non-replicated SSDs (network-ssd-nonreplicated), you can create a cluster with three or more hosts.

  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.

• With network HDD (network-hdd) or network SSD (network-ssd) storage, you can add any number of hosts within the current quota.

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 so that it exceeds 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 trigger threshold: a 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 of these thresholds. If both thresholds are set, 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, 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 the storage size when creating or updating a cluster. If the scheduled increase threshold is set, configure the maintenance window schedule.