Introducing pgrust v0.3: the bug-smashing release. We evaluated pgrust v0.2 and v0.3 against the same held-out corpus: 164,000 test cases from 50 open-source projects. pgrust v0.2 diverged from Postgres on 1,454 cases. pgrust v0.3 diverged on 11. pgrust is 300x faster than Postgres for analytical workloads, and we're a drop-in replacement. Held-out corpus included: @djangoproject, SQLAlchemy, Hibernate, @rails, and more. @pgrustdb is now much more Postgres-compatible and reliable than before. @JasonSeibel and I don't recommend running pgrust in production (yet), but we are successfully running it ourselves internally. - @AntithesisHQ and @workersdotio for simulation testing - Detail.dev by @danlovesproofs for LLM-assisted code analysis - Multiple home-built differential fuzzers - Kani for formal verification Our goal is for pgrust to be truly 100% compatible with Postgres. There are still bugs. You should still run Postgres for any data you can't afford to lose. But we want people trying pgrust on real workloads in non-critical environments. If you need Clickhouse performance queries in Postgres, are frustrated by the many gotchas in Postgres, or just geek out about databases and Rust, feel free to send me a DM as we would love to chat.

I'll be giving a talk next week at the @PlanetScale SF Database Meetup about how we made @pgrustdb and how we made it 300x faster than Postgres for analytics