From: Bruce Momjian Date: Wed, 18 Apr 2007 20:44:53 +0000 (+0000) Subject: Remove tabs from SGML source files. X-Git-Tag: REL8_3_BETA1~803 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=05cd021c3084327022955baa4746a2de0bcfbd42;p=thirdparty%2Fpostgresql.git Remove tabs from SGML source files. --- diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 2be11332c27..29a79dd5de0 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,4 +1,4 @@ - + Routine Database Maintenance Tasks @@ -481,11 +481,11 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". - 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. @@ -494,11 +494,11 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb". 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 nor the 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 nor the limits.