From e669b8d751c8cf00386c78bb548e505648d00994 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 4 May 2001 23:11:37 +0000
Subject: [PATCH] COMMIT_DELAY and COMMIT_SIBLINGS were missing from the list
of WAL configuration parameters in chapter 3.
---
doc/src/sgml/runtime.sgml | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index f51585692a5..f046f1f820d 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.62 2001/05/04 02:54:33 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.63 2001/05/04 23:11:37 tgl Exp $
-->
<Chapter Id="runtime">
@@ -1229,6 +1229,35 @@ env PGOPTIONS='-c geqo=off' psql
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>COMMIT_DELAY (<type>integer</type>)</term>
+ <listitem>
+ <para>
+ Time delay between writing a commit record to the WAL buffer and
+ flushing the buffer out to disk, in microseconds. A nonzero delay
+ allows multiple transactions to be committed with only one fsync,
+ if system load is high enough that additional transactions become
+ ready to commit within the given interval. But the delay is just
+ wasted time if no other transactions become ready to commit.
+ Therefore, the delay is only performed if at least COMMIT_SIBLINGS
+ other transactions are active at the instant that a backend has
+ written its commit record.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>COMMIT_SIBLINGS (<type>integer</type>)</term>
+ <listitem>
+ <para>
+ Minimum number of concurrent open transactions to require before
+ performing the COMMIT_DELAY delay. A larger value makes it more
+ probable that at least one other transaction will become ready to
+ commit during the delay interval.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term>WAL_BUFFERS (<type>integer</type>)</term>
<listitem>
--
GitLab