InnoDB:找到重复的索引-这很不好吗? [英] InnoDB: duplicate indixes found - is this very bad?

问题描述

最近，我们的Magento商店变得非常慢.我们真的不知道为什么.

recently our Magento store has become extremely slow. We dont really know why.

直到今天，当我进行数据库检查时，我注意到 900多个索引是相同的重复，即存在两个相同的索引.

Just today I noticed when I did a database check that more than 900 indexes are identical duplicates, i.e. two exist.

我的问题:这会影响效果吗? +如果可以，我将如何删除两者之一.

My question is: hoe can this impact performance? + if it does, how would I go about deleting one of the two.

谢谢，肖恩

示例

遇到的问题索引van de tabel mag_eav_form_fieldset_label 索引IDX_MAG_EAV_FORM_FIELDSET_LABEL_STORE_ID和IDX_GALI_EAV_FORM_FIELDSET_LABEL_STORE_ID看起来相同，可能两者均可删除. 索引IDX_MAG_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID和IDX_GALI_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID看起来相同，可能两者均可删除. 索引IDX_MAG_EAV_FORM_FIELDSET_LABEL_STORE_ID和IDX_EAV_FORM_FIELDSET_LABEL_STORE_ID看起来相同，可能两者之一都可以删除. 索引IDX_MAG_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID和IDX_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID看起来相同，可能两者均可删除. 遇到问题索引van de tabel mag_eav_form_type 索引IDX_MAG_EAV_FORM_TYPE_STORE_ID和IDX_GALI_EAV_FORM_TYPE_STORE_ID看起来相同，可能两者均可删除. 索引IDX_MAG_EAV_FORM_TYPE_STORE_ID和IDX_EAV_FORM_TYPE_STORE_ID看起来相同，可能两者均可删除. 以及UNQ_GALI_EAV_FORM_TYPE_CODE_THEME_STORE_ID的索引UNQ_MAG_EAV_FORM_TYPE_CODE_THEME_STORE_ID看起来相同，可能两者均可删除. 以及UNQ_EAV_FORM_TYPE_CODE_THEME_STORE_ID的索引UNQ_MAG_EAV_FORM_TYPE_CODE_THEME_STORE_ID看起来相同，可能两者之一都可以删除. 遇到问题索引van de tabel mag_eav_form_type_entity 索引IDX_MAG_EAV_FORM_TYPE_ENTITY_ENTITY_TYPE_ID和IDX_GALI_EAV_FORM_TYPE_ENTITY_ENTITY_TYPE_ID的外观相同，可能两者均可删除.

Problemen met The indexes van de tabel mag_eav_form_fieldset_label The indexes IDX_MAG_EAV_FORM_FIELDSET_LABEL_STORE_ID en IDX_GALI_EAV_FORM_FIELDSET_LABEL_STORE_ID look the same, possibly one of both can be deleted. The indexes IDX_MAG_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID en IDX_GALI_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID look the same, possibly one of both can be deleted. The indexes IDX_MAG_EAV_FORM_FIELDSET_LABEL_STORE_ID en IDX_EAV_FORM_FIELDSET_LABEL_STORE_ID look the same, possibly one of both can be deleted. The indexes IDX_MAG_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID en IDX_EAV_FORM_FIELDSET_LABEL_FIELDSET_ID look the same, possibly one of both can be deleted. Problemen met The indexes van de tabel mag_eav_form_type The indexes IDX_MAG_EAV_FORM_TYPE_STORE_ID en IDX_GALI_EAV_FORM_TYPE_STORE_ID look the same, possibly one of both can be deleted. The indexes IDX_MAG_EAV_FORM_TYPE_STORE_ID en IDX_EAV_FORM_TYPE_STORE_ID look the same, possibly one of both can be deleted. The indexes UNQ_MAG_EAV_FORM_TYPE_CODE_THEME_STORE_ID en UNQ_GALI_EAV_FORM_TYPE_CODE_THEME_STORE_ID look the same, possibly one of both can be deleted. The indexes UNQ_MAG_EAV_FORM_TYPE_CODE_THEME_STORE_ID en UNQ_EAV_FORM_TYPE_CODE_THEME_STORE_ID look the same, possibly one of both can be deleted. Problemen met The indexes van de tabel mag_eav_form_type_entity The indexes IDX_MAG_EAV_FORM_TYPE_ENTITY_ENTITY_TYPE_ID en IDX_GALI_EAV_FORM_TYPE_ENTITY_ENTITY_TYPE_ID look the same, possibly one of both can be deleted.

等

推荐答案

如果要安全删除它们，建议您在Percona工具箱中使用pt-duplicate-key-checker.它将自动为您生成放置索引SQL.

if you want to delete them safely, i suggest you to use pt-duplicate-key-checker in Percona toolkit. It will generate the drop index SQL for you automatically.

太多索引的确会降低性能，尤其是对于更新和插入. 您最好删除那些无用的索引.

Too many indexes do decrease performance, especially for update and insert. You would better drop those useless indexes.

这篇关于InnoDB:找到重复的索引-这很不好吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！