All Products
Search
Document Center

AnalyticDB for PostgreSQL:Manually pause and resume an instance

Last Updated:Jul 10, 2024

This topic describes how to manually pause and resume an AnalyticDB for PostgreSQL instance. This way, you can pause and resume your instance based on your business requirements to reduce costs.

Prerequisites

  • A pay-as-you-go AnalyticDB for PostgreSQL instance is created.

  • The AnalyticDB for PostgreSQL instance is in Serverless manual scheduling mode or elastic storage mode.

    Note

    You do not need to manually pause and resume AnalyticDB for PostgreSQL instances in Serverless automatic scheduling mode, because the instances can be automatically paused and resumed based on traffic detection. If no traffic is detected, the instances automatically enter the idle state. You are not charged for computing resources when the instances are in the idle state.

  • Before you pause an AnalyticDB for PostgreSQL instance, the instance is in the Running state.

  • Before you resume an AnalyticDB for PostgreSQL instance, the instance is in the Paused state.

Usage notes

  • After you initiate an instance pause, SQL statements that are being executed in the instance are terminated.

  • After you initiate an instance pause, a snapshot backup is immediately performed on the instance.

  • While an instance is in the Paused state, you cannot connect to the instance or execute SQL statements.

  • While an instance is in the Paused state, you can only release the instance, restore data of the instance, or resume the instance.

  • If an instance that has the data sharing feature enabled and shares its data is paused, the instances that have subscribed to the shared data can still consume the data but other instances cannot subscribe to the shared data.

Billing rules

The fees for using an AnalyticDB for PostgreSQL instance consist of the computing resource fee and the storage resource fee. The following table describes whether you are charged for the fees while an instance is in different states. For more information, see Pricing.

Instance status

Computing resource fee

Storage resource fee

Pausing

Charged

Charged

Paused

Free of charge

Charged

Idle

Free of charge

Charged

Resuming

Free of charge

Charged

Running

Charged

Charged

Note

While an AnalyticDB for PostgreSQL instance is in the Pausing or Running state, you are billed for computing resources per second.

Pause an instance

  1. Log on to the AnalyticDB for PostgreSQL console.
  2. In the upper-left corner of the console, select a region.
  3. Find the instance that you want to pause and choose More > Pause Instance in the Actions column.

  4. In the message that appears, click OK.

    After you click OK, the status of the instance changes to Pausing. After the instance is paused, the status of the instance changes to Paused.

    Note

    The instance pause process requires 10 to 15 minutes to complete.

Resume an instance

  1. Log on to the AnalyticDB for PostgreSQL console.
  2. In the upper-left corner of the console, select a region.
  3. Find the instance that you want to pause and choose More > Resume Instance in the Actions column.

  4. In the message that appears, click OK.

    After you click OK, the status of the instance changes to Resuming. After the instance is resumed, the status of the instance changes to Running.

    Note

    The instance resume process requires approximately 15 minutes to complete.