<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<oembed>
  <author_name>hirose31</author_name>
  <author_url>https://blog.hatena.ne.jp/hirose31/</author_url>
  <blog_title>（ひ）メモ</blog_title>
  <blog_url>https://hirose31.hatenablog.jp/</blog_url>
  <categories>
    <anon>mysql</anon>
  </categories>
  <description>Binary log corruption - Binary log may become corrupted and out of sync with database content. This will sometimes break replication but if you’re just planning on using binary log for point in time recovery it can go unnoticed. sync_binlog Is helping by syncing binary log, but at performance penalt…</description>
  <height>190</height>
  <html>&lt;iframe src=&quot;https://hatenablog-parts.com/embed?url=https%3A%2F%2Fhirose31.hatenablog.jp%2Fentry%2F20060803%2F1154590202&quot; title=&quot; MySQL Performance Blog » MySQL Crash Recovery - （ひ）メモ&quot; class=&quot;embed-card embed-blogcard&quot; scrolling=&quot;no&quot; frameborder=&quot;0&quot; style=&quot;display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;&quot;&gt;&lt;/iframe&gt;</html>
  <image_url></image_url>
  <provider_name>Hatena Blog</provider_name>
  <provider_url>https://hatena.blog</provider_url>
  <published>2006-08-03 16:30:02</published>
  <title> MySQL Performance Blog » MySQL Crash Recovery</title>
  <type>rich</type>
  <url>https://hirose31.hatenablog.jp/entry/20060803/1154590202</url>
  <version>1.0</version>
  <width>100%</width>
</oembed>
