<xml></xml>

Collapse All Expand All Code: All Code: Multiple Code: C# Code: Visual Basic Code: Visual C++

Berkeley DB .NET API Documentation
LogConfig..::.MaxFileSize Property
LogConfig Class See Also Send Feedback

The maximum size of a single file in the log, in bytes. Because Offset is an unsigned four-byte value, MaxFileSize may not be larger than the maximum unsigned four-byte value.

Namespace: BerkeleyDB
Assembly: libdb_dotnet53 (in libdb_dotnet53.dll) Version: 5.3.28.0

# Syntax

C#

    public uint MaxFileSize { get; set; }

Visual Basic (Declaration)

    Public Property MaxFileSize As UInteger

Visual C++

    public:
    property unsigned int MaxFileSize {
    	unsigned int get ();
    	void set (unsigned int value);
    }

# Remarks

When the logging subsystem is configured for on-disk logging, the default size of a log file is 10MB.

When the logging subsystem is configured for in-memory logging, the default size of a log file is 256KB. In addition, the configured log buffer size must be larger than the log file size. (The logging subsystem divides memory configured for in-memory log records into "files", as database environments configured for in-memory log records may exchange log records with other members of a replication group, and those members may be configured to store log records on-disk.) When choosing log buffer and file sizes for in-memory logs, applications should ensure the in-memory log buffer size is large enough that no transaction will ever span the entire buffer, and avoid a state where the in-memory buffer is full and no space can be freed because a transaction that started in the first log "file" is still active.

See Log File Limits in the Programmer's Reference Guide for more information.

If no size is specified by the application, the size last specified for the database region will be used, or if no database region previously existed, the default will be used.

# See Also

LogConfig Class
BerkeleyDB Namespace