Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit fb55fa0

Browse files
committed
Remove obsolete note about pg_vlock lock file.
1 parent aa903cf commit fb55fa0

File tree

2 files changed

+1
-13
lines changed

2 files changed

+1
-13
lines changed

doc/src/sgml/ref/vacuum.sgml

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.5 1999/07/22 15:09:15 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.6 1999/11/28 02:17:04 tgl Exp $
33
Postgres documentation
44
-->
55

@@ -184,16 +184,6 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
184184
recent changes, and allow the <productname>Postgres</productname>
185185
query optimizer to make better choices in planning user queries.
186186
</para>
187-
<para>
188-
If the server crashes during a <command>VACUUM</command> command,
189-
chances are it will leave a lock file hanging around.
190-
Attempts to re-run the <command>VACUUM</command> command
191-
result in an error message about the creation of a lock file. If you
192-
are sure <command>VACUUM</command> is not running,
193-
remove the <filename>pg_vlock</filename> file in your
194-
database directory
195-
(i.e. <filename><envar>PGDATA</envar>/base/dbname/pg_vlock</filename>).
196-
</para>
197187
</refsect2>
198188
</refsect1>
199189

src/bin/pgaccess/lib/help/vacuum.hlp

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ VACUUM opens every class in the database, cleans out records from rolled back tr
77

88
We recommend that active production databases be cleaned nightly, in order to keep statistics relatively current. The VACUUM query may be executed at any time, however. In particular, after copying a large class into Postgres or after deleting a large number of records, it may be a good idea to issue a VACUUM query. This will update the system catalogs with the results of all recent changes, and allow the Postgres query optimizer to make better choices in planning user queries.
99

10-
If the server crashes during a VACUUM command, chances are it will leave a lock file hanging around. Attempts to re-run the VACUUM command result in an error message about the creation of a lock file. If you are sure VACUUM is not running, remove the pg_vlock file in your database directory (i.e. PGDATA/base/dbname/pg_vlock).
11-
1210
" {} "Synopsis" {bold} "
1311
VACUUM \[ VERBOSE \] \[ ANALYZE \] \[ table \]
1412
VACUUM \[ VERBOSE \] ANALYZE \[ table \[ (column \[, ...\] ) \] \]

0 commit comments

Comments
 (0)