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 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
+ identified I/O problem. However, differences shown by pg_test_fsync
might not make any difference in real database throughput, especially
since many database servers are not speed-limited by their transaction
logs.
Usage
-
+
+pg_test_fsync [options]
+
-
pg_test_fsync accepts the following command-line arguments:
+
pg_test_fsync accepts the following
+ command-line options:
- Specifies the filename for test. The file should be in the
- same file system as the pg_xlog> directory.
-
/pg_xlog> contains the WAL> files.)
+ Specifies the filename to write test data in.
+ This file should be in the same file system that the
+ pg_xlog> directory is or will be placed in.
+ (
pg_xlog> contains the WAL> files.)
The default is test_fsync.out> in the current
directory.
Specifies the number of operations per test. The more operations
- per test, the greater the test's accuracy. The default is
- 2000.
+ per test, the greater the test's accuracy, but the longer it takes
+ to run. The default is 2000.