Thanks, updated as discussed!
Sergey Petrunia <sergefp@stripped> writes (abridged):
>> Bug#28141: Control C on query waiting on lock causes ERROR 1053 (server
>> If a thread is killed in the server, we throw "shutdown" only if one is
> actually in
>> progress; otherwise, we throw "query interrupted".
>> Control-C in the mysql command-line client is "incremental" now.
>> First Control-C sends KILL QUERY (when connected to 5.0+ server, otherwise, see
>> Next Control-C sends KILL CONNECTION
>> Next Control-C aborts client.
>> As the first two steps only pertain to an existing query,
>> Control-C will abort the client right away if no query is running.
>> client will give more detailed/consistent feedback on Control-C now.
> This will issue "KILL CONNECTION" command. According to
> it is not supported in 4.1 server (and this code is supposed to work with it
> Why is the change made in rr_quick() and not also in rr_index() and
> rr_sequential()? The latter two don't seem to have this new effect and we
> would really prefer them to work as closely as possible because the choice
> between these functions is cost-based.
Tatjana A. Nurnberg, Bugs Bunny * MySQL AB, http://www.mysql.de/ * EST
IRC: Azundris * Skype: azundris * MySQL-SIP: 4550 * eMail: azundris@stripped
.de: Firmensitz: MySQL GmbH, Radlkoferstr. 2, D-81373 Muenchen
Geschaeftsfuehrer: Hans von Bell, Kaj Arnoe - HRB Muenchen 162140