aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-05-02 18:26:54 +0000
committerBruce Momjian <bruce@momjian.us>2005-05-02 18:26:54 +0000
commit76668e6eb468caa6e09af71d6bee820e2dc0fc3c (patch)
tree4d036964b0b551dde801c82db1f78b41ab7a4a77 /doc/src
parentb656150ec0b7bab95cb04f4d11ffa46f9fd4118d (diff)
downloadpostgresql-76668e6eb468caa6e09af71d6bee820e2dc0fc3c.tar.gz
postgresql-76668e6eb468caa6e09af71d6bee820e2dc0fc3c.zip
Check the file system on postmaster startup and report any unreferenced
files in the server log. Heikki Linnakangas
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/maintenance.sgml19
1 files changed, 18 insertions, 1 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 5775d8d1ee7..6315dacf404 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.41 2005/02/20 02:21:26 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.42 2005/05/02 18:26:52 momjian Exp $
-->
<chapter id="maintenance">
@@ -474,6 +474,23 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
</para>
</sect1>
+ <sect1 id="check-files-after-crash">
+ <title>Check files after crash</title>
+
+ <indexterm zone="check-files-after-crash">
+ <primary>stale file</primary>
+ </indexterm>
+
+ <para>
+ <productname>PostgreSQL</productname> recovers automatically after crash
+ using the write-ahead log (see <xref linkend="wal">) and no manual
+ operations are normally needed. However, if there was a transaction running
+ when the crash occured that created or dropped a relation, the
+ transaction might have left a stale file in the data directory. If this
+ happens, you will get a notice in the log file stating which files can be
+ deleted.
+ </para>
+ </sect1>
<sect1 id="logfile-maintenance">
<title>Log File Maintenance</title>