Cannot change compute + storage plan (Azure PostgreSQL flexible server)

Question

Cannot change compute + storage plan (Azure PostgreSQL flexible server)

NIKOLAOS ZINAS 0

I have 2 Azure PostgreSQL flexible servers with a compute size of Standard_D8s_v3 each. I decided to move to AMD Standard_D8_ads_v5.

The first DB server was successfully updated compute + storage config within some minutes.

The deployment of the second one is getting a timeout after 2 hours 2 minutes 6 seconds.

I tried it twice the 2 last nights and I 'm getting the same result.

Amira Bedhiafi 42,941 Reputation points MVP Volunteer Moderator

2025-04-09T10:50:35.0333333+00:00

Hello Nikokaos !

Thank you for posting on Microsoft Learn.

Based on what you described, your issue can be related to the region/zone having limited capacity for the AMD v5 series

You need to try during off-peak hours or check capacity in another zone/region

You may also have long-running transactions or maintenance tasks so review pg_stat_activity for long-running queries to see any replication or backup operations.

Try to create a new server with desired specs and use logical replication and use Azure Database Migration Service for minimal downtime migration

You may need to consider a smaller maintenance window by reducing connection timeouts

If the issue persists, open a support ticket :)
Anonymous

2025-04-09T11:20:14.66+00:00
Hi NIKOLAOS ZINAS,

Greetings!

We apologize for the inconvenience caused.

We would like to inform you that, since your first Azure PostgreSQL Flexible Server update to Standard_D8ads_v5 succeeded but the second one times out consistently after 2h 2m 6s, this definitely suggests something environmental or backend-related is causing the deployment hang.

Here is how to systematically troubleshoot and work around it:

Azure has known regional quota/capacity limitations, especially for newer SKUs like the D8ads_v5. Please run the below command and Replace <region> with your region (e.g., eastus, westeurope) to confirm availability.

az vm list-skus --location <region> --size Standard_D8ads_v5 --output table

Check if the second server is stuck in a Updating, Inaccessible, or Failed state. Look at the activity logs and diagnostic logs for any errors or warnings that might give you more insight into what's causing the timeout. If the server stays in an updating state for ~2 hours then times out, it’s often a backend platform lockup. If this persists, please let us know here.

Were you also upgrading storage size or IOPS? Sometimes simultaneous upgrades (compute + storage) can trigger long-lived locks or quota-related failures. Try upgrading compute only, then do storage separately after success.

Try scaling compute down to Standard_D4s_v3 or similar, then retry the upgrade to D8ads_v5.

Go to the PostgreSQL server blade > Diagnose and Solve Problems > Service Issues or Performance Troubleshooting. This may expose backend issues or stuck operations.

Verify that there are no firewall or network issues that might be affecting the deployment.

Sometimes, transient errors can cause such issues. These are short-lived and can be mitigated by retrying the operation after some time.

Please refer to the below mentioned link for more information.

https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-troubleshoot-common-connection-issues

I hope this information helps. Please do let us know if you have any further queries.
NIKOLAOS ZINAS 0 Reputation points

2025-04-09T13:01:40.82+00:00
Thank you both for your prompt responses.

Trying to answer all your points:

It doesn't look to me as a quota problem, since I tried the 1st flexible server & failed, I tried the 2nd server & succeeded and tried again the 1st server and failed again.

The SKU list command shows the following:

ResourceType Locations Name Zones Restrictions

virtualMachines westeurope Standard_D8ads_v5 1,2,3 None

There are no long-running transactions or maintenance tasks (checked with pg_stat_activity).

All my tries performed during off-peak hours.

I change only compute capacity, not storage & IOPS.

The server status is: Ready.

There are no firewall or network issues affecting the deployment.

Since this DB server handles production traffic, I don't feel confident in scaling down the capacity and possibly get stuck in this config.

Activity logs are identical in both servers (except from the failed upscaling attempts).
Anonymous

2025-04-10T09:08:39.61+00:00

Hi @NIKOLAOS ZINAS,

Thank you for the update.

Could you please share the server details via private message as it will help us conduct a more thorough investigation.

Thank you,
Anonymous

2025-04-11T08:41:03.3266667+00:00

Hi @NIKOLAOS ZINAS,

We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

If you have found a solution, we would appreciate it if you could share it with the community, as it may be helpful to others. Otherwise, please provide more details, and we will do our best to assist you further.
Anonymous

2025-04-14T08:59:20.1166667+00:00

Hi @NIKOLAOS ZINAS,

We haven’t heard from you on the last response and wanted to follow up to check if your issue has been resolved.

If you have found a solution, we would appreciate it if you could share it with the community, as it may be helpful to others. Otherwise, please provide more details, and we will do our best to assist you further.