sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-22 00:02:02 -04:00
Code Issues Projects Releases Wiki Activity

Improve wording after wal_files removal.

Browse Source
This commit is contained in:
Bruce Momjian 2002-08-30 16:53:34 +00:00
parent 63653f7ffa
commit 2c65658c04
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/wal.sgml
View File

@ -1,4 +1,4 @@
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.17 2002/08/30 16:50:50 momjian Exp $ --> <!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.18 2002/08/30 16:53:34 momjian Exp $ -->
<chapter id="wal"> <chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title> <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@ -302,10 +302,10 @@
</para> </para>
<para> <para>
The number of 16MB segment files will always be at least There will be at least one 16MB segment file, and will normally
1, and will normally not exceed <varname>CHECKPOINT_SEGMENTS</varname>) not be more than <varname>CHECKPOINT_SEGMENTS</varname>)
+ 1. This may be used to estimate space requirements for WAL. + 1 files. You can use this to estimate space requirements for
Ordinarily, when old log segment files are no longer needed, WAL. Ordinarily, when old log segment files are no longer needed,
they are recycled (renamed to become the next sequential future they are recycled (renamed to become the next sequential future
segments). If, due to a short-term peak of log output rate, there segments). If, due to a short-term peak of log output rate, there
are more than <varname>CHECKPOINT_SEGMENTS</varname>) + 1 segment files, are more than <varname>CHECKPOINT_SEGMENTS</varname>) + 1 segment files,