aboutsummaryrefslogtreecommitdiff
path: root/src/bin/pgaccess/lib/help
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2000-03-31 11:22:36 +0000
committerBruce Momjian <bruce@momjian.us>2000-03-31 11:22:36 +0000
commita34ce62fdf91afdfb6e1d56d0b8e86d1ab92c4df (patch)
tree2b6c779c77cdb2a0f557fc317072441671b868e2 /src/bin/pgaccess/lib/help
parente854d3da54f22074e638dc126a298e064db1cb7a (diff)
downloadpostgresql-a34ce62fdf91afdfb6e1d56d0b8e86d1ab92c4df.tar.gz
postgresql-a34ce62fdf91afdfb6e1d56d0b8e86d1ab92c4df.zip
Update pgaccess to 0.98.5
Diffstat (limited to 'src/bin/pgaccess/lib/help')
-rw-r--r--src/bin/pgaccess/lib/help/vacuum.hlp2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/bin/pgaccess/lib/help/vacuum.hlp b/src/bin/pgaccess/lib/help/vacuum.hlp
index cbdf3551611..ec98382580e 100644
--- a/src/bin/pgaccess/lib/help/vacuum.hlp
+++ b/src/bin/pgaccess/lib/help/vacuum.hlp
@@ -7,6 +7,8 @@ VACUUM opens every class in the database, cleans out records from rolled back tr
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.
+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).
+
" {} "Synopsis" {bold} "
VACUUM \[ VERBOSE \] \[ ANALYZE \] \[ table \]
VACUUM \[ VERBOSE \] ANALYZE \[ table \[ (column \[, ...\] ) \] \]