File: README

package info (click to toggle)
db5.3 5.3.28%2Bdfsg2-11
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 158,620 kB
  • sloc: ansic: 448,573; java: 111,824; tcl: 80,544; sh: 44,264; cs: 33,697; cpp: 21,600; perl: 14,557; xml: 10,799; makefile: 4,030; javascript: 1,998; yacc: 1,003; awk: 965; sql: 801; erlang: 342; python: 216; php: 24; asm: 14
file content (40 lines) | stat: -rw-r--r-- 1,211 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# $Id$

getting_started/
		Examples from the Getting Started Guide

ex_access.c	Using just the DB access methods.

ex_apprec/	Application-specific recovery.

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

ex_bulk.c	Bulk interfaces.

ex_dbclient.c	Using DB from an RPC client.

ex_env.c	Setting up the DB environment.

ex_lock.c	Locking.

ex_mpool.c	Shared memory buffer pools.

ex_rep/		Replication.  This creates a toy stock quote server
		with DB's single-master, multiple-client replication,
		with communication over TCP.  See ex_rep/README.

ex_sequence.c	Sequences.

ex_thread.c	Threaded application with multiple readers and writers.

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.