clarify "rewritten" in pg_checksums docs

From: Michael Banck <michael(dot)banck(at)credativ(dot)de>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: clarify "rewritten" in pg_checksums docs
Date: 2020-09-01 13:13:58
Message-ID: 858086b6a42fb7d17995b6175856f7e7ec44d0a2.camel@credativ.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(dot)banck(at)credativ(dot)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

Attachment Content-Type Size
pg_checksums_docs.patch text/x-patch 653 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-09-01 13:14:26 Re: WIP: WAL prefetch (another approach)
Previous Message k.jamison@fujitsu.com 2020-09-01 13:02:28 RE: [Patch] Optimize dropping of relation buffers using dlist