clarify "rewritten" in pg_checksums docs
Michael Banck <michael.banck@credativ.de>
From: Michael Banck <michael.banck@credativ.de>
To: PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2020-09-01T13:13:58Z
Lists: pgsql-hackers
Attachments
- pg_checksums_docs.patch (text/x-patch) patch
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: michael.banck@credativ.de 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
Commits
-
doc: Tweak sentence for pg_checksums when enabling checksums
- 87483c7bb320 12.5 landed
- b7cf9e42ac2d 13.0 landed
- f0942b1327e8 14.0 landed