1<!--$Id: rtc.so,v 1.4 2008/01/17 03:26:51 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB Reference Guide: Release 4.7: Run-time configuration</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td> 13<td align=right><a href="../upgrade.4.7/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.7/repapi.html"><img src="../../images/next.gif" alt="Next"></a> 14</td></tr></table> 15<p align=center><b>Release 4.7: Run-time configuration</b></p> 16<p>In historic Berkeley DB releases, there were separate sleep and yield 17functions to be configured at run-time using the db_env_set_func_sleep 18and <a href="../../api_c/set_func_yield.html">db_env_set_func_yield</a> functions. These functions have been 19merged in the Berkeley DB 4.7 release. The replacement function should always 20yield the processor, and optionally wait for some period of time before 21allowing the thread to run again.</p> 22<p>Applications using the Berkeley DB run-time configuration interfaces should 23merge the functionality of their sleep and yield functions into a single 24configuration function.</p> 25<p>In the 4.7 Berkeley DB release, the db_env_set_func_map and 26db_env_set_func_unmap functions have been replaced. This change fixes 27problems where applications using the Berkeley DB run-time configuration 28interfaces could not open multiple <a href="../../api_c/env_class.html">DB_ENV</a> handles for the same 29database environment in a single application or join existing database 30environments from within multiple processes.</p> 31<p>Applications wanting to replace the Berkeley DB region creation functionality 32should replace their db_env_set_func_map and db_env_set_func_unmap calls 33with a call to the <a href="../../api_c/set_func_region_map.html">db_env_set_func_region_map</a> function. 34Applications wanting to replace the Berkeley DB region file mapping functionality 35should replace their db_env_set_func_map and db_env_set_func_unmap calls 36with a call to the <a href="../../api_c/set_func_file_map.html">db_env_set_func_file_map</a> function.</p> 37<table width="100%"><tr><td><br></td><td align=right><a href="../upgrade.4.7/intro.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../upgrade.4.7/repapi.html"><img src="../../images/next.gif" alt="Next"></a> 38</td></tr></table> 39<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 40</body> 41</html> 42
