head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.54; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.08; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.56; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.07.58; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DB_ENV->set_lk_max_objects |
![]() ![]() |
#include <db.h>int DB_ENV->set_lk_max_objects(DB_ENV *dbenv, u_int32_t max);
Set the maximum number of simultaneously locked objects supported by the Berkeley DB lock subsystem. This value is used by DB_ENV->open to estimate how much space to allocate for various lock-table data structures. The default value is 1000 objects. For specific information on configuring the size of the lock subsystem, see Configuring locking: sizing the system.
The DB_ENV->set_lk_max_objects interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.
The DB_ENV->set_lk_max_objects function returns a non-zero error value on failure and 0 on success.
The database environment's maximum number of objects 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_objects", one or more whitespace characters, and the number of objects. 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->set_lk_max_objects function may fail and return a non-zero error for the following conditions:
Called after DB_ENV->open was called.
The DB_ENV->set_lk_max_objects 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_objects function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
![]() ![]() |
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d57 1 d61 5 a65 6 DB_ENV->lock_detect, DB_ENV->lock_get, DB_ENV->lock_id, DB_ENV->lock_id_free, DB_ENV->lock_put, DB_ENV->lock_stat, d67 1 a67 1 DB_ENV->lock_vec. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d35 3 a37 8
The DB_ENV->set_lk_max_objects method configures a database environment, not only operations performed using the specified DB_ENV handle.
The DB_ENV->set_lk_max_objects interface may not be called after the DB_ENV->open interface is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_lk_max_objects will be ignored.
The DB_ENV->set_lk_max_objects method returns a non-zero error value on failure and 0 on success. d45 1 a45 1
The DB_ENV->set_lk_max_objects method may fail and return a non-zero error for the following conditions: d50 4 a53 6
The DB_ENV->set_lk_max_objects method 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_objects method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB_ENV->set_lk_max_objects interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.
The DB_ENV->set_lk_max_objects function returns a non-zero error value on failure and 0 on success. d51 1 a51 1
The DB_ENV->set_lk_max_objects function may fail and return a non-zero error for the following conditions: d56 6 a61 4
The DB_ENV->set_lk_max_objects 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_objects function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d63 1 a63 13 DB_ENV->set_lk_conflicts, DB_ENV->set_lk_detect, DB_ENV->set_lk_max_lockers, DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_objects, DB_ENV->lock_detect, DB_ENV->lock_get, DB_ENV->lock_id, DB_ENV->lock_id_free, DB_ENV->lock_put, DB_ENV->lock_stat, and DB_ENV->lock_vec. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d35 3 a37 8
The DB_ENV->set_lk_max_objects method configures a database environment, not only operations performed using the specified DB_ENV handle.
The DB_ENV->set_lk_max_objects interface may not be called after the DB_ENV->open interface is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_lk_max_objects will be ignored.
The DB_ENV->set_lk_max_objects method returns a non-zero error value on failure and 0 on success. d45 1 a45 1
The DB_ENV->set_lk_max_objects method may fail and return a non-zero error for the following conditions: d50 4 a53 6
The DB_ENV->set_lk_max_objects method 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_objects method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.