Comment by quotemstr

Only if DuckDB is an acceptable value of PostgreSQL. I agree that PostgreSQL has eaten many DB use-cases, but the breathless hype is becoming exhausting.

Look. In a PostgreSQL extension, I can't:

1. extend the SQL language with ergonomic syntax for my use-case,

2. teach the query planner to understand execution strategies that can't be made to look PostgreSQL's tuple-and-index execution model, or

3. extend the type system to plumb new kinds of metadata through the whole query and storage system via some extensible IR.

(Plus, embedded PostgreSQL still isn't a first class thing.)

Until PostgreSQL's extension mechanism is powerful enough for me to literally implement DuckDB as an extension, PostgreSQL is not a panacea. It's a good system, but nowhere near universal.

Now, once I can do DuckDB (including its language extensions) in PostgreSQL, and once I can use the thing as a library, let's talk.

(pg_duckdb doesn't count. It's a switch, not a unified engine.)