<li>The db_env_set_pageyield interface has been replaced by a new flag (DB_YIELDCPU) for the DB_ENV->set_flags interface.</li>
<li>The db_env_set_panicstate interface has been replaced by a new flag (DB_PANIC_STATE) for the DB_ENV->set_flags interface.</li>
<li>The db_env_set_region_init interface has been replaced by a new flag (DB_REGION_INIT) for the DB_ENV->set_flags interface.</li>
<li>The db_env_set_tas_spins interface has been replaced by the DB_ENV->set_tas_spins method.</li>
<li>The DB_ENV->set_mutexlocks interface has been replaced by a new flag (DB_NOLOCKING) for the DB_ENV->set_flags interface.</li>
<li>Fix a bug where input values from the DB_CONFIG file could overflow.</li>
<li>The C API lock, log, memory pool and transaction interfaces have been converted to method based interfaces; see the Upgrade documentation for specific details. [#920]</li>
<li>Fix a bug in which some DB_ENV configuration information could be lost by a failed DB_ENV->open command. [#4608]</li>
<li>Fix a bug where Berkeley DB could fail if the application attempted to allocate new database pages while the system was unable to write new log file buffers. [#4928]</li>
<li>Add a new flag (DB_GET_BOTH_RANGE) that adds support for range searches within sorted duplicate data sets. [#3378]</li>
<li>Fix a bug in which the DB->get or DB->pget methods, when used with secondary indices, could incorrectly leave an internally-created database cursor open. [#4465]</li>
<li>The DB->set_alloc method can no longer be called when the database is part of a database environment. [#4599]</li>
<li>Added implementation of DbEnv.lock_vec for Java. [#4094] Added some minimal protection so that the same Java Dbt cannot be used twice in the same API call, this will often catch multithreading programming errors with Dbts. [#4094]</li>
<li>Fix a bug in which a Db.put call with the Db.DB_APPEND would fail to correctly return the newly put record's record number. [#4527]</li>
<li>Fixed problems occurring in multithreaded java apps that use callbacks. [#4467]</li>
<li>Fix a bug where the size of a log file could not be set to the default value. [#4567]</li>
<li>Fix a bug where specifying a non-default log file size could cause other processes to be unable to join the environment and read its log files. [#4567]</li>
<li>Fix a bug where Berkeley DB could keep open file descriptors to log files returned by the DB_ENV->log_archive method (or the db_archive utility), making it impossible to move or remove them on Windows systems. [#3969]</li>
<li>Replace the log_get interface with a cursor into the log file. [#0043]</li>
<li>Add the DB_ODDFILESIZE flag to the DB_MPOOLFILE->open method supporting files not a multiple of the underlying page size in length.</li>
<li>Convert memp_XXX functional interfaces to a set of methods, either base methods off the DB_ENV handle or methods off of a DB_MPOOLFILE handle. [#920]</li>
<li>Add the DB_ODDFILESIZE flag to the DB_MPOOLFILE->open method supporting files not a multiple of the underlying page size in length.</li>
<li>Fix a bug where threads of control could deadlock opening a database environment with multiple memory pool caches. [#4696]</li>
<li>Fix a bug where the space needed for per-file memory pool statistics was incorrectly calculated. [#4772]</li>
<li>Fix a bug in which the db_dump utility would incorrectly attach to transaction, locking, or logging regions when salvaging, and thus could not be used to salvage databases in environments where these regions were present. [#4305]</li>
<li>Fix a bug in which the DB salvager could produce incorrectly formatted output for certain classes of corrupt database. [#4305]</li>
<li>Fix a bug in which the DB salvager could incorrectly salvage files containing multiple databases. [#4305]</li>
<li>Fix a bug where unprintable characters in subdatabase names could cause a dump of a database that could not then be loaded. [#4688]</li>
<li>Increase the size of the cache created by the db_stat and db_verify utilities to avoid failure on large databases. [#4688] [#4787]</li>
<li>Fix a bug in which a database verification performed with the DB_ORDERCHKONLY flag could fail incorrectly. [#4757]</li>
<li>Fix a bug which caused db_stat to display incorrect information about GB size caches. [#4812]</li>
<li>Fix a bug where Win9X systems region names could collide.</li>
<li>Fix a bug where configuring Berkeley DB to build the C++ API without also configuring for a shared library build would fail to build the C++ library. [#4343]</li>
<li>Change Berkeley DB installation to not strip binaries if --enable-debug was specified as a configuration option. [#4318]</li>
<li>Add the -pthread flag to AIX, FreeBSD and OSF/1 library loads. [#4350]</li>
<li>Fix a bug where the Berkeley DB 1.85 compatibility API failed to load in the 3.3.11 release. [#4368]</li>
<li>Port the Berkeley DB utility programs to the VxWorks environment. [#4378]</li>
<li>Made change to configuration so that dynamic libraries link correctly when C++ is used on AIX. [#4381]</li>
<li> Fix a variety of problems that prevented the Berkeley DB source tree from building on systems without ANSI C compiler support (for example, SunOS 4.X). [#4398]</li>
<li>Added missing DbMultiple*Iterator Java files to Makefile.in. [#4404]</li>
<li>Fix a bug that could prevent the db_dump185 utility from dumping Berkeley DB version 1.86 hash databases. [#4418]</li>
<li>Reduce the number of calls setting the errno value, to improve performance on Windows/NT in MT environments. [#4432]</li>
<li>Fix for Darwin (and probably some other) OS's that were getting 'yes' or other garbage in generated makefiles in place of a shared library name. [#4453]</li>
<li>C++: Remove inlining for constructor of tmpString internal class. This fixes warnings on Solaris profiling builds. [#4473]</li>
<li>DB now restarts system calls that are interrupted by signals. [#4480]</li>
<li>Fixed warnings for compiling Java native code on Solaris and OSF/1. [#4571]</li>
<li>Added better configuration for Java on Tru64 (OSF/1), Solaris,</li>
<li> Java files are now built as jar files. Berkeley DB classes are put into db.jar (which is an installed file on UNIX) and examples are put into dbexamples.jar. The classes directory is now a subdirectory of the build directory, rather than in java/classes. [#4575]</li>
