Tags: duckdb/duckdb
Tags
Fail fast extensions (#20605) Changes so that INSTALL also performs signature checks (according to database configuration). This is somewhat redundant, BUT avoids cases where one might successful install an extension that can't be then loaded. Logic is as follows: 1. files ending in ".duckdb_extension" can only be created in the INSTALL path 2. when moving, either ending ".duckdb_extension" is present both in source and target, OR it should not be present on target 3. on install, we first verify signature of the buffer, then copy data to "name.tmp-UUID.duckdb_extension", then move it to "name.duckdb_extension". Note that this is legal with both 1 & 2, and makes so that all files (written by duckdb) that ends in '.duckdb_extension' are signature checked 4. on load, we load only from files eneding in ".duckdb_extension" Basically there are 3 families of files: * **A**: those ending in '.duckdb_extension' * **B**. the other files **B** can be created and moved into freely **A** can only be created during install path (since it's the only place where we pass the flag, and we will only create **B**) **A** can only be moved into from other **A** files, while **A** can be moved to a **B** **A** is the only type of file we would load from
Bump iceberg (#19001) Includes duckdb/duckdb-iceberg#465 and duckdb/duckdb-iceberg#466
Backport @szarnyasg's PR 16999 (#17013) Thanks @szarnyasg!
PreviousNext