A really brutal workaround: DuckDB will respond to signals... could we temporarily install a signal handler that prevents SIGINT from killing the server, but lets it percolate through to DuckDB to interrupt? That feels fragile and complex, might be easier to learn how to patch DuckDB
SQLite's Python interface supports interrupting long-running queries. DuckDB's C API supports this, too, but it has not yet been exposed to the Python API. See https://github.com/duckdb/duckdb/issues/5938 and https://github.com/duckdb/duckdb/pull/3749
A really brutal workaround: DuckDB will respond to signals... could we temporarily install a signal handler that prevents SIGINT from killing the server, but lets it percolate through to DuckDB to interrupt? That feels fragile and complex, might be easier to learn how to patch DuckDB