Jelte Fennema-Nio
Jelte Fennema-Nio
It sounds like maybe we should be swapping out the postgres signal handler for SIGINT and SIGTERM for one that calls `db->Interrupt()`.
Leaving this in the 0.2.0 milestone. Hopefully by the time that 0.2.0 gets released DuckDB 1.2.0 will be released as well and we can benefit from https://github.com/duckdb/duckdb/pull/14034 If that turns...
Should get fixed automatically by #548
This is fixed now by #548
I'm pretty sure this is caused by to #93, but good to have an easily reproducable case.
Closing this, to keep the discussion focused in #105
Basically all clients use the extended query protocol. So we should definitely fix this.
Moved this to 0.1.0 milestone since this should be very easy to address in #217 by setting `disabled_filesystems = 'LocalFilesystem'`
> those changes aren't on main, but it is something to think about going forward. For clarity, @Y-- and me are working together for a POC that can be used...
Can you fix the merge conflicts with master? Then it should be much easier to try out. Also when compiling this PR locally I see a bunch of warnings.