Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-20T11:55:33Z
Lists: pgsql-hackers
Attachments
- v7-0001-Use-WAL-segment-instead-of-log-segment.patch (application/octet-stream) patch v7-0001
- v7-0002-Consistently-use-WAL-file-s-in-docs.patch (application/octet-stream) patch v7-0002
On Wed, Jul 20, 2022 at 12:55 PM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > > 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? Indeed. Thanks. Now, they are in sync with their peers in .conf.sample file as well as description in guc.c. PSA v7 patch set. Regards, Bharath Rupireddy.
Commits
-
Use the terminology "WAL file" not "log file" more consistently.
- 31dcfae83c00 16.0 landed