Help Center/ Relational Database Service_RDS for PostgreSQL/ User Guide/ Instance Management/ Instance Lifecycle/ Rebooting Instances or Read Replicas
Updated on 2026-07-06 GMT+08:00
View PDF
Share

Rebooting Instances or Read Replicas

Scenarios

You may need to reboot instances for routine maintenance purposes. For example, after you modify some parameters, a reboot is required for the modifications to take effect. You can reboot a primary DB instance or a read replica on the management console. You can reboot a single DB instance or multiple DB instances at a time.

Constraints

  • If the DB instance status is Abnormal, the reboot may fail.
  • An instance cannot be rebooted if its storage is full.
  • Rebooting a DB instance will cause service interruptions. During this period, the DB instance status is Rebooting.
  • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.

Procedure

  1. Log in to the RDS console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, locate the target DB instance, or click in the front of a DB instance and then locate the target read replica. Choose More > Reboot in the Operation column.

    Alternatively, click the target instance name on the Instances page to go to the Summary page. In the upper right corner, click Reboot.

    For primary/standby DB instances, if you reboot the primary instance, the standby instance is also rebooted automatically.

  4. In the displayed Reboot DB Instance dialog box, set Scheduled Time, select the confirmation check box, and click OK.

    Figure 1 Rebooting an instance

    Settings for the Scheduled Time field:

    • Immediate: The system reboots the instance immediately after you submit the task.
    • During maintenance window: If this option is selected, you can view the task details later on the Scheduled Tasks page. For details, see Task Center. Set the maintenance window to off-peak hours.

  5. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
  1. Log in to the RDS console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, select one or more DB instances or read replicas (maximum: 50) to be rebooted and choose More > Reboot above the DB instance list.
  4. In the displayed dialog box, select the check box and click Yes.
  5. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.

Related APIs

Parent Topic: Instance Lifecycle