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. You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled

You are unable to delete your Managed Service for PostgreSQL cluster in the DEAD status if it has deletion protection enabled

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

Issue descriptionIssue description

  • You are unable to delete a cluster in the DEAD status because it has deletion protection enabled.
  • Managed Service for PostgreSQL cluster switched to the UNKNOWN status right after it was created, and you are unable to delete it from the management console.

SolutionSolution

If your cluster status is DEAD or UNKNOWN, you can disable its deletion protection by running this YC CLI command:

yc managed-postgresql cluster update --deletion-protection=false <CLUSTER_ID>

Once done, you can delete this cluster as follows:

yc managed-postgresql cluster delete <CLUSTER_ID>

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket. When creating a ticket, specify your cluster ID and describe the issue in brief.

Was the article helpful?

Previous
Restoring a Managed Service for PostgreSQL cluster after running out of free storage space
Next
Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
© 2025 Direct Cursus Technology L.L.C.