vacuum_freeze_table_age

When a vacuum starts on a table whose age(relfrozenxid) exceeds vacuum_freeze_table_age (default 150M), that vacuum escalates itself to aggressive: it ignores the all-visible map bits and advances relfrozenxid. This is the polite escalation: it rides a vacuum that was going to run anyway. Keep it well under autovacuum_freeze_max_age, so aggressive passes happen on your trigger schedule rather than as the forced anti-wraparound scan.