Re: clarify "rewritten" in pg_checksums docs

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Banck <michael(dot)banck(at)credativ(dot)de>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: clarify "rewritten" in pg_checksums docs
Date: 2020-09-01 13:29:17
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 1 Sep 2020, at 15:13, Michael Banck <michael(dot)banck(at)credativ(dot)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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2020-09-01 13:34:11 Re: clarify "rewritten" in pg_checksums docs
Previous Message Tomas Vondra 2020-09-01 13:14:26 Re: WIP: WAL prefetch (another approach)