Data pages are not currently checksummed by default, though full page images
recorded in WAL records will be protected; see
linkend="app-initdb-data-checksums">
initdb
- for details about enabling data page checksums.
+ for details about enabling data checksums.
+
+
Data Checksums
+
+
+
+ Data pages are not checksum protected by default, but this can optionally be
+ enabled for a cluster. When enabled, each data page will be assigned a
+ checksum that is updated when the page is written and verified every time
+ the page is read. Only data pages are protected by checksums, internal data
+ structures and temporary files are not.
+
+
+ Checksums are normally enabled when the cluster is initialized using
+ linkend="app-initdb-data-checksums">
initdb .
+ They can also be enabled or disabled at a later time as an offline
+ operation. Data checksums are enabled or disabled at the full cluster
+ level, and cannot be specified individually for databases or tables.
+
+
+ The current state of checksums in the cluster can be verified by viewing the
+ value of the read-only configuration variable
+ linkend="guc-data-checksums" /> by issuing the command SHOW
+ data_checksums.
+
+
+ When attempting to recover from corrupt data it may be necessary to bypass
+ the checksum protection in order to recover data. To do this, temporarily
+ set the configuration parameter .
+
+
+
+
Off-line Enabling of Checksums
+
+ application can be used to enable or disable data checksums, as well as
+ verify checksums, on an offline cluster.
+
+
+
+
+
Write-Ahead Logging (WAL )