Skip to main content
Version: 11 - Zimtschnecke

Storage Analysis

The Storage analysis feature provides a global view of how the PostgreSQL database used by a workspace consumes storage, and exposes a small set of maintenance operations.

Access​

The Storage analysis screen is available at /workspace/:id/storage-analysis and can be reached from:

  • The workspace dashboard Storage usage widget via the Analysis link
  • The workspace quick access menu entry Storage analysis

How it works​

Operations are grouped into sections on the page. Each section shows:

  • A short description (read-only analysis vs write/maintenance)
  • A Run button that starts the operation
  • A Cancel button while an operation is in progress
  • The last result as JSON

Potentially heavy operations (database bloat analysis and VACUUM FULL) show a confirmation dialog before they start, warning about possible performance impact.

Permissions​

  • Read-only operations require workspace-level READ permission.
  • Write / maintenance operations require workspace-level WRITE permission.

Operations​

Read-only​

Executions with many execution_dumps​

Find executions that have a high number of execution dumps.

  • Many dumps are created by executions that run many operations and/or run for a long time with savepoint_retention = ALL.
  • Having many dumps is not necessarily a problem, but they may be unnecessary.
  • Consider adjusting savepoint_retention for individual executions or globally.

Parameters: min_count, limit.

Executions with large execution_dumps​

List the executions with the largest total execution dump storage.

  • Dump size depends on the amount of data held in variables at dump time.
  • To reduce storage usage, consider clearing large variables or adjusting savepoint_retention.

Parameters: limit.

Largest files​

List the largest files stored in the workspace.

Parameters: limit.

Largest DB tables​

Show the largest database tables by total on-disk size.

Parameters: limit.

Number of records per record_type​

Count the number of records per record type.

Parameters: include_deleted.

Trash / deleted analysis​

Show how many records exist, how many are in the trash, and how many are soft-deleted identity placeholder rows.

Soft-deleted identity rows cannot be linked because the original record no longer exists.

Total size per record_type​

Estimate total size occupied per record type.

Parameters: include_deleted.

Database bloat​

Estimate bloat per table (heap, indexes, and TOAST).

  • Bloat is unused/wasted on-disk space that can accumulate after updates/deletes.
  • VACUUM FULL can reclaim space, but it locks and rewrites tables.

Parameters: limit.

Write / maintenance​

VACUUM FULL on selected tables​

Run VACUUM (FULL, ANALYZE) on specific tables.

  • This locks and rewrites the selected tables.
  • Ensure you have enough free disk space for the rewrite.

Parameters: tables.

VACUUM FULL on all tables​

Run VACUUM (FULL, ANALYZE) on all eligible tables.

  • Heavy maintenance operation; expect a noticeable performance impact.
  • Ensure sufficient free disk space for table rewrites.