aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNathan Bossart <nathan@postgresql.org>2024-08-09 10:52:37 -0500
committerNathan Bossart <nathan@postgresql.org>2024-08-09 10:52:37 -0500
commitb07a9ee36e57281efcd22bbca2bfd486c2037aa7 (patch)
tree70a177153dff0a9b465f21ca31baf2a7ba2118f9
parent120dd033761dbd70ad6267ff7255430bc8a989ed (diff)
downloadpostgresql-b07a9ee36e57281efcd22bbca2bfd486c2037aa7.tar.gz
postgresql-b07a9ee36e57281efcd22bbca2bfd486c2037aa7.zip
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
-rw-r--r--doc/src/sgml/wal.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index b9f719b151b..5a2c693849b 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -185,7 +185,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.
@@ -211,7 +211,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>