Skip to content

CLI cannot load unsigned extension after open an existing db file (with -unsigned flag) #5022

@wangxiaoying

Description

@wangxiaoying

What happens?

The following error raises when start the client with on an existing db file.

Error: IO Error: Extension "build/release/extension/postgres_scanner/postgres_scanner.duckdb_extension" could not be loaded because its signature is either missing or invalid and unsigned extensions are disabled by configuration (allow_unsigned_extensions)

In-memory mode and opening a new db file will not raise this issue.

To Reproduce

Can use postgres extension to reproduce the issue. After building duckdb and postgres extension:

# Error if `test.db` exists, success if not
./duckdb/build/release/duckdb -unsigned test.db
D LOAD 'build/release/extension/postgres_scanner/postgres_scanner.duckdb_extension';

# No error
./duckdb/build/release/duckdb -unsigned
D LOAD 'build/release/extension/postgres_scanner/postgres_scanner.duckdb_extension';

OS:

OSX (m1)

DuckDB Version:

master branch (c2ca23e)

DuckDB Client:

CLI

Full Name:

Xiaoying Wang

Affiliation:

Simon Fraser University

Have you tried this on the latest master branch?

  • I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

  • I agree

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions