Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
Date: 2022-07-18 18:30:28
Message-ID: 20220718183028.GC3642254@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Overall, these patches look reasonable.

On Mon, Jul 18, 2022 at 04:24:12PM +0530, Bharath Rupireddy wrote:
> record. Because the entire content of data pages is saved in the
> - log on the first page modification after a checkpoint (assuming
> + WAL record on the first page modification after a checkpoint (assuming
> <xref linkend="guc-full-page-writes"/> is not disabled), all pages
> changed since the checkpoint will be restored to a consistent
> state.

nitpick: I would remove the word "record" in this change.

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-18 18:45:10 Re: postgres_fdw: using TABLESAMPLE to collect remote sample
Previous Message Nathan Bossart 2022-07-18 18:18:42 Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work