From: Howard Chu Date: Sat, 23 Jan 2016 16:51:42 +0000 (+0000) Subject: Update WRITEMAP doc X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=b5018e26bc155baea94a3552696ea9b8f0dc7046;p=openldap Update WRITEMAP doc --- diff --git a/libraries/liblmdb/lmdb.h b/libraries/liblmdb/lmdb.h index f684da7368..7bcdb9c704 100644 --- a/libraries/liblmdb/lmdb.h +++ b/libraries/liblmdb/lmdb.h @@ -545,9 +545,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).