Bug #82224 | Rows read via InnoDB FTS index are not accounte Handler% status counters | ||
---|---|---|---|
Submitted: | 14 Jul 2016 2:39 | Modified: | 14 Jul 2016 5:40 |
Reporter: | Marcos Albe (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S3 (Non-critical) |
Version: | 5.6, 5.6.31, 5.7.13 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[14 Jul 2016 2:39]
Marcos Albe
[14 Jul 2016 2:46]
Marcos Albe
Seems to be exclusive of InnoDB: msandbox@localhost (test) > alter table my_audit engine myisam; Query OK, 273 rows affected (0.03 sec) Records: 273 Duplicates: 0 Warnings: 0 msandbox@localhost (test) > flush status; select id from my_audit where MATCH(audited_changes) AGAINST('territory_id:|first_name:|last_name:|role_id:|active:' IN BOOLEAN MODE); show status like 'handler%'; Query OK, 0 rows affected (0.00 sec) +-----+ | id | +-----+ | 256 | | 258 | +-----+ 2 rows in set (0.01 sec) +----------------------------+-------+ | Variable_name | Value | +----------------------------+-------+ | Handler_commit | 0 | | Handler_delete | 0 | | Handler_discover | 0 | | Handler_external_lock | 2 | | Handler_mrr_init | 0 | | Handler_prepare | 0 | | Handler_read_first | 0 | | Handler_read_key | 0 | | Handler_read_last | 0 | | Handler_read_next | 3 | | Handler_read_prev | 0 | | Handler_read_rnd | 0 | | Handler_read_rnd_next | 0 | | Handler_rollback | 0 | | Handler_savepoint | 0 | | Handler_savepoint_rollback | 0 | | Handler_update | 0 | | Handler_write | 0 | +----------------------------+-------+
[14 Jul 2016 5:40]
MySQL Verification Team
Hello Marcos Albe, Thank you for the report. Observed this with 5.6.31 build. Thanks, Umesh