Use "dead" rather than "expired" for vacuumable rows.

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 4b321ca31bfc205a7b7f5996abc5099dcc6e7db3..3603692ee2580ec1c41a114ba73d9b9d98381eaf 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.64 2006/11/05 22:42:07 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.65 2006/12/27 14:55:17 momjian Exp $ -->
 
 <chapter id="maintenance">
  <title>Routine Database Maintenance Tasks</title>
@@ -142,9 +142,9 @@
    <para>
     There are two variants of the <command>VACUUM</command>
     command. The first form, known as <quote>lazy vacuum</quote> or
-    just <command>VACUUM</command>, marks expired data in tables and
+    just <command>VACUUM</command>, marks dead data in tables and
     indexes for future reuse; it does <emphasis>not</emphasis> attempt
-    to reclaim the space used by this expired data unless the space is
+    to reclaim the space used by this dead data unless the space is
     at the end of the table and an exclusive table lock can be easily 
     obtained. Unused space at the start or middle of the file does
     not result in the file being shortened and space returned to the
@@ -155,7 +155,7 @@
    <para>
     The second form is the <command>VACUUM FULL</command>
     command. This uses a more aggressive algorithm for reclaiming the
-    space consumed by expired row versions. Any space that is freed by
+    space consumed by dead row versions. Any space that is freed by
     <command>VACUUM FULL</command> is immediately returned to the
     operating system. Unfortunately, this variant of the
     <command>VACUUM</command> command acquires an exclusive lock on

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 8ca884ccf3ea1a844c2c8c0d572c33d7cb26c00d..f72f36bf392ec169cb2e704150a10afc384a25a7 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.44 2006/12/23 01:58:40 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.45 2006/12/27 14:55:17 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -29,7 +29,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
   <title>Description</title>
 
   <para>
-   <command>VACUUM</command> reclaims storage occupied by expired tuples.
+   <command>VACUUM</command> reclaims storage occupied by dead tuples.
    In normal <productname>PostgreSQL</productname> operation, tuples that
    are deleted or obsoleted by an update are not physically removed from
    their table; they remain present until a <command>VACUUM</command> is
@@ -152,7 +152,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
    <para>
     We recommend that active production databases be
     vacuumed frequently (at least nightly), in order to
-    remove expired rows. After adding or deleting a large number
+    remove dead rows. After adding or deleting a large number
     of rows, it may be a good idea to issue a <command>VACUUM
     ANALYZE</command> command for the affected table. This will update the
     system catalogs with