1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Disk Full Failure</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 HREF="mailto:pgsql-docs@postgresql.org"><LINK
12 TITLE="PostgreSQL 7.4.1 Documentation"
13 HREF="index.html"><LINK
15 TITLE="Monitoring Disk Usage"
16 HREF="diskusage.html"><LINK
18 TITLE="Monitoring Disk Usage"
19 HREF="diskusage.html"><LINK
21 TITLE="Write-Ahead Logging (WAL)"
25 HREF="stylesheet.css"><META
27 CONTENT="2003-12-22T03:48:47"></HEAD
33 SUMMARY="Header navigation table"
43 >PostgreSQL 7.4.1 Documentation</TH
67 >Chapter 24. Monitoring Disk Usage</TD
96 >24.2. Disk Full Failure</A
99 > The most important disk monitoring task of a database administrator
100 is to make sure the disk doesn't grow full. A filled data disk may
101 result in subsequent corruption of database indexes, but not of the
102 tables themselves. If the WAL files are on the same disk (as
103 is the case for a default configuration) then a filled disk during
104 database initialization may result in corrupted or incomplete WAL
105 files. This failure condition is detected and the database server
106 will refuse to start up.
109 > If you cannot free up additional space on the disk by deleting
110 other things you can move some of the database files to other file
111 systems and create a symlink from the original location. But
115 > cannot save the location layout
116 information of such a setup; a restore would put everything back in
117 one place. To avoid running out of disk space, you can place the
118 WAL files or individual databases in other locations while creating
122 > documentation and <A
123 HREF="manage-ag-alternate-locs.html"
125 > for more information about that.
134 > Some file systems perform badly when they are almost full, so do
135 not wait until the disk is full to take action.
145 SUMMARY="Footer navigation table"
156 HREF="diskusage.html"
184 >Monitoring Disk Usage</TD
190 HREF="diskusage.html"
198 >Write-Ahead Logging (<ACRONYM