pgrust
Ranked 8 of 22 databases by recommenders
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.
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.
79 people gave an opinion
- recommend it
- 34
- criticize it
- 45
- approval share
- 43%
Recommended in 5 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 34 people recommend itNeeds 10 or more, met.
- 0.7 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Very fast analytics queries
“new query executor that's hundreds of times faster than Postgres for OLAP workloads”
Comment from 16 Oct 2026 in “Postgres 19 delayed after AI reviewers find more bugs than humans can fix” “it is interesting to see an open source system that beats ClickHouse on ClickBench”
Comment from 24 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “pgrust on a c6a.2xl is faster than ClickHouse running on a c6a.metal”
Comment from 25 Oct 2026 in “We should be more ambitious with the software we build” - Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
Modern Rust codebase, memory safety
“we can't afford to have our most utilized workloads running on a software written before most of us even existed”
Comment from 5 Jun 2026 in “pg_durable: Microsoft open sources in-database durable execution” “LLMs give us unlimited manpower, and the language give us constraints to make more modern and safer softwares.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “I've also seen the benefits of Rust for this too.”
Comment from 9 May 2026 in “Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc” Open-source version performs as fast
“if the now-released open source variant performs roughly the same, and has no weird behavior in it”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “The open-source version without the alleged cheating devices is as fast if not faster”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “its current source code as OSS which scores even better and fixes all the accusations”
Comment from 24 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” Runs in browser via WebAssembly
“We also support compiling to wasm so you can embed it in the browser too”
Comment from 7 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD” “The WebAssembly demo that runs in your browser is a really neat touch”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
What people warn about
Each mark is one comment
Accused of benchmark cheating
“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”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “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”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “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"”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” - Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)”
- Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)”
- Comment from 25 Oct 2026 in “We should be more ambitious with the software we build”
Not production-ready yet
“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.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “Passing every regression test is huge, but extension compatibility will probably be the real test for production adoption.”
Comment from 11 Jul 2026 in “pgrust passes 100% of the Postgres regression tests” “never going to be production ready, never trustworthy enough to be used by anything serious”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” AGPL license concerns
“it's kind of wrong to port in such a direct way and change the license”
Comment from 7 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD” “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.”
Comment from 7 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD” “This is almost certainly a derived work (and thus a fork, and should thus have the original license and copyright preserved).”
Comment from 7 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD” AI-written code hard to trust
“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”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “will Claude change this test as a workaround in a future commit, no one knows because no one is reading the project code”
Comment from 23 Oct 2026 in “Remove pgrust: the entry is cheating (per-query kernels and result caching)” “There is also zero evidence a human has reviewed a meaningful amount of the code generated for the port”
Comment from 8 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD” - Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
- Comment from 8 Aug 2026 in “Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD”
Other databases people recommend
The four most recommended other databases, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| PostgreSQL | 816 | 233 | 78% | 13 | 10 yrs42 owners | Approved |
| MySQL | 124 | 107 | 54% | 12 | — | — |
| Microsoft SQL Server | 73 | 59 | 55% | 12 | 20 yrs6 owners | — |
| Microsoft Access | 62 | 39 | 61% | 12 | — | — |
| pgrustThis page | 34 | 45 | 43% | 5 | — | — |
What people said
40 of the 121 comments that mention it, newest first. Each links to the original comment.
“pgrust on a c6a.2xl is faster than ClickHouse running on a c6a.metal”
“shall every developer build their postgres to prove they are good enough developers?”
“The engine supports a narrow subset of SQL: scans, group-bys, filters, and sorting.”
“Prompting Claude to remove the evidence of cheating and then publishing that doesn't undo the cheating.”
“it is interesting to see an open source system that beats ClickHouse on ClickBench”
“its current source code as OSS which scores even better and fixes all the accusations”
“The open-source version without the alleged cheating devices is as fast if not faster”
“if the now-released open source variant performs roughly the same, and has no weird behavior in it”
“You'll see the numbers match the ClickBench numbers and that those files are dead code during the benchmark”
“The preview results would have been more appropriate to announce on a social media platform than as a PR to the ClickBench repo.”
“This absolutely does not pass any smell test, by your own admission you included the test files "by accident"”
“The point was that -preview didn't have the issues described, except for limited SQL support.”
“The longer you take to release it (or choose not to release it at all) the more it'll look like a cover-up.”
“The new general version is actually faster than the version accused of cheating.”
“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"”
“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”
“will Claude change this test as a workaround in a future commit, no one knows because no one is reading the project code”
“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”
“new query executor that's hundreds of times faster than Postgres for OLAP workloads”
“The more tangible example for me around LLM enabling what's previously long if not impossible tasks”
“Its unlikely an AI written project is one which people will want to maintain even if it "works"”
“There is also zero evidence a human has reviewed a meaningful amount of the code generated for the port”
“We also support compiling to wasm so you can embed it in the browser too”
“This is almost certainly a derived work (and thus a fork, and should thus have the original license and copyright preserved).”
“This brings cloning a template db from 100ms down to <10ms making it much better for tests.”
“it's kind of wrong to port in such a direct way and change the license”
“It's one person cosplaying a serious engineering team doing a mountain of work.”
“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.”
“it clearly states the location of the rest of the commits, so I wouldn't be critical of main itself”
“Passing every regression test is huge, but extension compatibility will probably be the real test for production adoption.”
“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.”
“never going to be production ready, never trustworthy enough to be used by anything serious”
“The code is so weird, people will have a hard time reading it when they need to check for correctness.”
“The WebAssembly demo that runs in your browser is a really neat touch”
“LLMs give us unlimited manpower, and the language give us constraints to make more modern and safer softwares.”
“An unfortunate aspect is that the code has become a bit more bloated in some regards due to usage of Result”
“Is ~300x faster than Postgres on analytical workloads.”
“we can't afford to have our most utilized workloads running on a software written before most of us even existed”
“You'll see it's much more faithful to Postgres than a C compiler that doesn't handle type checks.”
“I've also seen the benefits of Rust for this too.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.