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.53.26; 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.09; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.59; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.08.05; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.57; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DbEnv::set_lg_regionmax

DbEnv::set_lg_regionmax

 APIRef 

#include <db_cxx.h>


int
DbEnv::set_lg_regionmax(u_int32_t lg_regionmax);

Description

Set the size of the underlying logging subsystem region, in bytes. By default, or if the value is set to 0, the base region size is 60KB. The log region is used to store filenames, and so may need to be increased in size if a large number of files will be opened and registered with the specified Berkeley DB environment's log manager.

The DbEnv::set_lg_regionmax interface may be used only to configure Berkeley DB before the DbEnv::open interface is called.

The DbEnv::set_lg_regionmax method either returns a non-zero error value or throws an exception that encapsulates a non-zero error value on failure, and returns 0 on success.

The database environment's log region size 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_lg_regionmax", one or more whitespace characters, and the size in bytes. Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

Errors

The DbEnv::set_lg_regionmax method may fail and throw an exception or return a non-zero error for the following conditions:

EINVAL
An invalid flag value or parameter was specified.

Called after DbEnv::open was called.

The DbEnv::set_lg_regionmax method may fail and throw an exception or return a non-zero error for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the DbEnv::set_lg_regionmax method may fail and either return DB_RUNRECOVERY or throw an exception encapsulating DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DbEnv

See Also

DbEnv::set_lg_bsize, DbEnv::set_lg_dir, DbEnv::set_lg_max, DbEnv::set_lg_regionmax, DbEnv::log_archive, DbEnv::log_compare, DbEnv::log_file, DbEnv::log_flush, DbEnv::log_get, DbEnv::log_put, DbEnv::log_register, DbEnv::log_stat, and DbEnv::log_unregister.

APIRef

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 d17 1 a17 1 APIRef a62 1 DbEnv::log_cursor, d65 1 a68 2 DbEnv::log_unregister, DbLogc::logc_close d70 1 a70 1 DbLogc::logc_get. d73 1 a73 1 APIRef @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d33 2 a34 7

The DbEnv::set_lg_regionmax method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv::set_lg_regionmax interface may not be called after the DbEnv::open interface is called. If the database environment already exists when DbEnv::open is called, the information specified to DbEnv::set_lg_regionmax will be ignored. d50 4 a53 4 If a catastrophic error has occurred, the DbEnv::set_lg_regionmax method may fail and either return DB_RUNRECOVERY or throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d55 1 a55 1 DbEnv, DbLogc, DbLsn d57 16 a72 1 Logging Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d34 7 a40 2

The DbEnv::set_lg_regionmax interface may be used only to configure Berkeley DB before the DbEnv::open interface is called. d56 4 a59 4 If a catastrophic error has occurred, the DbEnv::set_lg_regionmax method may fail and either return DB_RUNRECOVERY or throw an exception encapsulating DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d61 1 a61 1 DbEnv d63 1 a63 16 DbEnv::set_lg_bsize, DbEnv::set_lg_dir, DbEnv::set_lg_max, DbEnv::set_lg_regionmax, DbEnv::log_archive, DbEnv::log_compare, DbEnv::log_cursor, DbEnv::log_file, DbEnv::log_flush, DbEnv::log_put, DbEnv::log_register, DbEnv::log_stat, DbEnv::log_unregister, DbLogc::logc_close and DbLogc::logc_get. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d33 2 a34 7

The DbEnv::set_lg_regionmax method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv::set_lg_regionmax interface may not be called after the DbEnv::open interface is called. If the database environment already exists when DbEnv::open is called, the information specified to DbEnv::set_lg_regionmax will be ignored. d50 4 a53 4 If a catastrophic error has occurred, the DbEnv::set_lg_regionmax method may fail and either return DB_RUNRECOVERY or throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d55 1 a55 1 DbEnv, DbLogc, DbLsn d57 16 a72 1 Logging Subsystem and Related Methods @