Restart Azure Database for PostgreSQL - Single Server using the Azure CLI
APPLIES TO: Azure Database for PostgreSQL - Single Server
This topic describes how you can restart an Azure Database for PostgreSQL server. You may need to restart your server for maintenance reasons, which causes a short outage as the server performs the operation.
The server restart will be blocked if the service is busy. For example, the service may be processing a previously requested operation such as scaling vCores.
The time required to complete a restart depends on the PostgreSQL recovery process. To decrease the restart time, we recommend you minimize the amount of activity occurring on the server prior to the restart. You may also want to increase the checkpoint frequency. You can also tune checkpoint related parameter values including
max_wal_size. It is also recommended to run
CHECKPOINT command prior to restarting the server.
To complete this how-to guide:
- Create an Azure Database for PostgreSQL server.
If you prefer to run CLI reference commands locally, install the Azure CLI. If you're running on Windows or macOS, consider running Azure CLI in a Docker container. For more information, see How to run the Azure CLI in a Docker container.
If you're using a local installation, sign in to the Azure CLI by using the az login command. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see Sign in with the Azure CLI.
When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the Azure CLI.
- This article requires version 2.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
Restart the server
Restart the server with the following command:
az postgres server restart --name mydemoserver --resource-group myresourcegroup