clarify "rewritten" in pg_checksums docs - Mailing list pgsql-hackers

From Michael Banck
Subject clarify "rewritten" in pg_checksums docs
Date
Msg-id 858086b6a42fb7d17995b6175856f7e7ec44d0a2.camel@credativ.de
Whole thread Raw
Responses Re: clarify "rewritten" in pg_checksums docs  (Daniel Gustafsson <daniel@yesql.se>)
List 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.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

Attachment

pgsql-hackers by date:

Previous
From: "k.jamison@fujitsu.com"
Date:
Subject: RE: [Patch] Optimize dropping of relation buffers using dlist
Next
From: Tomas Vondra
Date:
Subject: Re: WIP: WAL prefetch (another approach)