diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/runtime.sgml | 13 | ||||
| -rw-r--r-- | doc/src/sgml/wal.sgml | 27 |
2 files changed, 10 insertions, 30 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index afb7659af55..d97e368765d 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.129 2002/08/30 00:28:40 tgl Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.130 2002/08/30 16:50:49 momjian Exp $ --> <Chapter Id="runtime"> @@ -1950,17 +1950,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' </varlistentry> <varlistentry> - <term><varname>WAL_FILES</varname> (<type>integer</type>)</term> - <listitem> - <para> - Number of log files that are created in advance at checkpoint - time. This option can only be set at server start or in the - <filename>postgresql.conf</filename> file. - </para> - </listitem> - </varlistentry> - - <varlistentry> <term><varname>WAL_SYNC_METHOD</varname> (<type>string</type>)</term> <listitem> <para> diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 5c83b9f1e93..0baebb3c093 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.16 2002/07/05 19:06:11 momjian Exp $ --> +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.17 2002/08/30 16:50:50 momjian Exp $ --> <chapter id="wal"> <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title> @@ -276,9 +276,6 @@ By default a new 16MB segment file is created only if more than 75% of the current segment has been used. This is inadequate if the system generates more than 4MB of log output between checkpoints. - One can instruct the server to pre-create up to 64 log segments - at checkpoint time by modifying the <varname>WAL_FILES</varname> - configuration parameter. </para> <para> @@ -306,20 +303,14 @@ <para> The number of 16MB segment files will always be at least - <varname>WAL_FILES</varname> + 1, and will normally not exceed - <varname>WAL_FILES</varname> + MAX(<varname>WAL_FILES</varname>, - <varname>CHECKPOINT_SEGMENTS</varname>) + 1. This may be used to - estimate space requirements for WAL. Ordinarily, when an old log - segment files are no longer needed, they are recycled (renamed to - become the next sequential future segments). If, due to a short-term - peak of log output rate, there are more than - <varname>WAL_FILES</varname> + MAX(<varname>WAL_FILES</varname>, - <varname>CHECKPOINT_SEGMENTS</varname>) + 1 segment files, then - unneeded segment files will be deleted instead of recycled until the - system gets back under this limit. (If this happens on a regular - basis, <varname>WAL_FILES</varname> should be increased to avoid it. - Deleting log segments that will only have to be created again later - is expensive and pointless.) + 1, and will normally not exceed <varname>CHECKPOINT_SEGMENTS</varname>) + + 1. This may be used to estimate space requirements for WAL. + Ordinarily, when old log segment files are no longer needed, + they are recycled (renamed to become the next sequential future + segments). If, due to a short-term peak of log output rate, there + are more than <varname>CHECKPOINT_SEGMENTS</varname>) + 1 segment files, + the unneeded segment files will be deleted instead of recycled until the + system gets back under this limit. </para> <para> |