Azure Database for PostgreSQL flexible server stuck in UPDATE state — Cannot access or restart

Sarel Coetzer 0 Reputation points
2026-10-07T07:29:44.1966667+00:00

Problem description

I am experiencing an issue with my Azure Database for PostgreSQL flexible server, which has become unresponsive and is stuck in the 'Updating' state. I cannot access the server, and attempts to restart it have failed. No recent changes or operations seem to have triggered this problem, and there are no detailed error messages available beyond the server being stuck in 'Updating.'

Environment

Azure Database for PostgreSQL flexible server, compute tier: Memory Optimized, region not specified in case information.

What I've already tried

Based on the available case material, I attempted to access and restart the server, but both actions failed. No other troubleshooting steps or diagnostic outputs have been documented or attempted so far.

Current status

My server remains inaccessible and stuck in the 'Updating' state. I am seeking guidance on how to resolve this issue and bring the server back to a healthy, operational state.

Azure Database for PostgreSQL
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Salamat Shah 830 Reputation points MVP
    2026-10-07T08:53:20.47+00:00

    A PostgreSQL Flexible Server stuck in "Updating" typically indicates a backend operation (maintenance, scaling, patching, storage operation, or platform action) that has not completed successfully.

    Try this:

    1. Check Azure Activity Log for any ongoing or failed operations.
    2. Review Azure Service Health and Resource Health for platform incidents in the affected region.
    3. Attempt to identify any pending operation via Azure CLI: *az postgres flexible-server show * *--resource-group <rg> * --name <server>
    4. If restart, stop/start, and portal operations are blocked while the server remains in Updating, this usually requires Microsoft Support intervention to clear or complete the stuck backend operation.

    Since the server is inaccessible and restart attempts fail, open a Microsoft Support ticket and provide the server name, region, subscription ID, and timestamp when the issue began. This is likely not recoverable through customer actions alone.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.