aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/wal.sgml13
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 00f0c459ace..e706ee271c6 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.2 2001/02/18 04:50:43 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.3 2001/02/26 00:50:07 tgl Exp $ -->
<chapter id="wal">
<title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@@ -295,10 +295,13 @@
record to the log with <function>LogInsert</function> but before
performing a <function>LogFlush</function>. This delay allows other
backends to add their commit records to the log so as to have all
- of them flushed with a single log sync. Unfortunately, this
- mechanism is not fully implemented at release 7.1, so there is at
- present usually no benefit to be gained from increasing this parameter
- above its default value of zero.
+ of them flushed with a single log sync. No sleep will occur if fsync
+ is not enabled or if fewer than <varname>COMMIT_SIBLINGS</varname>
+ other backends are not currently in active transactions; this avoids
+ sleeping when it's unlikely that any other backend will commit soon.
+ Note that on most platforms, the resolution of a sleep request is
+ ten milliseconds, so that any nonzero <varname>COMMIT_DELAY</varname>
+ setting between 1 and 10000 microseconds will have the same effect.
</para>
</sect1>
</chapter>