Re: Fix documentation for max_wal_size and min_wal_size
От | sirisha chamarthi |
---|---|
Тема | Re: Fix documentation for max_wal_size and min_wal_size |
Дата | |
Msg-id | CAKrAKeVaGe6JLn3vsbJHoZg35Qq_MLeONu-MGEoTkVPkH06rww@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Fix documentation for max_wal_size and min_wal_size (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Fix documentation for max_wal_size and min_wal_size
|
Список | pgsql-hackers |
Hi
On Mon, Apr 17, 2023 at 9:38 PM Michael Paquier <michael@paquier.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.ntt@gmail.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."
В списке pgsql-hackers по дате отправления: