Long-running operations can block the client unintentionally (e.g., a query where millions of results are returned and LIMIT was forgotten). CTRL+C in this case would be the natural way of aborting this. Right now, CTRL+C kills the client, without a warning or a clean exit. If no command is running, CTRL+C already behaves well (exist on empty prompt, clearing prompt if non-empty); this should be kept.
Long-running operations can block the client unintentionally (e.g., a query where millions of results are returned and LIMIT was forgotten). CTRL+C in this case would be the natural way of aborting this. Right now, CTRL+C kills the client, without a warning or a clean exit. If no command is running, CTRL+C already behaves well (exist on empty prompt, clearing prompt if non-empty); this should be kept.