summaryrefslogtreecommitdiff
path: root/docs/programmer_reference/program_cache.html
diff options
context:
space:
mode:
authorLorry Tar Creator <lorry-tar-importer@baserock.org>2015-02-17 17:25:57 +0000
committer <>2015-03-17 16:26:24 +0000
commit780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch)
tree598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/program_cache.html
parent7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff)
downloadberkeleydb-master.tar.gz
Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz.HEADdb-6.1.23master
Diffstat (limited to 'docs/programmer_reference/program_cache.html')
-rw-r--r--docs/programmer_reference/program_cache.html41
1 files changed, 23 insertions, 18 deletions
diff --git a/docs/programmer_reference/program_cache.html b/docs/programmer_reference/program_cache.html
index 5bfbaf9e..a278318d 100644
--- a/docs/programmer_reference/program_cache.html
+++ b/docs/programmer_reference/program_cache.html
@@ -14,7 +14,7 @@
<body>
<div xmlns="" class="navheader">
<div class="libver">
- <p>Library Version 11.2.5.3</p>
+ <p>Library Version 12.1.6.1</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
@@ -22,9 +22,7 @@
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="program_ram.html">Prev</a> </td>
- <th width="60%" align="center">Chapter 15. 
- Programmer Notes
- </th>
+ <th width="60%" align="center">Chapter 15.  Programmer Notes </th>
<td width="20%" align="right"> <a accesskey="n" href="program_copy.html">Next</a></td>
</tr>
</table>
@@ -38,19 +36,25 @@
</div>
</div>
</div>
- <p>Many disk drives contain onboard caches. Some of these drives include
-battery-backup or other functionality that guarantees that all cached
-data will be completely written if the power fails. These drives can
-offer substantial performance improvements over drives without caching
-support. However, some caching drives rely on capacitors or other
-mechanisms that guarantee only that the write of the current sector
-will complete. These drives can endanger your database and potentially
-cause corruption of your data.</p>
- <p>To avoid losing your data, make sure the caching on your disk drives is
-properly configured so the drive will never report that data has been written
-unless the data is guaranteed to be written in the face of a power failure.
-Many times, this means that write-caching on the disk drive must
-be disabled.</p>
+ <p>
+ Many disk drives contain onboard caches. Some of these
+ drives include battery-backup or other functionality that
+ guarantees that all cached data will be completely written if
+ the power fails. These drives can offer substantial
+ performance improvements over drives without caching support.
+ However, some caching drives rely on capacitors or other
+ mechanisms that guarantee only that the write of the current
+ sector will complete. These drives can endanger your database
+ and potentially cause corruption of your data.
+ </p>
+ <p>
+ To avoid losing your data, make sure the caching on your
+ disk drives is properly configured so the drive will never
+ report that data has been written unless the data is
+ guaranteed to be written in the face of a power failure. Many
+ times, this means that write-caching on the disk drive must be
+ disabled.
+ </p>
</div>
<div class="navfooter">
<hr />
@@ -63,7 +67,8 @@ be disabled.</p>
<td width="40%" align="right"> <a accesskey="n" href="program_copy.html">Next</a></td>
</tr>
<tr>
- <td width="40%" align="left" valign="top">Memory-only or Flash configurations </td>
+ <td width="40%" align="left" valign="top">Memory-only or Flash
+ configurations </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>