
software engineer @microsoft | Azure HorizonDB | https://nitter.cf/t.co/2ZZmfMEDb1
Washington, USA
Joined October 2025
- Tweets758
- Following875
- Followers4.4K
- Likes2.4K
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!
Built a website that visualizes the relationships between different databases
whichdb.dev
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 :)
4
270
feels like necessary context:
nitter.cf/kitlangton/status/2119…
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
5
149
Joe Sluis retweeted
Why disaggregate @PostgreSQL storage? Some parts of PostgreSQL cannot scale horizontally, but others can. HorizonDB offloads suitable work to the scale-out layers, so the scale-up layer can handle more throughput. It's a Socrate-based @MSFTforPostgres (microsoft.com/en-us/research…)
Here's a helpful diagram of Postgres architecture that I encountered today
en.wikibooks.org/wiki/Postgr…
Built a tiny Postgres failover controller in Rust
it monitors a primary and two replicas and promotes a replica whenever the primary goes down
Joe Sluis retweeted
Hiring? In this AI economy? 😄
Turns out making things fast/secure matters$.
My team is hiring (Rust/C++ compiler). Share if you know anyone interested in compilers (backend).
apply.careers.microsoft.com/…
A B-tree index in Postgres doesn't really help when you're trying to find all the points within a certain area
One alternative is SP-GiST, an index type that supports data structures like quadtrees, which recursively divide space into quadrants and allow entire regions to be skipped during a search
potentially useful example:














