Our postgresql flexible server stuck in starting state for +24 hours

Sebastian Loef 5 Reputation points
2026-07-08T09:03:25.35+00:00

We tried changing the compute resource from B2ms to B2, since then the service has been stuck in starting state

Azure Database for PostgreSQL

Answer accepted by question author

Manoj Kumar Boyini 18,920 Reputation points Microsoft External Staff Moderator
2026-07-17T13:27:12.1333333+00:00

Hi @Sebastian Loef

The issue has been mitigated from our side, and the PostgreSQL Flexible Server is now in a Succeeded state.

Could you please verify the server status from your end and confirm whether you are able to access and use the server as expected?

We look forward to your confirmation.

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Richard Röntsch 0 Reputation points
    2026-07-08T11:05:37.4566667+00:00

    We facing teh same issue. We tried to change teh compute and now for last 24h it says, "The server is currently in 'updating' state. Please wait for the operation to complete.". Furthermore, Server not accepting TCP connections and psycopg2.OperationalError connection timed out. Point-in-time restore failed because source server is in Updating state. ARM API shows no visible running operation ID. Tried restore but there is an Azure capacity issue.
    Please share the solution fast

    Was this answer helpful?

    0 comments
  2. Alex Burlachenko 24,625 Reputation points MVP Volunteer Moderator
    2026-07-08T09:44:48.4466667+00:00

    hi Sebastian Loef & thx for sharing urs issue here at Q&A portal,

    This is platform-side now.

    A PostgreSQL Flexible Server stuck in Starting for 24+ hours after a compute resize is not normal, and there usually isn’t a safe customer-side fix for that state. Don’t keep retrying random changes in the portal. Open an Azure support ticket and include server name + region+subscription ID+timestamp of the resize+old/new compute SKU+current provisioning/state & any operation/correlation ID from Activity Log.

    If u have backups or a replica and the RTO is urgent, ask support whether restore-to-new-server is the fastest recovery path. But the stuck server itself needs Microsoft backend intervention.

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

    and at my blog https://ctrlaltdel.blog/

    Was this answer helpful?

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.