Bug #46203 | WHERE clause on Information_schema.processlist makes an unpredictable filter | ||
---|---|---|---|
Submitted: | 15 Jul 2009 13:01 | Modified: | 16 Jul 2009 18:41 |
Reporter: | Kristofer Pettersson | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1, azalea | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 Jul 2009 13:01]
Kristofer Pettersson
[15 Jul 2009 13:18]
Peter Gulutzan
It does look like a bug that a search for '%proceslist%' [sic] finds something that has 'processlist' in it. But for the rest: Isn't this expectable behaviour if we don't lock the PROCESSLIST table, or make a frozen copy?
[15 Jul 2009 13:22]
Peter Gulutzan
Bah, I must amend that last remark. It finds 'proceslist' because it's in "select id from information_schema.processlist where info like '%proceslist%' limit 1;". So isn't that expectable too?
[16 Jul 2009 6:55]
Sveta Smirnova
Thank you for the report. Verified as described. Really word "processlist" is not related: it can be anything: select id from information_schema.processlist where info like '%anything%'; id 2
[16 Jul 2009 16:06]
Peter Gulutzan
Perhaps this would be clearer if one puts INFO in the select list. For example: mysql> select id,info from information_schema.processlist -> where info like '%anything%'\G *************************** 1. row *************************** id: 1 info: select id,info from information_schema.processlist where info like '%anything%' 1 row in set (0.01 sec) Who is ID=1? Me! I'm looking at my own query, which contains 'anything' because I'm searching for 'anything'. Of course I will always find a string that's in the text of my own query.
[16 Jul 2009 18:41]
Kristofer Pettersson
Peter: My mistake. This is of course expected behaviour and not a bug.