From 3b7a958fcda37ab538bd382dc438df7fdd681a07 Mon Sep 17 00:00:00 2001 From: Howard Chu Date: Sat, 23 Jan 2016 16:51:42 +0000 Subject: [PATCH] mdbx: backport - Update WRITEMAP doc. Change-Id: I5c4b72e8c64dfe4ed04ca579f3545191165ef20a --- CHANGES | 1 + lmdb.h | 6 ++++-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/CHANGES b/CHANGES index d1ac8e15..3b819fa4 100644 --- a/CHANGES +++ b/CHANGES @@ -10,6 +10,7 @@ LMDB 0.9.18 Release Engineering already done for mdbx - Additional makefile var tweaks (ITS#8169) Documentation Add Getting Started page + Update WRITEMAP description LMDB 0.9.17 Release (2015/11/30) diff --git a/lmdb.h b/lmdb.h index 4aa8de13..4250795e 100644 --- a/lmdb.h +++ b/lmdb.h @@ -554,9 +554,11 @@ int mdb_env_create(MDB_env **env); * allowed. LMDB will still modify the lock file - except on read-only * filesystems, where LMDB does not use locks. *
  • #MDB_WRITEMAP - * Use a writeable memory map unless MDB_RDONLY is set. This is faster - * and uses fewer mallocs, but loses protection from application bugs + * Use a writeable memory map unless MDB_RDONLY is set. This uses + * fewer mallocs but loses protection from application bugs * like wild pointer writes and other bad updates into the database. + * This may be slightly faster for DBs that fit entirely in RAM, but + * is slower for DBs larger than RAM. * Incompatible with nested transactions. * Do not mix processes with and without MDB_WRITEMAP on the same * environment. This can defeat durability (#mdb_env_sync etc).