Re: pgsql: Make WAL segment size configurable at initdb time. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Make WAL segment size configurable at initdb time.
Date
Msg-id 20180920235932.GD1338@paquier.xyz
Whole thread Raw
In response to Re: pgsql: Make WAL segment size configurable at initdb time.  (David Steele <david@pgmasters.net>)
Responses Re: pgsql: Make WAL segment size configurable at initdb time.  (David Steele <david@pgmasters.net>)
List pgsql-committers
On Thu, Sep 20, 2018 at 11:48:08AM -0400, David Steele wrote:
>        </term>
>        <listitem>
>         <para>
> -        Reports the number of blocks (pages) in a WAL segment file.
> -        The total size of a WAL segment file in bytes is equal to
> -        <varname>wal_segment_size</varname> multiplied by <varname>wal_block_size</varname>;
> -        by default this is 16MB.  See <xref linkend="wal-configuration"/> for
> +        Reports the size of write ahead log segments.
> +        The default value is 16MB. See <xref linkend="wal-configuration"/> for
>          more information.
>         </para>
>        </listitem>

The GUC wal_segment_size reports as well 16MB in v10 or older versions,
so shouldn't the mention to wal_block_size be removed even further down?
--
Michael

Attachment

pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Remove special handling for open() in initdb for Windows
Next
From: David Steele
Date:
Subject: Re: pgsql: Make WAL segment size configurable at initdb time.