Segfault in 1.1.3, fixed in 1.5.1

[davetapley]

What happens?

Segfault in 1.1.3, fixed in 1.5.1, putting MRE here in case it helps in the future.

To Reproduce

Files: https://jefuller-my.sharepoint.com/:f:/p/dave/IgA6tVB8Vv4aSpsUM-z7k0iHAfCgp1DJci-7D-yhD49mZKg?e=5pfQeE

# duck_segfault.py 

from duckdb import connect

con = connect('53999.44.duckdb')

con.execute('''
CREATE TEMP TABLE ota_all AS
   SELECT * FROM '3892.parquet'
   WHERE sensoridx = 3892
   AND dataval IS NOT NULL;
''')

con.execute('''
INSERT OR IGNORE INTO ota (ts, val, source)
      SELECT gmt, ANY_VALUE(dataval), source
      FROM ota_all
      GROUP BY gmt, source
      HAVING COUNT(DISTINCT(dataval)) = 1;
''')

$ uv run python duck_segfault.py 

$ echo $?
139

# change to 1.5.1 in pyproject.toml

$ uv sync
Resolved 187 packages in 857ms
Uninstalled 1 package in 1ms
Installed 1 package in 6ms
 - duckdb==1.1.3
 + duckdb==1.5.1

$ uv run python duck_segfault.py 

$ echo $?
0

OS:

Ubuntu 22.04.5 LTS

DuckDB Package Version:

1.1.3

Python Version:

3.12.2

Full Name:

Dave Tapley

Affiliation:

JE Fuller

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

I have not tested with any build

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

Yes

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant configuration to reproduce the issue?

• Yes, I have

[evertlammerts]

Thanks for reporting @davetapley !