


software engineer @microsoft | Azure HorizonDB | whichdb.dev




my repo: github.com/JoeS51/rust-syste… and a good resource: postgresql.org/docs/current/…

Added fencing to my Postgres failover controller For this project, that just means running a docker command to stop the old primary container before promoting a replica
Built a tiny Postgres failover controller in Rust it monitors a primary and two replicas and promotes a replica whenever the primary goes down

Finally finished reading the Postgres 14 Internals book. Some general takeaways after reading this long, technical book: 1. Postgres is wonderful but not perfect. I started this book thinking that Postgres was the holy grail of databases (at least from everything I'd heard), but some of its architectural decisions probably wouldn't be made today if it were built from scratch. Things like transaction ID wraparound, its implementation of MVCC, and the process-per-connection model. The book specifically does a great job explaining how these things work and why they can be problematic. Understanding these limitations also gave me more appreciation for projects like OrioleDB and PgRust that are reimagining Postgres 2. Reading groups are very very helpful. I probably wouldn't have finished this book on my own. And even if I had, I don't think I would've learned nearly as much if I hadn't been able to talk about each chapter with other people 3. Everything I learned has been useful in some way. There were definitely moments when I wondered how much of what I was reading would actually be helpful, especially some of the implementation details. But I've already found myself connecting things I learned in this book to other papers I've read and conversations that I've had. That being said, there were some chapters that I found a little boring and could've skipped in hindsight In need of some book recs now!


I've been learning more about Postgres extensions for a new project at work and stumbled across this funny article



I've been tinkering with this for a little bit. Just a couple notes: - You might have seen this before! I posted it a couple months back but polished it up and finally got a domain - I could only afford the hand drawn logo - I haven't verified every detail about every database but I've gone through a lot of them. Let me know if you see any issues though! All feedback is welcome :)

Built a website that visualizes the relationships between different databases whichdb.dev



feels like necessary context:
I’m making a programming language called blood. Faster than rust, a powerful type system, all the power of effect systems, metaprogramming, zero-cost worktrees, semantic merging, sqlite-stored content-addressable code. Psychosis? Hopefully not. blood-lang.org

Happy to see Advent of Code is happening this year! Might have to do it in Blood (lang)