[myrrc]

• Support building and linking vortex-duckdb from Windows.
• Run vortex-sqllogictest and vortex-duckdb tests in CI for Windows-x64.
• Use url.to_file_path() instead of url.path() which produces a leading slash (/C:/...) on Windows.
• Remove -fno-gnu-unique since it's obsolete for duckdb 2.0's C++17.
• Fix sqllogic tests error messages to be working for Windows
• Replace back slashes with forward slashes in sqllogic test runner as duckdb produces paths with forward slashes in output.
• Fix spatial tests concurrently loading spatial extension, run tests sequentially

[codspeed]

Merging this PR will regress 1 benchmark

3 warnings

⚠️ Walltime results may be unreliable

Some benchmarks used the Walltime instrument outside CodSpeed Macro Runners, which can make the results inconsistent.

Learn more about Macro Runners

See affected benchmarks

⚠️ 1 benchmark is dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ Base and head ran on different runner types

Some benchmarks with significant performance changes were compared across different runner types, so the changes might not come from the code. Run base and head on the same runner type, or use CodSpeed Macro Runners for more stable results.

Learn more about Macro Runners

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
❌ 1 regressed benchmark
✅ 2201 untouched benchmarks
⏩ 370 skipped benchmarks¹
🗄️ 30 archived benchmarks run²

Warning

Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
❌	Walltime	lt_i64_nullable_avx2	8.3 µs	9.5 µs	-12.21%
⚡	CPU Simulation	test_scan_scalar_at[int_str]	1,015.3 µs	884.2 µs	+14.82%
⚡	CPU Simulation	test_repeated_scan_scalar_at[int_str]	386.8 µs	339.4 µs	+13.97%

Tip

Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.

---

_{Comparing myrrc/duckdb-win (beda46c) with develop (9c12160)}

Footnotes

1. 370 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. 30 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩

[robert3005]

We should have windows dedicated sql logic tests