Postgres rewritten in Rust
Ranked 11 of 22 databases by recommenders
People recommend it as a readable, free Rust codebase for learning and experiments, with clear performance and correctness measurements. Critics say it is immature and unsuitable for production use.
People recommend it as a readable, free Rust codebase for learning and experiments, with clear performance and correctness measurements. Critics say it is immature and unsuitable for production use.
55 people gave an opinion
- recommend it
- 23
- criticize it
- 32
- approval share
- 42%
Recommended in 1 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: not recommended
- June 2026: not recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 23 people recommend itNeeds 10 or more, met.
- 0.7 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not 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
Readable codebase for learning
“You gain access to a codebase that does it which you can learn a lot from too.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “Students could use it as an example of porting code.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” Unsafe code isolated and marked
“the unsafe footprint seems reasonable — the bulk of it in FFI wrappers”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “all of the unsafe code has been neatly isolated and clearly marked”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” Safer Rust design benefits security
“it's a good thing for security reasons if you're running a database server somewhere that attackers could get at it”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “doing it in safer, less error prone technology would be way better”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” Threaded design built on Rust safety
“there's some great stuff in here, particularly the direct-to-binary codegen, threads instead of processes and sync batching”
Comment from 30 Jul 2026 in “Postgres rewritten in Rust v0.2, now faster than Postgres and ClickHouse” “In this case it's justified because Rust allows safe implementation of threaded code.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
What people warn about
Each mark is one comment
LLM-generated code copied, not improved
“I'm sorry, but what is this need to just vibe code a port of an existing technology to a different language/framework/etc.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “Except you didn't improve the architecture, did you? You just asked an LLM to copy what was already there.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “"I took a static snapshot of code and converted it to another static snapshot of code" is meaningless.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” - Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
- Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
- Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
Immature, unsafe for production use
“very risky to use so probably only used for niche use cases at first”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “I would absolutely never trust an LLM Postgres rewrite (in any language) in production based on "only" Postgres's test suite passing.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “This stuff is all pretty immature though and I wouldn't actually build on it outside of some very narrow, well-understood workloads.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” - Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
Tests miss threading and ACID guarantees
“I would absolutely never trust an LLM Postgres rewrite (in any language) in production based on "only" Postgres's test suite passing.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “The only way they got that increase was by breaking the synchronization mechanisms that provide ACID guarantees in Postgres”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “the 100% Postgres regression tests do not test the threaded aspect of this project”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” Maintainer unknown; likely to die
“given the author/maintainer is essentially unknown, I highly doubt this will reach it's target audience”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “The project will die in a couple of days or weeks. You're making a mistake if you're seriously consider using this in any capacity.”
Comment from 9 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests” “Unless the Postgres team takes this and "owns" it accountability-wise, it's dead.”
Comment from 10 Jul 2026 in “Postgres rewritten in Rust, now passing 100% of the Postgres regression tests”
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 | — | — |
| Postgres rewritten in RustThis page | 23 | 32 | 42% | 1 | — | — |
What people said
40 of the 64 comments that mention it, newest first. Each links to the original comment.
“there's some great stuff in here, particularly the direct-to-binary codegen, threads instead of processes and sync batching”
“It's a product done by someone while claiming some level of compatibility with whatever they want to claim compatibility with.”
“this sounds really exciting”
“having AI rewrite it to the architecture I would want it to be and then changing things for fun is a better tutor”
“I'm a fan of how the quality is verified using clearly defined quantitative measurements for performance and correctness”
“The only way they got that increase was by breaking the synchronization mechanisms that provide ACID guarantees in Postgres”
“This stuff is all pretty immature though and I wouldn't actually build on it outside of some very narrow, well-understood workloads.”
“given the author/maintainer is essentially unknown, I highly doubt this will reach it's target audience”
“doing it in safer, less error prone technology would be way better”
“There's value in actually putting in the work.”
“Students could use it as an example of porting code.”
“Unless the Postgres team takes this and "owns" it accountability-wise, it's dead.”
“all of the unsafe code has been neatly isolated and clearly marked”
“You gain access to a codebase that does it which you can learn a lot from too.”
“You got me with the rewrite, you lost me with AI.”
“the unsafe footprint seems reasonable — the bulk of it in FFI wrappers”
“I don't know why anyone would choose this over the actively (community) maintained proper Postgres project.”
“on track to be faster and more scalable”
“all former expert understanding is buried down in slop so it is inaccessible”
“I'm sorry, but what is this need to just vibe code a port of an existing technology to a different language/framework/etc.”
“It's not just a rewrite ; it has improvements.”
“I see it as an interesting proof-of-concept.”
“This class of projects [LLM rewrite of a reliable piece of software honed over decades) is embarrassing.”
“the 100% Postgres regression tests do not test the threaded aspect of this project”
“In this case it's justified because Rust allows safe implementation of threaded code.”
“Except you didn't improve the architecture, did you? You just asked an LLM to copy what was already there.”
“You take ownership of it for your deployment and stop relying on continued free work.”
“Aiming for postgres compatible database with a 2026 architecture”
“you want to brag about how your LLM-generated slop is somehow more maintainable than the original”
“This is completely unsafe. It doesn't look like a rewrite that understands what's actually going on”
“very risky to use so probably only used for niche use cases at first”
“But it's an impressive achievement.”
“"I took a static snapshot of code and converted it to another static snapshot of code" is meaningless.”
“The project will die in a couple of days or weeks. You're making a mistake if you're seriously consider using this in any capacity.”
“something that should be celebrated as absolutely incredible”
“it's a good thing for security reasons if you're running a database server somewhere that attackers could get at it”
“I asked Claude to re-write this code into a new language that's in vogue right now!”
“I would absolutely never trust an LLM Postgres rewrite (in any language) in production based on "only" Postgres's test suite passing.”
“Why should a developer use this for anything beyond a pet project? Just because it is written in Rust?”
“I'm not entirely aure about that, but I do like the license in general.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.