MySQL Bugs: #60507: interrupting a running statement does not work when process id too high

Bug #60507	interrupting a running statement does not work when process id too high
Submitted:	17 Mar 2011 10:29	Modified:	18 Mar 2011 8:09
Reporter:	Daniel Seif	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.33	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
When a statement is running on a thread with a high id, the INTERRUPT command does not work.

Instead it returns 

 Action: INTERRUPT
Message: Error Code: 1094
         Unknown thread id: 817842872

How to repeat:
Execute a long-running query on a database with high process ids and click on the interrupt button.

To make it more clear: This is basically the same problem as in http://bugs.mysql.com/bug.php?id=60505

Not the process id of the server process is the problem, but
the thread id of the current connections in the database:

mysql> show full processlist\G

*************************** 1. row ***************************
     Id: 13705904350
   User: client
   Host: 127.0.0.1:51697
     db: mysql
Command: Sleep
   Time: 0
  State: 
   Info: NULL

....

The id is, what I'm talking about.

Duplicate of http://bugs.mysql.com/bug.php?id=60505

Hmpf.

This is not a duplicate, but a different error caused by the same mistake in the workbench code: thread ids in mysql can exceed the integer range, so please, please use bigints ...