| From: | "Greg Burd" <greg(at)burd(dot)me> |
|---|---|
| To: | "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: duckdb has extensible parser |
| Date: | 2026-05-19 00:12:33 |
| Message-ID: | ff237cde-23a5-470f-acc6-de62cc0f6fca@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 13, 2026, at 9:25 AM, Pavel Stehule wrote:
> Hi
>
> today I found an article about preparing a new parser for duckdb.
>
> I remember here was a discussion about it, so this can be an idea on how to do it.
>
> https://duckdb.org/2024/11/22/runtime-extensible-parsers
I've been working on Lime https://codeberg.org/gregburd/lime and a replacement of flex and bison in Postgres using Lime https://github.com/gburd/postgres/tree/lime which isn't yet stable or ready but the intention is/was to use a new parser that has the ability to be extended (changed) at runtime so that our extension authors can do some more interesting tricks.
Not a finished branch, but something to talk about for sure.
> Regards
>
> Pavel
best.
-greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-05-19 01:13:22 | Re: COPY FROM ON_ERROR SET_NULL bypasses domain NOT NULL with partial column list |
| Previous Message | Peter Smith | 2026-05-18 23:08:18 | Make the logical replication conflict messages more like each other |