|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.86 2008/06/16 03:13:14 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.87 2008/12/08 20:30:58 mha Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="maintenance"> |
4 | 4 | <title>Routine Database Maintenance Tasks</title> |
@@ -522,10 +522,16 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". |
522 | 522 | The <quote>autovacuum daemon</> actually consists of multiple processes. |
523 | 523 | There is a persistent daemon process, called the |
524 | 524 | <firstterm>autovacuum launcher</firstterm>, which is in charge of starting |
525 | | - an <firstterm>autovacuum worker</firstterm> process on each database every |
526 | | - <xref linkend="guc-autovacuum-naptime"> seconds. On each run, the worker |
527 | | - process checks each table within that database, and executes |
528 | | - <command>VACUUM</> and/or <command>ANALYZE</> commands as needed. |
| 525 | + <firstterm>autovacuum worker</firstterm> processes for all databases. The |
| 526 | + launcher will distribute the work across time, but attempt to start one |
| 527 | + worker on each database every <xref linkend="guc-autovacuum-naptime"> |
| 528 | + seconds. One worker will be launched for each database, with a maximum |
| 529 | + of <xref linkend="guc-autovacuum-max-workers"> processes running at the |
| 530 | + same time. If there are more than |
| 531 | + <xref linkend="guc-autovacuum-max-workers"> databases to be processed, |
| 532 | + the next database will be processed as soon as the first worker finishes. |
| 533 | + The worker processes will check each table within its database and |
| 534 | + execute <command>VACUUM</> and/or <command>ANALYZE</> as needed. |
529 | 535 | </para> |
530 | 536 |
|
531 | 537 | <para> |
|