Postgres db does not finish restarting (Azure Database for PostgreSQL flexible server) after connectivity issues / full storage

Question

Hi,

This Monday morning, our Azure Database for PostgreSQL flexible server instance turned out to have connectivity issues. None of our services could connect to it anymore and manually connecting also failed. These issues started last Saturday; before that everything connected fine.

I am restarting it, hoping to resolve the issue, but it's stayed in restarting state for 20 minutes now.

After further investigation, we notice its storage is full. I suspect this is related to it being unavailable / staying in restart state.

It's a Azure Database for PostgreSQL flexible server with configuration General Purpose, D2s_v3, 2 vCores, 8 GiB RAM, 256 GiB storage.

What can I do to restore this instance's availability?

Answer 1

Hi @Arthur Nieuwland

If your Azure Database for PostgreSQL Flexible Server instance is experiencing connectivity issues and is stuck in a restarting state due to full storage, you can try increasing the storage capacity. If allowed and the option is not grayed out, you can do this by scaling up the storage capacity of the instance.

If the instance remains stuck in a restarting state, you may need to wait some time for it to come back online. When the storage is full, it can take a while for the instance to recover. However, if it continues to take an extended period, you'll need to open a support case, as backend intervention may be required to increase the storage and bring the server back online.

Thank You