Postgres was rewritten in Rust… and somehow passed every test

What happens when PostgreSQL is rebuilt in Rust? In this video, we take a look at pgrust, an experimental Postgres rewrite that passes all 46,066 official PostgreSQL regression queries, works with a standard psql client, and can boot from an existing Postgres 18.3 data directory. How closely does it matches real Postgres behavior? We also look at the proposed thread-per-connection architecture, its potential advantages for concurrency, connection overhead, built-in pooling, analytical workloads, and future storage experiments. 🔗 Relevant Links pgrust repo - https://github.com/malisper/pgrust Test pgrust here - https://pgrust.com/ ❤️ More about us Radically better observability stack: https://betterstack.com/ Written tutorials: https://betterstack.com/community/ Example projects: https://github.com/BetterStackHQ 📱 Socials Twitter:   / betterstackhq   Instagram:   / betterstackhq   TikTok:   / betterstack   LinkedIn:   / betterstack   📌 Chapters: 0:00 PostgreSQL Was Rebuilt in Rust 0:32 Why Postgres Needs a Modern Rewrite 1:00 What Is pgrust and How Does It Work? 1:40 Testing pgrust With Docker and psql 1:55 Running Real SQL Queries and EXPLAIN 2:38 Postgres Process-per-Connection vs Rust Threads 3:10 Can pgrust Replace PostgreSQL Extensions? 4:23 Rust Thread per Connection 5:00 pgrust Performance Claims: 50% and 300x Faster 5:55 Developer Reactions, Risks and Skepticism 6:55 Production Readiness, AGPL and Compatibility 7:45 Should You Replace PostgreSQL With pgrust?