Correct WAL space calculation formula in docs.

Error pointed out by Fujii Masao, though not his patch.
This commit is contained in:
Simon Riggs 2010-10-15 10:17:12 +01:00
parent 23177114c6
commit 915116bc62

View File

@ -450,9 +450,9 @@
<para> <para>
There will always be at least one WAL segment file, and will normally There will always be at least one WAL segment file, and will normally
not be more than (2 + <varname>checkpoint_completion_target</varname>) * <varname>checkpoint_segments</varname> + 1 not be more files than the higher of <xref linkend="guc-wal-keep-segments"> or
or <varname>checkpoint_segments</> + <xref linkend="guc-wal-keep-segments"> + 1 (2 + <varname>checkpoint_completion_target</varname>) * <varname>checkpoint_segments</varname> + 1.
files. Each segment file is normally 16 MB (though this size can be Each segment file is normally 16 MB (though this size can be
altered when building the server). You can use this to estimate space altered when building the server). You can use this to estimate space
requirements for <acronym>WAL</acronym>. requirements for <acronym>WAL</acronym>.
Ordinarily, when old log segment files are no longer needed, they Ordinarily, when old log segment files are no longer needed, they