Comment by avinassh
1 year ago
As of now it has a single writer, same like SQLite. But we plan to add MVCC with multiple writers in the future. Pekka has experimented with MVCC earlier: https://github.com/penberg/tihku
1 year ago
As of now it has a single writer, same like SQLite. But we plan to add MVCC with multiple writers in the future. Pekka has experimented with MVCC earlier: https://github.com/penberg/tihku
I assume this will need to change the shared memory header protocol so either SQLite comes along for the ride or this is an incompatible ABI?
So a hard fork?
What is meant by a 'hard fork'? Are there different kinds of forks?
To me, a "hard" fork is one where you plan not to maintain any compatibility with your upstream and not to share any future code in either way (neither from original to fork nor back). "Soft" forks often retain a degree of compatibility, and some future developments can be shared.
(In this case, since it's a rewrite in Rust, it's not actually a fork at all, I think)
1 reply →
The kinds that keep file format compatibility?
Or are they claiming they will support MVCC with full file format and interprocess synchronization compatibility.
1 reply →