From: Michael Paquier <michael@paquier.xyz>
To: David Steele <david@pgmasters.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql: Make WAL segment size configurable at initdb time.
Date: Fri, 21 Sep 2018 08:59:32 +0900
Message-ID: <20180920235932.GD1338@paquier.xyz> (raw)
In-Reply-To: <68ea97d6-2ed9-f339-e57d-ab3a33caf3b1@pgmasters.net>
References: <E1duXBW-0003QB-4d@gemulon.postgresql.org>
<68ea97d6-2ed9-f339-e57d-ab3a33caf3b1@pgmasters.net>
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
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, david@pgmasters.net, andres@anarazel.de
Subject: Re: pgsql: Make WAL segment size configurable at initdb time.
In-Reply-To: <20180920235932.GD1338@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox