Please, prioritize it. Either that or at least give the option to do replication and migration to another managed db instance to be able to migrate a managed db instance without any downtime.

We switched to DO managed db to not have to maintain and implement replication over different servers but now while we are in production we noticed we are locked in and can not switch our data to another db instance without having a write lock on our application.

This is a very unpleasant situation and the first time in years we are considering leaving digitalocean because of it.

I see that in Settings the dropdown for server size does list smaller sizes, but they're greyed out because "Disk must be at least the same size". So maybe a downgrade option does exist in theory, but what's really missing is the option to upgrade CPU+RAM while keeping the same SSD size – just like droplets have. This would allow us to upgrade in place and later downgrade in place, which is currently impossible. (BTW it seems odd to me that CPU+RAM are tied to disk size. A small database might have lots of activity, and a large database might have little activity.)

Yes, this would be huge. As is, the only way to do this results in like 30 minutes of downtime while I export and import my data.

Same here — and it's not even possible to set up a continuous migration between two DO-managed postgres clusters.

Right now I'm paying 4x more for my database than I need, just because I had a traffic spike . This is not great.

+1 to add the a downgrade option as with droplets for Managed Database cluster service

I came here to ask for the same thing. And if downgrading is made available, but as with droplets it's not permitted to reduce disk size, then we'll need the same "CPU and RAM only" resize option that's available for droplets.