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

# DB_ENV->set_lk_max |

`

###

    #include <db.h>

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

# Description

The DB_ENV->set_lk_max function interface has been deprecated in favor of the DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_lockers, and DB_ENV->set_lk_max_objects functions. Please update your applications.

Set each of the maximum number of locks, lockers, and lock objects supported by the Berkeley DB lock subsystem to max. This value is used by DB_ENV->open to estimate how much space to allocate for various lock-table data structures. For specific information on configuring the size of the lock subsystem, see Configuring locking: sizing the system.

The DB_ENV->set_lk_max interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.

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

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

# Errors

The DB_ENV->set_lk_max function may fail and return a non-zero error for the following conditions:

EINVAL
  An invalid flag value or parameter was specified.

  Called after DB_ENV->open was called.

The DB_ENV->set_lk_max function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_lk_max function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

# See Also

DB_ENV->set_lk_conflicts, DB_ENV->set_lk_detect, DB_ENV->set_lk_max, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, lock_detect, lock_get, lock_id, lock_put, lock_stat, and lock_vec.`

Copyright Sleepycat Software