mariadb/bdb/examples_c
2001-03-04 19:42:05 -05:00
..
ex_access.c Import changeset 2001-03-04 19:42:05 -05:00
ex_btrec.c Import changeset 2001-03-04 19:42:05 -05:00
ex_dbclient.c Import changeset 2001-03-04 19:42:05 -05:00
ex_env.c Import changeset 2001-03-04 19:42:05 -05:00
ex_lock.c Import changeset 2001-03-04 19:42:05 -05:00
ex_mpool.c Import changeset 2001-03-04 19:42:05 -05:00
ex_thread.c Import changeset 2001-03-04 19:42:05 -05:00
ex_tpcb.c Import changeset 2001-03-04 19:42:05 -05:00
ex_tpcb.h Import changeset 2001-03-04 19:42:05 -05:00
README Import changeset 2001-03-04 19:42:05 -05:00

# $Id: README,v 11.3 2000/12/13 06:32:29 krinsky Exp $

ex_access.c	Using just the DB access methods.

ex_btrec.c	Using the BTREE access method with record numbers.

ex_env.c	Setting up the DB environment.

ex_lock.c	Locking.

ex_mpool.c	Shared memory buffer pools.

ex_tpcb.c	TPC/B.
		Ex_tpcb sets up a framework in which to run a TPC/B test.
		Database initialization (the -i flag) and running the
		benchmark (-n flag) must take place separately (i.e.,
		first create the database, then run 1 or more copies of
		the benchmark).  Furthermore, when running more than one
		TPCB process, it is necessary to run the deadlock detector
		(db_deadlock), since it is possible for concurrent tpcb
		processes to deadlock.  For performance measurement, it
		will also be beneficial to run the db_checkpoint process
		as well.