Database Size Trends
The Database Size tab shows how the size of each database on your PostgreSQL instance has evolved over the selected time period. It is the primary tool for storage capacity planning.
{screenshot: trends-database-size-tab}
Chart Description
The chart displays a line chart with one line per database, showing size in megabytes or gigabytes over time.
- X axis — Time (based on the selected range)
- Y axis — Database size (MB or GB, auto-scaled)
- Each line — One database on the instance
- Data points — One per AWR snapshot (every 30 minutes)
{screenshot: trends-database-size-chart}
Database Size Table
Below the chart, a summary table shows the current size and growth statistics for each database:
| Column | Description |
|---|---|
| Database | Database name |
| Current Size | Most recent recorded size |
| Size at Start | Size at the beginning of the selected period |
| Growth | Absolute size increase during the period |
| Growth % | Percentage growth during the period |
| Avg Daily Growth | Average daily size increase |
{screenshot: trends-database-size-table}
Capacity Planning with Size Trends
Use the Avg Daily Growth column to project future storage needs:
Projected size in N days = Current Size + (Avg Daily Growth × N)
For example, if a database is currently 50 GB and growing at 500 MB/day:
- In 30 days → ~65 GB
- In 90 days → ~95 GB
Plan storage provisioning accordingly, leaving a comfortable buffer.
Identifying Unexpected Growth
A sudden jump in database size may indicate:
- A large batch data load
- A missing DELETE or TRUNCATE in a scheduled job
- A bloat spike (tables not being vacuumed)
Correlate with AWR reports for the same period to identify the root cause.