Commit 1c1602b8 authored by Michael Paquier's avatar Michael Paquier

Simplify description of --data-checksums in documentation of initdb

The documentation mentioned that data checksums cannot be changed after
initialization, which is not true as pg_checksums can do that with its
--enable option introduced in v12.  This simply removes the sentence
telling so.

Reported-by: Basil Bourque
Author: Michael Paquier
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/15909-e9d74271f1647472@postgresql.org
Backpatch-through: 12
parent 93907478
...@@ -216,11 +216,10 @@ PostgreSQL documentation ...@@ -216,11 +216,10 @@ PostgreSQL documentation
<para> <para>
Use checksums on data pages to help detect corruption by the Use checksums on data pages to help detect corruption by the
I/O system that would otherwise be silent. Enabling checksums I/O system that would otherwise be silent. Enabling checksums
may incur a noticeable performance penalty. This option can only may incur a noticeable performance penalty. If set, checksums
be set during initialization, and cannot be changed later. If are calculated for all objects, in all databases. All checksum
set, checksums are calculated for all objects, in all databases. All failures will be reported in the
checksum failures will be reported in the <xref <xref linkend="pg-stat-database-view"/> view.
linkend="pg-stat-database-view"/> view.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment