I am trying to scale Azure Postgresql Flexible Server, but it just rolling in Started stage and nothing is happening. What could cause this? Server is working fine but we need more cores to keep up with demand, but currently unable to scale up.

Question

I am trying to scale Azure Postgresql Flexible Server, but it just rolling in Started stage and nothing is happening. What could cause this? Server is working fine but we need more cores to keep up with demand, but currently unable to scale up.

Mikko Uusitalo 25

I have tried to shutdown, restart and then tried to scale but the same problem. It is stuck in started stage.

Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-09T22:55:18.3033333+00:00

Hi @ Mikko Uusitalo

Thank you for reaching out regarding the issue with scaling your Azure PostgreSQL Flexible Server. I understand how important it is to ensure smooth performance and scalability, and I’d be happy to assist you.

Based on similar cases, here are some possible reasons why the server might be stuck in the "Started" state while scaling:

Storage Limit Reached – If the server has reached its maximum storage capacity, it may prevent scaling operations. Please check the current storage usage and consider a Point-In-Time Restore (PITR) if needed.

WAL Logs Delay – PostgreSQL uses Write-Ahead Logging (WAL), and a large number of logs could extend recovery time, delaying scaling completion.

Scaling Restrictions – Azure PostgreSQL Flexible Server has certain scaling constraints. Some changes may require a restart before taking effect.

You’ve mentioned trying shutdowns and restarts. If the issue persists, I recommend checking storage availability or performing a Point-In-Time Restore to create a fresh instance with the required resources.

If none of these steps resolve the issue, please share the details asked in the private message so that we can help you troubleshooting the issue.
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-10T19:41:50.4666667+00:00

Hi @ Mikko Uusitalo

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mikko Uusitalo 25 Reputation points

2025-06-11T09:06:32.4133333+00:00

Hello @Sai Raghunadh M ,

Nice to meet you! I am sorry not answering you sooner. I am currently at Finnish timezone so I have not had the time to answer to you.

I have checked that the storage limit has not been reached but have not tried point in time restoration because that means that we have to have scheduled downtime with our service. Is there some other config preventing the server to scale out? Is there some way to see if the scaling halts and what is causing it?
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-11T17:25:47.1566667+00:00

Hi @ Mikko Uusitalo

Nice to meet you.

Thank you for reaching out. I understand how critical seamless scaling is for your service, and I appreciate your patience.

Based on our investigation, the issue could be related to several factors:

Configuration Constraints: Some settings require a restart for scaling changes to take effect.

Resource Limits: While storage isn’t an issue, it’s worth checking if CPU or memory usage is hitting any thresholds.

Logs & Metrics Analysis: Reviewing logs and monitoring metrics in the Azure portal may reveal specific blockers affecting the scaling process.

Scaling Restrictions: Depending on the selected tier, there could be predefined limits on how much you can scale.

To move forward, I recommend checking log analytics for scaling-related events and reviewing Azure monitoring metrics. Please share the details asked in private message.

I’m happy to guide you.
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-12T16:44:26.1333333+00:00

Hi @ Mikko Uusitalo

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mihir Saxena 0 Reputation points Microsoft External Staff Moderator

2025-06-13T05:28:06.85+00:00
Hi @Mikko Uusitalo

Scaling issues in Azure Database for PostgreSQL Flexible Server especially when it gets stuck in the "Starting" or "Updating" state can be caused by various underlying factors.

Below is a step-by-step breakdown of causes and recommended resolution steps:

-- Ongoing or Failed Prior Operations:

Scaling won’t proceed if a previous operation (e.g., maintenance, backup, parameter update) is still running or failed.

Check via Activity Log and Look for operations in InProgress or Failed state with error messages.

Azure Portal > Monitor > Activity Log

-- Unsupported Scaling Path:

Cross-tier scaling often requires a restart or fails silently. Scale within the same tier first (e.g., GP 2 vCore to GP 4 vCore).

az postgres flexible-server update \ --resource-group <rg> \ --name <server> \ --sku-name Standard_D4s_v3

-- Maintenance or Engine Upgrade in Progress:

az postgres flexible-server show --resource-group <rg> --name <server> --query "maintenanceWindow"

-- VNet or NSG Misconfiguration:

If in a VNet, check that NSGs and route tables allow required traffic for Azure control plane.

