aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2024-12-30 15:39:09 -0300
committerEuAndreh <eu@euandre.org>2024-12-30 15:43:40 -0300
commit9dee89f4909ccf23cbcc11665364cd776625db03 (patch)
treea11194dcfb18582f90a2d5ffcba37428ca9cf173 /README.md
parenttests/dedo.go: Normalize tests (diff)
downloaddedo-9dee89f4909ccf23cbcc11665364cd776625db03.tar.gz
dedo-9dee89f4909ccf23cbcc11665364cd776625db03.tar.xz
src/dedo.go: Remove DB.NoSync option
Diffstat (limited to 'README.md')
-rw-r--r--README.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/README.md b/README.md
index fc2a1e0..b99baa1 100644
--- a/README.md
+++ b/README.md
@@ -758,8 +758,7 @@ lock-free MVCC using a single writer and multiple readers.
The two projects have somewhat diverged. LMDB heavily focuses on raw performance
while Bolt has focused on simplicity and ease of use. For example, LMDB allows
several unsafe actions such as direct writes for the sake of performance. Bolt
-opts to disallow actions which can leave the database in a corrupted state. The
-only exception to this in Bolt is `DB.NoSync`.
+opts to disallow actions which can leave the database in a corrupted state.
There are also a few differences in API. LMDB requires a maximum mmap size when
opening an `mdb_env` whereas Bolt will handle incremental mmap resizing