Re: doc: update the default of data checksums in the doc of pg_rewind

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: doc: update the default of data checksums in the doc of pg_rewind
Date: 2025-12-25 00:03:40
Message-ID: CAHGQGwGt3rkn=9G4LeTGqaS63ZS7gQTYXCaWEyt5NWEknpEn6A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 24, 2025 at 4:28 PM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> Hi,
>
> I noticed that the pg_rewind documentation still states that data
> checksums is disabled by default, but it has been changed to on since PG18.
>
> Here's a small patch to update this.

Thanks for the patch!

- the cluster was initialized with
<application>initdb</application>. Neither of these
- are currently on by default. <xref linkend="guc-full-page-writes"/>
- must also be set to <literal>on</literal>, but is enabled by default.
+ the cluster was initialized with <application>initdb</application>
(the latter
+ being the default). <xref linkend="guc-full-page-writes"/> must also be set
+ to <literal>on</literal>, but is enabled by default.

Isn't "(the default)" enough here instead of "(the latter being the default)"?

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Naga Appani 2025-12-25 00:09:14 Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring
Previous Message Michael Paquier 2025-12-24 23:45:20 Re: Switch buffile.c/h to use pgoff_t