From 823702be9d5e92392e2ff4d026aac4704000aed4 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 7 Dec 2005 14:35:45 +0000
Subject: [PATCH] Improve lazy vacuum wording.

---
 doc/src/sgml/maintenance.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index a3800c6082..5dfbd58b6c 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.52 2005/12/07 05:35:53 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.53 2005/12/07 14:35:45 momjian Exp $
 -->
 
 <chapter id="maintenance">
@@ -142,8 +142,8 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.52 2005/12/07 05:35:53 momj
     just <command>VACUUM</command>, marks expired 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
-    at the end of the table and an exclusive lock can be obtained easily
-    on the table. Unused space at the start or middle of the file does
+    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
     operating system. This variant of <command>VACUUM</command> can be
     run concurrently with normal database operations.
-- 
GitLab