Skip to content

Upgrade bundled DuckDB to 1.5.6 - #13

Merged
skuirrels merged 1 commit into
mainfrom
feature/duckdb-1.5.6
Oct 6, 2026
Merged

skuirrels merged 1 commit into
mainfrom
feature/duckdb-1.5.6

Conversation

@skuirrels

Copy link
Copy Markdown
Owner

Summary

  • Upgrades the bundled native DuckDB libraries from v1.5.5 to v1.5.6.
  • Updates the benchmark engine guard, package smoke test and fork READMEs to v1.5.6.
  • The v1.5.6 C API exports the same 547 symbols, enum values and struct layouts as v1.5.4 and v1.5.5; no managed changes are required.

Validation

  • dotnet test DuckDB.NET.Test against DuckDB v1.5.6: 7,030 passed, 0 failed.
  • Release-mode fork packages built, packed and validated with scripts/validate-fork-packages.sh; smoke tests passed on .NET 8 and .NET 10 with v1.5.6.

Benchmarks: DuckDB v1.5.4 vs v1.5.6

Same managed build (this branch) run against each native library on Apple Silicon, .NET 10, in-process BenchmarkDotNet job.

  • Geomean across 17 re-run benchmarks: best-case -0.39% (performance-neutral).
  • TPC-H Q1/Q6/Q12/Q14, analytical queries, result materialisation and prepared commands are within ±2.5% best-case.
  • ListAppenderBenchmark is bimodal on every DuckDB version (~150 ms or ~220–270 ms per process). Best-case times are equal (130.1 vs 130.1 ms, 148.7 vs 150.0 ms); 1.5.6 hit the slow mode more often (8/14 vs 4/14 processes), which is not statistically significant and has no matching appender change in the v1.5.6 changelog.

Bump DuckDbNativeVersion to 1.5.6 and update the benchmark engine guard,
package smoke test and fork READMEs to match. The 1.5.6 C API exports the
same symbols, enum values and struct layouts as 1.5.5.
@skuirrels
skuirrels merged commit 6d5466f into main Oct 6, 2026
1 of 2 checks passed

This branch was successfully deployed

1 active deployment
internal — 883276f1 Deployed Oct 6, 2026 by skuirrels via Authorize #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant