From f6bab284885a4594cfa8f199ba7458dca81059f3 Mon Sep 17 00:00:00 2001 From: Magnus Hagander Date: Mon, 8 Dec 2008 20:31:00 +0000 Subject: [PATCH] Clearify how processes are started by autovacuum, and what the effect of autovacuum_max_workers parameter is. Per discussion with Alvaro. --- doc/src/sgml/maintenance.sgml | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 26d9d5e0453..ce8f2513ac1 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,4 +1,4 @@ - + Routine Database Maintenance Tasks @@ -488,10 +488,16 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". Beginning in PostgreSQL 8.3, autovacuum has a multiprocess 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. On each run, the worker - process checks each table within that database, and VACUUM or - ANALYZE commands are issued as needed. + autovacuum worker processes for all databases. The + launcher will distribute the work across time, but attempt to start one + worker on each database every + seconds. One worker will be launched for each database, with a maximum + of processes running at the + same time. If there are more than + databases to be processed, + the next database will be processed as soon as the first worker finishes. + The worker processes will check each table within its database and + execute VACUUM and/or ANALYZE as needed.