Error when using duckdb.force_execution

[TianzeMYou]

Any idea on where this error stems from? Following the brief example from #172 (reply in thread)

I am running

\timing on

drop table if exists t1, t2;
create table t1(a int);
create table t2(b int);
INSERT INTO t1 SELECT generate_series(1, 10000);
INSERT INTO t2 SELECT generate_series(1, 10000);
ANALYZE t1, t2;
set duckdb.execution = true;
SELECT count(*) FROM t1, t2 WHERE t1.a = t2.b or t1.a = t2.b + 1;
set duckdb.execution = false;
SELECT count(*) FROM t1, t2 WHERE t1.a = t2.b or t1.a = t2.b + 1;

But run into

postgres=> SELECT count(*) FROM t1, t2 WHERE t1.a = t2.b or t1.a = t2.b + 1;
ERROR:  (PGDuckDB/DuckdbPlanNode) Catalog Error: unrecognized configuration parameter "http_file_cache_dir"

[JelteF]

That sounds like you've been building a custom DuckDB instead of using the one included in the pg_duckdb repo. The http_file_cache_dir is a custom thing we're currently adding, but that we're considering removing that feature in the next release.

[JelteF]

But to be clear: the only supported way to run pg_duckdb currently is to use the bundled duckdb.

[TianzeMYou]

Could you elaborate on that please? I am using pg_duckdb 0.2.0 (I know about 0.3.1 and will upgrade soon) and duckdb 1.2.0 at the "bundled commit" https://github.com/duckdb/duckdb/tree/5f5512b827df6397afd31daedb4bbdee76520019. I manually moved duckdb into pg_duckdb/third_party, do you mean that's causing the issue and if yes, what's the difference?

[JelteF]

It sounds like you're not including the cached_httpfs extension: https://github.com/duckdb/pg_duckdb/tree/main/third_party/cached_httpfs

We bundle that into our duckdb build using:

1. a custom cmake file: https://github.com/duckdb/pg_duckdb/blob/main/third_party/pg_duckdb_extensions.cmake
2. by using that cmake file in the command we use to build duckdb:

   pg_duckdb/Makefile

   Line 117 in 77f1abf

   EXTENSION_CONFIGS="../pg_duckdb_extensions.cmake" \