From fb55fa04786a759befb356e404b29a25c72d0f8a Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 28 Nov 1999 02:17:43 +0000
Subject: Remove obsolete note about pg_vlock lock file.

---
 doc/src/sgml/ref/vacuum.sgml | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 87666f47276..e7761397a0f 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.5 1999/07/22 15:09:15 thomas Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.6 1999/11/28 02:17:04 tgl Exp $
 Postgres documentation
 -->
 
@@ -184,16 +184,6 @@ NOTICE:  Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
     recent changes, and allow the <productname>Postgres</productname> 
     query optimizer to make better choices in planning user queries.
    </para>
-   <para>
-    If the server crashes during a <command>VACUUM</command> command, 
-    chances are it will leave a lock file hanging around.  
-    Attempts to re-run the <command>VACUUM</command> command
-    result in an error message about the creation of a lock file.  If you
-    are sure <command>VACUUM</command> is not running, 
-    remove the <filename>pg_vlock</filename> file in your
-    database directory 
-    (i.e. <filename><envar>PGDATA</envar>/base/dbname/pg_vlock</filename>).
-   </para>
   </refsect2>
  </refsect1>
 
-- 
cgit v1.2.3