pg_duckdb
pg_duckdb copied to clipboard
Don't plan twice for prepared statements
In #147 we added support for prepared statements, but that was done planning the query twice in DuckDB, once during planning to get the the column types of the result and once during execution. While this works, it's clearly suboptimal performance wise, and it's something we should change eventually.