Database Autonomy Service (DAS) provides the storage analysis feature for ApsaraDB RDS for PostgreSQL. You can use this feature to view the details of storage, such as the remaining days for which storage is available, the storage usage of individual tables, and the storage exception diagnosis of your ApsaraDB RDS for PostgreSQL instance. This feature helps you identify the storage exceptions in a timely manner to ensure service stability.
Prerequisites
Your RDS instance runs RDS High-availability Edition.
Usage notes
You can use the storage analysis feature to analyze up to 20,000 tables.
Procedure
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the left-side navigation pane, choose .
On the page that appears, click the Storage Analysis tab.
On the Storage Overview and Data Space tabs, view the storage usage of the database instance.
Tab
Section
Description
Storage Overview
Storage
You can view information such as exceptions, the average daily increase in space usage within the previous seven days, the number of days for which the remaining storage space is available, and the total amount of used space.
NoteYou can move your pointer over the
icon to view the details of each item.
Exceptions
You can view the exception information about tables or collections in the database instance.
Storage Trend
You can view the usage trend within a specific time range.
NoteThe time range can be up to seven days.
Tablespaces
You can view the detailed information and storage usage of each table in the database instance. You can click the name of a table to view the fields and indexes of the table.
Data Space
You can view the storage usage of each database in the database instance and the usage of tablespaces in the database.
Click the name of a table to view the fields and indexes of the table.
Reference
pg_repack: You can use the pg_repack extension to clear tablespaces. This helps you resolve the table bloat issues caused by a large number of operations (such as UPDATE) performed on tables.