1
0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00

doc: clarify default checksum behavior in non-master branches

Also simplify and correct data checksum wording in master now that it is
the default.  PG 13 did not have the awkward wording.

Reported-by: Felix <afripowered@gmail.com>

Reviewed-by: Laurenz Albe

Discussion: https://postgr.es/m/173928241056.707.3989867022954178032@wrigleys.postgresql.org

Backpatch-through: 14
This commit is contained in:
Bruce Momjian
2025-02-21 13:03:29 -05:00
parent 6ea0734e41
commit 901a1cf8b4
4 changed files with 12 additions and 14 deletions

View File

@@ -194,10 +194,8 @@
</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>
@@ -238,15 +236,15 @@
</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