postgres.git / summary / log / commit / refs

commit    4ed6001d7889f534e052e67e39acc2eb477fc645
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Thu Jul 18 01:06:50 2019 +0000

    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


 doc/src/sgml/ref/initdb.sgml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index 7fc3152c6d3..da5c8f53075 100644
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -216,11 +216,10 @@ PostgreSQL documentation
        <para>
         Use checksums on data pages to help detect corruption by the
         I/O system that would otherwise be silent. Enabling checksums
-        may incur a noticeable performance penalty. This option can only
-        be set during initialization, and cannot be changed later. If
-        set, checksums are calculated for all objects, in all databases. All
-        checksum failures will be reported in the <xref
-        linkend="pg-stat-database-view"/> view.
+        may incur a noticeable performance penalty. If set, checksums
+        are calculated for all objects, in all databases. All checksum
+        failures will be reported in the
+        <xref linkend="pg-stat-database-view"/> view.
        </para>
       </listitem>
      </varlistentry>


[parent: d4f283162e8d]