Database Autonomy Service (DAS) provides the storage analysis feature for ApsaraDB RDS for PostgreSQL. Use this feature to monitor storage usage, identify which tables or databases consume the most space, track growth trends, and detect storage exceptions such as table bloat — before they affect service availability.
Prerequisites
Before you begin, ensure that you have:
An ApsaraDB RDS for PostgreSQL instance running High-availability Edition
Usage notes
The storage analysis feature can analyze up to 20,000 tables.
View storage usage
Go to the Instances page. In the top navigation bar, select the region where your instance resides, then click the instance ID.
In the left-side navigation pane, choose Autonomy Service > Diagnostics.
Click the Storage Analysis tab.
On the Storage Overview and Data Space tabs, review the storage metrics described in the following table.
| Tab | Section | What to check |
|---|---|---|
| Storage Overview | Storage | Exceptions, average daily space increase over the previous seven days, estimated days of remaining storage, and total used space. Move your pointer over the  icon to see details for each metric. |
| Storage Overview | Exceptions | Tables or collections with storage anomalies, such as table bloat caused by a high volume of UPDATE operations. If bloat is detected, use pg_repack to reclaim space — see What's next. |
| Storage Overview | Storage Trend | Space usage trend over a specific time range (up to seven days). Use this to identify sudden growth patterns. |
| Storage Overview | Tablespaces | Storage usage and details for each table. Click a table name to view its fields and indexes. |
| Data Space | — | Storage usage per database and tablespace usage within each database. Click a table name to view its fields and indexes. |
What's next
If storage exceptions such as table bloat are detected, use the pg_repack extension to reclaim tablespace. Table bloat occurs when a large number of operations (such as UPDATE) performed on tables leave behind dead row versions that PostgreSQL does not immediately reclaim. For details, see Use the pg_repack extension to clear tablespaces.