https://bugs.kde.org/show_bug.cgi?id=356357
--- Comment #7 from k...@web.de --- > I think it would better to work on detecting and recovering corruption. > MDB_NOSYNC Don't flush system buffers to disk > when committing a transaction. This optimization > means a system crash can corrupt the database or > lose the last transactions if buffers are not yet > flushed to disk. Are there any experiences whith using LMDB and NOSYNC? Are there tools/ways to recover a corrupted database or lost transactions with LMDB? They might not even exist yet, if people don't use NOSYNC. I think that developing such a tool is out of the scope of this project. It seems that LMDB was built around the idea of not needing recovery. > How safe is your DB? LMDB is crash-proof on all current filesystem designs. -- You are receiving this mail because: You are watching all bug changes.
