<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Duplicate indexes and redundant indexes</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/</link>
	<description>Everything about MySQL Performance</description>
	<pubDate>Tue, 02 Dec 2008 14:37:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Finding out largest tables on MySQL Server &#171; Purab&#8217;s Blog</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-344251</link>
		<dc:creator>Finding out largest tables on MySQL Server &#171; Purab&#8217;s Blog</dc:creator>
		<pubDate>Wed, 13 Aug 2008 07:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-344251</guid>
		<description>[...] to data size often indicates there is a lot of indexes (so it is well possible there are some duplicates, redundant or simply unused indexes among them) or may be there is long primary key with Innodb tables. Of [...]</description>
		<content:encoded><![CDATA[<p>[...] to data size often indicates there is a lot of indexes (so it is well possible there are some duplicates, redundant or simply unused indexes among them) or may be there is long primary key with Innodb tables. Of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How to find duplicate and redundant indexes in MySQL at Xaprb</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-338520</link>
		<dc:creator>How to find duplicate and redundant indexes in MySQL at Xaprb</dc:creator>
		<pubDate>Fri, 01 Aug 2008 12:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-338520</guid>
		<description>[...] Zaitsev over at the excellent MySQL Performance Blog recently wrote an article on duplicated and redundant indexes &#8212; any indexes which cover exactly the same columns as another index, or cover a leftmost [...]</description>
		<content:encoded><![CDATA[<p>[...] Zaitsev over at the excellent MySQL Performance Blog recently wrote an article on duplicated and redundant indexes &#8212; any indexes which cover exactly the same columns as another index, or cover a leftmost [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-260643</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 31 Mar 2008 18:49:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-260643</guid>
		<description>Vaibogam,

This will catch indexes (A,B) and (A,C) as duplicate would not it ? 
It would be simple if indexes would be single column only :)</description>
		<content:encoded><![CDATA[<p>Vaibogam,</p>
<p>This will catch indexes (A,B) and (A,C) as duplicate would not it ?<br />
It would be simple if indexes would be single column only <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaibogam S</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-260480</link>
		<dc:creator>Vaibogam S</dc:creator>
		<pubDate>Mon, 31 Mar 2008 15:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-260480</guid>
		<description>A simple way to find out duplicate indexes in 5.0.x

SELECT * FROM information_schema.statistics WHERE table_schema = ‘?’ GROUP BY table_schema, table_name, column_name HAVING count(column_name) &#62; 1;

It would be better to include 'index_type' in GROUP BY clause to more accurate answer.

In the above query bind the ‘database name’ parameter.

-Bog</description>
		<content:encoded><![CDATA[<p>A simple way to find out duplicate indexes in 5.0.x</p>
<p>SELECT * FROM information_schema.statistics WHERE table_schema = ‘?’ GROUP BY table_schema, table_name, column_name HAVING count(column_name) &gt; 1;</p>
<p>It would be better to include &#8216;index_type&#8217; in GROUP BY clause to more accurate answer.</p>
<p>In the above query bind the ‘database name’ parameter.</p>
<p>-Bog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hitta indexdubletter</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-242037</link>
		<dc:creator>Hitta indexdubletter</dc:creator>
		<pubDate>Wed, 13 Feb 2008 07:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-242037</guid>
		<description>[...] läste en artikel på mysqlpeformanceblog om redundanta index. Eftersom jag inte vill skriva om den artikeln så hoppar jag direkt till [...]</description>
		<content:encoded><![CDATA[<p>[...] läste en artikel på mysqlpeformanceblog om redundanta index. Eftersom jag inte vill skriva om den artikeln så hoppar jag direkt till [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Finding out largest tables on MySQL Server &#124; MySQL Performance Blog</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-238934</link>
		<dc:creator>Finding out largest tables on MySQL Server &#124; MySQL Performance Blog</dc:creator>
		<pubDate>Mon, 04 Feb 2008 14:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-238934</guid>
		<description>[...] to data size often indicates there is a lot of indexes (so it is well possible there are some duplicates, redundant or simply unused indexes among them) or may be there is long primary key with Innodb tables. Of [...]</description>
		<content:encoded><![CDATA[<p>[...] to data size often indicates there is a lot of indexes (so it is well possible there are some duplicates, redundant or simply unused indexes among them) or may be there is long primary key with Innodb tables. Of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL Performance Blog &#187; Redundant index is not always bad</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-160073</link>
		<dc:creator>MySQL Performance Blog &#187; Redundant index is not always bad</dc:creator>
		<pubDate>Tue, 28 Aug 2007 09:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-160073</guid>
		<description>[...] year ago Peter wrote about redundant indexes and mentioned sometimes it is good to leave two indexes, even one is first part of another. I'm [...]</description>
		<content:encoded><![CDATA[<p>[...] year ago Peter wrote about redundant indexes and mentioned sometimes it is good to leave two indexes, even one is first part of another. I&#8217;m [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-44337</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Mon, 05 Feb 2007 21:49:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-44337</guid>
		<description>Olivier.

This is pretty strange idea.  Innodb PK is usually most efficient key to use for row data retrieval.</description>
		<content:encoded><![CDATA[<p>Olivier.</p>
<p>This is pretty strange idea.  Innodb PK is usually most efficient key to use for row data retrieval.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-41839</link>
		<dc:creator>Olivier</dc:creator>
		<pubDate>Fri, 02 Feb 2007 16:50:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-41839</guid>
		<description>Hi,

And what about Innodb PK ? I heard that to speed UP queries, I should declare an additionnal key on the PK, and force the use of this key instead of the primary (because innodb PK are stored in fragments). So, true or false ?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>And what about Innodb PK ? I heard that to speed UP queries, I should declare an additionnal key on the PK, and force the use of this key instead of the primary (because innodb PK are stored in fragments). So, true or false ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL Performance Blog &#187; Getting MySQL to use full key length</title>
		<link>http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-40575</link>
		<dc:creator>MySQL Performance Blog &#187; Getting MySQL to use full key length</dc:creator>
		<pubDate>Wed, 31 Jan 2007 19:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/08/17/duplicate-indexes-and-redundant-indexes/#comment-40575</guid>
		<description>[...] There is one bug, or "missing feature" in MySQL Optimizer which may give you hard time causing performance problems which may be hard to track down, it is using only part of the index when full index can be used or using shorter index while there is longer index available. The last item is yet another good reason for removing redundant indexes [...]</description>
		<content:encoded><![CDATA[<p>[...] There is one bug, or &#8220;missing feature&#8221; in MySQL Optimizer which may give you hard time causing performance problems which may be hard to track down, it is using only part of the index when full index can be used or using shorter index while there is longer index available. The last item is yet another good reason for removing redundant indexes [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
