From 2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Wed, 27 Oct 2010 21:24:02 -0400
Subject: [PATCH] Revert "Correct WAL space calculation formula in docs."
This reverts commit 915116bc62db2aaec7001bde6610128f4cbd29f9.
Per discussion, the previous formula was in fact correct.
http://archives.postgresql.org/pgsql-docs/2010-10/msg00038.php
---
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 e7980b386e9..faac54530d9 100644
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -481,9 +481,9 @@
<para>
There will always be at least one WAL segment file, and will normally
- 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
+ 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
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
--
GitLab