Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rocksdb version #1034

Open
yancyribbens opened this issue May 10, 2024 · 7 comments
Open

Rocksdb version #1034

yancyribbens opened this issue May 10, 2024 · 7 comments

Comments

@yancyribbens
Copy link

Just a question, but if I understand electrs will only work with an old version of rocksdb 7.8.3-2. I was thinking of trying out electrs on a different OS type then what the docs describe (debian or ubuntu). Building an older version of rocksdb shouldn't be too hard (fingers crossed) but just wondering the rational.

@yancyribbens
Copy link
Author

I guess this is only an issue with dynamic linking.

@yancyribbens
Copy link
Author

After a little more digging, I think the docs might be out of date. It seems that at least rocksdb 7.9.2 is supported romanz/rust-rocksdb@c1314a3

@romanz
Copy link
Owner

romanz commented May 24, 2024

In this project, we are using the same RocksDB version that is being used in the current Debian stable release, to allow dynamic linking:
https://packages.debian.org/bookworm/librocksdb-dev -> 7.8.3

@romanz
Copy link
Owner

romanz commented May 24, 2024

In theory, it's possible to update the RocksDB dependency and compile it from source - but currently RocksDB 7.8.3 is good enough for electrs.

@romanz
Copy link
Owner

romanz commented May 24, 2024

Actually, if there was a stable enough pure Rust key-value store, with performance characteristics similar to RocksDB, I would prefer switching to it -> #201

@yancyribbens
Copy link
Author

hmm yeah sled would be cool to try

@Kixunil
Copy link
Contributor

Kixunil commented Jun 17, 2024

If the Rust wrapper didn't break API we could've just used ranged versions and allow linking any version from a reasonable range. The users would just need to update Cargo.lock.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants