postgres.git / summary / log / commit / refs

commit    4bc8d9dc90bb98b915d9900a7c1a9482214814bb
Author:   Simon Riggs <simon@2ndQuadrant.com>
Date:     Fri Oct 15 09:19:10 2010 +0000
First released in: master (reverted before release), 9.0.2
Reverted by: 2cae0aeb9c61 (in 9.1.0)

    Correct WAL space calculation formula in docs.
    
    Error pointed out by Fujii Masao, though not his patch.


 doc/src/sgml/wal.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 70fc832e23d..757c884c87c 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -450,9 +450,9 @@
 
   <para>
    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
-   or <varname>checkpoint_segments</> + <xref linkend="guc-wal-keep-segments"> + 1
-   files.  Each segment file is normally 16 MB (though this size can be
+   not be more files than the higher of <xref linkend="guc-wal-keep-segments"> or
+   (2 + <varname>checkpoint_completion_target</varname>) * <varname>checkpoint_segments</varname> + 1.
+   Each segment file is normally 16 MB (though this size can be
    altered when building the server).  You can use this to estimate space
    requirements for <acronym>WAL</acronym>.
    Ordinarily, when old log segment files are no longer needed, they


[parent: fb9bb9f4cfb6]