An Azure managed PostgreSQL database service for app development and deployment.
Hi Miguel Silva,
Thank you for the update, and glad to hear the issue has been resolved.
Based on your findings, the behavior was caused by the server reaching full disk capacity, which can prevent the service from completing operations such as Start/Stop transitions and may leave the server in a “Starting” state.
Recreating the server from backup and enabling storage autogrow was the right approach to restore service availability and prevent recurrence.
As a best practice, we recommend continuing to monitor storage utilization and ensuring autogrow remains enabled to avoid similar situations in the future.
Please feel free to reach out if you need any further assistance.