<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Crash on FromDual GmbH</title><link>https://www.fromdual.com/tags/crash/</link><description>Recent content in Crash on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Wed, 05 Aug 2020 17:21:13 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/crash/index.xml" rel="self" type="application/rss+xml"/><item><title>Which table is hit by an InnoDB page corruption?</title><link>https://www.fromdual.com/blog/innodb-table-hit-by-page-corruption/</link><pubDate>Mon, 02 Aug 2010 17:49:38 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-table-hit-by-page-corruption/</guid><description>&lt;p&gt;InnoDB is known to have crash-recovery capabilities and thus is called a crash safe storage engine (in contrary to MyISAM). Nevertheless under certain circumstances it seems like InnoDB pages can get corrupt during a crash and then a manual crash-recovery is needed.&lt;/p&gt;</description></item></channel></rss>