Re: clarify "rewritten" in pg_checksums docs
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Banck <michael.banck@credativ.de>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Date: 2020-09-01T13:29:17Z
Lists: 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
Commits
-
doc: Tweak sentence for pg_checksums when enabling checksums
- 87483c7bb320 12.5 landed
- b7cf9e42ac2d 13.0 landed
- f0942b1327e8 14.0 landed