← Back to branch summary

~ubuntu-branches/ubuntu/edgy/rpm/edgy

« back to all changes in this revision

Viewing changes to db/docs/ref/am/close.html

  • Committer: Bazaar Package Importer
  • Author(s): Joey Hess
  • Date: 2002-01-22 20:56:57 UTC
  • Revision ID: james.westby@ubuntu.com-20020122205657-l74j50mr9z8ofcl5
Tags: upstream-4.0.3
Import upstream version 4.0.3

Show diffs side-by-side

added added

removed removed

Lines of Context:
db/docs/ref/am/close.html
 
1
<!--$Id: close.so,v 10.17 2001/03/10 19:05:21 bostic Exp $-->
 
2
<!--Copyright 1997-2001 by Sleepycat Software, Inc.-->
 
3
<!--All rights reserved.-->
 
4
<html>
 
5
<head>
 
6
<title>Berkeley DB Reference Guide: Database close</title>
 
7
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
 
8
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
 
9
</head>
 
10
<body bgcolor=white>
 
11
<a name="2"><!--meow--></a>
 
12
<table width="100%"><tr valign=top>
 
13
<td><h3><dl><dt>Berkeley DB Reference Guide:<dd>Access Methods</dl></h3></td>
 
14
<td align=right><a href="../../ref/am/sync.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am/second.html"><img src="../../images/next.gif" alt="Next"></a>
 
15
</td></tr></table>
 
16
<p>
 
17
<h1 align=center>Database close</h1>
 
18
<p>The <a href="../../api_c/db_close.html">DB-&gt;close</a> function is the standard interface for closing the database.
 
19
By default, <a href="../../api_c/db_close.html">DB-&gt;close</a> also flushes all modified records from the
 
20
database cache to disk.
 
21
<p>There is one flag that you can set to customize <a href="../../api_c/db_close.html">DB-&gt;close</a>:
 
22
<p><dl compact>
 
23
<p><dt><a href="../../api_c/db_close.html#DB_NOSYNC">DB_NOSYNC</a><dd>Do not flush cached information to disk.
 
24
</dl>
 
25
<b>It is important to understand that flushing cached information
 
26
to disk only minimizes the window of opportunity for corrupted data, it
 
27
does not eliminate the possibility.</b>
 
28
<p>While unlikely, it is possible for database corruption to happen if a
 
29
system or application crash occurs while writing data to the database. To
 
30
ensure that database corruption never occurs, applications must either:
 
31
<p><ul type=disc>
 
32
<li>Use transactions and logging with automatic recovery.
 
33
<li>Use logging and application-specific recovery.
 
34
<li>Edit a copy of the database, and, once all applications
 
35
using the database have successfully called <a href="../../api_c/db_close.html">DB-&gt;close</a>, use
 
36
system operations (for example, the POSIX rename system call) to
 
37
atomically replace the original database with the updated copy.
 
38
</ul>
 
39
<table width="100%"><tr><td><br></td><td align=right><a href="../../ref/am/sync.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../../reftoc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../../ref/am/second.html"><img src="../../images/next.gif" alt="Next"></a>
 
40
</td></tr></table>
 
41
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>
 
42
</body>
 
43
</html>