accessing information_schema.partitions causes plans to change

Bug #1192354 reported by Sergei Glushchenko on 2013-06-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Percona Server moved to
Fix Released
Sergei Glushchenko
Fix Released
Sergei Glushchenko
Fix Released
Sergei Glushchenko

Bug Description

This is to track upstream bug
All credits to Justin Swanhart.

[9 May 4:22] Justin Swanhart
MySQL 5.6 supposed supports persistent statistics.

I enabled persistent statistics in my "my.cnf" and I also enabled them with the ALTER TABLE statement. However, in my testing, a read-only workload quickly resets the statistics as evidenced by query plans changes which result in severe performance loss.

In my testing, the first few batches of test queries will execute in 20 seconds or less with the data in the buffer pool, but then a batch of queries will start taking 80 seconds or more. An examination of the EXPLAIN plan on one of the queries in the batch shows a query plan change.

Reproduction steps are described in upstream bug report.

Related branches

tags: added: upstream

In order to set triage, what is the reason for copying a MySQL bug to Percona Server bug db?

Found it.

Sergei -

Please submit the bugfixes to the upstream bug report.

Upstream fix in 5.5.34.

Percona now uses JIRA for bug reports so this bug report is migrated to:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.