doc: clarify default checksum behavior in non-master branches
authorBruce Momjian <[email protected]>
Fri, 21 Feb 2025 18:03:29 +0000 (13:03 -0500)
committerBruce Momjian <[email protected]>
Fri, 21 Feb 2025 18:03:29 +0000 (13:03 -0500)
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 <[email protected]>
Reviewed-by: Laurenz Albe
Discussion: https://postgr.es/m/173928241056.707.3989867022954178032@wrigleys.postgresql.org

Backpatch-through: 14

doc/src/sgml/wal.sgml

index 5a2c693849b6e34347395ef804afb2a8b365dd0d..1ecca196ed9fa4725fee144dbfdac0be0b3dcb66 100644 (file)
   </para>
 
   <para>
-   Checksums are normally enabled when the cluster is initialized using <link
+   Checksums can be enabled 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