From a228cc13aeabff308d6dfc98a1015865f5393fce Mon Sep 17 00:00:00 2001 From: Magnus Hagander Date: Mon, 9 Apr 2018 19:02:42 +0200 Subject: Revert "Allow on-line enabling and disabling of data checksums" This reverts the backend sides of commit 1fde38beaa0c3e66c340efc7cc0dc272d6254bb0. I have, at least for now, left the pg_verify_checksums tool in place, as this tool can be very valuable without the rest of the patch as well, and since it's a read-only tool that only runs when the cluster is down it should be a lot safer. --- doc/src/sgml/ref/initdb.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src/sgml/ref') diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml index 10a8a86a030..feefd9a41e0 100644 --- a/doc/src/sgml/ref/initdb.sgml +++ b/doc/src/sgml/ref/initdb.sgml @@ -214,9 +214,9 @@ PostgreSQL documentation 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. If set, checksums - are calculated for all objects, in all databases. See - for details. + 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. -- cgit v1.2.3