-
+
Routine Database Maintenance Tasks
- Beginning in
PostgreSQL 8.3, autovacuum has a
- multi-process architecture: there is a daemon process, called the
- autovacuum launcher, which is in charge of starting
- an autovacuum worker process on each database every
- seconds.
+
Beginning in
PostgreSQL 8.3, autovacuum has a
+ multi-process architecture: there is a daemon process, called the
+ autovacuum launcher, which is in charge of starting
+ an autovacuum worker process on each database every
+ seconds.
and ANALYZE> work to do takes too long to run, the deadline may
be failed to meet for other databases. Also, if a particular database
takes long to process, more than one worker may be processing it
- simultaneously. The workers are smart enough to avoid repeating work that
- other workers have done, so this is normally not a problem. Note that the
- number of running workers does not count towards the
- linkend="guc-max-connections"> nor the
- linkend="guc-superuser-reserved-connections"> limits.
+ simultaneously. The workers are smart enough to avoid repeating work that
+ other workers have done, so this is normally not a problem. Note that the
+
number of running workers does not count towards the
+
linkend="guc-max-connections"> nor the
+ linkend="guc-superuser-reserved-connections"> limits.