| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Make WAL segment size configurable at initdb time. |
| Date: | 2018-09-20 23:59:32 |
| Message-ID: | 20180920235932.GD1338@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-09-21 01:14:51 | Re: pgsql: Make WAL segment size configurable at initdb time. |
| Previous Message | Michael Paquier | 2018-09-20 21:44:15 | pgsql: Remove special handling for open() in initdb for Windows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2018-09-21 00:06:36 | Re: FETCH FIRST clause PERCENT option |
| Previous Message | Michael Paquier | 2018-09-20 23:51:55 | Re: Changing the setting of wal_sender_timeout per standby |