You may need to restart a database instance for maintenance purposes. For instance, if the number of connections reaches the upper limit or the instance has any performance issues, you can manually restart the database instance through the Console page.
Constraints and Restrictions
• If the database instance status is Exception, the restart may fail.
• Restarting a database instance will cause the database engine service to be restarted. Restarting a database instance will cause service interruption for a short period. During the restart process, the database instance status is Restarting.
• Restarting will cause the instance unavailability. After restarting, the instance will automatically clear the cache in memory. Please restart during the off-peak period of service to minimize disruption during peak service hours.
• For primary/standby instances, the corresponding standby instance will also be restarted synchronously and the service will also be interrupted.
Procedure
1. Log in to the eSurfing Cloud Portal.
2. Click Console and select the corresponding resource pool, such as East China 1.
3. In the upper left corner of the Console, click
and select Region and Project.
4. Select Database > RDS-PostgreSQL and go to the RDS-PostgreSQL Console.
5. On the Instance Management page, select the specified instance and click More > Restart. For primary/standby instances, the corresponding standby instance will also be restarted synchronously and the service will also be interrupted.
6. In the Restart box, click OK to restart the instance.
7. After the instance restart is complete, the instance status is Running.