On 2018-09-20 11:48:08 -0400, David Steele wrote: > Hi Andres, > > On 9/20/17 1:04 AM, Andres Freund wrote: > > > > Make WAL segment size configurable at initdb time. > > <...> > > > https://git.postgresql.org/pg/commitdiff/fc49e24fa69a15efacd5b8958115ed9c43c48f9a > It appears that fc49e24f missed updating the runtime config presets > documentation. > > Patch attached. > > Regards, > -- > -David > da...@pgmasters.net
> diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml > index e1073ac6d3..3bfd172441 100644 > --- a/doc/src/sgml/config.sgml > +++ b/doc/src/sgml/config.sgml > @@ -8440,10 +8440,8 @@ dynamic_library_path = > 'C:\tools\postgresql;H:\my_project\lib;$libdir' > </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> Why is this actually more correct? You mean because we have a conversion that does the mb conversion at display time? Greetings, Andres Freund
