From: Nathan Bossart <nathan@postgresql.org>
Date: Fri, 9 Aug 2024 15:52:37 +0000 (-0500)
Subject: doc: Fix name of CRC algorithm in "Reliability" section.
X-Git-Tag: REL_16_5~123
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=93c82d0e6a252dc2fb6d6c7ed240508140cd1480;p=postgresql.git

doc: Fix name of CRC algorithm in "Reliability" section.

This section claims we use CRC-32 for WAL records and two-phase
state files, but we've actually used CRC-32C since v9.5 (commit
5028f22f6e).  Fix that.

Reviewed-by: Robert Haas
Discussion: https://postgr.es/m/ZrUFpLP-w2zTAHqq%40nathan
Backpatch-through: 12
---

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index bb2a61b8017..704cf06a74f 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -187,7 +187,7 @@
    <itemizedlist>
     <listitem>
      <para>
-      Each individual record in a WAL file is protected by a CRC-32 (32-bit) check
+      Each individual record in a WAL file is protected by a CRC-32C (32-bit) check
       that allows us to tell if record contents are correct. The CRC value
       is set when we write each WAL record and checked during crash recovery,
       archive recovery and replication.
@@ -213,7 +213,7 @@
     </listitem>
     <listitem>
      <para>
-      Individual state files in <filename>pg_twophase</filename> are protected by CRC-32.
+      Individual state files in <filename>pg_twophase</filename> are protected by CRC-32C.
      </para>
     </listitem>
     <listitem>