pg_duckdb
pg_duckdb copied to clipboard
DuckDB-powered Postgres for high performance apps & analytics.
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [vite-tsconfig-paths](https://togithub.com/aleclarson/vite-tsconfig-paths) | [`^4.3.2` -> `^5.0.0`](https://renovatebot.com/diffs/npm/vite-tsconfig-paths/4.3.2/5.0.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/)...
We should add support for more list types (e.g. floating point lists, etc).
* This allows us to insert into tables by defining a custom insert operator * This makes schemas work natively without needing the current work-around
WIth #67 merged upstream, we can now support optional parameters to functions like `read_parquet`, etc.
This fixes a linker error when an older version of libduckdb is already installed. We should prefer the version we just finished building instead.
This mode is a (very long tail) mode that improves compatibility between DuckDB's SQL dialect and Postgres' SQL dialect. e.g.: * `SELECT COUNT(*) FROM tbl` returns a column named `count`,...
* We can now start multiple worker process that can read relation blocks and write buffer to shared memory to be consumed by duckdb reader threads. Problem can be viewed...
The goal is to return EXPLAIN plans in a "Postgres-style" format. Depends on #54.