diff options
Diffstat (limited to 'docs/programmer_reference/env.html')
| -rw-r--r-- | docs/programmer_reference/env.html | 105 |
1 files changed, 62 insertions, 43 deletions
diff --git a/docs/programmer_reference/env.html b/docs/programmer_reference/env.html index a1b62389..92b20e6c 100644 --- a/docs/programmer_reference/env.html +++ b/docs/programmer_reference/env.html @@ -14,13 +14,11 @@ <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">Chapter 9. - The Berkeley DB Environment - </th> + <th colspan="3" align="center">Chapter 9. The Berkeley DB Environment </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="arch_utilities.html">Prev</a> </td> @@ -34,9 +32,7 @@ <div class="titlepage"> <div> <div> - <h2 class="title"><a id="env"></a>Chapter 9. - The Berkeley DB Environment - </h2> + <h2 class="title"><a id="env"></a>Chapter 9. The Berkeley DB Environment </h2> </div> </div> </div> @@ -52,7 +48,8 @@ </dt> <dt> <span class="sect1"> - <a href="env_create.html">Creating a database environment</a> + <a href="env_create.html">Creating a database + environment</a> </span> </dt> <dt> @@ -62,7 +59,8 @@ </dt> <dt> <span class="sect1"> - <a href="env_open.html">Opening databases within the environment</a> + <a href="env_open.html">Opening databases within the + environment</a> </span> </dt> <dt> @@ -72,7 +70,8 @@ </dt> <dt> <span class="sect1"> - <a href="env_db_config.html">DB_CONFIG configuration file</a> + <a href="env_db_config.html">DB_CONFIG configuration + file</a> </span> </dt> <dt> @@ -84,17 +83,17 @@ <dl> <dt> <span class="sect2"> - <a href="env_naming.html#idp1570112">Specifying file naming to Berkeley DB</a> + <a href="env_naming.html#idp1149160">Specifying file naming to Berkeley DB</a> </span> </dt> <dt> <span class="sect2"> - <a href="env_naming.html#idp1584200">Filename resolution in Berkeley DB</a> + <a href="env_naming.html#idp1160456">Filename resolution in Berkeley DB</a> </span> </dt> <dt> <span class="sect2"> - <a href="env_naming.html#idp1605872">Examples</a> + <a href="env_naming.html#idp1182752">Examples</a> </span> </dt> </dl> @@ -134,35 +133,54 @@ </div> </div> </div> - <p>A Berkeley DB environment is an encapsulation of one or more databases, log -files and region files. Region files are the shared memory areas that -contain information about the database environment such as memory pool -cache pages. Only databases are byte-order independent and only -database files can be moved between machines of different byte orders. -Log files can be moved between machines of the same byte order. Region -files are usually unique to a specific machine and potentially to a -specific operating system release.</p> - <p>The simplest way to administer a Berkeley DB application environment is to -create a single <span class="bold"><strong>home</strong></span> directory that stores the files for the -applications that will share the environment. The environment home -directory must be created before any Berkeley DB applications are run. Berkeley DB -itself never creates the environment home directory. The environment can -then be identified by the name of that directory.</p> - <p>An environment may be shared by any number of processes, as well as by -any number of threads within those processes. It is possible for an -environment to include resources from other directories on the system, -and applications often choose to distribute resources to other -directories or disks for performance or other reasons. However, by -default, the databases, shared regions (the locking, logging, memory -pool, and transaction shared memory areas) and log files will be stored -in a single directory hierarchy.</p> - <p>It is important to realize that all applications sharing a database -environment implicitly trust each other. They have access to each -other's data as it resides in the shared regions, and they will share -resources such as buffer space and locks. At the same time, any -applications using the same databases <span class="bold"><strong>must</strong></span> share an environment -if consistency is to be maintained between them.</p> - <p>For more information on the operations supported by the database environment handle, see the <a href="../api_reference/C/env.html#envlist" class="olink">Database Environments and Related Methods</a> section in the <em class="citetitle">Berkeley DB C API Reference Guide.</em> </p> + <p> + A Berkeley DB environment is an encapsulation of one or more + databases, log files and region files. Region files are the + shared memory areas that contain information about the + database environment such as memory pool cache pages. Only + databases are byte-order independent and only database files + can be moved between machines of different byte orders. Log + files can be moved between machines of the same byte order. + Region files are usually unique to a specific machine and + potentially to a specific operating system release. + </p> + <p> + The simplest way to administer a Berkeley DB application + environment is to create a single <span class="bold"><strong>home</strong></span> + directory that stores the files for the + applications that will share the environment. The environment + home directory must be created before any Berkeley DB + applications are run. Berkeley DB itself never creates the + environment home directory. The environment can then be + identified by the name of that directory. + </p> + <p> + An environment may be shared by any number of processes, as + well as by any number of threads within those processes. It is + possible for an environment to include resources from other + directories on the system, and applications often choose to + distribute resources to other directories or disks for + performance or other reasons. However, by default, the + databases, shared regions (the locking, logging, memory pool, + and transaction shared memory areas) and log files will be + stored in a single directory hierarchy. + </p> + <p> + It is important to realize that all applications sharing a + database environment implicitly trust each other. They have + access to each other's data as it resides in the shared + regions, and they will share resources such as buffer space + and locks. At the same time, any applications using the same + databases <span class="bold"><strong>must</strong></span> share an + environment if consistency is to be maintained between + them. + </p> + <p> + For more information on the operations supported by the + database environment handle, see the <a href="../api_reference/C/env.html#envlist" class="olink">Database Environments and Related + Methods</a> section in the + <em class="citetitle">Berkeley DB C API Reference Guide.</em> + </p> </div> </div> <div class="navfooter"> @@ -178,7 +196,8 @@ if consistency is to be maintained between them.</p> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> - <td width="40%" align="right" valign="top"> Creating a database environment</td> + <td width="40%" align="right" valign="top"> Creating a database + environment</td> </tr> </table> </div> |