07 · Tables A→ZK · Maintain & tune performance
Reclaim storage & honor retention
Delete old unreferenced files with vacuum_table - always dry-run first.
vacuum_table deletes old, unreferenced data files (the ones
optimize and updates/deletes left behind), reclaiming
storage. It is not reversible - so always dry-run first.
Vacuum (dry-run, then execute)
eddytor vacuum table eddytor sales orders --dry-run
eddytor vacuum table eddytor sales orders # execute after reviewing{ "table": "eddytor.cfg_xxx.<uuid>_products", "retention_hours": 168, "dry_run": true }Then run again with "dry_run": false to execute.
Heads up
Vacuum is NOT idempotent - deleted files are gone
forever. The dry run is your safety net: it previews exactly what would be
removed. Always run it first and review the file count / space savings.
Retention & time-travel
retention_hours (default 168 = 7 days) sets how far back files are kept.
Heads up
Setting
retention_hours below 168 can break
time-travel. After vacuum, rollback_table and
restore_table to versions older than the retention
window fail - their files are deleted. Keep retention_hours >= 168 unless
you're certain you won't need to recover that far back. See
Vacuum cuts time-travel.Order
Run optimize first (creates compacted files), then vacuum (removes the old small ones). Confirm both in history.