Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
e669b8d7
Commit
e669b8d7
authored
23 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
COMMIT_DELAY and COMMIT_SIBLINGS were missing from the list of WAL
configuration parameters in chapter 3.
parent
8d2fe903
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/runtime.sgml
+30
-1
30 additions, 1 deletion
doc/src/sgml/runtime.sgml
with
30 additions
and
1 deletion
doc/src/sgml/runtime.sgml
+
30
−
1
View file @
e669b8d7
<!--
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.6
2
2001/05/04
02:54:33 momjian
Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.6
3
2001/05/04
23:11:37 tgl
Exp $
-->
-->
<Chapter Id="runtime">
<Chapter Id="runtime">
...
@@ -1229,6 +1229,35 @@ env PGOPTIONS='-c geqo=off' psql
...
@@ -1229,6 +1229,35 @@ env PGOPTIONS='-c geqo=off' psql
</listitem>
</listitem>
</varlistentry>
</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>
<varlistentry>
<term>WAL_BUFFERS (<type>integer</type>)</term>
<term>WAL_BUFFERS (<type>integer</type>)</term>
<listitem>
<listitem>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment