VACUUM performs an aggressive scan if the table's pg_class.relminmxid field has reached the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead tuples. The default is 150 million multixacts. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of autovacuum_multixact_freeze_max_age, so that a periodic manual VACUUM has a chance to run before an anti-wraparound is launched for the table. For more information see vacuum-for-multixact-wraparound.
- Query on pg_stat_progress_vacuum returns nothing
- PostgreSQL11 space reuse under high delete/update rate
- Why does it run even with autovacuum turned off in Cloudsql on GCP?
- What causes data on a read-replica to be an old_snapshot and cause conflict?
- insert blocks with ExclusiveLock on index in Postgres