Open dpxcc opened 1 day ago
Potentially related to https://github.com/duckdb/pg_duckdb/issues/19
It seems that the latest version cannot reproduce this anomaly
[postgres@halo-centos8 pg_duckdb]$ psql
psql (16.4)
Type "help" for help.
postgres=# create extension pg_duckdb;
CREATE EXTENSION
postgres=# SET duckdb.force_execution = ON;
SET
postgres=# CREATE TABLE t (a INT) PARTITION BY LIST (a);
CREATE TABLE
postgres=# CREATE TABLE s (b INT);
CREATE TABLE
postgres=# SELECT * FROM t JOIN s ON a = b;
a | b
---+---
(0 rows)
postgres=# \dx
List of installed extensions
Name | Version | Schema | Description
-----------+---------+------------+-----------------------------------------------------------------------------------------------
orafce | 4.14 | tpcds1 | Functions and operators that emulate a subset of functions and packages from the Oracle RDBMS
pg_duckdb | 0.2.0 | public | DuckDB Embedded in Postgres
pg_jieba | 1.1.1 | public | a parser for full-text search of Chinese
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
(4 rows)
postgres=# \q
[postgres@halo-centos8 pg_duckdb]$ git branch -v
* main 58718a7 Fix typo in NOTICE file (#407)
You need to compile Postgres with --enable-cassert
to reproduce
What happens?
Server crashes when executing the script below to scan partitioned table
To Reproduce
backtrace
OS:
Linux
pg_duckdb Version:
0.1.0
Postgres Version:
17.0
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?
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?