index 3af065615bc0dd8d21f29b9ddb822c172446a978..a12aa3abf01a8a867fd05349c89d8e25dfddd550 100644 (file)
</listitem>
<listitem>
<para>
- File system or storage subsystem faults where checksums happen to
- simply not be enabled.
+ File system or storage subsystem faults when data checksums are
+ disabled.
</para>
<para>
Note that <filename>amcheck</filename> examines a page as represented in some
index 71c4f96d0544bb017d8607e85db8dc5d5b3dfac0..e698e74e11633dba434411dce23ab868e79a39c4 100644 (file)
@@ -3532,8 +3532,8 @@ description | Waiting for a newly initialized WAL file to reach durable storage
</para>
<para>
Number of data page checksum failures detected in this
- database (or on a shared object), or NULL if data checksums are not
- enabled.
+ database (or on a shared object), or NULL if data checksums are
+ disabled.
</para></entry>
</row>
@@ -3543,8 +3543,8 @@ description | Waiting for a newly initialized WAL file to reach durable storage
</para>
<para>
Time at which the last data page checksum failure was detected in
- this database (or on a shared object), or NULL if data checksums are not
- enabled.
+ this database (or on a shared object), or NULL if data checksums are
+ disabled.
</para></entry>
</row>
index 27e0598f74c01206751cc87b909bb8a8ab2a5b6a..487c5d758ffbfd9c0eb13fae77c0a7252b632ad0 100644 (file)
@@ -85,7 +85,7 @@ test=# SELECT * FROM page_header(get_raw_page('pg_class', 0));
<para>
The <structfield>checksum</structfield> field is the checksum stored in
the page, which might be incorrect if the page is somehow corrupted. If
- data checksums are not enabled for this instance, then the value stored
+ data checksums are disabled for this instance, then the value stored
is meaningless.
</para>
</listitem>
index 52b5b8f793bc111aeaa95f2a5e27fab76ab726c4..4fc09761115e9234df5c9fd741a07d8c8dcc9143 100644 (file)
</listitem>
<listitem>
<para>
- Data pages are not currently checksummed by default, though full page images
- recorded in WAL records will be protected; see <link
- linkend="app-initdb-data-checksums"><application>initdb</application></link>
- for details about enabling data checksums.
+ Data pages are checksummed by default, and full page images
+ recorded in WAL records are always checksum protected.
</para>
</listitem>
<listitem>
</indexterm>
<para>
- By default, data pages are not protected by checksums, but this can
- optionally be enabled for a cluster. When enabled, each data page includes
+ By default, data pages are protected by checksums, but this can
+ optionally be disabled for a cluster. When enabled, each data page includes
a checksum that is updated when the page is written and verified each time
the page is read. Only data pages are protected by checksums; internal data
structures and temporary files are not.
</para>
<para>
- Checksums are normally enabled when the cluster is initialized using <link
+ Checksums can be disabled when the cluster is initialized using <link
linkend="app-initdb-data-checksums"><application>initdb</application></link>.
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