This article provides step-by-step instructions to stop the compute of an Azure Database for PostgreSQL flexible server instance.
Using the Azure portal:
Select your Azure Database for PostgreSQL flexible server instance.
In the resource menu, select Overview.
The status of the server must be Ready, for the Stop button to appear on the toolbar.
Select the Stop button.
In the Stop server dialog, confirm or abort your decision to stop the server.
A notification informs you that the server is stopping.
Also, the status of the server changes to Stopping.
When the process completes, a notification informs you that the server is stopped.
Also, the status of the server changes to Stopped.
You can stop the compute of a started server via the az postgres flexible-server stop command.
az postgres flexible-server stop \
--resource-group <resource_group> \
--name <server>
If you attempt to stop the compute of a server which isn't in Ready state, you receive an error like this:
Server will be automatically started after 7 days if you do not perform a manual start operation
(ServerIsNotReady) Restart or Stop Server can only be performed on Started servers. Server Name = <server>, Current Server State = <non_started_server_state>
Code: ServerIsNotReady
Message: Restart or Stop Server can only be performed on Started servers. Server Name = <server>, Current Server State = <non_started_server_state>
Note
Once the server is stopped, other management operations aren't available for the Azure Database for PostgreSQL flexible server. While the Azure Database for PostgreSQL flexible server is in stopped state, it could be briefly restarted for scheduled monthly maintenance, and then returned to its stopped state. This procedure ensures that even instances in a stopped state, stay up to date with all necessary patches and updates.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4