Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
This article provides step-by-step instructions to stop the compute of an Azure Database for PostgreSQL flexible server.
Steps to stop a server
Use the Azure portal:
Select your Azure Database for PostgreSQL flexible server.
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.
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 flexible servers in a stopped state, stay up to date with all necessary patches and updates.
Note
If your server uses the Burstable compute tier and exhausts its CPU credits, the stop operation can take longer than usual to complete. When credits are exhausted, the server is restricted to baseline CPU, which can delay management operations until credits rebuild. To review the credits available to your server, monitor the CPU Credits Remaining metric before you stop the server. For more information about the CPU credit model, see Compute options.