mirror of
https://github.com/isar/libmdbx.git
synced 2025-01-01 22:54:12 +08:00
mdbx: backport - Update WRITEMAP doc.
Change-Id: I5c4b72e8c64dfe4ed04ca579f3545191165ef20a
This commit is contained in:
parent
9d14f6a2ac
commit
3b7a958fcd
1
CHANGES
1
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)
|
||||
|
6
lmdb.h
6
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.
|
||||
* <li>#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).
|
||||
|
Loading…
x
Reference in New Issue
Block a user