autovacuum_vacuum_max_threshold

Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor. The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters.

English manual coverage begins with PostgreSQL 7.4. Source history and runtime observations have their own recorded version boundaries.

Reading PG 18·Select a recorded version

18 19 20

boot val: 100000000
category: Vacuuming / Automatic Vacuuming
context: sighup
doc same as: Unknown
documented: true
enumvals: Unknown
extra desc: -1 disables the maximum threshold.
lang: en
max val: 2147483647
metadata version: 18
min val: -1
name: autovacuum_vacuum_max_threshold
short desc: Maximum number of tuple updates or deletes prior to vacuum.
source: pg-settings-source-snapshot
unit: Unknown
vartype: integer

Definition PG 18

Specifies the maximum number of updated or deleted tuples needed to trigger a VACUUM in any one table, i.e., a limit on the value calculated with autovacuum_vacuum_threshold and autovacuum_vacuum_scale_factor. The default is 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a maximum number of updated or deleted tuples that will trigger a VACUUM operation. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing storage parameters.

Compare versions

Complete source facts

doc html

<p>
         Specifies the maximum number of updated or deleted tuples needed to
         trigger a <code class="command">VACUUM</code> in any one table, i.e., a limit on
         the value calculated with
         <code class="varname">autovacuum_vacuum_threshold</code> and
         <code class="varname">autovacuum_vacuum_scale_factor</code>.  The default is
         100,000,000 tuples.  If -1 is specified, autovacuum will not enforce a
         maximum number of updated or deleted tuples that will trigger a
         <code class="command">VACUUM</code> operation.  This parameter can only be set
         in the <code class="filename">postgresql.conf</code> file or on the server
         command line; but the setting can be overridden for individual tables
         by changing storage parameters.
        </p>

documentation revision

{"inputs":[{"file":"runtime-config-vacuum.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"599d3819c5fa60f160ba633df604ee9afd85549ffad2ae2fb0c3132a00d47417","version":"18.7"},{"file":"runtime-config-vacuum.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"b835e4b6c446cfdaf673750aba29ba28fc55ef6cc0c531558c1e394fdc05a140","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}

Source references

Original manual reference

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · wiki-repair-20261023:2722f74f230080a7cf1979453b59c6a4f50ab0290887750309cdc6947658afdd

Text language: en · wiki-repair-20261023:2722f74f230080a7cf1979453b59c6a4f50ab0290887750309cdc6947658afdd