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

From Bharath Rupireddy
Subject Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
Date
Msg-id CALj2ACW8YwHiCr5PqvW8625Wx1ZaaVumHY-uzS1JDabvbrgVCw@mail.gmail.com
Whole thread Raw
In response to Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages
List pgsql-hackers
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.

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Windows default locale vs initdb
Next
From: Justin Pryzby
Date:
Subject: Re: Allowing REINDEX to have an optional name