DuckDB 2.0 is out, and Query Farm’s extensions now have their own extension repository. To install A5, Airport, or another of our DuckDB extensions, use INSTALL extension_name FROM query_farm.

The DuckDB team made this possible with 2.0’s support for custom extension repositories. We can sign and distribute our own builds, and DuckDB verifies them against our repository’s signing keys.

Add the Query Farm repository once, then install the extensions you need. Here’s the complete setup for A5:

SET allow_extension_repositories = 'allowed';


CREATE EXTENSION REPOSITORY IF NOT EXISTS query_farm
    WITH PREFIX 'https://duckdb-extensions.query.farm';


INSTALL a5 FROM query_farm;
LOAD a5 FROM query_farm;

Use LOAD a5 FROM query_farm in subsequent sessions. Replace a5 with another Query Farm extension’s name to install and load it. This change applies to DuckDB 2.0 and later; earlier DuckDB versions continue to use community.

We’re making this move because we support these extensions, and we need to control when fixes reach the people using them. Until now, a release in our source repository needed a separate pull request to duckdb/community-extensions before it could be distributed there. DuckDB’s maintainers review submissions and manage builds for many independent projects. That shared infrastructure has helped our extensions reach a lot of people.

The difficulty for us has been predicting when an update will become available. Some updates have waited over a weekend: our crypto compatibility update for DuckDB 1.5 opened on Friday, February 13, and merged on Monday, February 16, about 68 hours later. The DuckDB team has a whole ecosystem to look after. Meeting our customers’ release deadlines is our responsibility.

We examined these turnaround times in June. The updated analysis covers 1,988 merged PRs through September. In September alone, the median was 28 hours, while the slowest 10% took more than four days to merge. Those timings include CI and revisions by extension authors, ourselves included. They don’t isolate review delays or measure when binaries became available.

Monthly time to merge for 1,988 community-extension PRs, October 2025 through September 2026. The median ranges from about four to fifty hours; the 90th percentile ranges from nineteen to 128 hours. September’s median is 28 hours and its 90th percentile is 102 hours.
Time from opening to merge for all PRs merged to duckdb/community-extensions, October 2025–September 2026, grouped by merge month. Includes extension updates, documentation, and infrastructure changes. PR data · Monthly figures.

Our own repository lets us build, test, sign, and publish on a schedule we control. It also makes us responsible for operating that distribution infrastructure and resolving problems with it.

We’ve also created small stub extensions for the community repository to help people following older installation instructions. The A5 stub explains how to add our repository and install the extension. If you’ve already done that, it loads the Query Farm build. It doesn’t add a repository or download code on your behalf; choosing to trust our repository remains your decision.

We’re still committed to DuckDB and its community. Taking on distribution is how we can better support everyone using our extensions, whether they’re customers or working on their own projects.

Browse Query Farm’s DuckDB extensions and try one with the setup above. If you maintain a DuckDB extension and want details about running a repository or handling the transition, get in touch. We’re happy to share what we’ve learned.