<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: On hot backups</title>
	<atom:link href="http://dom.as/2010/05/08/on-hot-backups/feed/" rel="self" type="application/rss+xml" />
	<link>http://dom.as/2010/05/08/on-hot-backups/</link>
	<description></description>
	<lastBuildDate>Sat, 17 Dec 2011 20:14:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Mark Callaghan</title>
		<link>http://dom.as/2010/05/08/on-hot-backups/#comment-1747</link>
		<dc:creator><![CDATA[Mark Callaghan]]></dc:creator>
		<pubDate>Tue, 19 Apr 2011 04:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://mituzas.lt/?p=739#comment-1747</guid>
		<description><![CDATA[Algorithm is obvious implies comments are not needed? Very funny to some, very annoying to others trying to debug a continuous crash that occurs during crash recovery.

Obscure and obfuscated open-source software becomes less interesting to me with each passing day.]]></description>
		<content:encoded><![CDATA[<p>Algorithm is obvious implies comments are not needed? Very funny to some, very annoying to others trying to debug a continuous crash that occurs during crash recovery.</p>
<p>Obscure and obfuscated open-source software becomes less interesting to me with each passing day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Huddleston</title>
		<link>http://dom.as/2010/05/08/on-hot-backups/#comment-1746</link>
		<dc:creator><![CDATA[Ryan Huddleston]]></dc:creator>
		<pubDate>Mon, 31 May 2010 17:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://mituzas.lt/?p=739#comment-1746</guid>
		<description><![CDATA[Just wanted to point out that xtrabackup/xtradb already has the feature of moving hot backup from on instance to another without restarting mysql

See &quot;Restoring a single .ibd file&quot; section here (same can apply to one whole DB):

http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup_manual]]></description>
		<content:encoded><![CDATA[<p>Just wanted to point out that xtrabackup/xtradb already has the feature of moving hot backup from on instance to another without restarting mysql</p>
<p>See &#8220;Restoring a single .ibd file&#8221; section here (same can apply to one whole DB):</p>
<p><a href="http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup_manual" rel="nofollow">http://www.percona.com/docs/wiki/percona-xtrabackup:xtrabackup_manual</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domas Mituzas</title>
		<link>http://dom.as/2010/05/08/on-hot-backups/#comment-1745</link>
		<dc:creator><![CDATA[Domas Mituzas]]></dc:creator>
		<pubDate>Thu, 20 May 2010 08:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://mituzas.lt/?p=739#comment-1745</guid>
		<description><![CDATA[@Heikki, thanks for update and clarification - though I still think that the documentation levels in that file are way under InnoDB standards in other parts, and some of information I&#039;d love to find in comments there was missing. I&#039;ll update the post.]]></description>
		<content:encoded><![CDATA[<p>@Heikki, thanks for update and clarification &#8211; though I still think that the documentation levels in that file are way under InnoDB standards in other parts, and some of information I&#8217;d love to find in comments there was missing. I&#8217;ll update the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heikki Tuuri</title>
		<link>http://dom.as/2010/05/08/on-hot-backups/#comment-1744</link>
		<dc:creator><![CDATA[Heikki Tuuri]]></dc:creator>
		<pubDate>Mon, 10 May 2010 15:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://mituzas.lt/?p=739#comment-1744</guid>
		<description><![CDATA[Domas,

you are claiming:
&quot;
Few years ago I was looking at crash recovery code, and realized that InnoDB has removed all the comments from the code, related to replay of transaction log. Judging by high quality of comments in the remaining codebase, I realized that it was all done to obscure any efforts to build another InnoDB hot backup solution – competitor to first Innobase standalone offering.
&quot;
I am not aware of any comments that would have been removed. InnoDB was published in the MySQL-3.23.35 source release in March 2000. At that time I did not have any plans for a Hot Backup product. If you look at the source code of MySQL-4.0.10 a couple of years later, you notice that comments have not been removed from log0recv.c. Instead, that file contains a couple of additional functions that are used by InnoDB Hot Backup.

The reason why log0recv.c is quite scarcely commented in 3.23.35 is that the algorithm is relatively straightforward and did not require extensive commenting.

Best regards,

Heikki Tuuri]]></description>
		<content:encoded><![CDATA[<p>Domas,</p>
<p>you are claiming:<br />
&#8221;<br />
Few years ago I was looking at crash recovery code, and realized that InnoDB has removed all the comments from the code, related to replay of transaction log. Judging by high quality of comments in the remaining codebase, I realized that it was all done to obscure any efforts to build another InnoDB hot backup solution – competitor to first Innobase standalone offering.<br />
&#8221;<br />
I am not aware of any comments that would have been removed. InnoDB was published in the MySQL-3.23.35 source release in March 2000. At that time I did not have any plans for a Hot Backup product. If you look at the source code of MySQL-4.0.10 a couple of years later, you notice that comments have not been removed from log0recv.c. Instead, that file contains a couple of additional functions that are used by InnoDB Hot Backup.</p>
<p>The reason why log0recv.c is quite scarcely commented in 3.23.35 is that the algorithm is relatively straightforward and did not require extensive commenting.</p>
<p>Best regards,</p>
<p>Heikki Tuuri</p>
]]></content:encoded>
	</item>
</channel>
</rss>

