From: David Steele <david@pgmasters.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-committers@postgresql.org
Subject: Re: pgsql: Make WAL segment size configurable at initdb time.
Date: Thu, 20 Sep 2018 21:14:51 -0400
Message-ID: <4b5568f5-72b7-5355-3450-973e11447569@pgmasters.net> (raw)
In-Reply-To: <20180920235932.GD1338@paquier.xyz>
References: <E1duXBW-0003QB-4d@gemulon.postgresql.org>
<68ea97d6-2ed9-f339-e57d-ab3a33caf3b1@pgmasters.net>
<20180920235932.GD1338@paquier.xyz>
On 9/20/18 7:59 PM, Michael Paquier wrote:
> 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?
Oddly, the GUC reports 16GB on `show wal_segment_size` but you get 2048
when querying pg_settings. I thought that was just the normal behavior
for older versions -- and it might be a problem to change it.
--
-David
david@pgmasters.net
Attachments:
signature.asc (application/pgp-signature, 873B) 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: david@pgmasters.net, michael@paquier.xyz, andres@anarazel.de
Subject: Re: pgsql: Make WAL segment size configurable at initdb time.
In-Reply-To: <4b5568f5-72b7-5355-3450-973e11447569@pgmasters.net>
* 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