Re: Fix documentation for max_wal_size and min_wal_size

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: masao(dot)fujii(at)oss(dot)nttdata(dot)com
Cc: michael(at)paquier(dot)xyz, sirichamarthi22(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fix documentation for max_wal_size and min_wal_size
Date: 2023-04-24 02:03:26
Message-ID: 20230424.110326.996711541280904430.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Mon, 24 Apr 2023 10:57:56 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> So, to clarify the situation, I would phrase it like this:
>
> The default size is 80MB. Note that if you have changed the WAL
> segment size from the default of 16MB with the initdb option
> --wal-segsize, the tool should have added the settings with the values
> equal to five times the specified segment size to the configuration
> file.
>
> It might be a bit wordy, though..

Or would the following work?

The default size is 80MB. Note that initdb may have added the setting
for this value if you have specified the WAL segment size when running
the tool.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2023-04-24 02:48:24 Re: Support logical replication of DDLs
Previous Message Kyotaro Horiguchi 2023-04-24 01:57:56 Re: Fix documentation for max_wal_size and min_wal_size