Problemsby IbisTrouble with DuckDB result
Databases5 posts from 5 people4d active+00 posts in the last 7 days, 1 the 7 days before (fading)
Posts per day
The posts behind it
5, newest firstWrong result: join_elimination drops a LEFT JOIN below a LIMIT/OFFSET under a DISTINCT### What happens? `join_elimination` removes a LEFT JOIN that sits below a `LIMIT ... OFFSET` when the query above only needs DISTINCT values of a left-side column. The join does not change the set of left-side values, but it does change how many rows there are, so it changes...duckdb/duckdb · bgiesbrecht1 repliesOpen ↗Unexpected Anti Join Result### What happens? What happens? Dear DuckDB Developers, I have encountered an unexpected execution result and have prepared a reproducible case, which I’ve included below. I would greatly appreciate it if you could take a moment to review it. ### To Reproduce ### OS: MacOS ###...duckdb/duckdb · TheoristCoderOpen ↗recursive `UNNEST` misaligns a sibling `UNNEST` result### What happens? When a recursive `unnest` of a nested LIST is selected alongside a second `unnest` of a regular LIST, DuckDB appears to reuse or misalign values from the second result across the recursive output. In the reproduction below, three flattened values and three...duckdb/duckdb · Explorer-Dong1 repliesOpen ↗ManualVuln3 approx_top_k() Import State Accepts Zero-Count Entries, Causing Assertion Failure in Debug and Silent Result Corruption in Release### What happens? `ApproxTopKImportState` (`extension/core_functions/aggregate/holistic/approx_top_k.cpp` lines 478 to 548) validates the structural shape of an imported aggregate state: `value_entries[i].length > target.capacity` (line 516) guards against an over-sized values...duckdb/duckdb · ylwango613Open ↗WHERE above an aggregate combined with QUALIFY returns one row of NULLs instead of an empty result### What happens? A `QUALIFY` window filter on top of a subquery whose `WHERE` clause excludes the row produced by the aggregate returns **one row containing `NULL`** instead of an empty result. The `WHERE` clause is effectively not respected: the row that `WHERE` should remove...duckdb/duckdb · Fly-a-Kite1 repliesOpen ↗
Companies and products named
About this problem
Evidence
5 posts from 5 people in 1 place, about 1 a week over 26 days. Mostly on duckdb/duckdb. Tools named alongside: Docker, GitHub.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about DuckDB with no known issue, sharing the word "result". First post Sep 18, 2026, latest Oct 13, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other DuckDB problems
DuckDB upgrades break working setupsDuckDB users keep filing bugsTrouble with DuckDB columnTrouble with DuckDB overflowDuckDB error messages are crypticTrouble with DuckDB internalTrouble with DuckDB nullTrouble with DuckDB valuesTrouble with DuckDB castDuckDB runs out of memoryDuckDB costs outgrow the value it givesDuckDB permissions are confusing and error-prone
History
steady to fading
fading to steady
steady to fading
new to steady
Trouble with DuckDB result (3 posts)