WAL kept and recycled rather than removed.
At a glance
| Property | Value |
|---|---|
| Parameter | min_wal_size |
| Category | Checkpoints |
| Default | 80MB |
| Value type | memory (kB/MB/GB) |
| Change scope | Reload (no restart) |
What it does
Below this amount, WAL files are recycled for future use instead of being deleted, smoothing out write bursts.
How to apply a change
Takes effect on configuration reload (sighup context). Run SELECT pg_reload_conf(); or send SIGHUP — no restart needed.
Inspect the current value and source with SHOW min_wal_size; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'min_wal_size';.
Tuning guidance
Raise alongside max_wal_size on bursty workloads so segments are reused rather than re-created.