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
  • Solution
  • If the issue persists
  1. Managed PostgreSQL
  2. You are unable to delete your Managed Service for PostgreSQL cluster in the Dead status if deletion protection was enabled for it

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

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

How this issue can manifest:

  • 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 immediately after creation, and you are unable to delete it from the management console.

SolutionSolution

If a cluster is in the DEAD/UNKNOWN status, you can disable deletion protection using the YC CLI:

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

Once this operation completes, you can delete this cluster in the YC CLI as well:

yc managed-postreqsl cluster delete <CLUSTER_ID>

If the issue persistsIf the issue persists

If the above actions didn't help, create a request for support.
In your request, specify the ID of the problem cluster and briefly describe the issue.

Was the article helpful?

Previous
Recovering a Managed Services for PostgreSQL cluster after its disks become Read Only
Next
Managed Service for PostgreSQL cluster switches to the Unknown state immediately after creation
Yandex project
© 2025 Yandex.Cloud LLC