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
{{ message }}
Repository navigation
Commit bd95a6b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(scenario): cancel in-flight statements on Ctrl-C and fit names by bytes
Running every scenario through a worker pool and absorbing repeat
interrupts made long statements uninterruptible, even at concurrency 1.
Concurrency 1, --local replay and capture now run on the main thread again,
so Ctrl-C reaches the driver as before. A SIGINT handler records the stop
and cancels in-flight statements through the new adapter
interrupt_connection (DuckDB interrupt, Postgres cancel_safe); without it a
DuckDB query interrupted only by the signal kept running in the background
and blocked cleanup. Concurrent runs cancel queued scenarios, cancel or
close in-flight worker connections, wait for teardown, and sweep started
scenarios on a valid or fresh connection. A second Ctrl-C prints one notice
and exits at once; daemon workers never block exit, and the next run of
the same scenarios drops what was left behind.
Identifier fitting now measures UTF-8 bytes and cuts on character
boundaries, so non-ASCII names fit Postgres's 63-byte limit.
0 commit comments