You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I install the extension in the private network, it hangs for a long time. If I try to use pg_terminate_backend to terminate the execution, It still fails to be canceled.
To Reproduce
OS:
Linux
pg_duckdb Version (if built from source use commit hash):
Okay, so looking at the report, I think the main issue here is that our internal DuckDBQueryOrThrow function does not handle cancel requests (at all). That's indeed something we should fix. I don't consider this super urgent, since we normally don't use DuckDBQueryOrThrow for queries that we expect to take a long time.
An easy way to reproduce this is by using duckdb.raw_query() with some long running query and seeing that pressing Ctrl+C has no effect. For example the following query takes ~18 seconds on my machine to complete and I have no way of canceling it in the middle:
selectduckdb.raw_query($$ selectcount(*) from generate_series(100000000000) $$);
JelteF
changed the title
duckdb.install_extension could not be terminated
DuckDBQueryOrThrow does not respond to cancel requests
Feb 28, 2025
What happens?
When I install the extension in the private network, it hangs for a long time. If I try to use pg_terminate_backend to terminate the execution, It still fails to be canceled.
To Reproduce
OS:
Linux
pg_duckdb Version (if built from source use commit hash):
66cb6e6
Postgres Version (if built from source use commit hash):
16.8
Hardware:
No response
Full Name:
Cobolbaby
Affiliation:
Inventec
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have not tested with any build
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: