rpm/db/examples_c
jbj 2376437b8f Conflict resolved.
CVS patchset: 5722
CVS date: 2002/09/19 21:06:40
2002-09-19 21:06:40 +00:00
..
ex_apprec Initial revision 2002-08-14 16:31:49 +00:00
ex_repquote db-4.1.17 orphans. 2002-08-14 17:31:52 +00:00
README Initial revision 2001-03-21 18:33:35 +00:00
bench_001.c Conflict resolved. 2002-09-19 21:06:40 +00:00
ex_access.c Initial revision 2001-03-21 18:33:35 +00:00
ex_btrec.c Initial revision 2001-03-21 18:33:35 +00:00
ex_dbclient.c Initial revision 2001-03-21 18:33:35 +00:00
ex_env.c Initial revision 2001-03-21 18:33:35 +00:00
ex_lock.c Initial revision 2001-03-21 18:33:35 +00:00
ex_mpool.c Initial revision 2001-03-21 18:33:35 +00:00
ex_thread.c Initial revision 2001-03-21 18:33:35 +00:00
ex_tpcb.c Initial revision 2001-03-21 18:33:35 +00:00
ex_tpcb.h Initial revision 2001-03-21 18:33:35 +00:00

README

# $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.