{"slug": "pgrust", "name": "pgrust", "category": "databases", "category_name": "Databases", "description": "", "recommenders": 3, "commenters": 18, "warners": 8, "score": -3.16, "rising": 0.35, "first": "2026-06-12", "latest": "2026-10-25", "why": "The WebAssembly demo that runs in your browser is a really neat touch", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 5, "compare": 2, "warn": 8}, "spark": [0, 0, 0, 0, 0, 0, 0, 0, 2, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "The WebAssembly demo that runs in your browser is a really neat touch", "kind": "", "icon": false, "domain": null, "github_repo": "github.com/malisper/pgrust", "official_url": "https://github.com/malisper/pgrust", "pricing": "", "aliases": ["pgrust"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 789936368, "item_id": 49371023, "url": "https://news.ycombinator.com/item?id=49371023", "by": "tehlike", "date": "2026-08-19", "version": null, "stance": "recommend", "quote": "The more tangible example for me around LLM enabling what's previously long if not impossible tasks: pgrust.", "excerpt": "The more tangible example for me around LLM enabling what's previously long if not impossible tasks: pgrust. https://github.com/malisper/pgrust", "context": "", "use_case": "", "switched_from": "", "story": "Asana cleared 5 years of engineering work in 2 weeks with Codex"}, {"id": 785788272, "item_id": 49111767, "url": "https://news.ycombinator.com/item?id=49111767", "by": "wonger_", "date": "2026-07-30", "version": null, "stance": "recommend", "quote": "I found this post by the author to be a good example of architectural changes in pgrust", "excerpt": "For other interested spectators, I found this post by the author to be a good example of architectural changes in pgrust (along with motivations): https://malisper.me/the-four-horsemen-behind-thousands-of-postgres-outages/", "context": "", "use_case": "", "switched_from": "", "story": "Why Don't People Use Formal Methods?"}, {"id": 781694432, "item_id": 48855902, "url": "https://news.ycombinator.com/item?id=48855902", "by": "simonw", "date": "2026-07-09", "version": null, "stance": "recommend", "quote": "The WebAssembly demo that runs in your browser is a really neat touch", "excerpt": "The WebAssembly demo that runs in your browser is a really neat touch: https://pgrust.com", "context": "", "use_case": "Postgres-compatible database", "switched_from": "", "story": "Postgres rewritten in Rust, now passing 100% of the Postgres regression tests"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 803643088, "item_id": 50227693, "url": "https://news.ycombinator.com/item?id=50227693", "by": "verdverm", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "we don't have the commits we need to audit", "excerpt": "we don't have the commits we need to audit the first commit has 400k files, the other two more than 1000 each, if you are going to ask others to audit this scale of ai generated code, can you tell us what you have done to audit it? What I have seen is your Ai adding a lint test to make sure it doesn't cheat again. Are you personally aware of this file? How can you ensure it doesn't alter it and reinject the hand roll", "context": "", "use_case": "columnar database", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803639920, "item_id": 50227495, "url": "https://news.ycombinator.com/item?id=50227495", "by": "0conclusive-dem", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "pgrust appears to be at best misleading, at worst vibeslop", "excerpt": "this feels reasonable. for communities like r/selfhosted there has been an influx of new projects, many of which initially get dismissed. this more generous attitude can likely go a long way. unfortunately though pgrust appears to be at best misleading, at worst vibeslop: https://github.com/ClickHouse/ClickBench/pull/2165 hacknews thread isn\u2019t much prettier either https://news.ycombinator.com/item?id=50205816", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803638432, "item_id": 50227402, "url": "https://news.ycombinator.com/item?id=50227402", "by": "hitekker", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "the people (person?) behind pgrust has not committed to releasing the offending code", "excerpt": "For those curious, see the accusation here https://github.com/ClickHouse/ClickBench/pull/2165 and then the HN thread https://news.ycombinator.com/item?id=50205816 HN is waiting for the source code for pgrust 0.4-preview to be released, the version which allegedly cheated Clickhouse benchmark. So far, the people (person?) behind pgrust has not committed to releasing the offending code, and has instead offered other co", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803622112, "item_id": 50226382, "url": "https://news.ycombinator.com/item?id=50226382", "by": "anonymous908213", "date": "2026-10-24", "version": null, "stance": "warn", "quote": "pgrust was removed from ClickBench for cheating the benchmark in three different ways", "excerpt": "> I find it understandable that, every time I see pgrust discussed on a news aggregator, most people dismiss it as vibeslop garbage because almost all of these rewrite projects are slop. If I didn't know Malis, I would make the same assumption, because who has the time to look into all of these projects? Because I know Malis, I didn't bother to look at it; I just trusted him Perhaps a poor choice, given just yesterda", "context": "", "use_case": "PostgreSQL rewrite in Rust", "switched_from": "", "story": "We should be more ambitious with the software we build"}]}], "who": [], "tags": [], "use_cases": ["postgres rewrite in rust", "running clickbench", "columnar database", "postgresql rewrite in rust", "analytical database", "embedded database"], "compared": [{"slug": "postgresql", "name": "PostgreSQL", "co": 10, "switched_from": 0, "switched_to": 0}, {"slug": "clickhouse", "name": "ClickHouse", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "codex", "name": "Codex", "co": 3, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 803742944, "item_id": 50233934, "url": "https://news.ycombinator.com/item?id=50233934", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "recommend", "quote": "pgrust on a c6a.2xl is faster than ClickHouse running on a c6a.metal", "excerpt": "Update: ClickHouse finished the preliminary benchmarks for 0.4-beta[0], the version we've open-sourced. If you compute the geomean across all queries and instance sizes, it comes out as 7% faster than the 0.4-preview entry[1] that was accused of cheating. To give you a sense of how fast it is, pgrust on a c6a.2xl is faster than ClickHouse running on a c6a.metal, a machine with 24x as many cores and costs 24x as much.", "context": "", "use_case": "Postgres-compatible database", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803653536, "item_id": 50228346, "url": "https://news.ycombinator.com/item?id=50228346", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "recommend", "quote": "If you can find anything suspicious in the binary, let me know, and I'm happy to dig in", "excerpt": "If you don't trust the logging, here's a script you can run that instruments the binary and shows that the files called out for cheating don't run during the benchmark: https://pgrust.com/downloads/archive/2026-09-clickbench-snapshot/verify-preview.sh It instruments the files that were called out in the PR, then runs ClickBench. You can run it and see that the code in those files doesn't run. If you can find anything", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803645904, "item_id": 50227869, "url": "https://news.ycombinator.com/item?id=50227869", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "recommend", "quote": "That's enough to run all the queries on ClickBench", "excerpt": "> I've seen his explanation. I don't find it convincing, at all You don't have to take my word for it. If you want you can inspect the binary yourself: https://pgrust.com/downloads/archive/2026-09-clickbench-snapshot/pgrust-v0.4-preview-aarch64-neoverse-v2.tar.gz You can run the binary with PGRUST_GRAVITY_REPORT=1 which logs the code path hit for every query. You'll see that all the code goes through the general quer", "context": "one of pgrust's developers", "use_case": "analytical database", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803645120, "item_id": 50227820, "url": "https://news.ycombinator.com/item?id=50227820", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "neutral", "quote": "you can check the binary we submitted yourself", "excerpt": "Unfortunately, we have some sensitive stuff in our internal repo that we can't share. Fortunately, you can check the binary we submitted yourself: https://pgrust.com/downloads/archive/2026-09-clickbench-snapshot/pgrust-v0.4-preview-aarch64-neoverse-v2.tar.gz You can run it with PGRUST_GRAVITY_REPORT=1 and it will log the codepath that was hit for every query On the lint, yes, I'm aware. It's one layer of defense. Whe", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803644160, "item_id": 50227760, "url": "https://news.ycombinator.com/item?id=50227760", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "neutral", "quote": "The engine supports a narrow subset of SQL", "excerpt": "Fair point: the 0.4-beta source doesn't prove anything about the benchmarked binary. So don't take my word for it or rely on the source we published as evidence. Instead, check the submitted binary itself: https://pgrust.com/downloads/archive/2026-09-clickbench-snapshot/pgrust-v0.4-preview-aarch64-neoverse-v2.tar.gz If you run it with PGRUST_GRAVITY_REPORT=1 it will report the code path hit for each query. You can se", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803636608, "item_id": 50227288, "url": "https://news.ycombinator.com/item?id=50227288", "by": "malisper", "date": "2026-10-25", "version": null, "stance": "recommend", "quote": "You'll find it's just as fast as we claim it is", "excerpt": "> This aged like milk. pgrust was caught cheating on all benchmarks this week. Can you back this up? Our code is open source here[0]. You're free to audit it and benchmark it as much as you want. You'll find it's just as fast as we claim it is [0] https://github.com/malisper/pgrust", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}], "threads": [{"url": "https://news.ycombinator.com/item?id=50225695", "title": "We should be more ambitious with the software we build", "mentions": 10}, {"url": "https://news.ycombinator.com/item?id=49208535", "title": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD", "mentions": 7}, {"url": "https://news.ycombinator.com/item?id=50205816", "title": "Remove pgrust: the entry is cheating (per-query kernels and result caching)", "mentions": 4}, {"url": "https://news.ycombinator.com/item?id=48841676", "title": "Postgres rewritten in Rust, now passing 100% of the Postgres regression tests", "mentions": 4}, {"url": "https://news.ycombinator.com/item?id=50119991", "title": "Postgres 19 delayed after AI reviewers find more bugs than humans can fix", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49109026", "title": "Why Don't People Use Formal Methods?", "mentions": 2}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {"neutral": 1}, "2026-07": {"warn": 2, "neutral": 2, "recommend": 2}, "2026-08": {"neutral": 1, "warn": 1, "compare": 2, "recommend": 1}, "2026-09": {"warn": 1}, "2026-10": {"warn": 4, "neutral": 1}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 803643088, "item_id": 50227693, "url": "https://news.ycombinator.com/item?id=50227693", "by": "verdverm", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "we don't have the commits we need to audit", "excerpt": "we don't have the commits we need to audit the first commit has 400k files, the other two more than 1000 each, if you are going to ask others to audit this scale of ai generated code, can you tell us what you have done to audit it? What I have seen is your Ai adding a lint test to make sure it doesn't cheat again. Are you personally aware of this file? How can you ensure it doesn't alter it and reinject the hand roll", "context": "", "use_case": "columnar database", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803639920, "item_id": 50227495, "url": "https://news.ycombinator.com/item?id=50227495", "by": "0conclusive-dem", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "pgrust appears to be at best misleading, at worst vibeslop", "excerpt": "this feels reasonable. for communities like r/selfhosted there has been an influx of new projects, many of which initially get dismissed. this more generous attitude can likely go a long way. unfortunately though pgrust appears to be at best misleading, at worst vibeslop: https://github.com/ClickHouse/ClickBench/pull/2165 hacknews thread isn\u2019t much prettier either https://news.ycombinator.com/item?id=50205816", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803638432, "item_id": 50227402, "url": "https://news.ycombinator.com/item?id=50227402", "by": "hitekker", "date": "2026-10-25", "version": null, "stance": "warn", "quote": "the people (person?) behind pgrust has not committed to releasing the offending code", "excerpt": "For those curious, see the accusation here https://github.com/ClickHouse/ClickBench/pull/2165 and then the HN thread https://news.ycombinator.com/item?id=50205816 HN is waiting for the source code for pgrust 0.4-preview to be released, the version which allegedly cheated Clickhouse benchmark. So far, the people (person?) behind pgrust has not committed to releasing the offending code, and has instead offered other co", "context": "", "use_case": "", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803622112, "item_id": 50226382, "url": "https://news.ycombinator.com/item?id=50226382", "by": "anonymous908213", "date": "2026-10-24", "version": null, "stance": "warn", "quote": "pgrust was removed from ClickBench for cheating the benchmark in three different ways", "excerpt": "> I find it understandable that, every time I see pgrust discussed on a news aggregator, most people dismiss it as vibeslop garbage because almost all of these rewrite projects are slop. If I didn't know Malis, I would make the same assumption, because who has the time to look into all of these projects? Because I know Malis, I didn't bother to look at it; I just trusted him Perhaps a poor choice, given just yesterda", "context": "", "use_case": "PostgreSQL rewrite in Rust", "switched_from": "", "story": "We should be more ambitious with the software we build"}, {"id": 803480672, "item_id": 50217542, "url": "https://news.ycombinator.com/item?id=50217542", "by": "remywang", "date": "2026-10-24", "version": null, "stance": "neutral", "quote": "it is interesting to see an open source system that beats ClickHouse on ClickBench", "excerpt": "So I spent some time poking at the released 0.4-beta code. Controversy aside, it is interesting to see an open source system that beats ClickHouse on ClickBench - 4 out of the 5 systems ahead of CH (Umbra, elosdb, Hyper, CedarDB) are all closed-source, while the only open one is pivotlake. What makes pgrust fast? There's no one single reason, but a combination of techniques like dictionary encoding [1], zone maps [2]", "context": "", "use_case": "analytical database", "switched_from": "", "story": "Remove pgrust: the entry is cheating (per-query kernels and result caching)"}, {"id": 803320992, "item_id": 50207562, "url": "https://news.ycombinator.com/item?id=50207562", "by": "verdverm", "date": "2026-10-23", "version": null, "stance": "warn", "quote": "the project has 3 mega commits of claude slop", "excerpt": "that requires someone (1) using PRs (2) looking at the PR the project has 3 mega commits of claude slop https://github.com/malisper/pgrust/commits/main/", "context": "", "use_case": "", "switched_from": "", "story": "Remove pgrust: the entry is cheating (per-query kernels and result caching)"}, {"id": 803316192, "item_id": 50207262, "url": "https://news.ycombinator.com/item?id=50207262", "by": "verdverm", "date": "2026-10-23", "version": null, "stance": "warn", "quote": "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", "excerpt": "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 The hype factory must grow, I suppose, though I would prefer if the model makers would stop with this \"complete the task by any and every means possible\" and replace it with \"I don't know, I should ask or do more learning\" At least they have added a test which looks to make sure th", "context": "", "use_case": "", "switched_from": "", "story": "Remove pgrust: the entry is cheating (per-query kernels and result caching)"}, {"id": 798311776, "item_id": 49894486, "url": "https://news.ycombinator.com/item?id=49894486", "by": "imhoguy", "date": "2026-09-29", "version": null, "stance": "warn", "quote": "Postgres rewirte in Rust, it has 3 versions looks like each one generated from scratch", "excerpt": "Absolutely, I should really put \"/s\" after that. Really I was thinking about exact example announced recently on HN: Postgres rewirte in Rust, it has 3 versions looks like each one generated from scratch https://github.com/malisper/pgrust", "context": "", "use_case": "Postgres rewrite in Rust", "switched_from": "", "story": "The problem is not AI code, but not knowing about system architecture or intent"}, {"id": 789936368, "item_id": 49371023, "url": "https://news.ycombinator.com/item?id=49371023", "by": "tehlike", "date": "2026-08-19", "version": null, "stance": "recommend", "quote": "The more tangible example for me around LLM enabling what's previously long if not impossible tasks: pgrust.", "excerpt": "The more tangible example for me around LLM enabling what's previously long if not impossible tasks: pgrust. https://github.com/malisper/pgrust", "context": "", "use_case": "", "switched_from": "", "story": "Asana cleared 5 years of engineering work in 2 weeks with Codex"}, {"id": 788261105, "item_id": 49266319, "url": "https://news.ycombinator.com/item?id=49266319", "by": "manjose2018", "date": "2026-08-11", "version": null, "stance": "compare", "quote": "Please consider comparing pg_clickhouse to pgrust.", "excerpt": "Please consider comparing pg_clickhouse to pgrust. https://malisper.me/how-we-made-postgres-hundreds-of-times-faster-the-query-engine/", "context": "", "use_case": "", "switched_from": "", "story": "pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries"}, {"id": 787477137, "item_id": 49217321, "url": "https://news.ycombinator.com/item?id=49217321", "by": "malisper", "date": "2026-08-07", "version": null, "stance": "recommend", "quote": "", "excerpt": "^For context, this is Greg Smith, the author of Postgres 9.0 High Performance[0]. That book was my first introduction to Postgres [0] https://www.amazon.com/dp/184951030X", "context": "", "use_case": "", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 787459360, "item_id": 49216210, "url": "https://news.ycombinator.com/item?id=49216210", "by": "patkepa", "date": "2026-08-07", "version": null, "stance": "compare", "quote": "does having it in pure rust, opens possibility of embedding pgrust directly into binary, making it an alternative to SQLite/turso?", "excerpt": "Question, does having it in pure rust, opens possibility of embedding pgrust directly into binary, making it an alternative to SQLite/turso?", "context": "", "use_case": "embedded database", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 787437185, "item_id": 49214824, "url": "https://news.ycombinator.com/item?id=49214824", "by": "jjice", "date": "2026-08-07", "version": null, "stance": "warn", "quote": "it's kind of wrong to port in such a direct way and change the license", "excerpt": "While I do like pgrust's license, I do feel like it's kind of wrong to port in such a direct way and change the license. I guess this isn't a fork, but it kind of is? It looks like according to this post [0], they did a Claude Fable + Opus re-write. I know that legally this is seemingly a valid way to do things and avoid copyright, but it feels wrong to me. I don't even necessarily think that my feelings are correct,", "context": "", "use_case": "", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 787370896, "item_id": 49210681, "url": "https://news.ycombinator.com/item?id=49210681", "by": "Whitespace", "date": "2026-08-07", "version": null, "stance": "neutral", "quote": "That's a lot of token momentum!", "excerpt": "main indeed has two commits, but it clearly states the location of the rest of the commits, so I wouldn't be critical of main itself. hey claude, do a breakthrough You can find the actual git history at the v0.2 github tag. Co-Authored-By: Fable <noreply@anthropic.com> Now we see https://github.com/malisper/pgrust/tree/v0.2 has almost 6000 commits in it, with the very first one on 2026-07-02. That's a lot of token mo", "context": "", "use_case": "", "switched_from": "", "story": "Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD"}, {"id": 785788272, "item_id": 49111767, "url": "https://news.ycombinator.com/item?id=49111767", "by": "wonger_", "date": "2026-07-30", "version": null, "stance": "recommend", "quote": "I found this post by the author to be a good example of architectural changes in pgrust", "excerpt": "For other interested spectators, I found this post by the author to be a good example of architectural changes in pgrust (along with motivations): https://malisper.me/the-four-horsemen-behind-thousands-of-postgres-outages/", "context": "", "use_case": "", "switched_from": "", "story": "Why Don't People Use Formal Methods?"}, {"id": 785148784, "item_id": 49071799, "url": "https://news.ycombinator.com/item?id=49071799", "by": "zX41ZdbW", "date": "2026-07-27", "version": null, "stance": "warn", "quote": "I tried pgrust on ClickBench recently, but it didn't work at all", "excerpt": "I tried pgrust on ClickBench recently, but it didn't work at all: https://github.com/ClickHouse/ClickBench/pull/983#issuecomment-5023912914", "context": "", "use_case": "running ClickBench", "switched_from": "", "story": "Pgrust was built: four attempts to rewrite Postgres in Rust with AI"}, {"id": 785148736, "item_id": 49071796, "url": "https://news.ycombinator.com/item?id=49071796", "by": "zX41ZdbW", "date": "2026-07-27", "version": null, "stance": "warn", "quote": "I tried pgrust on ClickBench recently, but it didn't work at all", "excerpt": "I tried pgrust on ClickBench recently, but it didn't work at all: https://github.com/ClickHouse/ClickBench/pull/983#issuecomment-5023912914", "context": "", "use_case": "running ClickBench", "switched_from": "", "story": "Postgres in Rust: three dead ends before we passed 100% of the regression suite"}, {"id": 781697184, "item_id": 48856074, "url": "https://news.ycombinator.com/item?id=48856074", "by": "psychoslave", "date": "2026-07-09", "version": null, "stance": "neutral", "quote": "naming it something like pgrust[1] makes sense for ease of discovery", "excerpt": "If this is still speaking about the Postgres rewrite in Rust, then naming it something like pgrust[1] makes sense for ease of discovery for anyone aware of these technologies. [1] https://github.com/malisper/pgrust I guess", "context": "", "use_case": "", "switched_from": "", "story": "Rewriting Bun in Rust"}, {"id": 781694432, "item_id": 48855902, "url": "https://news.ycombinator.com/item?id=48855902", "by": "simonw", "date": "2026-07-09", "version": null, "stance": "recommend", "quote": "The WebAssembly demo that runs in your browser is a really neat touch", "excerpt": "The WebAssembly demo that runs in your browser is a really neat touch: https://pgrust.com", "context": "", "use_case": "Postgres-compatible database", "switched_from": "", "story": "Postgres rewritten in Rust, now passing 100% of the Postgres regression tests"}, {"id": 781500800, "item_id": 48843800, "url": "https://news.ycombinator.com/item?id=48843800", "by": "vintagedave", "date": "2026-07-09", "version": null, "stance": "neutral", "quote": "This is impressive - but is a license change", "excerpt": "This is impressive - but is a license change, from the PostgresQL license [0] to AGPL [1]. I like the AGPL and think it's the best truly free open source license, but I worry if this is compatible. Ie, if this is rewritten from the original source, should the original apply? (Yes.) There has been a trend to rewrite open source software with a more restrictive license (like coretools in Rust). This looks considerably ", "context": "", "use_case": "Postgres rewrite in Rust", "switched_from": "", "story": "Postgres rewritten in Rust, now passing 100% of the Postgres regression tests"}, {"id": 781480464, "item_id": 48842529, "url": "https://news.ycombinator.com/item?id=48842529", "by": "queoahfh", "date": "2026-07-09", "version": null, "stance": "warn", "quote": "I am concerned about the quality. Even a cursory skim of the code makes the code appear asinine.", "excerpt": "I am concerned about the quality. Even a cursory skim of the code makes the code appear asinine. Unless the genius aspects of the code elude me. https://github.com/malisper/pgrust/blob/3646a73515a5e4ac7d0b7df88c61b180e1cabdb2/crates/backend/catalog/pg_inherits/src/lib.rs#L450 https://github.com/malisper/pgrust/blob/3646a73515a5e4ac7d0b7df88c61b180e1cabdb2/crates/backend/catalog/pg_inherits/src/lib.rs#L221", "context": "", "use_case": "", "switched_from": "", "story": "Postgres rewritten in Rust, now passing 100% of the Postgres regression tests"}, {"id": 776095536, "item_id": 48505971, "url": "https://news.ycombinator.com/item?id=48505971", "by": "saadn92", "date": "2026-06-12", "version": null, "stance": "neutral", "quote": "there's someone already doing this: https://github.com/malisper/pgrust", "excerpt": "there's someone already doing this: https://github.com/malisper/pgrust", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: FablePool \u2013 pool money behind a prompt, and Fable builds it in public"}]}