Library Version 12.1.6.0

DB_ENV->set_tx_max()
Prev | Chapter 12. The DB_TXN Handle | Next

## DB_ENV->set_tx_max()

    #include <db.h>

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

Configure the Berkeley DB database environment to support at least max active transactions. This value bounds the size of the memory allocated for transactions. Child transactions are counted as active until they either commit or abort.

Transactions that update multiversion databases are not freed until the last page version that the transaction created is flushed from cache. This means that applications using multi-version concurrency control may need a transaction for each page in cache, in the extreme case.

When all of the memory available in the database environment for transactions is in use, calls to DB_ENV->txn_begin() will fail (until some active transactions complete). If `DB_ENV->set_tx_max()` is never called, the database environment is configured to support at least 100 active transactions.

The database environment's number of active transactions 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 "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.

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()` 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->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.

### Parameters

#### max

The max parameter configures the minimum number of simultaneously active transactions supported by Berkeley DB database environment.

### Errors

The `DB_ENV->set_tx_max()` method may fail and return one of the following non-zero errors:

#### EINVAL

If the method was called after DB_ENV->open() was called; or if an invalid flag value or parameter was specified.

### Class

DB_ENV, DB_TXN

### See Also

Transaction Subsystem and Related Methods

Prev | Up | Next
DB_ENV->get_tx_timestamp() | Home | DB_ENV->set_tx_timestamp()