--- title: pgrust Faster Than Postgres? | Scaling Postgres 426 description: A Postgres-focused podcast episode covering several topics: pgrust, a Rust rewrite of PostgreSQL built using AI (Claude Opus) at a cost of $100K, has passed... canonical: https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: pgrust Faster Than Postgres? | Scaling Postgres 426 | daily.dev og:description: A Postgres-focused podcast episode covering several topics: pgrust, a Rust rewrite of PostgreSQL built using AI (Claude Opus) at a cost of $100K, has passed... og:url: https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo og:image: https://api.daily.dev/og/posts/H7lGxRmlo.png og:image:alt: pgrust Faster Than Postgres? | Scaling Postgres 426 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # pgrust Faster Than Postgres? | Scaling Postgres 426 **[Scaling Postgres](https://daily.dev/sources/scaling-postgres)** · 15 min read · 23 upvotes · 3 comments ## Summary A Postgres-focused podcast episode covering several topics: pgrust, a Rust rewrite of PostgreSQL built using AI (Claude Opus) at a cost of $100K, has passed 100% of Postgres regression tests. A follow-up version called PG Rust Fast claims to be 50% faster than Postgres on transactional workloads and comparable to ClickHouse for analytical ones, with $200K invested. The episode also covers PG Hard Storage, a cloud-native Postgres backup tool using streaming replication slots; a deep dive into how LISTEN/NOTIFY can cause lock cascades; SQL/PGQ graph query rewrites in Postgres 19; and a sharding solution for Postgres from PlanetScale called Necki. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is PG Rust and has it passed the Postgres regression test suite? PG Rust is a project rewriting Postgres in Rust that has passed 100% of the Postgres regression tests, tested against Postgres 18.3. It can boot from an existing Postgres data directory, but it is not yet production ready, not optimized, and not compatible with existing Postgres extensions. _Developers evaluating experimental Postgres alternatives can track milestones like this via daily.dev._ ### How much did it cost to build PG Rust using AI and which AI model was used? Building PG Rust idiomatic took four attempts and roughly $100,000 using Anthropic's Claude Opus model, after earlier attempts with a transpiled C-to-Rust version (5.3 million lines of unsafe code) and an abandoned tool called Fable proved unworkable. A further $200,000 was then spent on a follow-up version called PG Rust Fast aimed at improving performance. _Teams weighing AI-assisted rewrites of critical infrastructure can follow real cost breakdowns like this on daily.dev._ ### How much faster is PG Rust Fast compared to regular Postgres? PG Rust Fast is claimed to be over 50% faster than Postgres on transactional workloads and roughly as fast as ClickHouse on analytical workloads, using a new vectorized executor, a new JIT compiler that cuts JIT compilation latency from 50 milliseconds to five microseconds, and a scheduler that dynamically reprioritizes queries. This remains an internal, unreleased test result, with public release planned within two weeks of the report. _Anyone benchmarking Postgres alternatives can keep an eye on performance claims like this through daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@trevorsuna** · 2 upvotes > Passing the regression suite is a big milestone, but the 50% faster claim needs repeatable workloads and durability tests before I’d get too excited. The LISTEN/NOTIFY lock cascade discussion sounds useful too. **@eliasaliche** · 0 upvotes > It's very important to note that regression tests are in no way exhaustive testing. "Overfitting" is a real problem when the objective of an implementation is to pass tests. Also, C/C++'s architecture probably isn't the same as Rust's, so it's also possible that it works now but lacks any kind of architectural robustness. ## Similar posts on daily.dev - [GitHub - malisper/pgrust: Postgres rewritten in Rust, now passing 100% of the Postgres regression tests](https://daily.dev/posts/github---malisper-pgrust-postgres-rewritten-in-rust-now-passing-100-of-the-postgres-regression-te-t4anp8pcl) · Hacker News · 4 upvotes · 0 comments - [Rebuilding Postgres for 300x faster analytics: batching, operator fusion, and SIMD](https://daily.dev/posts/rebuilding-postgres-for-300x-faster-analytics-batching-operator-fusion-and-simd-tgtpnmlyi) · Hacker News · 0 upvotes · 0 comments --- Tags: [#database](https://daily.dev/tags/database), [#backend](https://daily.dev/tags/backend), [#rust](https://daily.dev/tags/rust), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"pgrust Faster Than Postgres? | Scaling Postgres 426","url":"https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo"},"datePublished":"2026-07-19T21:24:57.118Z","dateModified":"2026-09-14T06:14:53.737Z","description":"A Postgres-focused podcast episode covering several topics: pgrust, a Rust rewrite of PostgreSQL built using AI (Claude Opus) at a cost of $100K, has passed...","image":"https://i.ytimg.com/vi/8kUtAaO8SIg/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/8kUtAaO8SIg/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Scaling Postgres","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Scaling Postgres","logo":"https://media.daily.dev/image/upload/s--RbakkUgu--/f_auto,q_auto/v1780213462/logos/scaling-postgres?_a=BAMAMiWQ0","url":"https://daily.dev/sources/scaling-postgres"},"commentCount":3,"discussionUrl":"https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":23},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":3}],"keywords":"database,backend,rust,postgresql","timeRequired":"PT15M","video":{"@type":"VideoObject","name":"pgrust Faster Than Postgres? | Scaling Postgres 426","description":"A Postgres-focused podcast episode covering several topics: pgrust, a Rust rewrite of PostgreSQL built using AI (Claude Opus) at a cost of $100K, has passed...","thumbnailUrl":"https://i.ytimg.com/vi/8kUtAaO8SIg/sddefault.jpg","uploadDate":"2026-07-19T21:24:57.118Z","duration":"PT15M","url":"https://api.daily.dev/r/H7lGxRmlo","embedUrl":"https://www.youtube.com/embed/8kUtAaO8SIg"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Scaling Postgres","item":"https://daily.dev/sources/scaling-postgres"},{"@type":"ListItem","position":3,"name":"pgrust Faster Than Postgres? | Scaling Postgres 426"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo","comment":[{"@type":"Comment","text":"Passing the regression suite is a big milestone, but the 50% faster claim needs repeatable workloads and durability tests before I’d get too excited. The LISTEN/NOTIFY lock cascade discussion sounds useful too.","datePublished":"2026-07-20T02:17:49.145Z","url":"https://daily.dev/posts/H7lGxRmlo#c-d6FViFYCn","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"It’s very important to note that regression tests are in no way exhaustive testing. “Overfitting” is a real problem when the objective of an implementation is to pass tests. Also, C/C++'s architecture probably isn’t the same as Rust’s, so it’s also possible that it works now but lacks any kind of architectural robustness.","datePublished":"2026-07-20T19:02:16.677Z","dateModified":"2026-07-20T19:02:28.277Z","url":"https://daily.dev/posts/H7lGxRmlo#c-vRaMe8m5J","author":{"@type":"Person","name":"Elias Aliche","url":"https://daily.dev/eliasaliche","image":"https://media.daily.dev/image/upload/s--GVlzrUxp--/f_auto/v1732125180/avatars/avatar_DrmjqCjWat0UCbJgBJHBZ"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/pgrust-faster-than-postgres-scaling-postgres-426-h7lgxrmlo#faq","mainEntity":[{"@type":"Question","name":"What is PG Rust and has it passed the Postgres regression test suite?","acceptedAnswer":{"@type":"Answer","text":"PG Rust is a project rewriting Postgres in Rust that has passed 100% of the Postgres regression tests, tested against Postgres 18.3. It can boot from an existing Postgres data directory, but it is not yet production ready, not optimized, and not compatible with existing Postgres extensions. Developers evaluating experimental Postgres alternatives can track milestones like this via daily.dev."}},{"@type":"Question","name":"How much did it cost to build PG Rust using AI and which AI model was used?","acceptedAnswer":{"@type":"Answer","text":"Building PG Rust idiomatic took four attempts and roughly $100,000 using Anthropic's Claude Opus model, after earlier attempts with a transpiled C-to-Rust version (5.3 million lines of unsafe code) and an abandoned tool called Fable proved unworkable. A further $200,000 was then spent on a follow-up version called PG Rust Fast aimed at improving performance. Teams weighing AI-assisted rewrites of critical infrastructure can follow real cost breakdowns like this on daily.dev."}},{"@type":"Question","name":"How much faster is PG Rust Fast compared to regular Postgres?","acceptedAnswer":{"@type":"Answer","text":"PG Rust Fast is claimed to be over 50% faster than Postgres on transactional workloads and roughly as fast as ClickHouse on analytical workloads, using a new vectorized executor, a new JIT compiler that cuts JIT compilation latency from 50 milliseconds to five microseconds, and a scheduler that dynamically reprioritizes queries. This remains an internal, unreleased test result, with public release planned within two weeks of the report. Anyone benchmarking Postgres alternatives can keep an eye on performance claims like this through daily.dev."}}]} ```