From 57e084718097bd03598a3db8c06b3ba72670737d Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sun, 18 Feb 2001 04:50:43 +0000
Subject: Change default commit_delay to zero, update documentation.

---
 doc/src/sgml/wal.sgml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 06198bd6e1c..00f0c459ace 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.1 2001/01/24 23:15:19 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.2 2001/02/18 04:50:43 tgl Exp $ -->
 
 <chapter id="wal">
  <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
@@ -290,15 +290,15 @@
   </para>
 
   <para>
-   The <varname>COMMIT_DELAY</varname> parameter defines for how long
-   the backend will be forced to sleep after writing a commit record
-   to the log with <function>LogInsert</function> call but before
+   The <varname>COMMIT_DELAY</varname> parameter defines for how many
+   microseconds the backend will sleep after writing a commit
+   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 no point in changing this parameter from its default value
-   of 5 microseconds.
+   present usually no benefit to be gained from increasing this parameter
+   above its default value of zero.
   </para>
  </sect1>
 </chapter>
-- 
cgit v1.2.3