> I assume you're thinking of using FoundationDB as a page store, much like
https://github.com/neondatabase/neon uses S3?
Actually not, I'm replacing Postres storage entirely down to the tuple level with FoundationDB instead. Neon is really cool but you would lose out on the greatest part of FDB, the transaction processing, if you were to simply use it as a page store (S3 and friends is probably a better fit for something like that).
> If not, and you're trying to go more directly for FDB-KV, I hope you're aware of https://www.voltactivedata.com/blog/2015/04/foundationdbs-le...
Hadn't seen that before, thanks for linking! Remains to be seen how well I can get this to work although one interesting thing to note is that CockroachDB (which would be the closest thing to what I'm building) is also built on top of a distributed KV store, although one built into Cockroach.
> I'm writing a Postgres-wire-protocol-compatible OLTP database in Rust, using RocksDB for storage as a starting point (MVCC for free!), worrying right now more about correctness and test coverage than performance. But I definitely feel their point of wanting more granular locking at some point.
Same at the moment in terms of what to focus on! What excites me the most about my project is the idea of making actual Postgres become seamlessly fully distributed, like Cockroach but not just Postgres-compatible.
Would love to hear more about your project, have you published anything on it?