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
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
All solutions
    • All solutions for Managed PostgreSQL
    • Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only
    • You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it
    • Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation
    • Resolving issues with updating configurations of clusters with local-ssd disks
    • Resolving the consequences of cluster storage overflow with WAL logs
    • Resolving the psql error "could not translate host name to address nodename nor servname provided, or not known"
    • Resolving the error Unrecognized configuration parameter "stats_temp_directory"
    • Resolving the "max_connections conn_limit is too high" error
    • Resolving the "422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries" error
    • Understanding the Conn limit parameter
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Issue description
  • Troubleshooting and reproducing issues
  • Solution
  1. Managed PostgreSQL
  2. Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only

Restoring health of a Managed Services for PostgreSQL cluster after its disks become Read Only

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Troubleshooting and reproducing issues
  • Solution

Issue descriptionIssue description

The storage in your Managed Services for PostgreSQL cluster has become read-only.
New data is not written to your cluster's database tables.

Troubleshooting and reproducing issuesTroubleshooting and reproducing issues

Go to the Monitoring tab in the cluster management interface, open the Disk capacity on primary chart, and look up the ratio between the free and used bytes values.
This way, you can evaluate the percentage ratio of the cluster storage utilization.

When the storage is more than 97% full, the host automatically switches to read-only mode.
For all databases in this case, DEFAULT_TRANSACTION_READ_ONLY is set to TRUE using the ALTER DATABASE query.

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

SolutionSolution

You can avoid this by setting an alert on switching over to read-only mode. You can find the steps to set up such an alert here.

When you receive the alert, you can use two methods to disable this mode in your cluster:

  • By expanding the storage size: in this case, the service will automatically disable the read-only mode.
  • Manually, by following this guide.

Currently, there is no automatic method to expand cluster storage.

Was the article helpful?

Previous
All solutions for Managed PostgreSQL
Next
You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it
Yandex project
© 2025 Yandex.Cloud LLC