PostgreSQL flexible server storage increase does not get reflected

Question

PostgreSQL flexible server storage increase does not get reflected

John 0

After scaling up the storage of a PostgreSQL flexible server from 32GB to 64GB, the status shows "succeeded" and the information reflects 64GB. However, the free space percentage on the machine remains unchanged, and the sum of "available" and "used" storage still shows 32GB instead of the scaled-up 64GB. What could be causing this discrepancy?

It has also was not responding, availability falls to 0. Couldn't stop. After few hours i have restarted and it has wake up, but still with same storage space.

It doesn't behave on any other servers before.

User's image

Abhisek Mishra 845 Reputation points Microsoft External Staff Moderator

2025-09-17T11:46:57.42+00:00
Hi John,

Thanks for sharing your query on Microsoft Q&A!

Could you please share the details requested in the private message for further investigation.

Also, please confirm the following:

Can you confirm if the storage auto grow feature is enabled on your server?

Are there any active replication slots that may be affecting your server's storage?
VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-28T07:36:57.31+00:00

Hi,

Could you please share the details requested in above comment.

Thanks,
Vrishabh
John 0 Reputation points

2025-10-28T07:56:54.75+00:00

Abhisek Mishra contacted me in a private message, but after a month I still hadn't received any response as to whether and how the problem would be solved.

We solved the problem ourselves by creating a new machine based on a snapshot. Interestingly, the platform recreated the server with an error (the specification was 64GB, but in reality it was 32GB). So we attempted to increase the space to 128GB, which, surprisingly, worked, and the machine's space was increased from 32GB to 128GB.

The reported machine was deleted, perhaps increasing the space from (the phantom 64GB) to 128 would have had the same result.

A month wasted.

After recreation (19.1+12.6) = ~32
Sina Salam 25,921 Reputation points Volunteer Moderator

2025-10-28T17:13:57.0366667+00:00

Hi John,

Thanks for your feedback.

Good to read that you're able to resolve the issue, despite the long time waiting.

At this point we would like to close the thread or the benefit of others in the community. Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution with other some steps to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Thanks.

1 answer

Your answer

Abhisek Mishra 845 Reputation points Microsoft External Staff Moderator

2025-09-17T11:46:57.42+00:00

Hi John,

Thanks for sharing your query on Microsoft Q&A!

Could you please share the details requested in the private message for further investigation.

Also, please confirm the following:

Can you confirm if the storage auto grow feature is enabled on your server?

Are there any active replication slots that may be affecting your server's storage?
VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-28T07:36:57.31+00:00

Hi,

Could you please share the details requested in above comment.

Thanks,
Vrishabh
John 0 Reputation points

2025-10-28T07:56:54.75+00:00

Abhisek Mishra contacted me in a private message, but after a month I still hadn't received any response as to whether and how the problem would be solved.

We solved the problem ourselves by creating a new machine based on a snapshot. Interestingly, the platform recreated the server with an error (the specification was 64GB, but in reality it was 32GB). So we attempted to increase the space to 128GB, which, surprisingly, worked, and the machine's space was increased from 32GB to 128GB.

The reported machine was deleted, perhaps increasing the space from (the phantom 64GB) to 128 would have had the same result.

A month wasted.

After recreation (19.1+12.6) = ~32
Sina Salam 25,921 Reputation points Volunteer Moderator

2025-10-28T17:13:57.0366667+00:00

Hi John,

Thanks for your feedback.

Good to read that you're able to resolve the issue, despite the long time waiting.

At this point we would like to close the thread or the benefit of others in the community. Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution with other some steps to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Thanks.

Answer 1

Hello John,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Issue:

PostgreSQL flexible server storage increase does not get reflected.

Error Message:

After scaling up the storage of a PostgreSQL flexible server from 32GB to 64GB, the status shows "succeeded" and the information reflects 64GB. However, the free space percentage on the machine remains unchanged, and the sum of "available" and "used" storage still shows 32GB instead of the scaled-up 64GB.

Solution:

Customer solved the solved the issue by creating a new machine based on a snapshot. Interestingly, the platform recreated the server with an error (the specification was 64GB, but in reality it was 32GB).

They attempted to increase the space to 128GB, which, surprisingly, worked, and the machine's space was increased from 32GB to 128GB.

The reported machine was deleted, perhaps increasing the space from (the phantom 64GB) to 128 would have had the same result.

User's image

For references and how to solve the above:

Step 1: To snapshot and recreate, you can use az postgres flexible-server geo-backup show or snapshot tools. - Recreate server from backup/snapshot - https://free.blessedness.top/en-us/azure/postgresql/flexible-server/concepts-backup

Step 2: To verify actual specs after recreation:

az postgres flexible-server show \
  --name <server-name> \
  --resource-group <resource-group>

https://free.blessedness.top/en-us/cli/azure/postgres/flexible-server

Step 3: Resize the storage an if spec mismatch occurs:

az postgres flexible-server update \
  --name <server-name> \
  --resource-group <resource-group> \
  --storage-size 128

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/how-to-scale-storage-size

Step 4: To enable autogrow

az postgres flexible-server update \
  --name <server-name> \
  --resource-group <resource-group> \
  --storage-auto-grow Enabled

https://free.blessedness.top/en-us/azure/postgresql/flexible-server/how-to-scale-storage-size#configure-storage-autogrow

Step 5: To monitor and create alert, you can use Azure Monitor:

Set alerts for storage usage > 80%.
Track actual disk metrics.

https://free.blessedness.top/en-us/azure/azure-monitor/alerts/alerts-overview

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

Share via

PostgreSQL flexible server storage increase does not get reflected

1 answer

Your answer