+ endterm="sql-createtable-storage-parameters-title">.
must also be enabled for
autovacuum to work.
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
+ file or on the server command line; however, autovacuuming can be
+ disabled for individual tables by changing table storage parameters.
Note that even when this parameter is disabled, the system
set to any value other than -1, a message will be
logged if an autovacuum action is skipped due to the existence of a
conflicting lock. Enabling this parameter can be helpful
- in tracking autovacuum activity. This setting can only be set in
- the postgresql.conf> file or on the server command line.
+ in tracking autovacuum activity. 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.
Specifies the maximum number of autovacuum processes (other than the
- autovacuum launcher) which may be running at any one time. The default
+ autovacuum launcher) that may be running at any one time. The default
is three. This parameter can only be set at server start.
to trigger a VACUUM> in any one table.
The default is 50 tuples.
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
needed to trigger an ANALYZE> in any one table.
The default is 50 tuples.
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
when deciding whether to trigger a VACUUM>.
The default is 0.2 (20% of table size).
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
when deciding whether to trigger an ANALYZE>.
The default is 0.1 (10% of table size).
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
is a relatively low 200 million transactions.
This parameter can only be set at server start, but the setting
can be reduced for individual tables by
- changing storage parameters.
+ changing table storage parameters.
For more information see .
pg_multixact/members> and pg_multixact/offsets>
subdirectories, which is why the default is a relatively low
400 million multixacts.
- This parameter can only be set at server start, but the setting
- can be reduced for individual tables by changing storage parameters.
+ This parameter can only be set at server start, but the setting can
+ be reduced for individual tables by changing table storage parameters.
For more information see .
value will be used.
The default value is 20 milliseconds.
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
default), the regular
value will be used. Note that
the value is distributed proportionally among the running autovacuum
- workers, if there is more than one, so that the sum of the limits of
- each worker never exceeds the limit on this variable.
+ workers, if there is more than one, so that the sum of the limits for
+ each worker does not exceed the value of this variable.
This parameter can only be set in the postgresql.conf>
- file or on the server command line.
- This setting can be overridden for individual tables by
- changing storage parameters.
+ file or on the server command line;
+ but the setting can be overridden for individual tables by
+ changing table storage parameters.
the entries in it to the main GIN data structure in bulk.
The default is four megabytes (4MB>). This setting
can be overridden for individual GIN indexes by changing
- storage parameters.
+ index storage parameters.
See and
for more information.