VACUUM

Introduces VACUUM syntax for Iceberg tables and sinks to enable manual compaction, manifest rewrite, and snapshot expiration in RisingWave.

RisingWave supports VACUUM syntax for Iceberg engine tables and Iceberg sinks. This allows you to manage storage, reclaim disk space, and optimize performance for Iceberg data within RisingWave.

Syntax

VACUUM [FULL] schema_name.object_name;

• VACUUM: Rewrites eligible data manifests, then expires eligible old snapshots.
• VACUUM FULL: Compacts the specified Iceberg table or sink first, then performs the same manifest rewrite and snapshot expiration steps. This operation takes longer and requires extra disk space, as a new copy is written before the old copy is released.

The manifest rewrite and snapshot expiration steps do not override their maintenance settings. Manifest rewrite runs only when enable_manifest_rewrite = true and the configured rewrite thresholds select an eligible batch. Snapshot expiration runs only when enable_snapshot_expiration = true.

VACUUM FULL waits for the manual compaction task to finish before returning. If the target already has an automatic or manual compaction task queued or running, the new VACUUM FULL request returns an error instead of scheduling another task.

Parameters

Parameter	Description
FULL	Optional. If specified, compacts the table first, then rewrites eligible manifests and expires eligible snapshots.
object_name	Can be an Iceberg engine table or an Iceberg sink.

Example

-- Insert and update data
insert into t_vacuum_test values(1, 'alice', 100), (2, 'bob', 200), (3, 'charlie', 300);
FLUSH;
-- sleep 5s

-- Check data
select * from t_vacuum_test;

-- More inserts/updates
insert into t_vacuum_test values(4, 'david', 400), (5, 'eve', 500);
FLUSH;
-- sleep 5s
update t_vacuum_test set v1 = 150 where id = 1;
FLUSH;
-- sleep 5s

-- Run VACUUM and verify
VACUUM t_vacuum_test;

VACUUM FULL t_vacuum_test;