Re: Fix data checksum progress reporting docs

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix data checksum progress reporting docs
Date: 2026-07-09 08:28:18
Message-ID: 8D4EF043-0DA9-4DF1-A28C-E3598167D1D2@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

> On 9 Jul 2026, at 02:17, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Wed, Jul 8, 2026 at 10:24 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> The proposed changes all look good to me, thanks!
>
> Thanks for the review! I've pushed the patch.
>
> BTW, this is a separate issue, but also related to the data checksums docs,
> I found that the glossary entry for "Auxiliary process" includes
> the data checksums worker and data checksums worker launcher.
> However, their own glossary entries describe them as background workers,
> and they are implemented as dynamic background workers.
>
> This seems inconsistent. Other dynamic background workers, such as
> logical replication apply workers, are not listed as auxiliary processes.
> I don't see why the data checksums worker and launcher should be treated
> differently.
>
> Wouldn't it be better to remove the data checksums worker and data
> checksums worker launcher from the "Auxiliary process" entry?

You are absolutely right. And when looking at it I think we can simplify the
entry a bit as well to make it fit the style of the page better. What do you
think about the attached?

--
Daniel Gustafsson

Attachment Content-Type Size
0001-doc-Fix-glossary-entry-for-data-checksums-workers.patch application/octet-stream 3.7 KB

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-07-09 21:58:55 Re: 66.6. Database Page Layout
Previous Message Fujii Masao 2026-07-09 00:17:46 Re: Fix data checksum progress reporting docs