↑↓ select↵ open⌫ change scopeOpen full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Configuration Parameters

autovacuum_vacuum_insert_threshold

Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. 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 table 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

boot val
1000
category
Vacuuming / Automatic Vacuuming
context
sighup
doc same as
Unknown
documented
true
enumvals
Unknown
extra desc
-1 disables insert vacuums.
lang
en
max val
2147483647
metadata version
18
min val
-1
name
autovacuum_vacuum_insert_threshold
short desc
Minimum number of tuple inserts prior to vacuum.
source
pg-settings-source-snapshot
unit
Unknown
vartype
integer

Definition PG 18

Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. The default is 1000 tuples. If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. 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 table storage parameters.

Compare versions

Complete source facts

doc html

<p>
         Specifies the number of inserted tuples needed to trigger a
         <code class="command">VACUUM</code> in any one table.
         The default is 1000 tuples.  If -1 is specified, autovacuum will not
         trigger a <code class="command">VACUUM</code> operation on any tables based on
         the number of inserts.
         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 table 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

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · wiki-repair-20261023:6b929c45312be14189e617369355c54b0b20df0a46b424ec09ec06e9707b9b96

Text language: en · wiki-repair-20261023:6b929c45312be14189e617369355c54b0b20df0a46b424ec09ec06e9707b9b96