Update SGML docs to point to new /contrib/pg_test_fsync.

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 10ce786f15225a533f0e153e4cf09c7c08da7d94..e7a5a9182609be8965e583d7f8972dce6c5b09b8 100644 (file)
--- a/doc/src/sgml/wal.sgml
+++ b/doc/src/sgml/wal.sgml
@@ -130,7 +130,7 @@
    (BBU) disk controllers.  In such setups, the synchronize
    command forces all data from the controller cache to the disks,
    eliminating much of the benefit of the BBU.  You can run the utility
-   src/tools/fsync in the PostgreSQL source tree to see
+   contrib/pg_test_fsync in the PostgreSQL source tree to see
    if you are affected.  If you are affected, the performance benefits
    of the BBU can be regained by turning off write barriers in
    the file system or reconfiguring the disk controller, if that is
@@ -571,7 +571,7 @@
    the exception of fsync_writethrough, which can sometimes
    force a flush of the disk cache even when other options do not do so.
    However, it's quite platform-specific which one will be the fastest;
-   you can test option speeds using the utility src/tools/fsync
+   you can test option speeds using the utility contrib/pg_test_fsync
    in the PostgreSQL source tree.
    Note that this parameter is irrelevant if fsync
    has been turned off.