# Postgres rewritten in Rust

23 Hacker News commenters recommended Postgres rewritten in Rust and 32 criticized it, November 2025 to November 2026. It was recommended in 1 of 13 months.

**Verdict:** 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.

## Why people recommend it

- Readable codebase for learning (2 comments): "You gain access to a codebase that does it which you can learn a lot from too." ([source](https://news.ycombinator.com/item?id=48859334)) "Students could use it as an example of porting code." ([source](https://news.ycombinator.com/item?id=48860089))
- Unsafe code isolated and marked (2 comments): "the unsafe footprint seems reasonable — the bulk of it in FFI wrappers" ([source](https://news.ycombinator.com/item?id=48858889)) "all of the unsafe code has been neatly isolated and clearly marked" ([source](https://news.ycombinator.com/item?id=48859693))
- Safer Rust design benefits security (2 comments): "it's a good thing for security reasons if you're running a database server somewhere that attackers could get at it" ([source](https://news.ycombinator.com/item?id=48842715)) "doing it in safer, less error prone technology would be way better" ([source](https://news.ycombinator.com/item?id=48860320))
- Threaded design built on Rust safety (2 comments): "there's some great stuff in here, particularly the direct-to-binary codegen, threads instead of processes and sync batching" ([source](https://news.ycombinator.com/item?id=49112043)) "In this case it's justified because Rust allows safe implementation of threaded code." ([source](https://news.ycombinator.com/item?id=48853493))

## What people warn about

- LLM-generated code copied, not improved (6 comments): "I'm sorry, but what is this need to just vibe code a port of an existing technology to a different language/framework/etc." ([source](https://news.ycombinator.com/item?id=48857132)) "Except you didn't improve the architecture, did you? You just asked an LLM to copy what was already there." ([source](https://news.ycombinator.com/item?id=48853001)) ""I took a static snapshot of code and converted it to another static snapshot of code" is meaningless." ([source](https://news.ycombinator.com/item?id=48842852))
- Immature, unsafe for production use (4 comments): "very risky to use so probably only used for niche use cases at first" ([source](https://news.ycombinator.com/item?id=48843195)) "I would absolutely never trust an LLM Postgres rewrite (in any language) in production based on "only" Postgres's test suite passing." ([source](https://news.ycombinator.com/item?id=48842358)) "This stuff is all pretty immature though and I wouldn't actually build on it outside of some very narrow, well-understood workloads." ([source](https://news.ycombinator.com/item?id=48863386))
- Tests miss threading and ACID guarantees (3 comments): "I would absolutely never trust an LLM Postgres rewrite (in any language) in production based on "only" Postgres's test suite passing." ([source](https://news.ycombinator.com/item?id=48842358)) "The only way they got that increase was by breaking the synchronization mechanisms that provide ACID guarantees in Postgres" ([source](https://news.ycombinator.com/item?id=48864824)) "the 100% Postgres regression tests do not test the threaded aspect of this project" ([source](https://news.ycombinator.com/item?id=48853695))
- Maintainer unknown; likely to die (3 comments): "given the author/maintainer is essentially unknown, I highly doubt this will reach it's target audience" ([source](https://news.ycombinator.com/item?id=48861714)) "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." ([source](https://news.ycombinator.com/item?id=48842791)) "Unless the Postgres team takes this and "owns" it accountability-wise, it's dead." ([source](https://news.ycombinator.com/item?id=48859979))

## 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, "Postgres rewritten in Rust", https://hackerapproved.com/p/postgres-rewritten-in-rust/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).