Re: Fix documentation for max_wal_size and min_wal_size

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: sirisha chamarthi <sirichamarthi22(at)gmail(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(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-18 04:38:27
Message-ID: ZD4ewyz1/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Mon, Apr 17, 2023 at 07:57:58PM -0700, sirisha chamarthi wrote:
> On Fri, Apr 14, 2023 at 1:01 AM Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
> wrote:
>> So, I personally think it should be written like this: "The default
>> size is 80MB. However, if you have changed the WAL segment size from
>> the default of 16MB, it will be five times the segment size.", but I'm
>> not sure what the others think about this..

Yes, I was under the impression that this should mention 16MB, but
I'd also add a note about initdb when a non-default value is specified
for the segment size.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-18 05:44:39 Should we put command options in alphabetical order in the doc?
Previous Message Michael Paquier 2023-04-18 04:34:00 Re: A Question about InvokeObjectPostAlterHook