duckdb / duckdb

DuckDB is an analytical in-process SQL database management system
http://www.duckdb.org
MIT License
23.88k stars 1.9k forks source link

`exists` Keyword not Working on AArch64 Linux #14389

Closed redraiment closed 2 days ago

redraiment commented 2 weeks ago

What happens?

I downloaded duckdb_cli-linux-aarch64.zip from https://github.com/duckdb/duckdb/releases/tag/v1.1.2, and then executed the following SQL query multiple times:

select count(*)
from range(1000, 3000) as a(v), range(1000, 3000) as b(v)
where exists (select a.v != b.v);

Each time the query resulted in different outcomes, as shown in the screenshots below:

image

I have only encountered this issue on the AArch64 version of the Linux system; testing on the AArch64 version of macOS did not reveal any problems.

To Reproduce

select count(*)
from range(1000, 3000) as a(v), range(1000, 3000) as b(v)
where exists (select a.v != b.v);

OS:

AArch64 Debian GNU/Linux 12 (bookworm)

DuckDB Version:

1.1.2

DuckDB Client:

duckdb_cli

Hardware:

No response

Full Name:

Zepeng, Zhang

Affiliation:

Yinfn.com

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?

Yes

Did you include all code required to reproduce the issue?

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

redraiment commented 2 weeks ago

Add an additional piece of information:

I installed version v1.1.2 of duckdb on an AArch64 Android device through Termux with the command pkg install duckdb, and it returned the correct results.

Maybe only the one on Github Releases page with the issue.

szarnyasg commented 2 weeks ago

Thanks, I could reproduce with Ubuntu 24.04 running a Docker container on macOS (Apple Silicon M2).

szarnyasg commented 3 days ago

Hi @redraiment, a status report: we have found the cause of this issue and plan to fix it in DuckDB v1.1.3, scheduled for next week: https://duckdb.org/docs/dev/release_calendar.html