You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -329,6 +329,19 @@ possible LMDB error conditions:
329
329
*`MDB_KEYEXIST` and `MDB_NOTFOUND` are handled specially by some functions.
330
330
331
331
332
+
333
+
## OpenBSD
334
+
335
+
OpenBSD is only partially supported by LMDB. The issue is that OpenBSD does not have a unified buffer cache. This means that modifications made to a file through `write()` will not be visible to processes that have memory mapped the file. This is something that [may be fixed some day](http://openbsd-archive.7691.n7.nabble.com/Will-mmap-and-the-read-buffer-cache-be-unified-anyone-working-with-it-td271270.html).
336
+
337
+
In the mean-time, on OpenBSD you should always open environments with the `MDB_WRITEMAP` flag:
338
+
339
+
env.open("/path/to/db/", MDB_WRITEMAP);
340
+
341
+
Because nested transactions are incompatible with `MDB_WRITEMAP`, they cannot be used on OpenBSD. The test suite disables the nested transaction tests on OpenBSD.
342
+
343
+
344
+
332
345
## Support
333
346
334
347
To report a bug or submit a patch for lmdb++, please file an issue in the [issue tracker on GitHub](https://github.com/hoytech/lmdbxx/issues).
0 commit comments