When an instance experiences full connections or performance issues, you can restart the instance manually. This article describes the steps for restarting a RDS for PostgreSQL instance.

Prerequisites

Instances have been created and the instance is in Running state, for more details please see Creating an instance.

Precautions

The time to restart the instance depends on the load state of the instance, which will cause the business to flash out once or twice. Please operate with caution. It is recommended that you add a reconnection mechanism to the application, which can greatly reduce the impact of database connection disconnection on the business.

Procedure

In the upper-left corner of the top menu bar, select the project and region for the instance.

tip

If the project of the instance has not been set, the project should be selected as All resources.

Go to the Instances page, click … > Restart the instance in the Actions column of the target instance,

tip

You can also enter the target instance and click Restart Instance in the upper right corner of the page.

Confirm the instance information in the pop-up dialog box and select the Restart scope as All nodes (default) or Specify read-only node. After confirming that everything is correct, click OK.

tip

If you choose to Specify read-only node, you need to check the read-only node that needs to be restarted in the drop-down list of Read-only node. You can select up to all read-only nodes of the instance.

Return to the instance list page, refresh the current list, and the instance status changes to Restarting. After the restart is complete, the instance status changes to Running.

Last updated: 2025.11.17 16:15:04

Public security network record in Beijing: No. 11010802032137