The library is fully thread-aware and supports concurrent read/write access from multiple processes and threads.
is a bit misleading because if #20 is no, concurrency is upheld in spirit, only for concurrent reads, but for concurrent writes, lmdb will serialise it. "supports" up there means you can hit us with concurrent write calls, but we will queue them up and run them one after the other. so essentially, there is no concurrency in spirit. concurrent calls are flattened into sequential calls.
is a bit misleading because if #20 is no, concurrency is upheld in spirit, only for concurrent reads, but for concurrent writes, lmdb will serialise it. "supports" up there means you can hit us with concurrent write calls, but we will queue them up and run them one after the other. so essentially, there is no concurrency in spirit. concurrent calls are flattened into sequential calls.