search

zvibo / common-schema

Automatically exported from code.google.com/p/common-schema
0 stars 0 forks source link

Looking for innodb_index_stats in the wrong schema in mysql 5.6 #60

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Which version of common_schema are you using? (specify
revision+distribution)

2.2

Which component is failing? (specify the view, function, etc.)

innodb_index_stats

What is the expected output? What do you see instead?

mysql> select * from common_schema.innodb_index_stats;
ERROR 1109 (42S02): Unknown table 'innodb_index_stats' in information_schema

Can you provide with sample data?
N/A

(As of version 1.1), please provide output of
SELECT * FROM common_schema.status

                       project_name: common_schema
                            version: 2.2
                           revision: 523
                       install_time: 2014-05-21 11:00:47
                    install_success: 1
          base_components_installed: 1
 innodb_plugin_components_installed: 1
percona_server_components_installed: 0
              install_mysql_version: 5.6.16-64.2-56-log
                   install_sql_mode: NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION

Please provide any additional information below.

I recently upgraded from Percona server 5.5 to 5.6, and re-installed 
common_schema.

common_schema is expecting innodb_index_stats to be in information_schema, but 
it appears to have moved to the mysql schema instead.

Original issue reported on code.google.com by ike.wal...@flite.com on 21 May 2014 at 5:25

GoogleCodeExporter commented 8 years ago 
For context:
Percona Server has a matrix of features per-version.

Innodb-index-stats has been "Replaced by the upstream implementation"
http://www.percona.com/doc/percona-server/5.6/ps-versions-comparison.html#n-15

Original comment by toc...@gmail.com on 22 May 2014 at 2:24

GoogleCodeExporter commented 8 years ago 
So Percona Server 5.6 puts this table in the mysql schema? Not a problem, 
actually. Will fix

Original comment by shlomi.n...@gmail.com on 22 May 2014 at 4:22

GoogleCodeExporter commented 8 years ago 
Correct (and that this also works for MySQL 5.6 if there are common_schema 
features you have previously had to disable).

Original comment by toc...@gmail.com on 22 May 2014 at 4:51

GoogleCodeExporter commented 8 years ago 
This is not the same table and not the same table definition. I'll need to 
investigate the new 5.6 implementation.

Original comment by shlomi.n...@gmail.com on 27 May 2014 at 12:47