Ubuntu 12.04

same in
====
Installed: 5.5.34+maria-1~precise
Candidate: 5.5.34+maria-1~precise
Version table:

• • • 5.5.34+maria-1~precise 0
      1000 http://mariadb.cu.be//repo/5.5/ubuntu/ precise/main amd64 Packages
      100 /var/lib/dpkg/status
      ====

Works all right for me:

MariaDB [db]> insert into t1 select * from t1;
Query OK, 2097152 rows affected (22.14 sec)
Records: 2097152 Duplicates: 0 Warnings: 0

MariaDB [db]> select * from t1;
^CCtrl-C – query killed. Continuing normally.
ERROR 1317 (70100): Query execution was interrupted
MariaDB [db]>

elenst@ubuntu12-04:~$ which mysql
/usr/bin/mysql
elenst@ubuntu12-04:~$ dpkg -S /usr/bin/mysql
mariadb-client-core-5.5: /usr/bin/mysql

elenst@ubuntu12-04:~$ dpkg -l mariadb-client-core-5.5
...
ii mariadb-client-core-5.5 5.5.34+maria-1~precise MariaDB database core client binaries

Please attach your cnf files and provide the table definition (show create table), the number of rows in the table and the real query, I will give it another try with the additional data.
Thanks.

attaching configs ( /etc/mysql )

some more info:
1)

same effect if I open another terminal and run

kill -s INT 24350
(24350 is PID of mysql client)

during query execution: query not terminated, next query terminated.

so it's not related to keyboard, GUI, terminals etc. something with signal handler.

2)
issue is reproducible if ran as root unix user and non-root unix user.
issue is reproducible if ran as root mysql user and non-root mysql user.

3) issue persists after reboot.

I think I figured the missing point.

There are two important stages of executing a query, easily distinguishable on the client side:
1) the query is being processed by the server, nothing is happening in the client, the query is kind of "hanging";
2) the server is returning result set, the client starts printing it.

When you are saying that Ctrl-C does not work, do you mean the second stage, when the result set rows already started appearing in the client?

> 2) the server is returning result set, the client starts printing it.
exactly, stage (2)

The difference between MariaDB and MySQL behavior is visible on the following conditions:

• the client is connected to the server through the socket;
• the interruption occurs when the client has already started producing the result set.

MySQL client aborts the output immediately, saying

^C| 42 |
Ctrl-C – sending "KILL QUERY 52" to server ...
Ctrl-C – query aborted.
------
262144 rows in set (2.10 sec)

The next query fails with
mysql> select * from t1;
ERROR 1317 (70100): Query execution was interrupted

The next query works as usual.

MariaDB client does not do anything until the query is finished:

------
262144 rows in set (2.09 sec)

The next query fails with
MariaDB [test]> select * from t1;
ERROR 1317 (70100): Query execution was interrupted

The next query works as usual.

MySQL behavior is better in comparison, I would also want to be able to interrupt the undesirable output.
It would be even better if the next query didn't inherit the interruption, but maybe it's too difficult to do.

http://bazaar.launchpad.net/~maria-captains/maria/5.5/revision/3999

main issue seems fixed in 5.5.35+maria-1~precise
however seems there is still a problem.

after query terminated with Ctrl-C, next query is failed.

|    2545589 |

|    2545590 |

|    2545592 |

|    2545593 |

|    2545595 ||    2545595 |

Ctrl-C -- query killed. Continuing normally.

^C

+------------+

383850 rows in set (0.27 sec)

MariaDB [xxx]> select service_id from services;

ERROR 1317 (70100): Query execution was interrupted