Skip to main content

Module extension_name

Module extension_name 

Source
Expand description

Extension name validation per DuckDB community extension rules.

An extension name must match ^[a-z][a-z0-9_]*$ — a lowercase letter followed by lowercase letters, digits and underscores.

§Why no hyphens

The name is not just a label. The community build names the binary <name>.duckdb_extension, and DuckDB’s loader (TryInitialLoad and LoadExternalExtension in src/main/extension/extension_load.cpp, v1.5.5) takes the file’s base name, lowercases it, and looks up the entry point <base name>_init_c_api in the library. A hyphen would have to appear in that C symbol, which neither C nor Rust can define — so a hyphenated extension can never load, and the scaffold would generate entry_point!(my-ext_init_c_api, …), which does not even compile. None of the 395 published community extensions uses a hyphen.

§Names that are taken

A well-formed name may still be unusable for a community extension. validate_community_extension_name also refuses:

  • DUCKDB_EXTENSION_ALIASES: DuckDB rewrites these to another extension’s name before INSTALL and LOAD (ExtensionHelper::ApplyExtensionAlias), so INSTALL s3 FROM community downloads httpfs — an extension named s3 can never be installed or loaded by its name;
  • DUCKDB_CORE_EXTENSION_NAMES: the community-extensions FAQ says “if a core DuckDB extension of the same name exists or is created, the community extension of the same name has to be renamed”.

Sources, read 2026-10-30: src/main/extension/extension_alias.cpp, internal_extensions[] in src/main/extension/extension_helper.cpp and AUTOLOADABLE_EXTENSIONS in src/include/duckdb/main/extension_entries.hpp at DuckDB v1.4.4, v1.5.6 and v2.0.0 (main had the same aliases), and the core-extension table of docs/2.0/core_extensions/overview.md in duckdb/duckdb-web. scripts/check-extension-names.py fetches them again in CI and fails when they and these lists disagree. None of the 395 community extensions in duckdb/community-extensions (845779e) has a name listed here.

Uniqueness among community extensions is not checked: that is the author’s to look up (extensions/ in duckdb/community-extensions).

§Reference

https://duckdb.org/community_extensions/development, https://duckdb.org/community_extensions/faq

Constants§

DUCKDB_CORE_EXTENSION_NAMES
The names of DuckDB’s core extensions, current and since DuckDB v1.4.4, which a community extension may not take (the community-extensions FAQ: it “has to be renamed”).
DUCKDB_EXTENSION_ALIASES
DuckDB’s built-in extension aliases, as (alias, extension).
DUCKDB_RESERVED_EXTENSION_NAMES
Every name a community extension may not take: the aliases and the core extensions. Sorted.

Functions§

validate_community_extension_name
Validates a name for a community extension.
validate_extension_name
Validates the form of a DuckDB extension name.