Re: Fix documentation for max_wal_size and min_wal_size

From: sirisha chamarthi <sirichamarthi22(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 08:46:21
Message-ID: CAKrAKeVaGe6JLn3vsbJHoZg35Qq_MLeONu-MGEoTkVPkH06rww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

On Mon, Apr 17, 2023 at 9:38 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> 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.
>

How about the text below?

"The default size is 80MB. However, if you have changed the WAL segment size
from the default of 16MB with the initdb option --wal-segsize, it will be
five times the segment size."

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2023-04-18 08:58:11 Re: Adding argument names to aggregate functions
Previous Message Richard Guo 2023-04-18 07:14:01 Re: Allowing parallel-safe initplans