Bug #50218 | CTRL-C behavior faulty for mysql client on Windows | ||
---|---|---|---|
Submitted: | 11 Jan 2010 0:25 | Modified: | 11 Jan 2010 4:22 |
Reporter: | Roel Van de Paar | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
Version: | 5.1.42 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[11 Jan 2010 0:25]
Roel Van de Paar
[11 Jan 2010 0:30]
Roel Van de Paar
Regression of bug #17926 (also see bug #1989) 'SIGINT is handled in funny ways on windows, which could lead to problems when Control-C was pressed in the client during a long-running query. Now Control-C during a query aborts that query (by sending KILL to the server on a second connexion), while Control-C outside of a running query terminates the client.' Observed behavior is different, as per the above.
[11 Jan 2010 1:04]
Roel Van de Paar
Verifying as D2 (Dysfunction)
[11 Jan 2010 1:07]
Roel Van de Paar
For completeness, see bug #26892, bug #26243, bug #29497
[12 Jan 2010 2:25]
Vladislav Vaintroub
If I understand the issue correctly, it has nothing to do with the client. client sends kill and server in some circumstances kills the _future_ query, bnot the current query. Have seen this in Connector/Net too