Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
Date
Msg-id 20220720.162506.763089690525031660.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
List pgsql-hackers
At Wed, 20 Jul 2022 10:02:22 +0530, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.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



pgsql-hackers by date:

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