Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: bharath.rupireddyforpostgres@gmail.com
Cc: nathandbossart@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2022-07-20T07:25:06Z
Lists: 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
Commits
-
Use the terminology "WAL file" not "log file" more consistently.
- 31dcfae83c00 16.0 landed