aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2012-10-09 08:15:23 +0100
committerSimon Riggs <simon@2ndQuadrant.com>2012-10-09 08:15:23 +0100
commit82e429794b348cd80c1d1b011e21ffac98bc6e88 (patch)
tree1f5c0d08f151e43a276527c75ea52b49c02c45b8 /doc/src
parentbc433317ae2b0494dea4526b89dc7bb90a65d79b (diff)
downloadpostgresql-82e429794b348cd80c1d1b011e21ffac98bc6e88.tar.gz
postgresql-82e429794b348cd80c1d1b011e21ffac98bc6e88.zip
Add microsecs/op display to pg_test_fsync utility
e.g. fsync 2103.613 ops/sec ( 475 microsecs/op) Peter Geoghegan
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/pgtestfsync.sgml13
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/src/sgml/pgtestfsync.sgml b/doc/src/sgml/pgtestfsync.sgml
index 95ba3b81e0c..00ef209fa25 100644
--- a/doc/src/sgml/pgtestfsync.sgml
+++ b/doc/src/sgml/pgtestfsync.sgml
@@ -30,11 +30,14 @@
<application>pg_test_fsync</> is intended to give you a reasonable
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
- identified I/O problem. However, differences shown by <application>pg_test_fsync</application>
- might not make any difference in real database throughput, especially
- since many database servers are not speed-limited by their transaction
- logs.
+ as well as supplying diagnostic information in the event of an identified I/O
+ problem. However, differences shown by
+ <application>pg_test_fsync</application> might not make any significant
+ difference in real database throughput, especially since many database servers
+ are not speed-limited by their transaction logs.
+ <application>pg_test_fsync</application> reports average file sync operation
+ time in microseconds for each wal_sync_method, which can be used to inform
+ efforts to optimize the value of <varname>commit_delay</varname>.
</para>
</refsect1>