diff options
| author | Lorry Tar Creator <lorry-tar-importer@baserock.org> | 2015-02-17 17:25:57 +0000 |
|---|---|---|
| committer | <> | 2015-03-17 16:26:24 +0000 |
| commit | 780b92ada9afcf1d58085a83a0b9e6bc982203d1 (patch) | |
| tree | 598f8b9fa431b228d29897e798de4ac0c1d3d970 /docs/programmer_reference/heap_conf.html | |
| parent | 7a2660ba9cc2dc03a69ddfcfd95369395cc87444 (diff) | |
| download | berkeleydb-master.tar.gz | |
Diffstat (limited to 'docs/programmer_reference/heap_conf.html')
| -rw-r--r-- | docs/programmer_reference/heap_conf.html | 60 |
1 files changed, 33 insertions, 27 deletions
diff --git a/docs/programmer_reference/heap_conf.html b/docs/programmer_reference/heap_conf.html index e22e5a00..aaca8090 100644 --- a/docs/programmer_reference/heap_conf.html +++ b/docs/programmer_reference/heap_conf.html @@ -14,17 +14,16 @@ <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> - <th colspan="3" align="center">Heap access method specific configuration</th> + <th colspan="3" align="center">Heap access method specific + configuration</th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="hash_conf.html">Prev</a> </td> - <th width="60%" align="center">Chapter 2. - Access Method Configuration - </th> + <th width="60%" align="center">Chapter 2. Access Method Configuration </th> <td width="20%" align="right"> <a accesskey="n" href="rq_conf.html">Next</a></td> </tr> </table> @@ -34,35 +33,41 @@ <div class="titlepage"> <div> <div> - <h2 class="title" style="clear: both"><a id="heap_conf"></a>Heap access method specific configuration</h2> + <h2 class="title" style="clear: both"><a id="heap_conf"></a>Heap access method specific + configuration</h2> </div> </div> </div> <p> - Configuring the Heap access method is fairly simple. Beyond the general - configuration required for any access method, you can configure how large - the database will become, as well as the amount by which the database grows. + Configuring the Heap access method is fairly simple. Beyond + the general configuration required for any access method, you + can configure how large the database will become, as well as + the amount by which the database grows. </p> <p> - If you provide no configuration relative to the heap size, then the - database will grow without bound. Whether this is desirable depends on - how much disk space is available to your application. + If you provide no configuration relative to the heap size, + then the database will grow without bound. Whether this is + desirable depends on how much disk space is available to your + application. </p> - <p> - You can limit the size of the on-disk database file by using the - <a href="../api_reference/C/dbset_heapsize.html" class="olink">DB->set_heapsize()</a> method. If the size specified on this method is - reached, then further attempts to insert/update records will fail - with a <code class="literal">DB_HEAP_FULL</code> error message. + <p> + You can limit the size of the on-disk database file by + using the <a href="../api_reference/C/dbset_heapsize.html" class="olink">DB->set_heapsize()</a> method. If the size specified on + this method is reached, then further attempts to insert/update + records will fail with a <code class="literal">DB_HEAP_FULL</code> error + message. </p> - <p> - Heap databases are organized into regions, and each region is a constant - size. The size of the region in a heap database is limited by the page - size, the first page of the region contains a bitmap describing the - available space on the remaining pages in the region. When the database - experiences write contention, a region is added to reduce contention. - This means heap databases can grow in size very quickly. In order to - control the amount by which the database increases, the size of the region - is configurable via <a href="../api_reference/C/dbset_heap_regionsize.html" class="olink">DB->set_heap_regionsize()</a>. + <p> + Heap databases are organized into regions, and each region + is a constant size. The size of the region in a heap database + is limited by the page size, the first page of the region + contains a bitmap describing the available space on the + remaining pages in the region. When the database experiences + write contention, a region is added to reduce contention. This + means heap databases can grow in size very quickly. In order + to control the amount by which the database increases, the + size of the region is configurable via + <a href="../api_reference/C/dbset_heap_regionsize.html" class="olink">DB->set_heap_regionsize()</a>. </p> </div> <div class="navfooter"> @@ -76,7 +81,8 @@ <td width="40%" align="right"> <a accesskey="n" href="rq_conf.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Hash access method specific configuration </td> + <td width="40%" align="left" valign="top">Hash access method specific + configuration </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> |