how to execute 'SET unsafe_enable_version_guessing = true;' in postgresql to make iceberg_scan working correctly?

[chaosong]

[Y--]

Hi @chaosong can you try to run this?

SELECT * FROM duckdb.raw_query($$ SET unsafe_enable_version_guessing = true; $$)

[chaosong]

Hi @chaosong can you try to run this?

SELECT * FROM duckdb.raw_query($$ SET unsafe_enable_version_guessing = true; $$)

There is an error, but it works! Thank you!

[Y--]

Interesting, when I tried on my end I didn't see this error:

y=# SELECT * FROM duckdb.raw_query($$ SET unsafe_enable_version_guessing = true; $$);
NOTICE:  result: Success
BOOLEAN
[ Rows: 0]


 raw_query
-----------

(1 row)

Is pg_duckdb installed in your test database?
(I'm also surprised it still returned success :-)

[chaosong]

Interesting, when I tried on my end I didn't see this error:

y=# SELECT * FROM duckdb.raw_query($$ SET unsafe_enable_version_guessing = true; $$);
NOTICE:  result: Success
BOOLEAN
[ Rows: 0]


 raw_query
-----------

(1 row)

Is pg_duckdb installed in your test database? (I'm also surprised it still returned success :-)

[chaosong]

SET duckdb.force_execution TO false and the error is gone

[Y--]

Ah yeah if duckdb.force_execution=true then it make sense (though it is confusing I agree).

cc @JelteF let's discuss how we could improve this (ignoring 'duckdb.force_execution' when query has duckdb.<some_function_from_pgduckdb> for eg?)