#include <db.h>

DB_ENV->mutex_set_max(DB_ENV *dbenv, u_int32_t max);  

Configure the total number of mutexes to allocate. This method is deprecated. The maximum size of the mutex region is now inferred by the sizes of the other memory structures, and so this method is no longer needed. For example, the cache requires one mutex per page in the cache. When you specify the cache size, DB assumes a page size of 4K and allocates mutexes accordingly. If your page size is different than 4K, you indicate this using DB_ENV->set_mp_pagesize() . DB will then allocate the proper number of mutexes based on this new page size.

You can use this method to override DB's mutex calculation, but it is not recommended to do so.

Calling the DB_ENV->mutex_set_max() method discards any value previously set using the DB_ENV->mutex_set_increment() method.

The database environment's total number of mutexes may also be configured using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "mutex_set_max", one or more whitespace characters, and the total number of mutexes. Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

The DB_ENV->mutex_set_max() method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->mutex_set_max() method may not be called after the DB_ENV->open() method is called. If the database environment already exists when DB_ENV->open() is called, the information specified to DB_ENV->mutex_set_max() will be ignored.

The DB_ENV->mutex_set_max() method returns a non-zero error value on failure and 0 on success.



The max parameter is the absolute number of mutexes to allocate.


The DB_ENV->mutex_set_max() method may fail and return one of the following non-zero errors:


An invalid flag value or parameter was specified.



See Also

Mutex Methods