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

From Daniel Gustafsson
Subject Re: clarify "rewritten" in pg_checksums docs
Date
Msg-id A318B839-4935-4FCD-BD93-F9A141C16E22@yesql.se
Whole thread Raw
In response to clarify "rewritten" in pg_checksums docs  (Michael Banck <michael.banck@credativ.de>)
Responses Re: clarify "rewritten" in pg_checksums docs  (Michael Banck <michael.banck@credativ.de>)
List pgsql-hackers
> On 1 Sep 2020, at 15:13, Michael Banck <michael.banck@credativ.de> wrote:

> 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.

Makes sense, I can see that confusion.

> So maybe "rewritten in-place" is better, as per the attached?

Isn't "modified in-place" a more accurate description of the process?

cheers ./daniel



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: WIP: WAL prefetch (another approach)
Next
From: Michael Banck
Date:
Subject: Re: clarify "rewritten" in pg_checksums docs