How to downscale a Managed Database

I have a managed Postgres Database that I temporarily scaled up to the $60/month version, to account for an expected spike. Since the spike is over, I’d like to go back down to the $30/month node plan.

However, these plans are greyed out, with the Text “Disk must be at least the same size” superimposed over the items.

Is there a way to force-migrate the database back to a lower plan without destroying my data?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


Check the below Community question that was answered on how to downgrade DB cluster using DO API/DOCTL CLI:

I hope this helps!

Regards, Rajkishore

So, the $15/month and $30/month have the same disk size (25GB), but I can’t scale down. Why? The $15/month was inactive for me =(

There is no way to force migrate a database to a lower plan that has less disk space. Because that would require a file system level of migration which we do not support. We do not analyze your FS to determine how much diskspace is used and how to do that and truncating a file system could be dangerous depending on disk space used.

You would need to create a new smaller cluster with the desired space and then import your data.

Additionally, depending on your load spikes, if it is mostly READ access you can create READ replicas to increase the capacity of your DB without having to resize to a larger size.

You can also setup a primary DB as a WRITE only server, while creating multiple READ replicas to scale your DB usage without changing disk space and giving you more flexibility in spinning up additional resources and then destroying them when they are no longer in use.