aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-02-01 16:43:51 -0500
committerBruce Momjian <bruce@momjian.us>2011-02-01 16:44:22 -0500
commit7106f74e2a6feb31c022dd98e7d93ab656dc079d (patch)
treeb90e831a8c6414bedbb765f1bc4ef7ce09ec0850 /doc/src
parent15f55cc38a82dfa3d7898a7c30a303b1b3e87dc3 (diff)
downloadpostgresql-7106f74e2a6feb31c022dd98e7d93ab656dc079d.tar.gz
postgresql-7106f74e2a6feb31c022dd98e7d93ab656dc079d.zip
Clarify documentation to state that "zero_damaged_pages" does not force
data to disk, so the table or index should be recreated before the parameter is turned off again.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3a0f755b080..141430c56d2 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -6059,15 +6059,17 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
<para>
Detection of a damaged page header normally causes
<productname>PostgreSQL</> to report an error, aborting the current
- command. Setting <varname>zero_damaged_pages</> to on causes
- the system to instead report a warning, zero out the damaged page,
- and continue processing. This behavior <emphasis>will destroy data</>,
- namely all the rows on the damaged page. But it allows you to get
+ transaction. Setting <varname>zero_damaged_pages</> to on causes
+ the system to instead report a warning, zero out the damaged
+ page in memory, and continue processing. This behavior <emphasis>will destroy data</>,
+ namely all the rows on the damaged page. However, it does allow you to get
past the error and retrieve rows from any undamaged pages that might
- be present in the table. So it is useful for recovering data if
+ be present in the table. It is useful for recovering data if
corruption has occurred due to a hardware or software error. You should
generally not set this on until you have given up hope of recovering
- data from the damaged pages of a table. The
+ data from the damaged pages of a table. Zerod-out pages are not
+ forced to disk so it is recommended to recreate the table or
+ the index before turning this parameter off again. The
default setting is <literal>off</>, and it can only be changed
by a superuser.
</para>