Berkeley DB: DB_ENV->mutex_set_max
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++

### DB_ENV->mutex_set_max |

`

###

    #include <db.h>

    int
    DB_ENV->mutex_set_increment(DB_ENV *dbenv, u_int32_t increment);

    int
    DB_ENV->mutex_get_increment(DB_ENV *dbenv, u_int32_t *incrementp);

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

    int
    DB_ENV->mutex_get_max(DB_ENV *dbenv, u_int32_t *maxp);

### Description: DB_ENV->mutex_set_max

Configure the total number of mutexes to allocate.

Berkeley DB allocates a default number of mutexes based on the initial configuration of the database environment. That default calculation may be too small if the application has an unusual need for mutexes (for example, if the application opens an unexpectedly large number of databases) or too large (if the application is trying to minimize its memory footprint). The DB_ENV->mutex_set_max method is used to specify an absolute number of mutexes to allocate.

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.

### Parameters

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

### Errors

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

EINVAL
  An invalid flag value or parameter was specified.

### Description: DB_ENV->mutex_get_max

The DB_ENV->mutex_get_max method returns the total number of mutexes allocated.

The DB_ENV->mutex_get_max method may be called at any time during the life of the application.

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

### Parameters

maxp
  The DB_ENV->mutex_get_max method returns the total number of mutexes allocated in maxp.

### Description: DB_ENV->mutex_set_increment

Configure the number of additional mutexes to allocate.

Additionally, an application may want to allocate mutexes for its own use. The DB_ENV->mutex_set_increment method is used to add a number of mutexes to the default allocation.

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

The database environment's number of additional 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_increment", one or more whitespace characters, and the number of additional 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_increment method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->mutex_set_increment 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_increment will be ignored.

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

### Parameters

increment
  The increment parameter is the number of additional mutexes to allocate.

### Errors

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

EINVAL
  An invalid flag value or parameter was specified.

### Description: DB_ENV->mutex_get_increment

The DB_ENV->mutex_get_increment method returns the number of additional mutexes to allocate.

The DB_ENV->mutex_get_increment method may be called at any time during the life of the application.

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

### Parameters

incrementp
  The DB_ENV->mutex_get_increment method returns the number of additional mutexes to allocate in incrementp.

### Class

DB_ENV

### See Also

Database Environments and Related Methods`

Copyright (c) 1996-2006 Oracle Corporation - All rights reserved.