# pgrust 34 Hacker News commenters recommended pgrust and 45 criticized it, November 2025 to November 2026. It was recommended in 5 of 13 months. **Verdict:** Recommended as a Postgres-compatible database written in Rust, passing all Postgres regression tests and claiming fast analytics queries. Most common caveat: critics allege benchmark cheating and doubt production readiness. ## Why people recommend it - Very fast analytics queries (4 comments): "new query executor that's hundreds of times faster than Postgres for OLAP workloads" ([source](https://news.ycombinator.com/item?id=50123206)) "it is interesting to see an open source system that beats ClickHouse on ClickBench" ([source](https://news.ycombinator.com/item?id=50217542)) "pgrust on a c6a.2xl is faster than ClickHouse running on a c6a.metal" ([source](https://news.ycombinator.com/item?id=50233934)) - Modern Rust codebase, memory safety (3 comments): "we can't afford to have our most utilized workloads running on a software written before most of us even existed" ([source](https://news.ycombinator.com/item?id=48418221)) "LLMs give us unlimited manpower, and the language give us constraints to make more modern and safer softwares." ([source](https://news.ycombinator.com/item?id=48855001)) "I've also seen the benefits of Rust for this too." ([source](https://news.ycombinator.com/item?id=48078468)) - Open-source version performs as fast (3 comments): "if the now-released open source variant performs roughly the same, and has no weird behavior in it" ([source](https://news.ycombinator.com/item?id=50212402)) "The open-source version without the alleged cheating devices is as fast if not faster" ([source](https://news.ycombinator.com/item?id=50215992)) "its current source code as OSS which scores even better and fixes all the accusations" ([source](https://news.ycombinator.com/item?id=50217205)) - Runs in browser via WebAssembly (2 comments): "We also support compiling to wasm so you can embed it in the browser too" ([source](https://news.ycombinator.com/item?id=49217221)) "The WebAssembly demo that runs in your browser is a really neat touch" ([source](https://news.ycombinator.com/item?id=48855902)) ## What people warn about - Accused of benchmark cheating (6 comments): "if the database is not able to be run with a variety of queries other than the one used by ClickBench then don't submit it to the benchmark" ([source](https://news.ycombinator.com/item?id=50210337)) "If the Ai came back to me with a 1600x improvement (still in pgrust readme), I would be highly suspicious of the Ai and the code it wrote" ([source](https://news.ycombinator.com/item?id=50207262)) "You don't get to create a new submission that (allegedly) fixes all of the issues and then say that the previous accusations are "false"" ([source](https://news.ycombinator.com/item?id=50210597)) - Not production-ready yet (3 comments): "The maintainer here did nothing (just a little chat here and there), but is sure that only optimizations are missing for this to be production-ready." ([source](https://news.ycombinator.com/item?id=48858586)) "Passing every regression test is huge, but extension compatibility will probably be the real test for production adoption." ([source](https://news.ycombinator.com/item?id=48871688)) "never going to be production ready, never trustworthy enough to be used by anything serious" ([source](https://news.ycombinator.com/item?id=48858566)) - AGPL license concerns (3 comments): "it's kind of wrong to port in such a direct way and change the license" ([source](https://news.ycombinator.com/item?id=49214824)) "AGPL is a dealbreaker. Not for me personally, but it will never see wide adoption because it's a banned license in most corporate environments." ([source](https://news.ycombinator.com/item?id=49211258)) "This is almost certainly a derived work (and thus a fork, and should thus have the original license and copyright preserved)." ([source](https://news.ycombinator.com/item?id=49216477)) - AI-written code hard to trust (5 comments): "If the Ai came back to me with a 1600x improvement (still in pgrust readme), I would be highly suspicious of the Ai and the code it wrote" ([source](https://news.ycombinator.com/item?id=50207262)) "will Claude change this test as a workaround in a future commit, no one knows because no one is reading the project code" ([source](https://news.ycombinator.com/item?id=50208564)) "There is also zero evidence a human has reviewed a meaningful amount of the code generated for the port" ([source](https://news.ycombinator.com/item?id=49217976)) ## Alternatives hackers recommend - [PostgreSQL](https://hackerapproved.com/p/postgresql.md): 816 recommend - [MySQL](https://hackerapproved.com/p/mysql.md): 124 recommend - [Microsoft SQL Server](https://hackerapproved.com/p/microsoft-sql-server.md): 73 recommend - [Microsoft Access](https://hackerapproved.com/p/microsoft-access.md): 62 recommend - [Turso](https://hackerapproved.com/p/turso.md): 53 recommend ## Cite as Hacker Approved, "pgrust", https://hackerapproved.com/p/pgrust/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).