From 2477997658ddd1d10e95993d612263430599e4bd Mon Sep 17 00:00:00 2001 From: Hallvard Furuseth Date: Tue, 12 Jan 2016 23:18:06 +0100 Subject: [PATCH] mdbx: backport - lmdb.h Caveats: Reserved vs. actual mem/disk usage. Change-Id: Ia7c250e14bd5a59c8600f74c5843ad0bb37ebd33 --- lmdb.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lmdb.h b/lmdb.h index 81808981..4aa8de13 100644 --- a/lmdb.h +++ b/lmdb.h @@ -76,6 +76,11 @@ * access to locks and lock file. Exceptions: On read-only filesystems * or with the #MDB_NOLOCK flag described under #mdb_env_open(). * + * - An LMDB configuration will often reserve considerable \b unused + * memory address space and maybe file size for future growth. + * This does not use actual memory or disk space, but users may need + * to understand the difference so they won't be scared off. + * * - By default, in versions before 0.9.10, unused portions of the data * file might receive garbage data from memory freed by other code. * (This does not happen when using the #MDB_WRITEMAP flag.) As of