Bug #86317 | reorganize partition set information_schema.PARTITIONS.table_rows to 0 | ||
---|---|---|---|
Submitted: | 15 May 2017 3:30 | Modified: | 20 May 2017 3:42 |
Reporter: | Rob Burrowes | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | Ver 14.14 Distrib 5.7.17 | OS: | FreeBSD (11.0-RELEASE-p2) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
Tags: | partition, reorganize |
[15 May 2017 3:30]
Rob Burrowes
[20 May 2017 3:42]
MySQL Verification Team
Hi Rob, I don't see this as a bug. The statistics for that table is just not "calculated" yet, it should show after a while. The same thing was with 5.6 (the old values are no more correct then the zeroes you are getting with 5.7). Have you tried running analyze after reorganize? for e.g. ALTER TABLE `wikk`.`log_summary` ANALYZE PARTITION p2009_04; ALTER TABLE `wikk`.`log_summary` ANALYZE PARTITION p2009_05; and after the analyze you check the statistics: SELECT PARTITION_NAME, TABLE_ROWS, PARTITION_DESCRIPTION FROM information_schema.PARTITIONS WHERE TABLE_SCHEMA = 'wikk' AND TABLE_NAME = 'log_summary'; all best Bogdan