Bug #73839 | InnoDB: unable to purge a record | ||
---|---|---|---|
Submitted: | 8 Sep 2014 15:57 | Modified: | 18 Dec 2014 9:01 |
Reporter: | Jacky Shu | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.6.19 | OS: | Linux (CentOS 2.6.32-279.5.1.el6.x86_64) |
Assigned to: | CPU Architecture: | Any |
[8 Sep 2014 15:57]
Jacky Shu
[8 Sep 2014 16:13]
MySQL Verification Team
related: http://bugs.mysql.com/bug.php?id=73767 ("Unable to purge a record" with ibuf and varchar fields containing spaces)
[9 Sep 2014 10:20]
MySQL Verification Team
Thank you for the report. This is most likely duplicate of Bug #73767. Could you please upload complete error log(make it private), any relevant info which you think triggering this issue? Thanks, Umesh
[12 Sep 2014 7:53]
MySQL Verification Team
Thank you for providing the requested details. Could you please also provide the table structure of index id 38819? You could get the db/table details from information_schma, with something like using below query(not tested): select A.INDEX_ID, B.NAME DB_TABLE from information_schema.INNODB_SYS_INDEXES A,information_schema.INNODB_SYS_TABLES B WHERE A.TABLE_ID=B.TABLE_ID AND A.INDEX_ID=38819; See, on how to get table name based on index id etc http://dev.mysql.com/doc/refman/5.6/en/innodb-sys-indexes-table.html
[12 Sep 2014 7:56]
MySQL Verification Team
Also, pls keep reading related Bug #73767 Looks like others also affected and for more details on this from Dev's..
[15 Sep 2014 15:28]
Jacky Shu
Compared the data of table with index 38819 between master (5.1) and slave (5.6), didn't find data drift.
[18 Dec 2014 9:03]
MySQL Verification Team
Marking as duplicate of Bug #73767