--- title: DuckDB v2.0: Your Database Deserves a Better Parser description: DuckDB v2.0 replaces its PostgreSQL-derived, YACC/Bison-based SQL parser with a new Parsing Expression Grammar (PEG) parser. The change is motivated by the... canonical: https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: DuckDB v2.0: Your Database Deserves a Better Parser | daily.dev og:description: DuckDB v2.0 replaces its PostgreSQL-derived, YACC/Bison-based SQL parser with a new Parsing Expression Grammar (PEG) parser. The change is motivated by the... og:url: https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets og:image: https://api.daily.dev/og/posts/83tznVeTs.png og:image:alt: DuckDB v2.0: Your Database Deserves a Better Parser 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. # DuckDB v2.0: Your Database Deserves a Better Parser **[DuckDB](https://daily.dev/sources/duckdb)** · 15 min read · 0 upvotes · 0 comments ## Summary DuckDB v2.0 replaces its PostgreSQL-derived, YACC/Bison-based SQL parser with a new Parsing Expression Grammar (PEG) parser. The change is motivated by the difficulty of extending the old LALR(1) grammar without introducing shift/reduce conflicts. The new PEG parser, first introduced experimentally in v1.2/v1.5, uses packrat parsing (memoization) to avoid exponential slowdowns on malformed input, preserves DuckDB's existing AST and query behavior, and enables extensions to register their own grammar rules and transformers at runtime rather than relying on fallback parsing. The post walks through DuckSQL additions like expression statements, CONNECT/DISCONNECT, external resources syntax, and COPY TO partitioning, and demonstrates building a Google-style pipe-syntax extension using the new grammar extension API. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What parser does DuckDB v2.0 use instead of the PostgreSQL-derived parser? DuckDB v2.0 replaces its original PostgreSQL-derived, YACC/Bison LALR(1) parser with a new Parsing Expression Grammar (PEG) based parser. The PEG grammar was first introduced experimentally in v1.2 for CLI autocomplete and became a full opt-in parser in v1.5, before becoming the default in v2.0. It preserves the same DuckSQL dialect and produces the same internal AST for the binder. _Track how DuckDB's parser rewrite lands by following database engineering coverage on daily.dev._ ### How does DuckDB avoid exponential slowdown when parsing malformed SQL with a PEG parser? DuckDB uses packrat parsing, a memoization technique that caches the result of each grammar rule at each token position so it is never re-evaluated at that position. Without it, a query with 19 unmatched opening parentheses took 10.6 seconds to fail in the experimental v1.5 PEG parser, doubling with each extra parenthesis; with packrat parsing enabled, the same query is rejected in about 0.001 seconds. _Developers evaluating PEG parser designs can follow this kind of performance deep dive on daily.dev._ ### How can a DuckDB extension add new SQL syntax with the new PEG parser instead of using a fallback parser? Extensions register grammar extensions that plug directly into DuckDB's PEG grammar, specifying an existing rule to extend (such as SelectAtom) plus a transformer function that converts the resulting parse tree into DuckDB's AST. This lets an extension like a pipe-syntax implementation reuse existing rules such as GroupByClause instead of reimplementing all of SQL, unlike the older fallback-parser approach used by extensions like psql and duckpgq. _Anyone building DuckDB extensions can keep up with parser extensibility changes via daily.dev._ ## Similar posts on daily.dev - [Announcing DuckDB 1.5.0](https://daily.dev/posts/announcing-duckdb-1-5-0-3oljixkez) · DuckDB · 54 upvotes · 1 comments --- Tags: [#sql](https://daily.dev/tags/sql), [#duckdb](https://daily.dev/tags/duckdb) [View this post on daily.dev](https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets) ```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":"DuckDB v2.0: Your Database Deserves a Better Parser","url":"https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets"},"datePublished":"2026-08-20T15:22:20.213Z","dateModified":"2026-08-25T06:22:06.504Z","description":"DuckDB v2.0 replaces its PostgreSQL-derived, YACC/Bison-based SQL parser with a new Parsing Expression Grammar (PEG) parser. The change is motivated by the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6beaf53ab1c4ae5911329992e3dfef79?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6beaf53ab1c4ae5911329992e3dfef79?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DuckDB","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":"DuckDB","logo":"https://media.daily.dev/image/upload/s--3luD3Wei--/f_auto/v1714800008/logos/duckdb","url":"https://daily.dev/sources/duckdb"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"sql,duckdb","timeRequired":"PT15M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DuckDB","item":"https://daily.dev/sources/duckdb"},{"@type":"ListItem","position":3,"name":"DuckDB v2.0: Your Database Deserves a Better Parser"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/duckdb-v2-0-your-database-deserves-a-better-parser-83tznvets#faq","mainEntity":[{"@type":"Question","name":"What parser does DuckDB v2.0 use instead of the PostgreSQL-derived parser?","acceptedAnswer":{"@type":"Answer","text":"DuckDB v2.0 replaces its original PostgreSQL-derived, YACC/Bison LALR(1) parser with a new Parsing Expression Grammar (PEG) based parser. The PEG grammar was first introduced experimentally in v1.2 for CLI autocomplete and became a full opt-in parser in v1.5, before becoming the default in v2.0. It preserves the same DuckSQL dialect and produces the same internal AST for the binder. Track how DuckDB's parser rewrite lands by following database engineering coverage on daily.dev."}},{"@type":"Question","name":"How does DuckDB avoid exponential slowdown when parsing malformed SQL with a PEG parser?","acceptedAnswer":{"@type":"Answer","text":"DuckDB uses packrat parsing, a memoization technique that caches the result of each grammar rule at each token position so it is never re-evaluated at that position. Without it, a query with 19 unmatched opening parentheses took 10.6 seconds to fail in the experimental v1.5 PEG parser, doubling with each extra parenthesis; with packrat parsing enabled, the same query is rejected in about 0.001 seconds. Developers evaluating PEG parser designs can follow this kind of performance deep dive on daily.dev."}},{"@type":"Question","name":"How can a DuckDB extension add new SQL syntax with the new PEG parser instead of using a fallback parser?","acceptedAnswer":{"@type":"Answer","text":"Extensions register grammar extensions that plug directly into DuckDB's PEG grammar, specifying an existing rule to extend (such as SelectAtom) plus a transformer function that converts the resulting parse tree into DuckDB's AST. This lets an extension like a pipe-syntax implementation reuse existing rules such as GroupByClause instead of reimplementing all of SQL, unlike the older fallback-parser approach used by extensions like psql and duckpgq. Anyone building DuckDB extensions can keep up with parser extensibility changes via daily.dev."}}]} ```