Incorrect result from DuckDB execution

[dpxcc]

What happens?

Turning on duckdb.force_execution produces incorrect result
Please see the repro below

To Reproduce

postgres=# CREATE TABLE s (a text[]);
CREATE TABLE
postgres=# INSERT INTO s VALUES (ARRAY['abc', 'def', 'ghi']);
INSERT 0 1
postgres=# CREATE TABLE t AS TABLE s;
SELECT 1
postgres=# SELECT * FROM t;
       a       
---------------
 {abc,def,ghi}
(1 row)

postgres=# SET duckdb.force_execution TO true;
SET
postgres=# SELECT * FROM t;
  a   
------
 \x01
(1 row)

OS:

Linux

pg_duckdb Version (if built from source use commit hash):

0.2.0

Postgres Version (if built from source use commit hash):

17.2

Hardware:

No response

Full Name:

Cheng Chen

Affiliation:

Mooncake Labs

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a stable release

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?

• Yes, I have

[JelteF]

Hmm. Strange... Somehow that CREATE TABLE AS is significant, since this incorrect output does not occur when querying the s table.

Copy pastable reproduction script:

CREATE TABLE s (a text[]);
INSERT INTO s VALUES (ARRAY['abc', 'def', 'ghi']);
CREATE TABLE t AS TABLE s;
SELECT * FROM s;
SELECT * FROM t;
SET duckdb.force_execution TO true;
SELECT * FROM s;
SELECT * FROM t;