mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-15 08:20:16 +08:00
Revert "Correct WAL space calculation formula in docs."
This reverts commit 915116bc62
.
Per discussion, the previous formula was in fact correct.
http://archives.postgresql.org/pgsql-docs/2010-10/msg00038.php
This commit is contained in:
parent
0d5deebe11
commit
2cae0aeb9c
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user