We're Building Postgres in Rust. Using the LLVM of Databases

ComputerGuru

Author also discussing it on their Twitter [0]. I’m reserving judgement for now, but this has lots of potential usecases even apart from replacing postgres. [0]: https://x.com/glcst/status/2077759127682486561?s=46

Omega359

The llvm of databases is not turso, it's datafusion.

polyrand

I'm already quite excited about Turso being SQLite-compatible, but adding many features on top. And when a feature is not directly compatible with SQLite (ie: you can't directly read the file with `sqlite3`, it's straightforward to convert). This is great because you know you'll always be able to continue working with that database. Even if Turso stopped working, it's still a valid SQLite database. A combination I would be excited about is: - Full support for Postgres protocol/wire format (ie: Postgres, but in-process, backed by a single file). - Optional: Client/server architecture for further scaling and remote management using existing Postgres tooling - All backed by a SQLite-compatible file They are already adding MVCC to SQLite anyway. So their effort seems doable, and I hope they succeed.

scotty79

Will it have fast COUNT-s?

hoppp

Sounds cool but also why? Is it so it's possible to have 1 database and then switch from sqlite to postgres without data migration?

khuey

As someone who doesn't follow databases that closely, how is this different from Amazon Aurora (other than being open source)?

mhh__

Would be interested in strategic value add versus cedardb (although cedar is closed source in a way that at the moment I think may kill it)