11
<h3>Running pg_autovacuum recommended</h3>
11
<h3>Running autovacuum recommended</h3>
13
Introduced in PostgreSQL 8.1, the pg_autovacuum process which was previously
13
Introduced in PostgreSQL 8.1, the autovacuum process which was previously
14
14
implemented as an external service process is now integrated into the backend. It will
15
15
run VACUUM automatically if a configurable amount of data has changed.
18
18
Running VACUUM is mandatory on a PostgreSQL server to keep data consistent
19
and the server performant. As a start, it is recommended to enable the pg_autovacuum
19
and the server performant. As a start, it is recommended to enable the autovacuum
20
20
daemon by setting 'autovacuum', 'stats_start_collector' and 'stats_row_level'
21
in postgresql.conf to 'on'. With a usually neglectable performance penalty from the
22
data change tracking, you will gain automatic performing VACUUM runs.
25
To adjust pg_autovacuum performance for individual needs, you might need to tune
21
in postgresql.conf to 'on'.
23
In PostgreSQL 8.3 and newer, autovacuum is enabled by default unless you
24
turn off 'track_activities' or 'track_counts'.
27
With a usually neglible performance penalty from the
28
data change tracking, you will gain automatic VACUUM runs.
31
To adjust autovacuum performance for individual needs, you might need to tune
26
32
its settings using global parameters in postgresql.conf, or individually on each table; see