tag:blogger.com,1999:blog-16959946.post1980497015011271957..comments2023-12-09T16:44:47.897+01:00Comments on The Data Charmer: Some hidden goods in MySQL 5.5Giuseppe Maxiahttp://www.blogger.com/profile/15801583338057324813noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-16959946.post-56987955821857398222010-12-16T21:37:00.597+01:002010-12-16T21:37:00.597+01:00Matthew,
Thanks for this tip. I forgot about this ...Matthew,<br />Thanks for this tip. I forgot about this option!Giuseppe Maxiahttps://www.blogger.com/profile/15801583338057324813noreply@blogger.comtag:blogger.com,1999:blog-16959946.post-6569457029851883982010-12-16T18:26:23.399+01:002010-12-16T18:26:23.399+01:00Hey Giuseppe!
One of my favorite under publicised...Hey Giuseppe!<br /><br />One of my favorite under publicised feature enhancements is mysqldump --dump-slave=1|2 <br /><br />http://dev.mysql.com/doc/refman/5.5/en/mysqldump.html#option_mysqldump_dump-slave<br /><br />mysqldump now gives you the ability to set up a new replication slave by cloning an existing one. Locking the master or taking a file system snapshot from the slave are no longer needed.Matthew Montgomeryhttps://www.blogger.com/profile/04421029174237420523noreply@blogger.comtag:blogger.com,1999:blog-16959946.post-45563619499424261662010-12-16T16:25:27.100+01:002010-12-16T16:25:27.100+01:00Hi Mark,
Thanks for the explanation. This is exact...Hi Mark,<br />Thanks for the explanation. This is exactly what I was looking for.<br />Let's hope that the information_schema (or performance_schema) tables catch up with the SHOW ENGINE INNODB STATUS soon.Giuseppe Maxiahttps://www.blogger.com/profile/15801583338057324813noreply@blogger.comtag:blogger.com,1999:blog-16959946.post-11478355039860188482010-12-16T15:46:18.386+01:002010-12-16T15:46:18.386+01:00Hey Giuseppe!
"I don't know if the table...Hey Giuseppe!<br /><br />"I don't know if the tables can replace the SHOW ENGINE INNODB STATUS. Perhaps someone can comment on this issue and provide more information?"<br /><br />Yes and No.. :) <br /><br />The INNODB_TRX table now lists everything available in the TRANSACTIONS section of SHOW ENGINE INNODB STATUS (and more), so that can effectively replace it if you are using it for transaction information. <br /><br />However, the rest of the "static" output has yet to be exposed in a structured format - in a GA release anyway. <br /><br />The next release "should" (caveats apply et al) have some incarnation of the INNODB_METRICS table, examples of which were given at the UC this year:<br /><br />http://www.innodb.com/wp/wp-content/uploads/2010/04/InnoDB_Monitoring_System_2010.pdf<br /><br />http://lists.mysql.com/commits/110693<br /><br />That would leave foreign key and deadlock errors left as use cases..Mark Leithhttps://www.blogger.com/profile/07526409233197705882noreply@blogger.com