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

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: bharath(dot)rupireddyforpostgres(at)gmail(dot)com
Cc: nathandbossart(at)gmail(dot)com, 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-20 07:25:06
Message-ID: 20220720.162506.763089690525031660.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Wed, 20 Jul 2022 10:02:22 +0530, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote in
> Done. PSA v6 patch set.

Thanks!

- Specifies the minimum size of past log file segments kept in the
+ Specifies the minimum size of past WAL files kept in the

- log file by reducing the value of this parameter. On a system with
+ file by reducing the value of this parameter. On a system with

Looks fine. And postgresq.conf.sample has the following lines:

#archive_library = '' # library to use to archive a logfile segment

#archive_command = '' # command to use to archive a logfile segment

#archive_timeout = 0 # force a logfile segment switch after this

#restore_command = '' # command to use to restore an archived logfile segment

Aren't they need the same fix?

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-07-20 07:57:35 Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Previous Message Masahiko Sawada 2022-07-20 07:20:54 Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns