What happens?
DO $$
BEGIN
SET LOCAL duckdb.force_execution = true;
CREATE TEMP TABLE tmp_tble1 AS
SELECT id FROM mytable WHERE id IN ('ersaiDN2dO4YojZ','ersFI2HutTimVaO');
SET LOCAL duckdb.force_execution = false;
END $$;
When query with both these ids 'ersaiDN2dO4YojZ' and 'ersFI2HutTimVaO' as above, the temp table is not populating. If I give only one value then working fine. Using azure postgreSQL and enabled PG_duckdb extension.
To Reproduce
DO $$
BEGIN
SET LOCAL duckdb.force_execution = true;
CREATE TEMP TABLE tmp_tble1 AS
SELECT id FROM mytable WHERE id IN ('ersaiDN2dO4YojZ','ersFI2HutTimVaO');
SET LOCAL duckdb.force_execution = false;
END $$;
OS:
Azure Database for PostgreSQL flexible server
DuckDB Version:
PG_DUCKDB azure extension
DuckDB Client:
PG_DUCKDB azure extension
Hardware:
No response
Full Name:
Rojo Joseph
Affiliation:
Riversand
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?
Did you include all code required to reproduce the issue?
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
What happens?
DO $$
BEGIN
SET LOCAL duckdb.force_execution = true;
CREATE TEMP TABLE tmp_tble1 AS
SELECT id FROM mytable WHERE id IN ('ersaiDN2dO4YojZ','ersFI2HutTimVaO');
SET LOCAL duckdb.force_execution = false;
END $$;
When query with both these ids 'ersaiDN2dO4YojZ' and 'ersFI2HutTimVaO' as above, the temp table is not populating. If I give only one value then working fine. Using azure postgreSQL and enabled PG_duckdb extension.
To Reproduce
DO $$
BEGIN
SET LOCAL duckdb.force_execution = true;
CREATE TEMP TABLE tmp_tble1 AS
SELECT id FROM mytable WHERE id IN ('ersaiDN2dO4YojZ','ersFI2HutTimVaO');
SET LOCAL duckdb.force_execution = false;
END $$;
OS:
Azure Database for PostgreSQL flexible server
DuckDB Version:
PG_DUCKDB azure extension
DuckDB Client:
PG_DUCKDB azure extension
Hardware:
No response
Full Name:
Rojo Joseph
Affiliation:
Riversand
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?
Did you include all code required to reproduce the issue?
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)