summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/contrib.sgml1
-rw-r--r--doc/src/sgml/filelist.sgml1
-rw-r--r--doc/src/sgml/pgtestfsync.sgml70
3 files changed, 72 insertions, 0 deletions
diff --git a/doc/src/sgml/contrib.sgml b/doc/src/sgml/contrib.sgml
index d78847395e5..f5bd493543f 100644
--- a/doc/src/sgml/contrib.sgml
+++ b/doc/src/sgml/contrib.sgml
@@ -112,6 +112,7 @@ psql -d dbname -f <replaceable>SHAREDIR</>/contrib/<replaceable>module</>.sql
&pgstandby;
&pgstatstatements;
&pgstattuple;
+ &pgtestfsync;
&pgtrgm;
&pgupgrade;
&seg;
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index aa2d801deb7..9d4cfc927ba 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -124,6 +124,7 @@
<!entity pgstandby SYSTEM "pgstandby.sgml">
<!entity pgstatstatements SYSTEM "pgstatstatements.sgml">
<!entity pgstattuple SYSTEM "pgstattuple.sgml">
+<!entity pgtestfsync SYSTEM "pgtestfsync.sgml">
<!entity pgtrgm SYSTEM "pgtrgm.sgml">
<!entity pgupgrade SYSTEM "pgupgrade.sgml">
<!entity seg SYSTEM "seg.sgml">
diff --git a/doc/src/sgml/pgtestfsync.sgml b/doc/src/sgml/pgtestfsync.sgml
new file mode 100644
index 00000000000..e4b7ecaaa3e
--- /dev/null
+++ b/doc/src/sgml/pgtestfsync.sgml
@@ -0,0 +1,70 @@
+<!-- doc/src/sgml/pgtestfsync.sgml -->
+
+<sect1 id="pgtestfsync">
+ <title>pg_test_fsync</title>
+
+ <indexterm zone="pgtestfsync">
+ <primary>pg_test_fsync</primary>
+ </indexterm>
+
+ <para>
+ <application>pg_test_fsync</> is intended to give you a reasonable
+ idea of what the fastest fsync_method is on your specific system,
+ as well as supplying diagnostic information in the event of an
+ identified I/O problem. However, differences shown by test_fsync
+ might not make any difference in real database throughput, especially
+ since many database servers are not speed-limited by their transaction
+ logs.
+ </para>
+
+ <sect2>
+ <title>Usage</title>
+
+ <sect2>
+ <title><application>pg_test_fsync</> Options</title>
+
+ <para>
+ <application>pg_test_fsync</application> accepts the following command-line arguments:
+
+ <variablelist>
+
+ <varlistentry>
+ <term><option>-f</option></term>
+ <term><option>--filename</option></term>
+ <listitem>
+ <para>
+ Specifies the filename for test. The file should be in the
+ same file system as the <filename>pg_xlog</> directory.
+ <filename>/pg_xlog</> contains the <acronym>WAL</> files.)
+ The default is <filename>test_fsync.out</> in the current
+ directory.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>-o</option></term>
+ <term><option>--ops-per-test</option></term>
+ <listitem>
+ <para>
+ Specifies the number of operations per test. The more operations
+ per test, the greater the test's accuracy. The default is
+ 2000.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+ </para>
+
+ </sect2>
+
+ <sect2>
+ <title>Author</title>
+
+ <para>
+ Bruce Momjian <email>bruce@momjian.us</email>
+ </para>
+ </sect2>
+
+</sect1>