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

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


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


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 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 often the system flushes dirty buffers to disk and how often the log is checkpointed.

See Also