An Azure managed PostgreSQL database service for app development and deployment.
Hello Jesse,
If the Azure Database for PostgreSQL Flexible Server has remained in Starting state for hours and Stop/Restart operations are being rejected because another operation is in progress, repeatedly issuing start/stop/restart commands is unlikely to resolve the current operation.
I recommend checking the following first:
- In the Azure portal, open the PostgreSQL Flexible Server and check Resource Health and Service Health for any platform-related issue.
- Review the server's Activity Log and capture the latest Start operation, timestamp, status, and correlation/tracking ID.
- Under Diagnose and solve problems, review the available troubleshooting information for the server. Microsoft provides built-in troubleshooting guides for PostgreSQL Flexible Server in the Azure portal.
If the server continues to remain in Starting and management operations are still rejected, please open an Azure Support request and provide the resource ID, region, Activity Log details, and correlation/tracking ID so that the stuck operation can be investigated.
If recovery of the existing server is not acceptable for a production workload, you can also consider point-in-time recovery (PITR) to a new Flexible Server, provided the required restore point is within the configured backup retention period. Microsoft documents that PostgreSQL Flexible Server automatically performs backups and supports point-in-time recovery within the configured retention period.
Microsoft documentation: