Clarify autovacuum wording.
authorBruce Momjian <bruce@momjian.us>
Fri, 23 Sep 2005 02:42:34 +0000 (02:42 +0000)
committerBruce Momjian <bruce@momjian.us>
Fri, 23 Sep 2005 02:42:34 +0000 (02:42 +0000)
doc/src/sgml/release.sgml

index 04e62d3d8ac97ada269adb209c67711f5757f761..4a8b6a0b85d8dab711abbe8257ecb591e6cdffff 100644 (file)
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.372 2005/09/23 02:25:35 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.373 2005/09/23 02:42:34 momjian Exp $
 
 Typical markup:
 
@@ -177,9 +177,9 @@ pg_[A-Za-z0-9_]                 <application>
         Integrating autovacuum into the server allows it to be
         automatically started and stopped in sync with the database
         server, and allows autovacuum to be configured from
-        <filename>postgresql.conf</>.  Autovacuum now checks to see if
-        the database is in danger of xid wraparound and
-        <command>VACUUM</command>s the whole database if needed.
+        <filename>postgresql.conf</>.  Also autovacuum now checks
+        if the database is in danger of xid wraparound and
+        vacuums the database if needed.
        </para>
       </listitem>
      </varlistentry>