If true, Berkeley DB will not write or synchronously flush the log on transaction commit.

Namespace:  BerkeleyDB
Assembly:  libdb_dotnet52 (in libdb_dotnet52.dll) Version: 5.2.28.0

Syntax

C#
public bool TxnNoSync { get; set; }
Visual Basic (Declaration)
Public Property TxnNoSync As Boolean
Visual C++
public:
property bool TxnNoSync {
	bool get ();
	void set (bool value);
}

Remarks

This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but if the application or system fails, it is possible some number of the most recently committed transactions may be undone during recovery. The number of transactions at risk is governed by how many log updates can fit into the log buffer, how often the operating system flushes dirty buffers to disk, and how often the log is checkpointed.

See Also