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 @ Berkeley DB: DB_ENV->set_tx_max

DB_ENV->set_tx_max

 APIRef 

#include <db.h>


int
DB_ENV->set_tx_max(DB_ENV *dbenv, u_int32_t tx_max);

Description

Set the maximum number of active transactions that are supported by the environment. This value bounds the size of backing shared memory regions. Note that child transactions must be counted as active until their ultimate parent commits or aborts.

When there are more than the specified number of concurrent transactions, calls to txn_begin will fail (until some active transactions complete). If no value is specified, a default value of 20 is used.

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

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

The database environment's maximum number of active transactions 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_tx_max", one or more whitespace characters, and the number of transactions. 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_tx_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_tx_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_tx_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_tx_max, DB_ENV->set_tx_recover, DB_ENV->set_tx_timestamp, txn_abort, txn_begin, txn_checkpoint, txn_commit, txn_discard, txn_id, txn_prepare, txn_recover, and txn_stat.

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 d33 1 a33 1 calls to DB_ENV->txn_begin will fail (until some active transactions d58 8 a65 9 DB_TXN->abort, DB_ENV->txn_begin, DB_ENV->txn_checkpoint, DB_TXN->commit, DB_TXN->discard, DB_TXN->id, DB_TXN->prepare, DB_ENV->txn_recover, DB_TXN->set_timeout d67 1 a67 1 DB_ENV->txn_stat. @ 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_tx_max method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->set_tx_max 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_tx_max will be ignored.

The DB_ENV->set_tx_max method returns a non-zero error value on failure and 0 on success. d45 1 a45 1

The DB_ENV->set_tx_max method may fail and return a non-zero error for the following conditions: d50 4 a53 6

The DB_ENV->set_tx_max 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_tx_max method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_TXN d55 14 a68 1 Transaction Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d36 8 a43 3

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

The DB_ENV->set_tx_max function returns a non-zero error value on failure and 0 on success. d51 1 a51 1

The DB_ENV->set_tx_max function may fail and return a non-zero error for the following conditions: d56 6 a61 4

The DB_ENV->set_tx_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_tx_max function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d63 1 a63 14 DB_ENV->set_tx_max, DB_ENV->set_tx_recover, DB_ENV->set_tx_timestamp, DB_TXN->abort, DB_ENV->txn_begin, DB_ENV->txn_checkpoint, DB_TXN->commit, DB_TXN->discard, DB_TXN->id, DB_TXN->prepare, DB_ENV->txn_recover, DB_TXN->set_timeout and DB_ENV->txn_stat. @ 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_tx_max method configures a database environment, not only operations performed using the specified DB_ENV handle.

The DB_ENV->set_tx_max 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_tx_max will be ignored.

The DB_ENV->set_tx_max method returns a non-zero error value on failure and 0 on success. d45 1 a45 1

The DB_ENV->set_tx_max method may fail and return a non-zero error for the following conditions: d50 4 a53 6

The DB_ENV->set_tx_max 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_tx_max method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DB_ENV, DB_TXN d55 14 a68 1 Transaction Subsystem and Related Methods @