<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>评论：实例说明optimize table在优化mysql时很重要</title>
	<atom:link href="http://blog.51yip.com/mysql/1222.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.51yip.com/mysql/1222.html</link>
	<description>－－一步，二步，三步，N步，二行脚印</description>
	<lastBuildDate>Tue, 07 Jun 2022 01:26:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>来自：涛涛</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-17848</link>
		<dc:creator>涛涛</dc:creator>
		<pubDate>Wed, 20 Feb 2019 10:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-17848</guid>
		<description>OPTIMIZE  一张删除了几千万条数据的表大概要多长时间</description>
		<content:encoded><![CDATA[<p>OPTIMIZE  一张删除了几千万条数据的表大概要多长时间</p>
]]></content:encoded>
	</item>
	<item>
		<title>来自：fanyank</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-17806</link>
		<dc:creator>fanyank</dc:creator>
		<pubDate>Sun, 21 Oct 2018 13:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-17806</guid>
		<description>楼上正解，引用MySQL官方文档给出的解释
In the InnoDB multi-versioning scheme, a row is not physically removed from the database immediately when you delete it with an SQL statement. InnoDB only physically removes the corresponding row and its index records when it discards the update undo log record written for the deletion. This removal operation is called a purge, and it is quite fast, usually taking the same order of time as the SQL statement that did the deletion.</description>
		<content:encoded><![CDATA[<p>楼上正解，引用MySQL官方文档给出的解释<br />
In the InnoDB multi-versioning scheme, a row is not physically removed from the database immediately when you delete it with an SQL statement. InnoDB only physically removes the corresponding row and its index records when it discards the update undo log record written for the deletion. This removal operation is called a purge, and it is quite fast, usually taking the same order of time as the SQL statement that did the deletion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>来自：蓝天</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-17683</link>
		<dc:creator>蓝天</dc:creator>
		<pubDate>Thu, 02 Nov 2017 15:23:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-17683</guid>
		<description>这应该是类似于oracle的高水位吧</description>
		<content:encoded><![CDATA[<p>这应该是类似于oracle的高水位吧</p>
]]></content:encoded>
	</item>
	<item>
		<title>来自：有点不同的见地</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-17602</link>
		<dc:creator>有点不同的见地</dc:creator>
		<pubDate>Wed, 03 May 2017 09:32:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-17602</guid>
		<description>对于为什么删除了表数据表的空间并没有减少的问题我有点不同的看法；
我觉得是因为mysql  MVCC的控制原因，删除了的数据其实还在那里，标记了删除的版本号  并不是你所说的空在那里。</description>
		<content:encoded><![CDATA[<p>对于为什么删除了表数据表的空间并没有减少的问题我有点不同的看法；<br />
我觉得是因为mysql  MVCC的控制原因，删除了的数据其实还在那里，标记了删除的版本号  并不是你所说的空在那里。</p>
]]></content:encoded>
	</item>
	<item>
		<title>来自：royce</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-3451</link>
		<dc:creator>royce</dc:creator>
		<pubDate>Fri, 19 Apr 2013 05:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-3451</guid>
		<description>不错，建议支持新浪微博分享</description>
		<content:encoded><![CDATA[<p>不错，建议支持新浪微博分享</p>
]]></content:encoded>
	</item>
	<item>
		<title>来自：ruochen</title>
		<link>http://blog.51yip.com/mysql/1222.html/comment-page-1#comment-410</link>
		<dc:creator>ruochen</dc:creator>
		<pubDate>Thu, 10 Mar 2011 11:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.51yip.com/?p=1222#comment-410</guid>
		<description>注意这个bug

      * InnoDB Storage Engine: The OPTIMIZE TABLE statement would
        reset the auto-increment counter for an InnoDB table. Now the
        auto-increment value is preserved across this operation.
        (Bug#18274: http://bugs.mysql.com/bug.php?id=18274)</description>
		<content:encoded><![CDATA[<p>注意这个bug</p>
<p>      * InnoDB Storage Engine: The OPTIMIZE TABLE statement would<br />
        reset the auto-increment counter for an InnoDB table. Now the<br />
        auto-increment value is preserved across this operation.<br />
        (Bug#18274: <a href="http://bugs.mysql.com/bug.php?id=18274)" rel="nofollow">http://bugs.mysql.com/bug.php?id=18274)</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
