Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for PostgreSQL
    • Restoring a Managed Service for PostgreSQL cluster after running out of free storage space
    • You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
    • Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
    • Resolving issues with updating configurations of clusters with `local-ssd` disks
    • Resolving the issue 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` error
    • Resolving the `Unrecognized configuration parameter stats_temp_directory` error
    • Resolving the `max_connections conn_limit is too high` error
    • Resolving the `Must be superuser to create this extension` error
    • Fixing the `terminating connection due to administrator command` and `ERROR: odyssey: remote server read/write error` errors
    • Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
    • How `Conn limit` works
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Issue description
  • Diagnostics and issue reproduction
  • Solution
  1. Managed Service for PostgreSQL
  2. Restoring a Managed Service for PostgreSQL cluster after running out of free storage space

Restoring a Managed Service for PostgreSQL cluster after running out of free storage space

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Diagnostics and issue reproduction
  • Solution

Issue descriptionIssue description

  • The Managed Service for PostgreSQL cluster is running in read-only mode.
  • Any writes to the cluster's database tables fail.

Diagnostics and issue reproductionDiagnostics and issue reproduction

Go to the Monitoring tab in the management console, open the Disk capacity on primary chart, and review the ratio between the free and used bytes values to estimate the percentage of cluster storage utilization.

Note

When the storage is more than 95% full, the host will automatically switch to read-only mode. In this case, the ALTER DATABASE statement sets the DEFAULT_TRANSACTION_READ_ONLY = TRUE flag for all databases.

In this mode, any INSERT, DELETE, or UPDATE operations return an error.

SolutionSolution

You can avoid this by setting up an alert to monitor switching to read-only mode. To learn more about how to set it up, see this article on Managed Service for PostgreSQL.

Upon receiving the alert, you can recover the cluster from this mode in two ways:

  • Expanding the storage size: Managed Service for PostgreSQL will automatically disable read-only mode.
  • Manually by following these steps.

Currently, there is no way to automatically expand cluster storage.

Was the article helpful?

Previous
All solutions for Managed Service for PostgreSQL
Next
You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
© 2025 Direct Cursus Technology L.L.C.