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
  • Solution
  • If the issue persists
  1. Managed Service for PostgreSQL
  2. Resolving issues with updating configurations of clusters with `local-ssd` disks

Fixing issues with updating configurations of clusters with local-ssd

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

When trying to increase the storage size or change the host class of a Managed Service for PostgreSQL cluster with local-ssd, you get one or multiple error messages:

  • UNPROCESSABLE ENTITY
  • GATEWAY_REQUEST_ERROR

SolutionSolution

You cannot increase your cluster storage size because the cluster uses local-ssd.

Try increasing the cluster size in increments of 100 GB for Intel Broadwell and Intel Cascade Lake, or in increments of 368 GB for the Intel Ice Lake. Make sure to back up your data in advance.

For clusters with this type of disk storage, we recommend changing the host class by creating and then restoring a backup.

If the issue persistsIf the issue persists

If you need to change the configuration of an existing cluster with local-ssd, create a support ticket. Provide the following information in your ticket:

  1. ID of the Managed Service for PostgreSQL cluster for which you want to change the disk size or host class.
  2. Description of the scenario where you need to change the disk configuration of an existing cluster.

Warning

When you update the configuration of an existing cluster with local-ssd, all cluster hosts will be undergoing maintenance one by one, including the master host.

The replicas will be queued randomly. If a replica needs to be restarted during maintenance, it will become unavailable. If the master host needs restarting and becomes unavailable, one of the replicas will assume its role.

In case you use the master host's FQDN to access the cluster, such a cluster may become unavailable. To make your application continuously available, access the cluster using a specific FQDN that always points to the master host.

Was the article helpful?

Previous
Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
Next
Resolving the issue of cluster storage overflow with WAL logs
© 2025 Direct Cursus Technology L.L.C.