-- Resource Locks or Policy Restrictions:

az lock list --resource-group <rg>

Check for reference - az postgres flexible-server

Your answer

Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-09T22:55:18.3033333+00:00

Hi @ Mikko Uusitalo

Thank you for reaching out regarding the issue with scaling your Azure PostgreSQL Flexible Server. I understand how important it is to ensure smooth performance and scalability, and I’d be happy to assist you.

Based on similar cases, here are some possible reasons why the server might be stuck in the "Started" state while scaling:

Storage Limit Reached – If the server has reached its maximum storage capacity, it may prevent scaling operations. Please check the current storage usage and consider a Point-In-Time Restore (PITR) if needed.

WAL Logs Delay – PostgreSQL uses Write-Ahead Logging (WAL), and a large number of logs could extend recovery time, delaying scaling completion.

Scaling Restrictions – Azure PostgreSQL Flexible Server has certain scaling constraints. Some changes may require a restart before taking effect.

You’ve mentioned trying shutdowns and restarts. If the issue persists, I recommend checking storage availability or performing a Point-In-Time Restore to create a fresh instance with the required resources.

If none of these steps resolve the issue, please share the details asked in the private message so that we can help you troubleshooting the issue.
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-10T19:41:50.4666667+00:00

Hi @ Mikko Uusitalo

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mikko Uusitalo 25 Reputation points

2025-06-11T09:06:32.4133333+00:00

Hello @Sai Raghunadh M ,

Nice to meet you! I am sorry not answering you sooner. I am currently at Finnish timezone so I have not had the time to answer to you.

I have checked that the storage limit has not been reached but have not tried point in time restoration because that means that we have to have scheduled downtime with our service. Is there some other config preventing the server to scale out? Is there some way to see if the scaling halts and what is causing it?
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-11T17:25:47.1566667+00:00

Hi @ Mikko Uusitalo

Nice to meet you.

Thank you for reaching out. I understand how critical seamless scaling is for your service, and I appreciate your patience.

Based on our investigation, the issue could be related to several factors:

Configuration Constraints: Some settings require a restart for scaling changes to take effect.

Resource Limits: While storage isn’t an issue, it’s worth checking if CPU or memory usage is hitting any thresholds.

Logs & Metrics Analysis: Reviewing logs and monitoring metrics in the Azure portal may reveal specific blockers affecting the scaling process.

Scaling Restrictions: Depending on the selected tier, there could be predefined limits on how much you can scale.

To move forward, I recommend checking log analytics for scaling-related events and reviewing Azure monitoring metrics. Please share the details asked in private message.

I’m happy to guide you.
Sai Raghunadh M 4,120 Reputation points Microsoft External Staff Moderator

2025-06-12T16:44:26.1333333+00:00

Hi @ Mikko Uusitalo

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Mihir Saxena 0 Reputation points Microsoft External Staff Moderator

2025-06-13T05:28:06.85+00:00

Hi @Mikko Uusitalo

Scaling issues in Azure Database for PostgreSQL Flexible Server especially when it gets stuck in the "Starting" or "Updating" state can be caused by various underlying factors.

Below is a step-by-step breakdown of causes and recommended resolution steps:

-- Ongoing or Failed Prior Operations:

Scaling won’t proceed if a previous operation (e.g., maintenance, backup, parameter update) is still running or failed.

Check via Activity Log and Look for operations in InProgress or Failed state with error messages.

Azure Portal > Monitor > Activity Log

-- Unsupported Scaling Path:

Cross-tier scaling often requires a restart or fails silently. Scale within the same tier first (e.g., GP 2 vCore to GP 4 vCore).

az postgres flexible-server update \ --resource-group <rg> \ --name <server> \ --sku-name Standard_D4s_v3

-- Maintenance or Engine Upgrade in Progress:

az postgres flexible-server show --resource-group <rg> --name <server> --query "maintenanceWindow"

-- VNet or NSG Misconfiguration:

If in a VNet, check that NSGs and route tables allow required traffic for Azure control plane.

-- Resource Locks or Policy Restrictions:

az lock list --resource-group <rg>

Check for reference - az postgres flexible-server

Share via

I am trying to scale Azure Postgresql Flexible Server, but it just rolling in Started stage and nothing is happening. What could cause this? Server is working fine but we need more cores to keep up with demand, but currently unable to scale up.

Your answer