diff options
author | Robert Haas <rhaas@postgresql.org> | 2010-10-27 21:24:02 -0400 |
---|---|---|
committer | Robert Haas <rhaas@postgresql.org> | 2010-10-27 21:24:02 -0400 |
commit | 2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b (patch) | |
tree | f7f4d7b83fb92d786feccb35230756d8f347c5f4 | |
parent | 0d5deebe11818a54f79ca66e1a1d41dae0e0b52b (diff) | |
download | postgresql-2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b.tar.gz postgresql-2cae0aeb9c61aef48b6de3fb5c4f7785a06bca0b.zip |
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
-rw-r--r-- | doc/src/sgml/wal.sgml | 6 |
1 files 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 |