Trying to understand general goal/state/bugs of the project about rkv HOT 2 OPEN

Is this project a higher-level abstraction/ORM around lmdb-rs that aims to eventually support multiple DBs?

My intent in writing it was to provide a safe, typed abstraction that smoothed off many of the sharp edges of LMDB but preserved its performance.

I'm sure some of the goals have shifted over time (e.g., rkv now seems to support multiple backends!), but I believe those are still the core. @victorporof and @mykmelez can likely comment more.

Are the bugs corrupting the DB in this repo or in lmdb-rs (it's hard to tell since they're tracked in bugzilla rather than on github) or are these fundamental problems with LMDB itself?

They look like crashes in LMDB itself; I would be surprised if lmdb-rs would behave any differently if your own code called it instead of rkv, and in theory that is also true if you used mdb.c.

The two public-visible bugs map to these in LMDB:

https://www.openldap.org/lists/openldap-bugs/201410/msg00051.html
https://www.openldap.org/its/index.cgi/Incoming?id=9037;selectid=9037

How likely am I to get bitten by the crashes/bugs you mention in the use case I described?

I suspect that you will not; if you control your key length, filesystem, etc. then your system is a great deal more predictable than Firefox running on millions of end-user computers and operating systems and filesystems.

https://bugzilla.mozilla.org/show_bug.cgi?id=1596063 is tracking three crashes. One has occurred once, one is "low volume" but a startup crash, and one is non-public.

from rkv.

I don't have much to add beyond what @rnewman said. As he noted, the crashes in question look like crashes in LMDB, although I haven't been able to absolutely confirm that. Nevertheless, it's unlikely that you'll experience them, unless you happen to be distributing software to tens of millions of users running a variety of often-archaic versions of popular desktop operating systems.

As for the goals, as far as I know, they remain the same at a high level as @rnewman stated. However, I haven't been involved much since @victorporof took over primary responsibility for the project, so he's the authoritative source for info about its goals and direction.

from rkv.