All Products
Search
Document Center

PolarDB:FAQ about storage billing

Last Updated:Mar 28, 2026

Answers to common questions about PolarDB storage billing.

What are the differences between pay-as-you-go and subscription storage billing?

The billing differences depend on your storage class.

PSL4 and PSL5 storage classes:

Pay-as-you-goSubscription
Capacity specificationNot required. Storage scales automatically based on actual usage.Required. Specify the maximum storage capacity upfront.
Payment timingCharged hourly based on actual usage.Pay all fees upfront.

ESSD storage class:

Pay-as-you-goSubscription
Capacity specificationRequired.Required.
Payment timingCharged hourly.Pay all fees upfront.
Important

With ESSD storage, insufficient storage space may cause write failures and affect your services. Monitor usage closely and configure automatic storage scaling to prevent this.

Can I switch only the storage billing method?

No. Switching the storage billing method requires switching the billing method of the entire cluster. For details, see Switch billing methods.

Important

This change affects the entire cluster, not just storage. Plan accordingly before switching.

Can I disable the hot standby storage cluster after enabling it?

No. Once you enable the hot standby storage cluster at purchase, it cannot be disabled. Consider this carefully before purchasing a cluster. For more information, see High-availability Mode (Hot Standby Cluster).

Is the hot standby storage cluster charged separately?

No. The hot standby storage cluster is not billed independently. Instead, enabling it doubles the unit price of the associated bucket. For pricing details, see Bucket.

How do I disable the table recycle bin to reduce storage costs?

Disabling the table recycle bin and clearing its contents frees up the storage space occupied by retained tables.

  1. Log on to the PolarDB console and set the loose_recycle_bin parameter to OFF. For details, see Set cluster and node parameters.

  2. Run the following statement to clear tables from the recycle bin:

    call dbms_recycle.purge_table('TABLE_NAME');

    Replace TABLE_NAME with the name of the table to purge. For details, see Manage the recycle bin.

My cluster is locked but still shows available storage space. What do I do?

This applies to ESSD clusters only. When an ESSD disk becomes full, PolarDB locks the disk and sets it to read-only to prevent data corruption. A 3 GB buffer is reserved, so the disk locks before the displayed available space reaches zero.

To resolve this, choose one of the following options:

Tip: To avoid unexpected locks, configure automatic storage scaling when you set up an ESSD cluster.