Hi,
the pg_checksums docs mention that "When enabling checksums, every file
in the cluster is rewritten".
>From IRC discussions, "rewritten" seems ambiguous, it could mean that a
second copy of the file is written and then switched over, implying
increased storage demand during the operation.
So maybe "rewritten in-place" is better, as per the attached?
Michael
--
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax: +49 2166 9901-100
Email: [email protected]
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz
diff --git a/doc/src/sgml/ref/pg_checksums.sgml b/doc/src/sgml/ref/pg_checksums.sgml
index 8e7807f86b..1dd4e54ff1 100644
--- a/doc/src/sgml/ref/pg_checksums.sgml
+++ b/doc/src/sgml/ref/pg_checksums.sgml
@@ -47,8 +47,8 @@ PostgreSQL documentation
<para>
When verifying checksums, every file in the cluster is scanned. When
- enabling checksums, every file in the cluster is rewritten. Disabling
- checksums only updates the file <filename>pg_control</filename>.
+ enabling checksums, every file in the cluster is rewritten in-place.
+ Disabling checksums only updates the file <filename>pg_control</filename>.
</para>
</refsect1>
