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
0cf3db21
Commit
0cf3db21
authored
14 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Fix broken markup, also minor copy-editing.
parent
4609caf3
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/pgtestfsync.sgml
+14
-10
14 additions, 10 deletions
doc/src/sgml/pgtestfsync.sgml
with
14 additions
and
10 deletions
doc/src/sgml/pgtestfsync.sgml
+
14
−
10
View file @
0cf3db21
...
@@ -9,9 +9,10 @@
...
@@ -9,9 +9,10 @@
<para>
<para>
<application>pg_test_fsync</> is intended to give you a reasonable
<application>pg_test_fsync</> is intended to give you a reasonable
idea of what the fastest fsync_method is on your specific system,
idea of what the fastest <xref linkend="guc-wal-sync-method"> is on your
specific system,
as well as supplying diagnostic information in the event of an
as well as supplying diagnostic information in the event of an
identified I/O problem. However, differences shown by test_fsync
identified I/O problem. However, differences shown by
pg_
test_fsync
might not make any difference in real database throughput, especially
might not make any difference in real database throughput, especially
since many database servers are not speed-limited by their transaction
since many database servers are not speed-limited by their transaction
logs.
logs.
...
@@ -20,11 +21,13 @@
...
@@ -20,11 +21,13 @@
<sect2>
<sect2>
<title>Usage</title>
<title>Usage</title>
<sect2>
<synopsis>
<title><application>pg_test_fsync</> Options</title>
pg_test_fsync [options]
</synopsis>
<para>
<para>
<application>pg_test_fsync</application> accepts the following command-line arguments:
<application>pg_test_fsync</application> accepts the following
command-line options:
<variablelist>
<variablelist>
...
@@ -33,9 +36,10 @@
...
@@ -33,9 +36,10 @@
<term><option>--filename</option></term>
<term><option>--filename</option></term>
<listitem>
<listitem>
<para>
<para>
Specifies the filename for test. The file should be in the
Specifies the filename to write test data in.
same file system as the <filename>pg_xlog</> directory.
This file should be in the same file system that the
<filename>/pg_xlog</> contains the <acronym>WAL</> files.)
<filename>pg_xlog</> directory is or will be placed in.
(<filename>pg_xlog</> contains the <acronym>WAL</> files.)
The default is <filename>test_fsync.out</> in the current
The default is <filename>test_fsync.out</> in the current
directory.
directory.
</para>
</para>
...
@@ -48,8 +52,8 @@
...
@@ -48,8 +52,8 @@
<listitem>
<listitem>
<para>
<para>
Specifies the number of operations per test. The more operations
Specifies the number of operations per test. The more operations
per test, the greater the test's accuracy
. The default i
s
per test, the greater the test's accuracy
, but the longer it take
s
2000.
to run. The default is
2000.
</para>
</para>
</listitem>
</listitem>
</varlistentry>
</varlistentry>
...
...
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