database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-05 09:19:17 +03:00
Code

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

Browse Source
This commit is contained in:
Bruce Momjian 2011-01-21 12:52:16 -05:00
parent b35bfcae93
commit 5925aa09a9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/wal.sgml
View File

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