Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to freeze row versions while scanning a table. The default is 50 million transactions. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of autovacuum_freeze_max_age, so that there is not an unreasonably short time between forced autovacuums. For more information see vacuum-for-wraparound.
- What is autovacuum_vacuum_cost_delay in autovacuum in PostgreSQL?
- Hibernate 3.3.2GA improperly loads bytea data from PostgreSQL 9.0 and all type mappings are correct
- PostgreSQL11 space reuse under high delete/update rate
- What causes data on a read-replica to be an old_snapshot and cause conflict?
- insert blocks with ExclusiveLock on index in Postgres