Then you should update the DuckDB documentation, which currently states that for the DuckDB format AIO shall be implemented in the future, not in the current release.
The release announcement links to several pages from a few months ago, like:
Today I see in the release announcement "DuckDB 2.0 introduces asynchronous I/O for reading Parquet and CSV files, as well as DuckDB's native storage format. "
So it seems that the announcement has been updated, because I am pretty sure that yesterday the ending of this sentence did not exist.
> Other formats, such as JSON files and DuckDB's native database format, use synchronous I/O.
For the future:
> Most of its benefit comes from accessing remote data, but cold local reads can also benefit, albeit less. Next, we plan to add async reads for JSON and DuckDB-native files, as these are the two other formats most relevant to DuckDB core. Formats that live in out-of-tree extensions are not on the roadmap yet.
Sorry, does this mean that their own duckdb format already supports async or doesn't?