<?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>Comments for Percona.TV MySQL Videos</title>
	<atom:link href="http://www.percona.tv/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.percona.tv</link>
	<description>MySQL Webinars and Videos from Percona</description>
	<lastBuildDate>Thu, 18 Feb 2010 18:33:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on InnoDB Data Recovery Tutorial by UZCANGA</title>
		<link>http://www.percona.tv/percona-screencasts/innodb-recovery-tutorial/comment-page-1#comment-1191</link>
		<dc:creator>UZCANGA</dc:creator>
		<pubDate>Thu, 18 Feb 2010 18:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=19#comment-1191</guid>
		<description><![CDATA[Hi.

I try for excute the create_defs.pl command but no get anything in my table_defs-h file. This file contains only de standar info just llike the create_defs.pl file.

Any sugestion?

Thanks]]></description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>I try for excute the create_defs.pl command but no get anything in my table_defs-h file. This file contains only de standar info just llike the create_defs.pl file.</p>
<p>Any sugestion?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on InnoDB Data Recovery Tutorial by Alfredo Herrejon</title>
		<link>http://www.percona.tv/percona-screencasts/innodb-recovery-tutorial/comment-page-1#comment-103</link>
		<dc:creator>Alfredo Herrejon</dc:creator>
		<pubDate>Fri, 21 Aug 2009 15:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=19#comment-103</guid>
		<description><![CDATA[Hello Ryan, First of all thank you very much it was so helpful for me I truncated a production table so I am in serious problems, i followed all your steps, before .configure all was ok, also ./configure showed me the thanks message but the problem was when i made the make command after the ./configure i got some warnings like 

constraints_parser.c:88: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘ulint’
constraints_parser.c: In function ‘check_fields_sizes’:
constraints_parser.c:130: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 4 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_new’:
constraints_parser.c:231: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘ibrec_init_offsets_old’:
constraints_parser.c:265: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c:288: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’
constraints_parser.c: In function ‘check_for_a_record’:
constraints_parser.c:320: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
constraints_parser.c:324: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a
page_parser.c: In function ‘process_ibpage’:
page_parser.c:42: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c:46: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’
page_parser.c: In function ‘process_ibfile’:
page_parser.c:72: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’

at first I ignored that but when i made the page_parser with my ibdata1 file and got all the pages whe i used the constrains_parsers i am getting empty rows totally empty, do you know if the warning are causing the error, or what could i made wrong? Thanks in advance Alfredo Herrejon]]></description>
		<content:encoded><![CDATA[<p>Hello Ryan, First of all thank you very much it was so helpful for me I truncated a production table so I am in serious problems, i followed all your steps, before .configure all was ok, also ./configure showed me the thanks message but the problem was when i made the make command after the ./configure i got some warnings like </p>
<p>constraints_parser.c:88: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘ulint’<br />
constraints_parser.c: In function ‘check_fields_sizes’:<br />
constraints_parser.c:130: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’<br />
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 2 has type ‘ulint’<br />
constraints_parser.c:144: warning: format ‘%u’ expects type ‘unsigned int’, but argument 4 has type ‘ulint’<br />
constraints_parser.c: In function ‘ibrec_init_offsets_new’:<br />
constraints_parser.c:231: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’<br />
constraints_parser.c: In function ‘ibrec_init_offsets_old’:<br />
constraints_parser.c:265: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’<br />
constraints_parser.c:288: warning: format ‘%i’ expects type ‘int’, but argument 2 has type ‘ulint’<br />
constraints_parser.c: In function ‘check_for_a_record’:<br />
constraints_parser.c:320: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’<br />
constraints_parser.c:324: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 3 has type ‘int’<br />
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a<br />
page_parser.c: In function ‘process_ibpage’:<br />
page_parser.c:42: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’<br />
page_parser.c:46: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’<br />
page_parser.c: In function ‘process_ibfile’:<br />
page_parser.c:72: warning: format ‘%u’ expects type ‘unsigned int’, but argument 3 has type ‘time_t’</p>
<p>at first I ignored that but when i made the page_parser with my ibdata1 file and got all the pages whe i used the constrains_parsers i am getting empty rows totally empty, do you know if the warning are causing the error, or what could i made wrong? Thanks in advance Alfredo Herrejon</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to XtraDB, a Scalable InnoDB-based Storage Engine by Erik Jones</title>
		<link>http://www.percona.tv/mysql-camp/intro-to-xtradb-a-scalable-innodb-based-storage-engine/comment-page-1#comment-101</link>
		<dc:creator>Erik Jones</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=49#comment-101</guid>
		<description><![CDATA[The sound cut out on this for me at 4:55.]]></description>
		<content:encoded><![CDATA[<p>The sound cut out on this for me at 4:55.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Think About Performance by Phil</title>
		<link>http://www.percona.tv/percona-performance-conference/ppc-how-to-think-about-performance-selena-deckelmann/comment-page-1#comment-99</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sun, 09 Aug 2009 19:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=24#comment-99</guid>
		<description><![CDATA[Cant seem to get this one to play]]></description>
		<content:encoded><![CDATA[<p>Cant seem to get this one to play</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intro to XtraDB, a Scalable InnoDB-based Storage Engine by Iggi</title>
		<link>http://www.percona.tv/mysql-camp/intro-to-xtradb-a-scalable-innodb-based-storage-engine/comment-page-1#comment-96</link>
		<dc:creator>Iggi</dc:creator>
		<pubDate>Wed, 05 Aug 2009 21:33:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=49#comment-96</guid>
		<description><![CDATA[The audio drops out at around 4:56 and doesn&#039;t pick up again until near the end of the video.]]></description>
		<content:encoded><![CDATA[<p>The audio drops out at around 4:56 and doesn&#8217;t pick up again until near the end of the video.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Emulate a More Granular Slow Query Log With Maatkit by Ryan</title>
		<link>http://www.percona.tv/percona-screencasts/emulate-a-more-granular-slow-query-log-with-maatkit/comment-page-1#comment-65</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 02 Jul 2009 19:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=11#comment-65</guid>
		<description><![CDATA[This technique has largely been superseded by the ridiculously awesome --type tcpdump command-line option.  Check that out!

-- Ryan Lowe]]></description>
		<content:encoded><![CDATA[<p>This technique has largely been superseded by the ridiculously awesome &#8211;type tcpdump command-line option.  Check that out!</p>
<p>&#8211; Ryan Lowe</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Answering Vadim&#8217;s .ibd Recovery Challenge by Vadim</title>
		<link>http://www.percona.tv/percona-screencasts/answering-vadims-ibd-recovery-challenge/comment-page-1#comment-63</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Thu, 02 Jul 2009 17:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=13#comment-63</guid>
		<description><![CDATA[Gavin,

You may see see that different KEY_BLOCK_SIZE needed (and therefore Barracuda format) by initial  file size of table. Usually empty InnoDB table takes 92K, but file I proposed was 64K]]></description>
		<content:encoded><![CDATA[<p>Gavin,</p>
<p>You may see see that different KEY_BLOCK_SIZE needed (and therefore Barracuda format) by initial  file size of table. Usually empty InnoDB table takes 92K, but file I proposed was 64K</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Answering Vadim&#8217;s .ibd Recovery Challenge by Gavin Towey</title>
		<link>http://www.percona.tv/percona-screencasts/answering-vadims-ibd-recovery-challenge/comment-page-1#comment-58</link>
		<dc:creator>Gavin Towey</dc:creator>
		<pubDate>Wed, 01 Jul 2009 18:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.percona.tv/?p=13#comment-58</guid>
		<description><![CDATA[This answer works if you happen to get lucky and guess all the correct options, but how would you know that the file format needs to be Barracuda, and the KEY_BLOCK_SIZE should be 4?

The innodb manual gives some good info for exploring ibd file: http://www.innodb.com/doc/innodb_plugin-1.0/innodb-file-format.html#innodb-file-format-identifying

In particular the command:
od -t x1 -j 54 -N 4 tryme.ibd

The result is:
0000066 00 00 00 27
0000072

The 27 is what you&#039;re looking for, it&#039;s a number that describes the file format and options.

By creating innodb tables with different options, and then running the hex dump on the resulting ibd file, you can find a create table statement that you *know* will match the orhpan .ibd file you have.

Also, don&#039;t forget IMPORT TABLESPACE and DISCARD tablespace.  This is a better way to handle the .ibd file than doing this on the filesystem because this method would only work if this table was the first one you created in innodb (or worse, the Nth)  Using the tablespace commands will give you some additional information in the error logs on failure which will increase your chances of getting it right.]]></description>
		<content:encoded><![CDATA[<p>This answer works if you happen to get lucky and guess all the correct options, but how would you know that the file format needs to be Barracuda, and the KEY_BLOCK_SIZE should be 4?</p>
<p>The innodb manual gives some good info for exploring ibd file: <a href="http://www.innodb.com/doc/innodb_plugin-1.0/innodb-file-format.html#innodb-file-format-identifying" rel="nofollow">http://www.innodb.com/doc/innodb_plugin-1.0/innodb-file-format.html#innodb-file-format-identifying</a></p>
<p>In particular the command:<br />
od -t x1 -j 54 -N 4 tryme.ibd</p>
<p>The result is:<br />
0000066 00 00 00 27<br />
0000072</p>
<p>The 27 is what you&#8217;re looking for, it&#8217;s a number that describes the file format and options.</p>
<p>By creating innodb tables with different options, and then running the hex dump on the resulting ibd file, you can find a create table statement that you *know* will match the orhpan .ibd file you have.</p>
<p>Also, don&#8217;t forget IMPORT TABLESPACE and DISCARD tablespace.  This is a better way to handle the .ibd file than doing this on the filesystem because this method would only work if this table was the first one you created in innodb (or worse, the Nth)  Using the tablespace commands will give you some additional information in the error logs on failure which will increase your chances of getting it right.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
