I cannot scale the Postgres Flexible server up.

Question

I cannot scale the Postgres Flexible server up. Options to scale it on Compute + Storage do not show up. Is there any reason for that?

Answer 1

If you cannot see the options to scale your Azure Database for PostgreSQL flexible server under Compute + Storage, there could be several reasons:

1. Permissions: Ensure that you have at least READ permission on the owning resource group. Without the necessary permissions, the scaling options may not be visible.
2. Server State: The server might be in a state that does not allow scaling. For example, if there are ongoing operations or maintenance tasks, scaling options may be temporarily unavailable.
3. Resource Limitations: Check if your current configuration meets the requirements for scaling. There may be limits on the number of vCores or storage size based on your subscription or the specific tier you are using.
4. Region Restrictions: Some features may not be available in certain regions. Make sure that the region where your server is deployed supports the scaling options you are trying to use.
5. Functional Limitations: There are functional limitations regarding scaling operations. For instance, scaling up the server storage requires a server restart, and you cannot scale down storage once it has been increased.

If you continue to experience issues, consider checking the Azure portal for any notifications or errors that might provide more context on the problem.

Answer 2

Hi Julian Urrego,
Thank you for reaching out to Microsoft QA!
When the Compute + Storage blade doesn’t show the expected options, it’s usually because the server or your access is in a state where scaling isn’t allowed. Please go through the checks below and let me know what you find:

Server state:

Open the server in the Azure portal and confirm it is in a Running state.

If the server is starting, stopping, updating, or under maintenance, scaling options will be temporarily unavailable until that operation completes.

Permissions:

Verify the role assigned to your account on the subscription or resource group.

You need a role with write permissions on the server (for example, Contributor, Owner, or a suitable custom role). With only Reader access you can open the blade, but you won’t be able to see or change configuration values.

Existing operations:

Check the Activity log for the server and the portal Notifications to see whether any other operations are currently running (start/stop, restore, storage increase, HA change, etc.).

If there is an active operation, wait for it to finish and then try the Compute + Storage blade again.

Scaling limits and behavior:

Confirm that the target compute and storage values are within the supported limits for your tier and region.

Keep in mind that storage can only be increased; it cannot be reduced, so smaller sizes will not appear as options.

Using the Azure portal:

In the portal, navigate to your PostgreSQL flexible server and open Compute + Storage.

Look for the Configuration section; if it doesn’t load, try refreshing the blade, signing out and back in, or testing in a different browser / InPrivate window to rule out a UI caching issue.

If none of these seem to resolve your issue, you might want to provide a bit more detail. Here are some follow-up questions that could help:

What specific actions have you attempted when trying to scale the server?

Are there any error messages that pop up when you try to access the scaling options?

Is your server currently experiencing any heavy utilization or is it under maintenance?

What specific region is your server deployed in?

Hope this helps!
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.