Christophe Pettus clarifies that the PostgreSQL GUC min_wal_size defines a minimum threshold for WAL segment recycling rather than a data retention strategy. Operators frequently misconfigure this setting, leading to scenarios where excessive WAL accumulation causes failure on standby replicas. Understanding this distinction is critical for preventing replication breaks in high-throughput environments.
- min_wal_size is a floor for WAL recycling, not a retention policy.
- Misunderstanding this GUC often leads to standby replication failures.
- High write volumes can cause WAL segments to exceed the floor limit.
- Review current settings if standbys are dropping due to disk pressure.
- Adjust min_wal_size carefully to balance disk usage and replication stability.
Fleet impact: For PostgreSQL fleets, verify that min_wal_size is not inadvertently causing WAL bloat on standbys, which can lead to replication lag or outages. Ensure standby disk capacity accounts for the recycled WAL segments and monitor replication status closely after any GUC changes.