2
<!--Copyright 1997-2002 by Sleepycat Software, Inc.-->
3
<!--All rights reserved.-->
4
<!--See the file LICENSE for redistribution information.-->
7
<title>Berkeley DB: DB_ENV->log_put</title>
8
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
9
<meta name="keywords" content="embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++">
12
<a name="2"><!--meow--></a>
13
<table width="100%"><tr valign=top>
15
<h1>DB_ENV->log_put</h1>
18
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
26
DB_ENV->log_put(DB_ENV *env,
27
DB_LSN *lsn, const DBT *data, u_int32_t flags);
30
<p>The DB_ENV->log_put method appends records to the log. The <a href="../api_c/lsn_class.html">DB_LSN</a> of
31
the put record is returned in the <b>lsn</b> argument. The <b>flags</b>
32
argument may be set to one of the following values:
34
<p><dt><a name="DB_FLUSH">DB_FLUSH</a><dd>The log is forced to disk after this record is written, guaranteeing
35
that all records with <a href="../api_c/lsn_class.html">DB_LSN</a> values less than or equal to the
36
one being "put" are on disk before DB_ENV->log_put returns.
38
<p>The caller is responsible for providing any necessary structure to
39
<b>data</b>. (For example, in a write-ahead logging protocol, the
40
application must understand what part of <b>data</b> is an operation
41
code, what part is redo information, and what part is undo information.
42
In addition, most transaction managers will store in <b>data</b> the
43
<a href="../api_c/lsn_class.html">DB_LSN</a> of the previous log record for the same transaction, to
44
support chaining back through the transaction's log records during
46
<p>The DB_ENV->log_put method returns a non-zero error value on failure and 0 on success.
48
<p>The <a href="../api_c/log_flush.html">DB_ENV->log_flush</a> method may fail and return a non-zero error for the following conditions:
50
<p><dt>EINVAL<dd>An invalid flag value or parameter was specified.
51
<p>The record to be logged is larger than the maximum log record.
53
<p>The DB_ENV->log_put method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions.
54
If a catastrophic error has occurred, the DB_ENV->log_put method may fail and
55
return <a href="../ref/program/errorret.html#DB_RUNRECOVERY">DB_RUNRECOVERY</a>,
56
in which case all subsequent Berkeley DB calls will fail in the same way.
58
<a href="../api_c/env_class.html">DB_ENV</a>, <a href="../api_c/logc_class.html">DB_LOGC</a>, <a href="../api_c/lsn_class.html">DB_LSN</a>
60
<a href="../api_c/log_list.html">Logging Subsystem and Related Methods</a>
62
<table width="100%"><tr><td><br></td><td align=right>
63
<a href="../api_c/c_index.html"><img src="../images/api.gif" alt="API"></a><a href="../reftoc.html"><img src="../images/ref.gif" alt="Ref"></a>
65
<p><font size=1><a href="http://www.sleepycat.com">Copyright Sleepycat Software</a></font>