<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Eucalyptus</title>
    <link>https://blog.eucalyptus.cc/</link>
    
    <image>
      <url>https://blog.eucalyptus.cc/icon.png</url>
      <title>Eucalyptus</title>
      <link>https://blog.eucalyptus.cc/</link>
    </image>
    
    <atom:link href="https://blog.eucalyptus.cc/rss.xml" rel="self" type="application/rss+xml"/>
    
    <description>一个记录建站折腾历程与生活碎片的个人博客，分享技术踩坑心得、工具推荐，以及日常里的微小确幸。在这里，代码与烟火气并存。</description>
    <pubDate>Tue, 10 Nov 2026 10:29:22 GMT</pubDate>
    <generator>http://hexo.io/</generator>
    
    <item>
      <title>Hexo 腾讯视频追剧页插件：hexo-tengxun-eucalyptus 安装使用</title>
      <link>https://blog.eucalyptus.cc/2026/11/10/b391e9b5/</link>
      <guid>https://blog.eucalyptus.cc/2026/11/10/b391e9b5/</guid>
      <pubDate>Tue, 10 Nov 2026 12:00:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;一款 Hexo 通用插件，自动同步腾讯视频「加追」和「预约」列表，生成卡片网格追剧页。不绑定 anzhiyu 主题，任何 Hexo 博客都能用。&lt;/p&gt;
&lt;h2 id=&quot;最终效果&quot;&gt;&lt;a href=&quot;#最终效果&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>一款 Hexo 通用插件，自动同步腾讯视频「加追」和「预约」列表，生成卡片网格追剧页。不绑定 anzhiyu 主题，任何 Hexo 博客都能用。</p><h2 id="最终效果"><a href="#最终效果" class="headerlink" title="最终效果"></a>最终效果</h2><p>Demo：<a href="https://blog.eucalyptus.cc/zhuijus/">https://blog.eucalyptus.cc/zhuijus/</a></p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-10/1.avif" alt="全页效果"></p><p>核心能力：</p><ul><li><strong>账号同步</strong>：拉取腾讯视频「加追」和「预约」列表，自动按集数进度分组</li><li><strong>手动清单</strong>：不想绑账号也能手动填 cid 维护清单</li><li><strong>卡片网格</strong>：竖版海报墙 + tabs 切换 + 搜索过滤</li><li><strong>智能增量</strong>：集数没变的剧跳过详情接口，大幅缩短同步时间</li><li><strong>Cookie 降级</strong>：登录态过期时自动用上一次缓存按标记重分组，页面不崩</li></ul><h2 id="安装"><a href="#安装" class="headerlink" title="安装"></a>安装</h2><p>方式一：从 npm（推荐，稳定版）</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">npm install hexo-tengxun-eucalyptus</span><br></pre></td></tr></table></figure><p>方式二：从 GitHub（跟随最新 master，适合想改源码的同学）</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">npm install git+https://github.com/ShiningStarLi/hexo-tengxun-eucalyptus.git</span><br></pre></td></tr></table></figure><p>Hexo ≥ 5.0 自动识别插件，无需额外注册。</p><h2 id="配置（可选）"><a href="#配置（可选）" class="headerlink" title="配置（可选）"></a>配置（可选）</h2><p>在站点 <code>_config.yml</code> 里加一段 <code>zhuiju_vqq:</code>，所有字段都有默认值，不配也能用：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">zhuiju_vqq:</span></span><br><span class="line">  <span class="attr">enable:</span> <span class="literal">true</span>            <span class="comment"># 是否启用（默认 true）</span></span><br><span class="line">  <span class="attr">path:</span> <span class="string">zhuijus/</span>          <span class="comment"># 生成的页面路径（默认 zhuijus/）</span></span><br><span class="line">  <span class="attr">title:</span> <span class="string">追剧列表</span>         <span class="comment"># 页面标题（默认「追剧列表」）</span></span><br><span class="line">  <span class="attr">quote:</span> <span class="string">&#x27;&#x27;</span>               <span class="comment"># 页面顶部引言（可选）</span></span><br><span class="line">  <span class="attr">columns:</span> <span class="number">5</span>              <span class="comment"># 桌面端每行卡片数（默认 5）</span></span><br><span class="line">  <span class="attr">primary_color:</span> <span class="literal">null</span>     <span class="comment"># 主色调 null 时跟随 Hexo 主题变量 --anzhiyu-main</span></span><br><span class="line">  <span class="attr">groups:</span>                 <span class="comment"># 分组定义（顺序即 tabs 顺序）</span></span><br><span class="line">    <span class="bullet">-</span> &#123; <span class="attr">key:</span> <span class="string">airing</span>,    <span class="attr">label:</span> <span class="string">追剧</span> &#125;</span><br><span class="line">    <span class="bullet">-</span> &#123; <span class="attr">key:</span> <span class="string">finished</span>,  <span class="attr">label:</span> <span class="string">已完结</span> &#125;</span><br><span class="line">    <span class="bullet">-</span> &#123; <span class="attr">key:</span> <span class="string">reserved</span>,  <span class="attr">label:</span> <span class="string">预约</span> &#125;</span><br></pre></td></tr></table></figure><h2 id="两种运行模式"><a href="#两种运行模式" class="headerlink" title="两种运行模式"></a>两种运行模式</h2><h3 id="A-账号同步（推荐）"><a href="#A-账号同步（推荐）" class="headerlink" title="A. 账号同步（推荐）"></a>A. 账号同步（推荐）</h3><p>在浏览器登录腾讯视频（<a href="https://v.qq.com）后：">https://v.qq.com）后：</a></p><ol><li>打开 DevTools → Console</li><li>执行 <code>copy(document.cookie)</code> — 整串 cookie 已复制到剪贴板</li><li>粘贴到博客项目根目录，保存为 <code>.vqq-cookie</code>（无扩展名）</li></ol><p>然后跑同步命令：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">npx hexo zhuiju -u</span><br></pre></td></tr></table></figure><p>脚本自动调三个接口：</p><table><thead><tr><th>接口</th><th>鉴权</th><th>用途</th></tr></thead><tbody><tr><td><code>getAlbumList</code></td><td><strong>需要 Cookie</strong></td><td>「加追」列表（scene&#x3D;1）+ 「预约」列表（scene&#x3D;2）</td></tr><tr><td><code>float_vinfo2</code></td><td>无</td><td>单部剧详情：标题&#x2F;封面&#x2F;年份&#x2F;题材&#x2F;主演&#x2F;集数</td></tr><tr><td><code>GetGradeDetail</code></td><td>无</td><td>评分、评分人数、好评率</td></tr></tbody></table><p>Cookie 通常一到两个月过期，过期时脚本会自动用上一次缓存兜底，页面照常显示，只是不会更新数据。什么时候想更新了，重新 <code>copy(document.cookie)</code> 覆盖 <code>.vqq-cookie</code> 再跑一遍就行。</p><h3 id="B-手动清单"><a href="#B-手动清单" class="headerlink" title="B. 手动清单"></a>B. 手动清单</h3><p>不想用账号同步的话，在 <code>source/_data/zhuiju_src.json</code> 里手动填：</p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">  <span class="attr">&quot;airing&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span></span><br><span class="line">    <span class="punctuation">&#123;</span> <span class="attr">&quot;cid&quot;</span><span class="punctuation">:</span> <span class="string">&quot;xxx&quot;</span><span class="punctuation">,</span> <span class="attr">&quot;url&quot;</span><span class="punctuation">:</span> <span class="string">&quot;https://v.qq.com/x/cover/xxx.html&quot;</span> <span class="punctuation">&#125;</span></span><br><span class="line">  <span class="punctuation">]</span><span class="punctuation">,</span></span><br><span class="line">  <span class="attr">&quot;finished&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span></span><br><span class="line">    <span class="punctuation">&#123;</span> <span class="attr">&quot;cid&quot;</span><span class="punctuation">:</span> <span class="string">&quot;yyy&quot;</span><span class="punctuation">,</span> <span class="attr">&quot;url&quot;</span><span class="punctuation">:</span> <span class="string">&quot;https://v.qq.com/x/cover/yyy.html&quot;</span> <span class="punctuation">&#125;</span></span><br><span class="line">  <span class="punctuation">]</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p><code>cid</code> 就是腾讯视频 URL <code>https://v.qq.com/x/cover/&lt;cid&gt;.html</code> 里那串字母数字。之后同样跑 <code>npx hexo zhuiju -u</code>。</p><h2 id="构建部署"><a href="#构建部署" class="headerlink" title="构建部署"></a>构建部署</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 同步数据（A 模式需要 Cookie，B 模式需要 zhuiju_src.json）</span></span><br><span class="line">npx hexo zhuiju -u</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 构建静态页面（zhuijus.json → public/zhuijus/index.html）</span></span><br><span class="line">npx hexo clean &amp;&amp; npx hexo generate</span><br><span class="line"></span><br><span class="line"><span class="comment"># 3. 本地预览</span></span><br><span class="line">npx hexo s</span><br><span class="line"></span><br><span class="line"><span class="comment"># 4. 部署到你的服务器（用你自己的部署方式：rsync / git push / 云函数 ...）</span></span><br></pre></td></tr></table></figure><p>构建后访问 <code>https://你的域名/zhuijus/</code> 就能看到追剧页。</p><h2 id="文件结构"><a href="#文件结构" class="headerlink" title="文件结构"></a>文件结构</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">项目根目录/</span><br><span class="line">├── node_modules/</span><br><span class="line">│   └── hexo-tengxun-eucalyptus/   # npm 插件（自动注册 command + generator）</span><br><span class="line">├── source/</span><br><span class="line">│   ├── _data/</span><br><span class="line">│   │   ├── zhuijus.json           # 同步结果缓存（构建时只读这个，不联网）</span><br><span class="line">│   │   └── zhuiju_src.json        # 手动清单（B 模式，可选）</span><br><span class="line">│   └── ...</span><br><span class="line">├── .vqq-cookie                    # 腾讯视频登录 Cookie（A 模式，gitignore 建议忽略）</span><br><span class="line">└── _config.yml                    # 可选：zhuiju_vqq 配置段</span><br></pre></td></tr></table></figure><h2 id="实现细节（源码阅读）"><a href="#实现细节（源码阅读）" class="headerlink" title="实现细节（源码阅读）"></a>实现细节（源码阅读）</h2><p>下面是插件内部的一些设计思路，对想二次开发的同学有用。</p><h3 id="1-并发抓详情"><a href="#1-并发抓详情" class="headerlink" title="1. 并发抓详情"></a>1. 并发抓详情</h3><p>原脚本串行 <code>for...of + sleep(250ms)</code>，27 部剧 × 2 个接口 ≈ 14 秒。</p><p>改成每批 5 个并发（Promise.all + chunk 分组），因为详情接口和评分接口都是无鉴权的，腾讯不会限流。耗时从 14s 降到 2-3s。</p><h3 id="2-智能增量更新"><a href="#2-智能增量更新" class="headerlink" title="2. 智能增量更新"></a>2. 智能增量更新</h3><p>列表接口返回的 <code>mark_label_list[].prime_text</code> 已经告诉我当前集数了。和上次缓存对比一下，没变的剧直接沿用旧数据，跳过详情+评分接口。</p><p>实测效果：27 部里通常只有 3-5 部在更新，剩下 22 部全跳过 → 跑一轮 3-5 秒。</p><h3 id="3-Cookie-过期自动降级"><a href="#3-Cookie-过期自动降级" class="headerlink" title="3. Cookie 过期自动降级"></a>3. Cookie 过期自动降级</h3><p>catch 到 <code>ret=15006</code>（登录态失效）不退出，而是读上次缓存 <code>zhuijus.json</code>，重新按 <code>autoGroup</code> 分组写回去，再跑 <code>hexo generate</code>。页面照常显示。</p><h3 id="封面缩略分流"><a href="#封面缩略分流" class="headerlink" title="封面缩略分流"></a>封面缩略分流</h3><p>腾讯 vcover CDN 的缩略后缀<strong>横版竖版不通用</strong>：</p><table><thead><tr><th>CDN</th><th>&#x2F;0 原图</th><th>&#x2F;220</th><th>&#x2F;498</th></tr></thead><tbody><tr><td>vt-pic（竖版海报）</td><td>1.17 MB</td><td><strong>55 KB ✅</strong></td><td>✅</td></tr><tr><td>hz-pic（横版海报）</td><td>366 KB</td><td><strong>400 ❌</strong></td><td><strong>42 KB ✅</strong></td></tr></tbody></table><p>所以插件里按 URL 分流：</p><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// vt-pic 用 /220，hz-pic 用 /498</span></span><br><span class="line"><span class="keyword">const</span> <span class="title function_">sizedCover</span> = (<span class="params">url</span>) =&gt; &#123;</span><br><span class="line">  <span class="keyword">const</span> clean = url.<span class="title function_">replace</span>(<span class="regexp">/\/(0|220|300|498|640)$/</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">  <span class="keyword">const</span> thumb = <span class="regexp">/hz-pic/i</span>.<span class="title function_">test</span>(clean) ? <span class="string">&#x27;/498&#x27;</span> : <span class="string">&#x27;/220&#x27;</span>;</span><br><span class="line">  <span class="keyword">return</span> <span class="string">`<span class="subst">$&#123;clean&#125;</span><span class="subst">$&#123;thumb&#125;</span>`</span>;</span><br><span class="line">&#125;;</span><br></pre></td></tr></table></figure><p>腾讯 CDN <strong>不支持 AVIF 参数</strong>（imageView2、imageMogr2 都无响应），想转 AVIF 得自己下载 → 转码 → 传 CDN，收益不大。</p><h2 id="主题适配"><a href="#主题适配" class="headerlink" title="主题适配"></a>主题适配</h2><p>插件生成的页面用独立的 <code>&lt;style&gt;</code> 标签包裹，不污染主题样式。主色调默认跟随 Hexo 主题变量 <code>var(--anzhiyu-main, #3db4f2)</code> —— anzhiyu 用户直接用，其他主题如果没这个变量会 fallback 到蓝色 <code>#3db4f2</code>，或者在 <code>_config.yml</code> 的 <code>zhuiju_vqq.primary_color</code> 里硬指定一个。</p><h2 id="UI-设计参考"><a href="#UI-设计参考" class="headerlink" title="UI 设计参考"></a>UI 设计参考</h2><table><thead><tr><th>参考项目</th><th>说明</th><th>链接</th></tr></thead><tbody><tr><td><strong>Hexo AniList</strong></td><td>卡片网格 + tabs + 搜索 + 评分徽章，本次追剧页的主要参考</td><td><a href="https://ajratnam.github.io/hexo-anilist/customization.html">https://ajratnam.github.io/hexo-anilist/customization.html</a></td></tr><tr><td>hexo-bilibili-bangumi</td><td>anzhiyu 主题自带的 B 站追番页，同款卡片布局</td><td>主题内置 <code>/bangumis/</code></td></tr></tbody></table><h2 id="仓库"><a href="#仓库" class="headerlink" title="仓库"></a>仓库</h2><ul><li><strong>npm</strong>：<a href="https://www.npmjs.com/package/hexo-tengxun-eucalyptus">https://www.npmjs.com/package/hexo-tengxun-eucalyptus</a></li><li><strong>GitHub</strong>：<a href="https://github.com/ShiningStarLi/hexo-tengxun-eucalyptus">https://github.com/ShiningStarLi/hexo-tengxun-eucalyptus</a></li></ul><p>有问题可以在文章下面留言。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Hexo/">Hexo</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%85%BE%E8%AE%AF%E8%A7%86%E9%A2%91/">腾讯视频</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/npm/">npm</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/11/10/b391e9b5/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>给博客养一条大肥鱼：桌宠的设计与实现</title>
      <link>https://blog.eucalyptus.cc/2026/11/04/8b60f883/</link>
      <guid>https://blog.eucalyptus.cc/2026/11/04/8b60f883/</guid>
      <pubDate>Tue, 03 Nov 2026 16:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;之前博客右下角挂着一个 AI</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>之前博客右下角挂着一个 AI 小助手：点开是面板，关掉是图标，说话要等接口，内容还要等打字机效果。</p><p>可它真正被用到的场景只有四种：回到顶部、跳去评论、关灯、看看这站是谁写的。</p><p>于是我把它拆了，换成一只常驻的大肥鱼。点它有反应，右键出菜单，第一次来会打招呼，还能告诉你离我多远。</p><p>这篇讲它的结构、几个关键设计，以及怎么配置。</p><h2 id="一、它由哪几块组成"><a href="#一、它由哪几块组成" class="headerlink" title="一、它由哪几块组成"></a>一、它由哪几块组成</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">themes/anzhiyu/</span><br><span class="line">├── layout/includes/pet.pug          # 挂载点（10 行）</span><br><span class="line">└── source/pet/</span><br><span class="line">    ├── pet.js                       # 全部逻辑，约 1000 行</span><br><span class="line">    ├── pet.css                      # 全部样式，约 370 行</span><br><span class="line">    └── LICENSE                      # 素材与代码的 MIT 协议</span><br><span class="line"></span><br><span class="line">scripts/pet-data.js                  # 构建期生成 pet-data.json</span><br><span class="line">source/_data/pet_about.yml           # 「关于我」文案</span><br><span class="line">source/_data/pet_visitor.yml         # 博主坐标（算距离用）</span><br></pre></td></tr></table></figure><p>原则是「一个挂载点 + 一个 JS + 一个 CSS」，不往主题的模板里塞逻辑。</p><p>挂载点只有三件事：声明素材地址、引入样式、放一个空的 <code>&lt;video&gt;</code>：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">script.</span><br><span class="line">  window.__BLOG_PET_BASE__ = &#x27;https://img.eucalyptus.cc/pet/&#x27;;</span><br><span class="line">link(rel=&quot;stylesheet&quot;, href=url_for(&quot;/pet/pet.css&quot;), media=&quot;print&quot;, onload=&quot;this.media=&#x27;all&#x27;&quot;)</span><br><span class="line">#blog-pet(aria-hidden=&quot;true&quot;, hidden)</span><br><span class="line">  video#blog-pet-video(autoplay, muted, loop, playsinline, preload=&quot;auto&quot;)</span><br><span class="line">script(src=url_for(&quot;/pet/pet.js&quot;), defer)</span><br></pre></td></tr></table></figure><p>素材走自己的对象存储，换 CDN 只改这一行地址。</p><h2 id="二、素材：透明视频"><a href="#二、素材：透明视频" class="headerlink" title="二、素材：透明视频"></a>二、素材：透明视频</h2><p>角色是带 alpha 通道的 WebM，一个文件同时解决「会动」和「没有底色」两件事——不用 GIF（体积大、边缘锯齿），也不用序列帧（要自己写播放器）。</p><p>目录约定很简单：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">&lt;BASE&gt;/idle.webm            待机，循环</span><br><span class="line">&lt;BASE&gt;/actions/*.webm       点击反应，播完回到待机</span><br></pre></td></tr></table></figure><p>加载策略围绕「别拖慢首屏」设计：</p><table><thead><tr><th>资源</th><th>大小</th><th>时机</th></tr></thead><tbody><tr><td><code>idle.webm</code></td><td>441 KB</td><td>首屏，CDN 缓存一年</td></tr><tr><td>点击动画 ×3</td><td>≈1.5 MB</td><td>浏览器空闲时预取</td></tr><tr><td><code>pet.js</code> &#x2F; <code>pet.css</code></td><td>12 KB &#x2F; 2.6 KB（gzip）</td><td>每页，JS <code>defer</code>、CSS 非阻塞</td></tr></tbody></table><p>点击动画不跟着首屏抢带宽，等 <code>requestIdleCallback</code>（最多 4 秒）再拉；省流量模式和 2G 直接跳过。CSS 用 <code>media=&quot;print&quot;</code> + <code>onload</code> 切回来，不占关键渲染路径，代价是样式到达前 <code>&lt;video&gt;</code> 是裸的——所以 <code>#blog-pet</code> 先带 <code>hidden</code>，等 JS 量好尺寸再摘掉。</p><h2 id="三、坐标系：量出角色真正占的地方"><a href="#三、坐标系：量出角色真正占的地方" class="headerlink" title="三、坐标系：量出角色真正占的地方"></a>三、坐标系：量出角色真正占的地方</h2><p>播放器给的是 460×259 的矩形，但角色只占中间一块。这个差别决定三件事：拖到屏幕边缘时按什么夹取、气泡贴在哪里、菜单从哪边弹。</p><p>所以用 canvas 读一帧的 alpha 求包围盒：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">var</span> ctx = c.<span class="title function_">getContext</span>(<span class="string">&#x27;2d&#x27;</span>, &#123; <span class="attr">willReadFrequently</span>: <span class="literal">true</span> &#125;);</span><br><span class="line">ctx.<span class="title function_">drawImage</span>(video, <span class="number">0</span>, <span class="number">0</span>, vw, vh);</span><br><span class="line"><span class="keyword">var</span> data = ctx.<span class="title function_">getImageData</span>(<span class="number">0</span>, <span class="number">0</span>, vw, vh).<span class="property">data</span>;</span><br><span class="line"><span class="keyword">if</span> (data[(y * vw + x) * <span class="number">4</span> + <span class="number">3</span>] &gt; <span class="number">100</span>) &#123; <span class="comment">/* 只认实体像素 */</span> &#125;</span><br></pre></td></tr></table></figure><p>两个细节是刻意设计的：</p><p><strong>阈值取 100。</strong> 太低会把描边、阴影算进去，包围盒虚胖一圈；100 以上才是”实体”。</p><p><strong>顶边要按行密度重新找。</strong> 头顶有一缕很细的呆毛，一两像素宽，却会把包围盒顶边拉到很高——气泡贴上去就成了”飘在天上”。所以再扫一遍每行像素数，取第一行够密的当头顶：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">var</span> dense = <span class="title class_">Math</span>.<span class="title function_">max</span>(<span class="number">3</span>, <span class="title class_">Math</span>.<span class="title function_">round</span>((vw / <span class="number">2</span>) * <span class="number">0.03</span>));  <span class="comment">// 该行像素数 ≥ 全宽 3%</span></span><br><span class="line"><span class="keyword">for</span> (<span class="keyword">var</span> yy = minY; yy &lt;= maxY; yy += <span class="number">2</span>) &#123;</span><br><span class="line">  <span class="keyword">if</span> ((rows[yy] || <span class="number">0</span>) &gt;= dense) &#123; headY = yy; <span class="keyword">break</span>; &#125;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>这套坐标只依赖「当前这一帧」，所以角色换姿势时不用额外维护数据：打开气泡就现场量一次，拖拽时用位移平移，松手再精确贴一次。</p><h2 id="四、气泡：一个组件，五种内容"><a href="#四、气泡：一个组件，五种内容" class="headerlink" title="四、气泡：一个组件，五种内容"></a>四、气泡：一个组件，五种内容</h2><p>公告、访客信息、友链推荐、关于我、文章摘要，全都复用同一套气泡，靠参数区分：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="title function_">showBubble</span>(&#123;</span><br><span class="line">  <span class="attr">tag</span>: <span class="string">&#x27;访客信息&#x27;</span>, <span class="attr">tagIcon</span>: <span class="string">&#x27;icon-location-dot&#x27;</span>,</span><br><span class="line">  <span class="attr">text</span>: <span class="string">&#x27;...&#x27;</span>,</span><br><span class="line">  <span class="attr">ms</span>: <span class="number">30000</span>,                    <span class="comment">// 0 = 不自动关</span></span><br><span class="line">  <span class="attr">link</span>: <span class="string">&#x27;/about/&#x27;</span>, <span class="attr">linkText</span>: <span class="string">&#x27;关于本人 →&#x27;</span>,</span><br><span class="line">  <span class="attr">countdown</span>: <span class="number">5</span>, <span class="attr">onFire</span>: fn      <span class="comment">// 倒计时跳转 + 取消按钮</span></span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><p>同一套组件的几种样子：</p><table><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/2.avif" alt="公告气泡"></td><td><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/4.avif" alt="友链推荐：5 秒倒计时，可取消"></td></tr><tr><td><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/5.avif" alt="关于我"></td><td><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/6.avif" alt="文章摘要"></td></tr></tbody></table><p>设计上的几个取舍：</p><ul><li><strong>长文本</strong>：超过 70 字自动放宽到 340px，文本区最高 <code>50vh</code>，超出在气泡内滚动，绝不顶破屏幕。</li><li><strong>内容变了就重新定位</strong>：取消友链跳转后文案从三行缩成一行，气泡矮了一半，位置要跟着重算，否则底下会空一大块。</li><li><strong>尾巴对着角色中心</strong>（而不是矩形中心）：鱼被拖到屏幕边缘时，尾巴仍然指着它。</li><li><strong>层级分明</strong>：桌宠 9998，气泡 10002。气泡必须压在桌宠之上，因为桌宠的矩形框有透明区域，会拦截点击。</li></ul><p>至于「什么时候弹」，是一套有节制的规则：一次只弹一个，切换内容就替换；同一个信息在一个会话里不重复打扰。</p><h2 id="五、交互：点击与拖动"><a href="#五、交互：点击与拖动" class="headerlink" title="五、交互：点击与拖动"></a>五、交互：点击与拖动</h2><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">wrap.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pointerdown&#x27;</span>, ...);   <span class="comment">// setPointerCapture</span></span><br><span class="line">wrap.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pointermove&#x27;</span>, ...);   <span class="comment">// 超过 6px 才算拖</span></span><br></pre></td></tr></table></figure><ul><li><strong>6px 阈值</strong>区分「点一下」和「拖一下」，否则手抖就变成拖动，点击反应永远触发不了。</li><li><strong>位置持久化</strong>：<code>pointermove</code> 里 200ms 节流写一次 <code>localStorage</code>，松手、失焦、页面卸载各兜一次底。</li><li><strong>允许露在屏幕外</strong>：夹取边界用真实包围盒（<code>minX = -vis.l</code>），鱼可以只露半个身子在边缘，不会卡在离边缘一百像素的地方过不去。</li><li><strong>拖动时气泡跟随</strong>：按位移平移，不用重新采样，松手后精确贴边一次。</li></ul><h2 id="六、菜单：把主题的功能借过来"><a href="#六、菜单：把主题的功能借过来" class="headerlink" title="六、菜单：把主题的功能借过来"></a>六、菜单：把主题的功能借过来</h2><p>右键（触屏为长按）弹出菜单，两页：功能、表情。</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/1.avif" alt="右键菜单：功能页"></p><p>功能页除了自己的入口（公告、访客信息、友链推荐、关于我），还接管了主题原本的右侧悬浮按钮：回到顶部、跳到评论、阅读模式、切换深浅、单栏&#x2F;双栏。</p><p>做法是把那组按钮<strong>藏起来但不删掉</strong>：</p><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">@media</span> (<span class="attribute">min-width</span>: <span class="number">769px</span>) &#123; <span class="selector-id">#rightside</span> &#123; <span class="attribute">display</span>: none <span class="meta">!important</span>; &#125; &#125;</span><br></pre></td></tr></table></figure><p>菜单项只是代理点击：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;darkmode&#x27;</span>).<span class="title function_">click</span>();</span><br></pre></td></tr></table></figure><p><code>display:none</code> 的元素依然能收到 <code>.click()</code>，事件照常触发；真删了 DOM，代理就断了。移动端不藏——桌宠在 ≤768px 不显示，藏了就没有入口。</p><h2 id="七、访客信息：中文地名-英文坐标"><a href="#七、访客信息：中文地名-英文坐标" class="headerlink" title="七、访客信息：中文地名 + 英文坐标"></a>七、访客信息：中文地名 + 英文坐标</h2><p>「欢迎来自 XX 的朋友」需要两样东西：地名、距离。麻烦在于中文地名源通常不给坐标，给坐标的源通常只有英文，于是并行请求两个：</p><table><thead><tr><th>来源</th><th>提供</th><th>备注</th></tr></thead><tbody><tr><td><code>ip.zxinc.org/api.php?type=json</code></td><td>中文省市（「中国 &#x2F; 陕西省 &#x2F; 西安市」）</td><td>支持 CORS，无经纬度</td></tr><tr><td><code>api.ip.sb</code> → <code>ipapi.co</code> → <code>ipinfo.io</code></td><td>经纬度</td><td>三级降级，各 3.2 秒超时</td></tr></tbody></table><p>地名用中文源的（去掉「省&#x2F;市」后缀，显示成「陕西 西安」），距离用英文源的坐标算 Haversine。结果按会话缓存，再点秒出。</p><p>隐私上只到城市级：不显示 IP 原文，博主这边的坐标也只存市中心，距离本身就说明了一切。</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-04/3.avif" alt="访客信息气泡"></p><h2 id="八、什么时候主动说话"><a href="#八、什么时候主动说话" class="headerlink" title="八、什么时候主动说话"></a>八、什么时候主动说话</h2><p>桌宠不该话多，所以主动开口只有两个场景：</p><ul><li><strong>首次访问</strong>：用访客信息打招呼（「嘿，从 XX 飘过来的朋友 &#x2F; 离我 N 公里」+ 时段问候）。一个会话只打一次。</li><li><strong>切到文章页</strong>：等页面的 AI 摘要写完，再以「本文摘要」念一遍（最多等 10 秒，没有就退回正文首段）。</li></ul><p>公告没有自动弹，改成菜单入口——想看的自己点，不打扰不想看的人。文案的哈希会记录在 <code>sessionStorage</code> 里，改一次公告，老访客也会重新收到一次。</p><p>时段的问候语按大肥鱼的口吻写：</p><table><thead><tr><th>时间</th><th>文案</th></tr></thead><tbody><tr><td>0–6</td><td>这个点还不睡？我眼皮都快抬不起来了 😴</td></tr><tr><td>6–12</td><td>早上好呀，今天也一起摸鱼吧 🐟</td></tr><tr><td>12–18</td><td>下午好，喝口水歇会儿再卷 ☕</td></tr><tr><td>18–24</td><td>天黑啦，早点收工回家 🌙</td></tr></tbody></table><h2 id="九、和-PJAX-共存"><a href="#九、和-PJAX-共存" class="headerlink" title="九、和 PJAX 共存"></a>九、和 PJAX 共存</h2><p>主题开了 PJAX，切页时只替换 <code>#body-wrap</code>。桌宠挂在 <code>layout.pug</code> 的 body 层，不在替换范围内，所以切页不重载、不重播入场。</p><p>代价是要自己接事件：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pjax:send&#x27;</span>,     <span class="function">() =&gt;</span> &#123; <span class="title function_">hideBubble</span>(); <span class="title function_">closeMenu</span>(); &#125;);</span><br><span class="line"><span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pjax:complete&#x27;</span>, <span class="function">() =&gt;</span> &#123; <span class="title function_">maybeShowArticleSummary</span>(); &#125;);</span><br></pre></td></tr></table></figure><h2 id="十、想改的话，改哪里"><a href="#十、想改的话，改哪里" class="headerlink" title="十、想改的话，改哪里"></a>十、想改的话，改哪里</h2><table><thead><tr><th>想改什么</th><th>改哪里</th></tr></thead><tbody><tr><td>素材地址</td><td><code>themes/anzhiyu/layout/includes/pet.pug</code> 里的 <code>__BLOG_PET_BASE__</code></td></tr><tr><td>公告文案</td><td><code>_config.anzhiyu.yml</code> 的 <code>aside.card_announcement.content</code>（卡片关了也有效）</td></tr><tr><td>关于我</td><td><code>source/_data/pet_about.yml</code>（<code>&#123;years&#125;</code> 会按建站年份自算）</td></tr><tr><td>坐标 &#x2F; 距离基准</td><td><code>source/_data/pet_visitor.yml</code></td></tr><tr><td>菜单项、气泡逻辑</td><td><code>themes/anzhiyu/source/pet/pet.js</code></td></tr><tr><td>视觉样式</td><td><code>themes/anzhiyu/source/pet/pet.css</code></td></tr></tbody></table><h2 id="后记"><a href="#后记" class="headerlink" title="后记"></a>后记</h2><p>它现在做的事：点击有反应、右键菜单、公告、访客信息、友链推荐（5 秒缓冲可取消）、关于我、文章摘要，外加接管回顶&#x2F;评论&#x2F;阅读模式&#x2F;深浅&#x2F;单栏双栏。</p><p>回头看，这类”常驻小部件”的难点不在动画，而在两件事：<strong>知道自己占多大地方</strong>，以及<strong>知道什么时候该闭嘴</strong>。前者靠像素采样，后者靠一套「一次只弹一个、同一信息不重复」的规则。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%A1%8C%E5%AE%A0/">桌宠</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/11/04/8b60f883/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Twikoo 评论反垃圾实战：人机验证、频率、词表与 LLM 四层防线</title>
      <link>https://blog.eucalyptus.cc/2026/11/01/4a1a0cc/</link>
      <guid>https://blog.eucalyptus.cc/2026/11/01/4a1a0cc/</guid>
      <pubDate>Sun, 01 Nov 2026 04:45:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、凌晨的刷屏&quot;&gt;&lt;a href=&quot;#一、凌晨的刷屏&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、凌晨的刷屏"><a href="#一、凌晨的刷屏" class="headerlink" title="一、凌晨的刷屏"></a>一、凌晨的刷屏</h2><p>博客的评论区一直是”开着但没人管”的状态，直到某天早上看日志，发现凌晨被刷了一波：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/1.avif" alt="凌晨的刷屏记录"></p><p>用的是同一套 Chrome UA，评论内容一模一样，<code>accessToken</code> 全是 null —— 典型的脚本灌水，不执行 JS，直接 <code>POST</code> 一个 JSON 到 Twikoo 接口。</p><p>好在 Twikoo 默认有频率限制，这一波全被”发言频率过高”挡在了外面。但这也说明一件事：<strong>默认配置只是在苟着</strong>，稍微调松一点，或者换个 IP 池，评论区就守不住了。</p><p>于是花了一上午，把反垃圾从头配了一遍。</p><h2 id="二、关键词拦不住的那一类"><a href="#二、关键词拦不住的那一类" class="headerlink" title="二、关键词拦不住的那一类"></a>二、关键词拦不住的那一类</h2><p>垃圾评论其实有两类，很多人只防了第一类：</p><table><thead><tr><th>类型</th><th>长相</th><th>关键词能挡吗</th></tr></thead><tbody><tr><td>流量型</td><td>脚本连发、同一句话刷几十个页面</td><td>✅ 能</td></tr><tr><td>语义型</td><td>「写得真好，欢迎回访我的站点 xxx.com」</td><td>❌ 挡不住</td></tr></tbody></table><p>第二类是人（或者半自动工具）写的，不带任何敏感词，但意图明确。它过得了关键词，也过得了频率限制——因为一天就那么几条。</p><p>所以要分层：<strong>便宜的规则挡量，贵的模型挡质。</strong></p><h2 id="三、四层防线"><a href="#三、四层防线" class="headerlink" title="三、四层防线"></a>三、四层防线</h2><p>最后落地的方案是这样：</p><table><thead><tr><th>层</th><th>手段</th><th>挡什么</th></tr></thead><tbody><tr><td>1</td><td>人机验证（极验 &#x2F; Cap）</td><td>不执行 JS 的脚本</td></tr><tr><td>2</td><td>频率限制</td><td>换着页面刷的脚本</td></tr><tr><td>3</td><td>屏蔽词 &#x2F; 违禁词</td><td>带明显关键词的垃圾</td></tr><tr><td>4</td><td>LLM 语义检测</td><td>不带关键词的软广告</td></tr></tbody></table><p>再加上 <code>HIDE_SPAM=true</code>，被判为垃圾的评论前台一律不可见。</p><h2 id="四、第一层：人机验证"><a href="#四、第一层：人机验证" class="headerlink" title="四、第一层：人机验证"></a>四、第一层：人机验证</h2><h3 id="4-1-先配了极验"><a href="#4-1-先配了极验" class="headerlink" title="4.1 先配了极验"></a>4.1 先配了极验</h3><p>Twikoo 后台选「极验 Geetest」，填两个值就行：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/2.avif" alt="极验配置"></p><p>配好之后是能用的。「数据详情」里能看到验证请求数和成功数：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/3.avif" alt="极验验证数据"></p><p>前台发评论则会弹出滑块：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/4.avif" alt="极验滑块"></p><p>但还是决定换掉，原因有三个：</p><ol><li><strong>30 天试用</strong>，到期要付费，后台不显示剩余额度，说不清哪天就失效了；</li><li><strong>每次多一次跨网请求</strong>，读者要动手拖一下，多一步就少一点评论意愿；</li><li>它是”老大哥式”的验证——把访客的设备和行为数据交给第三方判断，对一个小博客来说有点重。</li></ol><h3 id="4-2-换成-Cap"><a href="#4-2-换成-Cap" class="headerlink" title="4.2 换成 Cap"></a>4.2 换成 Cap</h3><p>Cap 的思路和传统验证码相反：<strong>不是让机器做不出、人一眼能做，而是让机器也做得出来，但每条都要花算力。</strong></p><p>流程是这样：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">点发送</span><br><span class="line">  → 你的 Twikoo 容器随机出一道题，配一个一次性 token</span><br><span class="line">  → 浏览器本地算 SHA-256，凑出满足条件的答案（约 0.3 秒）</span><br><span class="line">  → 容器验答案、作废 token</span><br><span class="line">  → 通过才允许保存评论</span><br></pre></td></tr></table></figure><p>配置只要三个字段，而且后两个留空：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/5.avif" alt="Cap 配置"></p><table><thead><tr><th>字段</th><th>值</th></tr></thead><tbody><tr><td><code>CAPTCHA_PROVIDER</code></td><td><code>Cap</code></td></tr><tr><td><code>CAP_API_ENDPOINT</code></td><td>留空（留空即内嵌模式）</td></tr><tr><td><code>CAP_SECRET_KEY</code></td><td>留空</td></tr></tbody></table><p>留空是有讲究的：只要 <code>CAP_API_ENDPOINT</code> 为空，Twikoo 就会把 <code>CAP_BUILTIN</code> 置为 true，出题和判卷都走你自己的容器（日志里的 <code>CAP_CHALLENGE</code> &#x2F; <code>CAP_REDEEM</code>），<strong>不需要任何第三方服务，也没有额度</strong>。</p><p>所以读者的体验就是转半秒进度圈，什么都不用点：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/6.avif" alt="Cap 正在验证"></p><p>对脚本来说就难受了：token 一次性、不能预生成、必须真跑一遍 JS。昨晚那种 <code>curl</code> 直发的请求，连题都拿不到。</p><h3 id="4-3-把前端组件也搬到本地"><a href="#4-3-把前端组件也搬到本地" class="headerlink" title="4.3 把前端组件也搬到本地"></a>4.3 把前端组件也搬到本地</h3><p>内嵌模式下，前端还需要一个 <code>&lt;cap-widget&gt;</code> 自定义元素来画界面。Twikoo 默认是从 <code>cdn.jsdmirror.com</code> ，可以把组件拿下来自己托管：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 下载（放哪儿都行，这里放站点的 cdn 目录）</span></span><br><span class="line">curl -sL https://cdn.jsdmirror.com/npm/@cap.js/widget -o <span class="built_in">source</span>/cdn/js/cap-widget.js</span><br></pre></td></tr></table></figure><p>然后在 <code>themes/anzhiyu/layout/includes/additional-js.pug</code> 里加一行：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">//- Cap 人机验证组件（本地自托管；已注册 cap-widget 时 Twikoo 会跳过 CDN）</span><br><span class="line">script(defer src=url_for(&#x27;/cdn/js/cap-widget.js&#x27;))</span><br></pre></td></tr></table></figure><p>Twikoo 加载前会先查 <code>customElements.get(&#39;cap-widget&#39;)</code>，已经注册过就直接跳过 CDN，等于零外部依赖。</p><h2 id="五、第二层：频率限制"><a href="#五、第二层：频率限制" class="headerlink" title="五、第二层：频率限制"></a>五、第二层：频率限制</h2><p>两个字段，单位都是「条 &#x2F; 10 分钟」：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/8.avif" alt="频率限制"></p><table><thead><tr><th>字段</th><th>值</th><th>含义</th></tr></thead><tbody><tr><td><code>LIMIT_PER_MINUTE</code></td><td>5</td><td>单个 IP 每 10 分钟最多 5 条</td></tr><tr><td><code>LIMIT_PER_MINUTE_ALL</code></td><td>30</td><td>全站每 10 分钟最多 30 条</td></tr></tbody></table><p>名字里带 <code>MINUTE</code> 但实际窗口是 10 分钟，别被误导。</p><p>单 IP 取 5：正常读者十分钟内连发 5 条已经很罕见，而脚本一秒钟就能发 3 条。全站取 30 是兜底——万一攻击者换 IP，也不至于把整个评论区打满。</p><h2 id="六、第三层：词表"><a href="#六、第三层：词表" class="headerlink" title="六、第三层：词表"></a>六、第三层：词表</h2><p>Twikoo 有两个词表，效果完全不同，很多人会搞混：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/9.avif" alt="词表配置"></p><table><thead><tr><th>字段</th><th>命中后</th><th>适用</th></tr></thead><tbody><tr><td><code>BLOCKED_WORDS</code></td><td>评论<strong>直接提交失败</strong></td><td>明确的广告词，几乎不会误伤</td></tr><tr><td><code>FORBIDDEN_WORDS</code></td><td>评论照常发出，但<strong>标记为垃圾</strong></td><td>模糊词，可能误伤，靠后台恢复</td></tr></tbody></table><p>配好之后，带屏蔽词的评论会直接提交失败，前台提示「包含屏蔽词」，这条根本不会入库。</p><p>有两个细节值得记一下：</p><ol><li><strong>分隔符是英文逗号</strong>，中文逗号会被当成词的一部分。</li><li><strong>匹配是”包含”，不分词</strong>，所以短词必误伤。比如别写 <code>av</code>——它会命中 <code>JavaScript</code>；也别写”兼职””资源”这种正常讨论里常见的词。</li></ol><p>所以我的做法是：长而独特的词进 <code>BLOCKED_WORDS</code>，模糊的、可能误伤的进 <code>FORBIDDEN_WORDS</code>。</p><h2 id="七、第四层：让大模型做裁判"><a href="#七、第四层：让大模型做裁判" class="headerlink" title="七、第四层：让大模型做裁判"></a>七、第四层：让大模型做裁判</h2><h3 id="为什么是-LLM"><a href="#为什么是-LLM" class="headerlink" title="为什么是 LLM"></a>为什么是 LLM</h3><p>Twikoo 支持四种外部检测，优先级是固定的：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">腾讯云内容安全 &gt; Akismet &gt; Jev &gt; LLM</span><br></pre></td></tr></table></figure><p>同时配多个不会叠加，只有最前面那个生效。</p><ul><li><strong>腾讯云</strong>：涉政涉黄这类合规判定最准，但要实名、要密钥、按量计费（25 元&#x2F;万条）；</li><li><strong>Akismet</strong>：个人博客免费，但中文库弱，而且评论内容要发到国外；</li><li><strong>LLM</strong>：填一个 API key 就行，中文语义好，价格比腾讯云还便宜。</li></ul><p>对一个一天几条评论的博客来说，LLM 的性价比最高，而且不用多养一个云账号。</p><h3 id="配置"><a href="#配置" class="headerlink" title="配置"></a>配置</h3><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/11.avif" alt="LLM 配置"></p><table><thead><tr><th>字段</th><th>值</th></tr></thead><tbody><tr><td><code>LLM_API_KEY</code></td><td>你的 DeepSeek key</td></tr><tr><td><code>LLM_API_ENDPOINT</code></td><td>留空（默认 <code>https://api.deepseek.com/v1</code>）</td></tr><tr><td><code>LLM_MODEL</code></td><td>留空，或用你账号可用的模型名</td></tr><tr><td><code>LLM_REQUEST_EXTRA_JSON</code></td><td><code>&#123;&quot;reasoning_effort&quot;:&quot;none&quot;,&quot;temperature&quot;:0&#125;</code></td></tr></tbody></table><p>最后那个字段是合进请求体的额外参数：</p><ul><li><code>temperature: 0</code>：分类任务要稳定，同一条评论不能今天判垃圾、明天判正常；</li><li><code>reasoning_effort: none</code>：推理型模型默认会先吐一大段思考过程，JSON 混在中间就解析失败，关掉它直接出答案。</li></ul><p>注意它是<strong>整段忽略</strong>语义：JSON 语法错一个字符，整条配置就失效了，而且不报错。</p><h3 id="它按什么标准判"><a href="#它按什么标准判" class="headerlink" title="它按什么标准判"></a>它按什么标准判</h3><p>内置提示词里写得很明确，判垃圾的有六类：</p><ol><li>商业广告 &#x2F; 推广 &#x2F; 买卖（代开发票、加微信、兼职、办证……）</li><li><strong>昵称像广告 + 留了网址</strong>（正文再正常也判垃圾）</li><li>无意义灌水（顶顶顶、111111、asdfgh）</li><li>辱骂 &#x2F; 侮辱性用语</li><li>网址字段里的可疑链接、SEO 垃圾</li><li>机器人式模板问候</li></ol><p>判定范围是<strong>正文、昵称、网址三个字段全看</strong>。这就是它比关键词强的地方：正文写得人模人样，昵称是”加微信领福利”，还留了个外链——关键词一个都不命中，模型一眼看穿。</p><p>想调整尺度，可以自己写 <code>LLM_SPAM_PROMPT</code>，但它是<strong>整段替换</strong>，新提示词必须自带「只输出 JSON」的约束，否则会一直校验失败。</p><h3 id="成本"><a href="#成本" class="headerlink" title="成本"></a>成本</h3><p>一条评论几百 token，<strong>大约几毛钱一千条</strong>。一天 10 条评论的话，一年不到五块钱。</p><h2 id="八、怎么验证真的生效了"><a href="#八、怎么验证真的生效了" class="headerlink" title="八、怎么验证真的生效了"></a>八、怎么验证真的生效了</h2><p>反垃圾最怕的是”以为配了其实没配”。Twikoo 的两个特性让这件事特别隐蔽：</p><ol><li>管理员发的评论<strong>跳过所有检测</strong>（<code>isAdminUser</code> 为 true 时直接 <code>isSpam = false</code>），所以自己登录着测永远测不出来；</li><li>检测失败是 <code>try/catch</code> 静默吞掉的，日志记一行，评论照常显示。</li></ol><p>所以只能看日志：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker logs twikoo --since 24h 2&gt;&amp;1 | grep -E <span class="string">&quot;LLM 判定|垃圾评论检测异常|包含屏蔽词&quot;</span></span><br></pre></td></tr></table></figure><p>正常的输出长这样：</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-11-01/12.avif" alt="LLM 判定日志"></p><ul><li><code>LLM 判定为 SPAM</code> → 通了</li><li><code>垃圾评论检测异常</code> → 挂了（密钥错、欠费、模型名不对）</li></ul><p>测试的时候记住：<strong>必须无痕窗口</strong>（非管理员身份），而且要发一条<strong>不含任何关键词</strong>的广告，否则会被第三层提前拦掉，根本走不到第四层。</p><h2 id="九、最终配置"><a href="#九、最终配置" class="headerlink" title="九、最终配置"></a>九、最终配置</h2><p>所有配置都在 Twikoo 后台 → 设置里，整理成一张表：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line">人机验证</span><br><span class="line">  CAPTCHA_PROVIDER      = Cap</span><br><span class="line">  CAP_API_ENDPOINT      = （留空）</span><br><span class="line">  CAP_SECRET_KEY        = （留空）</span><br><span class="line"></span><br><span class="line">反垃圾</span><br><span class="line">  LIMIT_PER_MINUTE      = 5</span><br><span class="line">  LIMIT_PER_MINUTE_ALL  = 30</span><br><span class="line">  LIMIT_LENGTH          = 500</span><br><span class="line">  BLOCKED_WORDS         = 代发,加微信,加QQ,刷单,日结,网赚,办证,...</span><br><span class="line">  FORBIDDEN_WORDS       = 优惠券,免费领取,点击链接,扫码,福利,推广,广告,...</span><br><span class="line">  NOTIFY_SPAM           = true</span><br><span class="line">  HIDE_SPAM             = true</span><br><span class="line"></span><br><span class="line">AI 检测</span><br><span class="line">  LLM_API_KEY           = sk-xxxxxxxx</span><br><span class="line">  LLM_REQUEST_EXTRA_JSON= &#123;&quot;reasoning_effort&quot;:&quot;none&quot;,&quot;temperature&quot;:0&#125;</span><br></pre></td></tr></table></figure><h2 id="小结"><a href="#小结" class="headerlink" title="小结"></a>小结</h2><p>三层免费的规则 + 一层便宜的模型，加起来一年不到十块钱，把评论区的垃圾率压到了零。</p><p>几个值得记住的点：</p><ul><li><strong>极验能用，但更适合有预算的站</strong>；个人博客 Cap 足够，还免费；</li><li><strong>管理员测不出反垃圾</strong>，一定要无痕；</li><li><strong>关键词按”包含”匹配</strong>，短词必误伤；</li><li><strong>外部检测只生效一个</strong>，别以为能叠加；</li><li><strong>失败是静默的</strong>，定期 grep 一下日志；</li><li>验证码挡住的是脚本，语义层挡住的是人，两层缺一不可。</li></ul><p>评论区清净了，才有心情继续写东西。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Twikoo/">Twikoo</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/11/01/4a1a0cc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>AI 助手 2.0：多轮对话、卡片化与文章页感知</title>
      <link>https://blog.eucalyptus.cc/2026/10/31/16077c3f/</link>
      <guid>https://blog.eucalyptus.cc/2026/10/31/16077c3f/</guid>
      <pubDate>Sat, 31 Oct 2026 11:40:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;六月份的时候给博客装了一个首页 AI 小助手，记录在 &lt;div class=&#39;anzhiyu-tag-link&#39;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>六月份的时候给博客装了一个首页 AI 小助手，记录在 <div class='anzhiyu-tag-link'><a class="tag-Link"  href="/2026/06/28/1133165e/">    <div class="tag-link-tips">站内地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://img.eucalyptus.cc/images/logo.png" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://img.eucalyptus.cc/images/logo.png" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">基于 Node.js + 大模型的 AI 客服系统</div>            <div class="tag-link-sitename">blog.eucalyptus.cc</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div> 里：Express 起一个 5004 端口的服务，抓 RSS 建文章索引，SSE 流式把大模型的回复吐给前端，前端在右下角挂一个对话窗。</p><p>用了四个月，功能没坏，但体验上的毛病越攒越多。这一轮集中修了一遍，顺手把几个”其实一直在丢数据”的 bug 也挖出来了。这篇按问题拆开写，代码都是线上跑着的版本。</p><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-10-31/1.avif" alt="文章页打开对话框：提示「你正在看《…》」，快捷按钮跟着变成「本文摘要 &#x2F; 文章推荐 &#x2F; 关于我」"></p><h2 id="一次对话暴露的六个问题"><a href="#一次对话暴露的六个问题" class="headerlink" title="一次对话暴露的六个问题"></a>一次对话暴露的六个问题</h2><p>随便找一段真实对话，问题就很密集：</p><ol><li>问「有推荐的文章吗」，正文里又列了一遍文章清单，<strong>而卡片区已经展示了同样三篇</strong>，重复；</li><li>清单里还夹着一坨 <code>&lt;a href=&quot;…&quot;&gt;标题&lt;/a&gt;</code> 字面量 —— 前端不转义，模型输出的标签直接被当成文本显示出来；</li><li>问「有推荐的友链吗」，答「没找到和友链相关的文章」—— 它只会在文章库里找，压根没有友链这个概念；</li><li>回复结尾全是 emoji，开头还莫名其妙是个逗号「，我这边暂时没有…」；</li><li>问「这篇讲什么」，它不知道你在看哪篇；</li><li>换一篇文章再问，前面那篇的上下文还在，答非所问。</li></ol><p>第 4 条的开头逗号最迷惑，排查后发现不是模型的问题，是<strong>前端丢了一个 SSE 分片</strong>：第一个 chunk 只用于显示、没累加进 <code>fullReply</code>，第二个 chunk 到达时用 <code>fullReply</code> 覆盖，首位就被吃掉了。模型说的其实是「抱歉呀，我这边暂时…」，显示成了「，我这边暂时…」。</p><h2 id="改法总览"><a href="#改法总览" class="headerlink" title="改法总览"></a>改法总览</h2><table><thead><tr><th>问题</th><th>改法</th><th>落点</th></tr></thead><tbody><tr><td>正文罗列文章清单</td><td>提示词禁止，清单交给卡片</td><td><code>server.js</code> <code>buildSystemPrompt()</code></td></tr><tr><td><code>&lt;a&gt;</code> 标签字面量</td><td>渲染前先剥 HTML 标签</td><td><code>ai-chatbot.js</code> <code>renderMarkdown()</code></td></tr><tr><td>emoji &#x2F; 开头标点</td><td>提示词约束 + 前端 <code>tidyReply()</code> 兜底</td><td>同上</td></tr><tr><td>友链问不到</td><td><code>link.yml</code> 生成 <code>flinks.json</code>，固定话术</td><td><code>ai_bot/tools/gen_flinks.js</code></td></tr><tr><td>不知道在看哪篇</td><td>前端传 <code>location.pathname</code>，后端找文章取摘要</td><td><code>buildCurrentReply()</code></td></tr><tr><td>换页串台</td><td>pjax &#x2F; popstate 时清空会话</td><td><code>resetConversation()</code></td></tr></tbody></table><h2 id="让回复像人：口径要写死"><a href="#让回复像人：口径要写死" class="headerlink" title="让回复像人：口径要写死"></a>让回复像人：口径要写死</h2><p>原来的系统提示词里有一句「推荐文章时必须使用 HTML 超链接格式：<code>&lt;a href=&quot;文章链接&quot;&gt;文章标题&lt;/a&gt;</code>」——这就是第 1、2 条问题的直接来源。改成两个分支：有匹配文章时，明确告诉模型”链接由卡片展示，正文别列清单”；没有匹配时，禁止编造文章标题。</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">buildSystemPrompt</span>(<span class="params">articlesContext</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> hasArticles = <span class="title class_">Boolean</span>(articlesContext &amp;&amp; articlesContext.<span class="title function_">trim</span>());</span><br><span class="line"></span><br><span class="line">  <span class="keyword">const</span> articleRules = hasArticles</span><br><span class="line">    ? <span class="string">`- 相关文章会由页面底部的「相关文章推荐」卡片自动展示，所以正文里不要罗列文章标题清单，也不要输出链接、Markdown 链接或 &lt;a&gt; 标签</span></span><br><span class="line"><span class="string">- 只有读者明确问起某篇具体文章时，才可以自然提一次标题，但不要附带链接</span></span><br><span class="line"><span class="string">- 读者问某篇文章讲了什么时，直接用上面给出的「内容摘要」概括 1-2 句`</span></span><br><span class="line">    : <span class="string">`- 当前没有可引用的博客文章，就用自己的知识回答，但不要编造或罗列博客里并不存在的文章标题`</span>;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">return</span> <span class="string">`你是<span class="subst">$&#123;config.BOT_NAME&#125;</span>… <span class="subst">$&#123;articlesContext&#125;</span> …<span class="subst">$&#123;articleRules&#125;</span>`</span>;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>emoji 和开头标点属于”模型偶尔不听话”的类型，提示词之外还得有兜底。前端拿到文本先过一道 <code>tidyReply()</code>：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">tidyReply</span>(<span class="params">text</span>) &#123;</span><br><span class="line">  <span class="comment">// 去掉 emoji / 符号表情</span></span><br><span class="line">  <span class="keyword">var</span> out = <span class="title class_">String</span>(text).<span class="title function_">replace</span>(<span class="regexp">/[\u&#123;1F000&#125;-\u&#123;1FAFF&#125;\u&#123;2600&#125;-\u&#123;27BF&#125;\u&#123;2B00&#125;-\u&#123;2BFF&#125;\u&#123;FE0F&#125;\u&#123;200D&#125;]/gu</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">  <span class="comment">// 每行行首的标点（列表的 &quot;-&quot; 要保留）</span></span><br><span class="line">  out = out.<span class="title function_">split</span>(<span class="string">&#x27;\n&#x27;</span>).<span class="title function_">map</span>(<span class="keyword">function</span> (<span class="params">line</span>) &#123;</span><br><span class="line">    <span class="keyword">return</span> line.<span class="title function_">replace</span>(<span class="regexp">/^[\s，。、；：,.!?！？;:~～…—]+/</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">  &#125;).<span class="title function_">join</span>(<span class="string">&#x27;\n&#x27;</span>);</span><br><span class="line">  <span class="keyword">return</span> out.<span class="title function_">replace</span>(<span class="regexp">/[ \t]&#123;2,&#125;/g</span>, <span class="string">&#x27; &#x27;</span>).<span class="title function_">trim</span>();</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>实测四种输入：<code>，我这边暂时没有…😄 所以没法介绍</code> → <code>我这边暂时没有… 所以没法介绍</code>；<code>😅 好的，下面说说：「技术」</code> → <code>好的，下面说说：「技术」</code>；<code>  ~ 直接回答，没问题。</code> 正常；列表行 <code>- [Bensz](…)</code> 的 <code>-</code> 保留。</p><h2 id="卡片化：文章和友链共用一套样式"><a href="#卡片化：文章和友链共用一套样式" class="headerlink" title="卡片化：文章和友链共用一套样式"></a>卡片化：文章和友链共用一套样式</h2><p>后端不再把清单塞进正文，改成结构化字段：<code>relevant_articles</code>（文章）和 <code>relevant_links</code>（友链）。前端两个构造函数：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">buildArticleCards</span>(<span class="params">articles, title</span>) &#123;</span><br><span class="line">  <span class="keyword">var</span> html = <span class="string">&#x27;&lt;div class=&quot;ai-chatbot-articles&quot;&gt;&lt;div class=&quot;ai-chatbot-articles-title&quot;&gt;&#x27;</span> + (title || <span class="string">&#x27;相关文章推荐：&#x27;</span>) + <span class="string">&#x27;&lt;/div&gt;&#x27;</span>;</span><br><span class="line">  articles.<span class="title function_">forEach</span>(<span class="keyword">function</span> (<span class="params">a</span>) &#123;</span><br><span class="line">    html += <span class="string">&#x27;&lt;a class=&quot;ai-chatbot-article-card&quot; href=&quot;&#x27;</span> + a.<span class="property">url</span> + <span class="string">&#x27;&quot; target=&quot;_blank&quot;&gt;&#x27;</span></span><br><span class="line">      + <span class="string">&#x27;&lt;div class=&quot;ai-chatbot-article-body&quot;&gt;&#x27;</span></span><br><span class="line">      + <span class="string">&#x27;&lt;div class=&quot;ai-chatbot-article-title&quot;&gt;&#x27;</span> + a.<span class="property">title</span> + <span class="string">&#x27;&lt;/div&gt;&#x27;</span></span><br><span class="line">      + (a.<span class="property">tags</span> &amp;&amp; a.<span class="property">tags</span>.<span class="property">length</span> ? <span class="string">&#x27;&lt;div class=&quot;ai-chatbot-article-tags&quot;&gt;&#x27;</span> + <span class="title function_">tags</span>(a.<span class="property">tags</span>) + <span class="string">&#x27;&lt;/div&gt;&#x27;</span> : <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">      + <span class="string">&#x27;&lt;/div&gt;&lt;/a&gt;&#x27;</span>;</span><br><span class="line">  &#125;);</span><br><span class="line">  <span class="keyword">return</span> html + <span class="string">&#x27;&lt;/div&gt;&#x27;</span>;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>这里踩了个小坑：标签 <code>&lt;span&gt;</code> 之前是卡片的直接子元素，而卡片是 <code>display:flex; align-items:stretch</code>，于是每个标签被拉成一根<strong>竖条</strong>（<code>#Hexo</code> 竖着排）。包一层 <code>.ai-chatbot-article-tags</code> 才恢复成横排小胶囊。</p><p>首页点「文章推荐」，三张卡片带着标签横排出来：</p><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-10-31/3.avif" alt="首页点「文章推荐」：最新三篇以卡片渲染，标签横排"></p><h2 id="多轮对话"><a href="#多轮对话" class="headerlink" title="多轮对话"></a>多轮对话</h2><p>前端在内存里记最近 3 轮，随请求发 <code>history</code>；同时把上一轮卡片里的文章 url 回传，后端据此还原出带摘要的文章对象，这样「第一篇讲什么」「这篇再细说」这类自己匹配不到关键词的追问也能答。</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 前端</span></span><br><span class="line"><span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(&#123;</span><br><span class="line">  <span class="attr">message</span>: message,</span><br><span class="line">  <span class="attr">history</span>: chatHistory.<span class="title function_">slice</span>(-<span class="variable constant_">HISTORY_TURNS</span> * <span class="number">2</span>),</span><br><span class="line">  <span class="attr">context_articles</span>: lastArticles.<span class="title function_">map</span>(<span class="keyword">function</span> (<span class="params">a</span>) &#123; <span class="keyword">return</span> &#123; <span class="attr">url</span>: a.<span class="property">url</span> &#125;; &#125;),</span><br><span class="line">  <span class="attr">page</span>: location.<span class="property">pathname</span> || <span class="string">&#x27;&#x27;</span>,</span><br><span class="line">  <span class="attr">client</span>: <span class="number">2</span></span><br><span class="line">&#125;)</span><br></pre></td></tr></table></figure><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 后端：历史上限 8 条、每条 600 字</span></span><br><span class="line"><span class="keyword">function</span> <span class="title function_">normalizeHistory</span>(<span class="params">history</span>) &#123;</span><br><span class="line">  <span class="keyword">return</span> (<span class="title class_">Array</span>.<span class="title function_">isArray</span>(history) ? history : [])</span><br><span class="line">    .<span class="title function_">filter</span>(<span class="function"><span class="params">h</span> =&gt;</span> h &amp;&amp; (h.<span class="property">role</span> === <span class="string">&#x27;user&#x27;</span> || h.<span class="property">role</span> === <span class="string">&#x27;assistant&#x27;</span>) &amp;&amp; <span class="keyword">typeof</span> h.<span class="property">content</span> === <span class="string">&#x27;string&#x27;</span>)</span><br><span class="line">    .<span class="title function_">map</span>(<span class="function"><span class="params">h</span> =&gt;</span> (&#123; <span class="attr">role</span>: h.<span class="property">role</span>, <span class="attr">content</span>: h.<span class="property">content</span>.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">600</span>) &#125;))</span><br><span class="line">    .<span class="title function_">slice</span>(-<span class="number">8</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">// 当前句子没匹配到文章时，回落到上一轮卡片里的文章</span></span><br><span class="line"><span class="keyword">const</span> matched = <span class="title function_">findRelevantArticles</span>(message);</span><br><span class="line"><span class="keyword">const</span> relevantArticles = matched.<span class="property">length</span> ? matched : <span class="title function_">resolveContextArticles</span>(contextArticles);</span><br></pre></td></tr></table></figure><h2 id="友链：别让模型编链接"><a href="#友链：别让模型编链接" class="headerlink" title="友链：别让模型编链接"></a>友链：别让模型编链接</h2><p>友链数据本来就在博客的 <code>source/_data/link.yml</code> 里，写个脚本转成 <code>ai_chatbot/flinks.json</code>：跳过「失联」分组和本站自己，<code>recommend: true</code> 的排前面（共 11 条）。</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// ai_bot/tools/gen_flinks.js</span></span><br><span class="line"><span class="keyword">for</span> (<span class="keyword">const</span> group <span class="keyword">of</span> groups) &#123;</span><br><span class="line">  <span class="keyword">if</span> (!group || group.<span class="property">lost_contact</span>) <span class="keyword">continue</span>;</span><br><span class="line">  <span class="keyword">for</span> (<span class="keyword">const</span> item <span class="keyword">of</span> group.<span class="property">link_list</span> || []) &#123;</span><br><span class="line">    <span class="keyword">if</span> (item.<span class="property">link</span>.<span class="title function_">replace</span>(<span class="regexp">/\/+$/</span>, <span class="string">&#x27;&#x27;</span>) === selfUrl) <span class="keyword">continue</span>;   <span class="comment">// 不推荐自己</span></span><br><span class="line">    links.<span class="title function_">push</span>(&#123; <span class="attr">name</span>: item.<span class="property">name</span>, <span class="attr">url</span>: item.<span class="property">link</span>, <span class="attr">descr</span>: item.<span class="property">descr</span>, <span class="attr">recommend</span>: item.<span class="property">recommend</span> === <span class="literal">true</span> &#125;);</span><br><span class="line">  &#125;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>命中 <code>友链|友情链接|flink|推荐博主</code> 这类问法时<strong>不调模型</strong>，直接返回前 3 条真实链接，标题走卡片。这样既省钱又不可能编错。</p><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-10-31/4.avif" alt="点「友链推荐」：三张友链卡片，名字 + 一句话描述，整张可点"></p><h2 id="自我介绍也做了点小工程"><a href="#自我介绍也做了点小工程" class="headerlink" title="自我介绍也做了点小工程"></a>自我介绍也做了点小工程</h2><p>「关于我」是一段固定文案，但里面「建站 1583 天」这种数字写死就会过期。做法是在 <code>faq.json</code> 里存建站日，答案里用占位符，返回时实时替换：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">siteDays</span>(<span class="params"></span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> launch = faqData.<span class="property">site</span>.<span class="property">launch</span>;                     <span class="comment">// 2022-07-01</span></span><br><span class="line">  <span class="keyword">return</span> <span class="title class_">Math</span>.<span class="title function_">max</span>(<span class="number">0</span>, <span class="title class_">Math</span>.<span class="title function_">floor</span>((<span class="title class_">Date</span>.<span class="title function_">now</span>() - <span class="keyword">new</span> <span class="title class_">Date</span>(launch + <span class="string">&#x27;T00:00:00+08:00&#x27;</span>)) / <span class="number">86400000</span>));</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">function</span> <span class="title function_">renderAnswer</span>(<span class="params">text</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> days = <span class="title function_">siteDays</span>();</span><br><span class="line">  <span class="keyword">return</span> text</span><br><span class="line">    .<span class="title function_">replace</span>(<span class="regexp">/\&#123;days\&#125;/g</span>, <span class="function">() =&gt;</span> <span class="title class_">String</span>(days))</span><br><span class="line">    .<span class="title function_">replace</span>(<span class="regexp">/\&#123;years\&#125;/g</span>, <span class="function">() =&gt;</span> <span class="title class_">String</span>(<span class="title class_">Math</span>.<span class="title function_">max</span>(<span class="number">1</span>, <span class="title class_">Math</span>.<span class="title function_">floor</span>(days / <span class="number">365</span>))));</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>现在文案里写的是「它已经陪了我 {years} 年」，今天算出 4，明年自动变 5。</p><h2 id="文章页感知：直接复用已有的-AI-摘要"><a href="#文章页感知：直接复用已有的-AI-摘要" class="headerlink" title="文章页感知：直接复用已有的 AI 摘要"></a>文章页感知：直接复用已有的 AI 摘要</h2><p>文章页本来就有一块 AI 摘要（另一套服务生成，存在 Redis 里，键是 <code>ai:summary:p:&lt;abbrlink&gt;</code>）。所以机器人不需要重新生成一份：</p><ol><li>前端把 <code>location.pathname</code> 带上，形如 <code>/2024/09/04/43948a6a/</code>；</li><li>后端取最后一段当 abbrlink，在 RSS 文章表里定位；</li><li>调 <code>http://127.0.0.1:3000/api/summary?key=p:&lt;abbrlink&gt;</code> 拿现成摘要，内网失败回落公网域名；</li><li>都没命中就退回 RSS 正文前 180 字，文案从「的摘要」改成「大致讲了」，不假装有摘要。</li></ol><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">fetchAiSummary</span>(<span class="params">abbr</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> hit = summaryCache.<span class="title function_">get</span>(abbr);</span><br><span class="line">  <span class="keyword">if</span> (hit &amp;&amp; <span class="title class_">Date</span>.<span class="title function_">now</span>() - hit.<span class="property">at</span> &lt; <span class="variable constant_">SUMMARY_CACHE_TTL</span>) <span class="keyword">return</span> hit.<span class="property">text</span>;   <span class="comment">// 10 分钟内存缓存</span></span><br><span class="line">  <span class="keyword">for</span> (<span class="keyword">const</span> base <span class="keyword">of</span> <span class="variable constant_">SUMMARY_ENDPOINTS</span>) &#123;</span><br><span class="line">    <span class="keyword">try</span> &#123;</span><br><span class="line">      <span class="keyword">const</span> resp = <span class="keyword">await</span> axios.<span class="title function_">get</span>(base, &#123; <span class="attr">params</span>: &#123; <span class="attr">key</span>: <span class="string">&#x27;p:&#x27;</span> + abbr &#125;, <span class="attr">timeout</span>: <span class="number">1500</span> &#125;);</span><br><span class="line">      <span class="keyword">if</span> (resp.<span class="property">data</span> &amp;&amp; resp.<span class="property">data</span>.<span class="property">summary</span>) <span class="keyword">return</span> resp.<span class="property">data</span>.<span class="property">summary</span>.<span class="title function_">trim</span>();</span><br><span class="line">    &#125; <span class="keyword">catch</span> (e) &#123; <span class="comment">/* 换下一个源 */</span> &#125;</span><br><span class="line">  &#125;</span><br><span class="line">  <span class="keyword">return</span> <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>文章页打开对话框时，欢迎气泡会多一句「你正在看《…》，想看内容概要就点「本文摘要」」，快捷按钮也多一个「本文摘要」。首页没有这个按钮。</p><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-10-31/2.avif" alt="点「本文摘要」：直接复用文章页那份 AI 摘要，末尾附文章卡片"></p><p>不在文章页时如果有人点（比如浏览器还缓存着旧页面），也不会掉进模型乱答，后端直接回一句兜底话术。</p><h2 id="换页就清空"><a href="#换页就清空" class="headerlink" title="换页就清空"></a>换页就清空</h2><p>本站是 pjax，站内跳转不重载页面，对话窗是全局固定元素，所以状态会跨页残留：在 A 文章页打开、跳到 B，气泡里还写着「你正在看《A》」。</p><p>改法是记住渲染时的路径，<code>pjax:complete / pjax:success / pjax:end</code> 和 <code>popstate</code> 都挂上同步逻辑：路径变了就清空对话（保留欢迎气泡）+ 清空 <code>chatHistory</code> &#x2F; <code>lastArticles</code>，再按新页面重铺欢迎块。</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">syncIntroToPage</span>(<span class="params"></span>) &#123; <span class="keyword">if</span> (chatbotOpen) <span class="title function_">loadIntro</span>(); &#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">function</span> <span class="title function_">loadIntro</span>(<span class="params"></span>) &#123;</span><br><span class="line">  <span class="keyword">var</span> pagePath = <span class="title function_">currentPath</span>();</span><br><span class="line">  <span class="keyword">if</span> (introLoaded &amp;&amp; introPage === pagePath) <span class="keyword">return</span>;      <span class="comment">// 同页反复开合，不重复请求</span></span><br><span class="line">  <span class="keyword">if</span> (introPage &amp;&amp; introPage !== pagePath) <span class="title function_">resetConversation</span>();  <span class="comment">// 换页：清空上一篇的对话</span></span><br><span class="line">  introPage = pagePath;</span><br><span class="line">  <span class="comment">// …fetch intro、渲染 hint + chips</span></span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><h2 id="两个真会咬人的-bug"><a href="#两个真会咬人的-bug" class="headerlink" title="两个真会咬人的 bug"></a>两个真会咬人的 bug</h2><h3 id="1-流式解析把半截-JSON-丢了"><a href="#1-流式解析把半截-JSON-丢了" class="headerlink" title="1. 流式解析把半截 JSON 丢了"></a>1. 流式解析把半截 JSON 丢了</h3><p>错误日志里攒了 <strong>56 条</strong> <code>Parse stream error</code>，最早能追到 7 月。原因：上游是 br 压缩流，<code>data</code> 事件的分片边界不按行切，而代码对每个 chunk 直接 <code>split(&#39;\n&#39;)</code> 再 <code>JSON.parse</code>，半截 JSON 必然抛错被丢掉——表现就是<strong>回复里少几个字</strong>，肉眼很难发现。</p><p>修法是按字节缓冲、只在遇到换行符时才取整行：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">let</span> rawBuf = <span class="title class_">Buffer</span>.<span class="title function_">alloc</span>(<span class="number">0</span>);</span><br><span class="line"></span><br><span class="line">response.<span class="property">data</span>.<span class="title function_">on</span>(<span class="string">&#x27;data&#x27;</span>, <span class="function">(<span class="params">chunk</span>) =&gt;</span> &#123;</span><br><span class="line">  rawBuf = <span class="title class_">Buffer</span>.<span class="title function_">concat</span>([rawBuf, chunk]);</span><br><span class="line">  <span class="keyword">let</span> idx;</span><br><span class="line">  <span class="keyword">while</span> ((idx = rawBuf.<span class="title function_">indexOf</span>(<span class="number">10</span>)) !== -<span class="number">1</span>) &#123;           <span class="comment">// 0x0A</span></span><br><span class="line">    <span class="keyword">const</span> line = rawBuf.<span class="title function_">subarray</span>(<span class="number">0</span>, idx).<span class="title function_">toString</span>(<span class="string">&#x27;utf8&#x27;</span>);</span><br><span class="line">    rawBuf = rawBuf.<span class="title function_">subarray</span>(idx + <span class="number">1</span>);</span><br><span class="line">    <span class="title function_">handleSseLine</span>(line);                                 <span class="comment">// 只处理完整行</span></span><br><span class="line">  &#125;</span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><p>验证方式是写了个假上游，把 SSE 内容 brotli 压缩后按 <strong>7 字节</strong>一片发出去（边界故意落在 JSON 中间和汉字中间），旧逻辑必丢字，新逻辑三个分片全对：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">chunk events: 3</span><br><span class="line">assembled: 你好，这是完整回复，没有丢字。</span><br></pre></td></tr></table></figure><h3 id="2-DONE-之后再写一次，进程直接崩"><a href="#2-DONE-之后再写一次，进程直接崩" class="headerlink" title="2. [DONE] 之后再写一次，进程直接崩"></a>2. <code>[DONE]</code> 之后再写一次，进程直接崩</h3><p><code>/api/chat/stream</code> 在收到 <code>[DONE]</code> 时 <code>res.end()</code>，随后上游连接 <code>end</code> 事件又 <code>res.write</code> 一次，抛 <code>ERR_STREAM_WRITE_AFTER_END</code>。这是<strong>未捕获的 error 事件</strong>，node 进程当场退出，pm2 只是把它拉起来。</p><p>商汤那档不发 <code>[DONE]</code>，所以线上一直没炸；但面板里把模型切到 DeepSeek（OpenAI 兼容、会发 <code>[DONE]</code>）就会每轮对话崩一次。</p><p>修法是收尾幂等：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">let</span> clientEnded = <span class="literal">false</span>;</span><br><span class="line"><span class="keyword">const</span> <span class="title function_">endClient</span> = (<span class="params">payload</span>) =&gt; &#123;</span><br><span class="line">  <span class="keyword">if</span> (clientEnded) <span class="keyword">return</span>;</span><br><span class="line">  clientEnded = <span class="literal">true</span>;</span><br><span class="line">  <span class="keyword">try</span> &#123; <span class="keyword">if</span> (payload) res.<span class="title function_">write</span>(<span class="string">`data: <span class="subst">$&#123;<span class="built_in">JSON</span>.stringify(payload)&#125;</span>\n\n`</span>); res.<span class="title function_">end</span>(); &#125;</span><br><span class="line">  <span class="keyword">catch</span> (e) &#123; <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;SSE close error:&#x27;</span>, e.<span class="property">message</span>); &#125;</span><br><span class="line">&#125;;</span><br></pre></td></tr></table></figure><p>本地连打 3 次流式请求，进程存活（<code>AI Chatbot Service Running</code>）。</p><h2 id="兼容与上线"><a href="#兼容与上线" class="headerlink" title="兼容与上线"></a>兼容与上线</h2><p>前端更新、后端先上线，中间有一段时间是”新后端 + 老前端”。所以加了版本号：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 前端</span></span><br><span class="line"><span class="attr">client</span>: <span class="number">2</span></span><br><span class="line"><span class="comment">// 后端</span></span><br><span class="line"><span class="keyword">const</span> wantsCards = <span class="title class_">Number</span>(req.<span class="property">body</span>.<span class="property">client</span>) &gt;= <span class="number">2</span>;</span><br></pre></td></tr></table></figure><p>老前端（不带 <code>client</code>）拿到的是带 markdown 链接的文本清单，新前端拿到 <code>relevant_links</code> 渲染成卡片，不会出现「只剩一句引导、下面什么都没有」。</p><p>上线节奏是：<code>scp</code> 文件 → <code>node --check</code> → 备份 <code>.bak-&lt;时间戳&gt;</code> → <code>pm2 restart ai-chatbot --update-env</code>；只改数据文件（<code>faq.json</code>、<code>flinks.json</code>）时用 <code>GET /api/reload</code> 热加载，不重启、不断服务。</p><h2 id="别的踩坑记录"><a href="#别的踩坑记录" class="headerlink" title="别的踩坑记录"></a>别的踩坑记录</h2><ul><li><strong>改 <code>.styl</code> 必须 <code>hexo clean</code></strong>：hexo 按入口 <code>index.styl</code> 的 mtime 判缓存，只跑 <code>generate</code> 不会重编 CSS。这次”清空按钮跑到第二行”就是 CSS 没进包导致的，排查时先看了一眼编译产物里有没有 <code>.ai-chatbot-header-left</code> 就定位了。</li><li><strong>图标字体里没有 trash</strong>：<code>eucalyptus</code> 字体只有 <code>arrows-rotate</code>、<code>circle-xmark</code> 这类，没有垃圾桶，所以清空按钮改成内联 SVG（<code>stroke: currentColor</code> 跟着 hover 变色）。</li><li><strong>不同字形的墨迹大小不一样</strong>：一开始用 <code>icon-arrows-rotate</code>，视觉上比全屏图标大一圈。用 fontTools 量了字形包围盒才确认——16px 时旋转箭头墨迹 15.5×14.5，而 <code>maximize</code> 只有 13.5×11.5，所以单独把那个图标降到 13px 才对齐。</li><li><strong>pjax 事件名各家不统一</strong>：<code>pjax:complete</code>、<code>pjax:success</code>、<code>pjax:end</code> 全挂上，重复触发反正幂等。</li></ul><h2 id="小结"><a href="#小结" class="headerlink" title="小结"></a>小结</h2><p>这次没有换模型、没有换框架，纯粹是把”提示词、数据结构、状态管理、流式解析”这四层各修了一遍。效果最明显的三个变化：回复不再自我重复、追问能接住上一句、文章页问摘要能答对。</p><p>最值钱的反而不是功能，而是那两个 bug —— <strong>一直在悄悄丢字的解析器和一颗随时会引爆的崩溃炸弹</strong>。功能是看得见的，这种是看不见的，只有去翻错误日志才会发现：56 条报错静静地躺在那里四个月。</p><p>如果你也在博客上挂了类似的小助手，建议去翻一眼流式解析那段：<code>chunk.toString().split(&#39;\n&#39;)</code> 这种写法，在压缩流面前基本必挂。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/ChatBot/">ChatBot</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/10/31/16077c3f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>新增列表卡片：无封面排版 + AI 摘要动态拉取</title>
      <link>https://blog.eucalyptus.cc/2026/10/25/3f7c1a92/</link>
      <guid>https://blog.eucalyptus.cc/2026/10/25/3f7c1a92/</guid>
      <pubDate>Sun, 25 Oct 2026 10:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;之前给博客做过一版「横向卡片」（配置项叫 &lt;code&gt;home_card_style:</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>之前给博客做过一版「横向卡片」（配置项叫 <code>home_card_style: horizontal</code>），后来主题更新，那套模板和 CSS 一起没了，配置项也变成了孤儿。这次换个思路：<strong>不另写模板</strong>，直接在 <code>post-ui.pug</code> 里加分支，用一个整数开关切换「封面卡片」和「列表卡片」。</p><p>顺带解决了另一个更烦的问题：卡片里那句摘要。</p><p>以前它是「正文去掉 HTML 标签后截取 500 字」，也就是文章开头那句话。而文章页顶部明明有一块 <strong>AI-摘要</strong>，是真正的总结。为什么不直接把那段搬过来？</p><p>这篇文章就记录这两件事：<strong>怎么加一张卡片</strong>，以及<strong>怎么让卡片里的摘要真的”活”起来</strong>——不是抄一份快照，而是跟着服务端缓存自动更新。</p><p>示例：<br><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-25/1.png"></p><h2 id="正文"><a href="#正文" class="headerlink" title="正文"></a>正文</h2><h3 id="文件路径分布"><a href="#文件路径分布" class="headerlink" title="文件路径分布"></a>文件路径分布</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line">blog/</span><br><span class="line">├── _config.anzhiyu.yml                                  # post_card_style 开关</span><br><span class="line">├── source/_data/ai_summary.json                          # 构建时兜底的摘要快照</span><br><span class="line">├── themes/anzhiyu/</span><br><span class="line">│   ├── layout/</span><br><span class="line">│   │   ├── index.pug                                     # 引入卡片摘要脚本</span><br><span class="line">│   │   └── includes/</span><br><span class="line">│   │       ├── mixins/post-ui.pug                        # 卡片结构 + 分支</span><br><span class="line">│   │       └── head/config_site.pug                      # 把 abbrlink 注入全局变量</span><br><span class="line">│   └── source/</span><br><span class="line">│       ├── css/_extra/post_card_list/index.css           # 列表卡片样式</span><br><span class="line">│       └── js/anzhiyu/</span><br><span class="line">│           ├── ai_abstract.js                            # 文章页：请求时带上 abbrlink</span><br><span class="line">│           └── card_summary.js                           # 首页：按 abbrlink 拉摘要</span><br><span class="line">└── ...</span><br></pre></td></tr></table></figure><p><code>css/_extra/</code> 下的文件会被 <code>themes/anzhiyu/source/css/index.styl</code> 里的 <code>@import &#39;_extra/**/*.css&#39;</code> 自动收录，所以新增样式文件<strong>不用改入口</strong>。</p><h3 id="一、开关：一个整数，两套版式"><a href="#一、开关：一个整数，两套版式" class="headerlink" title="一、开关：一个整数，两套版式"></a>一、开关：一个整数，两套版式</h3><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 首页双栏显示</span></span><br><span class="line"><span class="attr">article_double_row:</span> <span class="literal">true</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 文章卡片样式（首页 / 分类 / 标签页的文章列表）</span></span><br><span class="line"><span class="comment"># 1 = 封面卡片（默认，配合 article_double_row 双栏显示）</span></span><br><span class="line"><span class="comment"># 2 = 列表卡片：无封面，标题左侧竖条 + 日期/分类/标签胶囊 + 摘要 + 字数·阅读时长 + 右侧箭头</span></span><br><span class="line"><span class="attr">post_card_style:</span> <span class="number">2</span></span><br></pre></td></tr></table></figure><h3 id="二、模板：只加分支，不另写文件"><a href="#二、模板：只加分支，不另写文件" class="headerlink" title="二、模板：只加分支，不另写文件"></a>二、模板：只加分支，不另写文件</h3><p>原来的 mixin 是「有封面就渲染封面，没封面就整行文字」。列表卡片要的是”永远没有封面，但内容重新排布”，所以在 mixin 顶部算出两个变量，后面按条件走：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">mixin postUI(posts)</span><br><span class="line">  - const cardStyle = theme.post_card_style || 1</span><br><span class="line">  - const isListCard = cardStyle === 2</span><br><span class="line">  - const showListWords = isListCard &amp;&amp; theme.wordcount.enable &amp;&amp; theme.wordcount.post_wordcount</span><br><span class="line">  each article , index in page.posts.data</span><br><span class="line">    - let link = article.link || article.path</span><br><span class="line">    div(class = (index === 0 ? &#x27;recent-post-item lastestpost-item&#x27; : &#x27;recent-post-item&#x27;) + (isListCard ? &#x27; post-list-card&#x27; : &#x27;&#x27;) data-abbrlink=(isListCard ? (article.abbrlink || &#x27;&#x27;) : &#x27;&#x27;) onclick=`pjax.loadUrl(&#x27;$&#123;url_for(link)&#125;&#x27;)`)</span><br></pre></td></tr></table></figure><p>三点改动：</p><ol><li>卡片多了 <code>post-list-card</code> 类，CSS 全部挂在这个类下面，<strong>别的版式完全不受影响</strong>；</li><li><code>data-abbrlink</code> 留给后面的摘要脚本用（<code>abbrlink</code> 是 hexo-abbrlink 生成的短链，唯一且稳定）；</li><li>封面那一段加 <code>&amp;&amp; !isListCard</code>，列表卡片不渲染 <code>.post_cover</code>。</li></ol><p>分类的位置也变了：封面卡片把它塞在标题上方的小字里，列表卡片把它做成胶囊放到元信息行。所以分类渲染也加了条件：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">if (!isListCard &amp;&amp; theme.post_meta.page.categories &amp;&amp; article.categories.data.length &gt; 0)</span><br><span class="line">  each item, index in article.categories.data</span><br><span class="line">    .article-categories-original=item.name</span><br></pre></td></tr></table></figure><p>元信息行里（日期之后）再补一个分类胶囊，多级分类合成一个，用 <code>/</code> 连接：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">if (isListCard &amp;&amp; theme.post_meta.page.categories &amp;&amp; article.categories.data.length &gt; 0)</span><br><span class="line">  span.post-list-card-category</span><br><span class="line">    i.eucalyptus.icon-book-open</span><br><span class="line">    each item, idx in article.categories.data</span><br><span class="line">      if idx &gt; 0</span><br><span class="line">        span.post-list-card-cat-sep= &#x27;/&#x27;</span><br><span class="line">      a.post-list-card-cat-link(href=url_for(item.path) title=item.name onclick=&quot;window.event.cancelBubble=true;&quot;)= item.name</span><br></pre></td></tr></table></figure><p>正文后面追加字数、阅读时长和右侧箭头（箭头是卡片的直接子元素，方便绝对定位到整卡高度）：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line">if showListWords || showListMin2read</span><br><span class="line">  .post-list-card-footer</span><br><span class="line">    if showListWords</span><br><span class="line">      span= wordcount(article.content) + &#x27; 字&#x27;</span><br><span class="line">    if showListWords &amp;&amp; showListMin2read</span><br><span class="line">      span.post-list-card-sep |</span><br><span class="line">    if showListMin2read</span><br><span class="line">      span= min2read(article.content, &#123;cn: 350, en: 160&#125;) + &#x27; &#x27; + _p(&#x27;post.min2read_unit&#x27;)</span><br><span class="line">if isListCard</span><br><span class="line">  span.post-list-card-arrow</span><br><span class="line">    i.eucalyptus.icon-angle-right</span><br></pre></td></tr></table></figure><h3 id="三、样式：全部挂在一个类下面"><a href="#三、样式：全部挂在一个类下面" class="headerlink" title="三、样式：全部挂在一个类下面"></a>三、样式：全部挂在一个类下面</h3><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/* 卡片外壳：注意这里用 width:auto，不是 100% */</span></span><br><span class="line"><span class="selector-id">#recent-posts</span> &gt; <span class="selector-class">.recent-post-item</span><span class="selector-class">.post-list-card</span> &#123;</span><br><span class="line">  <span class="attribute">display</span>: block;</span><br><span class="line">  <span class="attribute">width</span>: auto;</span><br><span class="line">  <span class="attribute">height</span>: auto;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">22px</span> <span class="number">88px</span> <span class="number">22px</span> <span class="number">26px</span>;   <span class="comment">/* 右边留出箭头的宽度 */</span></span><br><span class="line">  <span class="attribute">box-sizing</span>: border-box;</span><br><span class="line">  <span class="attribute">border</span>: <span class="built_in">var</span>(--style-border);</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">12px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 标题左侧那条竖线：用伪元素，才能有圆角和垂直居中 */</span></span><br><span class="line"><span class="selector-id">#recent-posts</span> &gt; <span class="selector-class">.recent-post-item</span><span class="selector-class">.post-list-card</span> <span class="selector-class">.article-title</span> &#123;</span><br><span class="line">  <span class="attribute">position</span>: relative;</span><br><span class="line">  <span class="attribute">padding-left</span>: <span class="number">14px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">1.35rem</span>;</span><br><span class="line">  -webkit-<span class="selector-tag">line</span>-clamp: <span class="number">2</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-id">#recent-posts</span> &gt; <span class="selector-class">.recent-post-item</span><span class="selector-class">.post-list-card</span> <span class="selector-class">.article-title</span><span class="selector-pseudo">::before</span> &#123;</span><br><span class="line">  <span class="attribute">content</span>: <span class="string">&quot;&quot;</span>;</span><br><span class="line">  <span class="attribute">position</span>: absolute;</span><br><span class="line">  <span class="attribute">left</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">top</span>: <span class="number">50%</span>;</span><br><span class="line">  <span class="attribute">width</span>: <span class="number">4px</span>;</span><br><span class="line">  <span class="attribute">height</span>: <span class="number">1.1em</span>;</span><br><span class="line">  <span class="attribute">transform</span>: <span class="built_in">translateY</span>(-<span class="number">50%</span>);</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">4px</span>;</span><br><span class="line">  <span class="attribute">background</span>: <span class="built_in">var</span>(--anzhiyu-main);</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>颜色全部用主题变量（<code>--anzhiyu-main</code> &#x2F; <code>--anzhiyu-secondbg</code> &#x2F; <code>--anzhiyu-theme-op</code>），所以<strong>换主题色、深浅色模式都不用改样式</strong>。箭头那块淡色底用的是 <code>--anzhiyu-theme-op</code>（主色的 14% 透明度）。</p><h3 id="四、踩到的五个坑"><a href="#四、踩到的五个坑" class="headerlink" title="四、踩到的五个坑"></a>四、踩到的五个坑</h3><table><thead><tr><th>#</th><th>现象</th><th>原因</th><th>解法</th></tr></thead><tbody><tr><td>1</td><td>列表卡片被压成两列窄条</td><td><code>article_double_row: true</code> 在 ≥1201px 上给 <code>.recent-post-item</code> 设了 <code>width: 49%</code></td><td>用 <code>#recent-posts &gt; .recent-post-item.post-list-card</code> 提高权重，显式 <code>width: 100%</code></td></tr><tr><td>2</td><td>移动端卡片溢出屏幕右侧</td><td>我把 <code>width: 100%</code> 当默认值，而手机端卡片还有 <code>margin: 20px</code></td><td>默认改 <code>width: auto</code>，只在 ≥1201px 的媒体查询里写 <code>width: 100%</code></td></tr><tr><td>3</td><td>两个分类出现两个书图标</td><td>每个分类渲染一个胶囊</td><td>改成”一个胶囊装所有分类”，用 <code>/</code> 分隔</td></tr><tr><td>4</td><td>摘要不显示</td><td>主题全局有一条 <code>.content &#123; opacity: 0; height: 0 &#125;</code>（双栏版式为了省略摘要）</td><td>列表卡片显式 <code>opacity: 1; height: auto</code></td></tr><tr><td>5</td><td>改完样式没生效</td><td>Hexo 只按入口文件 mtime 判断，<code>_page/*.styl</code>、<code>_extra/*.css</code> 改了不会触发 CSS 重编译</td><td><code>hexo clean &amp;&amp; hexo generate</code></td></tr></tbody></table><p>第 4 条值得多说一句：我一开始以为是”摘要没渲染”，查了半天模板，其实 HTML 里一直有 <code>.content</code> 节点，只是被 CSS 藏起来了。<strong>先看 DOM，再看 CSS</strong>，能省一半时间。</p><h3 id="五、让摘要真的变成”摘要”"><a href="#五、让摘要真的变成”摘要”" class="headerlink" title="五、让摘要真的变成”摘要”"></a>五、让摘要真的变成”摘要”</h3><h4 id="5-1-第一版：静态-JSON"><a href="#5-1-第一版：静态-JSON" class="headerlink" title="5.1 第一版：静态 JSON"></a>5.1 第一版：静态 JSON</h4><p>最省事的做法是抓一遍，存成数据文件，模板里直接读：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">- const listAiSummary = isListCard &amp;&amp; site.data.ai_summary ? site.data.ai_summary[article.abbrlink] : null</span><br><span class="line">case listAiSummary ? 4 : theme.index_post_content.method</span><br><span class="line">  when 4</span><br><span class="line">    .content!= listAiSummary</span><br></pre></td></tr></table></figure><p><code>_data/ai_summary.json</code> 长这样，按 abbrlink 索引：</p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">  <span class="attr">&quot;16496380&quot;</span><span class="punctuation">:</span> <span class="string">&quot;本文介绍了一套基于大模型能力为 Hexo 博客自动生成拟人化评论的系统……&quot;</span><span class="punctuation">,</span></span><br><span class="line">  <span class="attr">&quot;83caee76&quot;</span><span class="punctuation">:</span> <span class="string">&quot;本文介绍了基于 Ollama 的 AI 摘要生成系统部署与 Hexo 主题集成方案……&quot;</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p>能跑，但有个死穴：<strong>它是快照</strong>。Redis 里的摘要重新生成、过期、或者你发了新文章，这个文件不会自动变，只能再抓一遍。</p><h4 id="5-2-为什么首页拿不到摘要"><a href="#5-2-为什么首页拿不到摘要" class="headerlink" title="5.2 为什么首页拿不到摘要"></a>5.2 为什么首页拿不到摘要</h4><p>看一下摘要服务的逻辑（Node + Express + Redis）：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">getCacheKey</span>(<span class="params">text</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> contentHash = crypto.<span class="title function_">createHash</span>(<span class="string">&#x27;md5&#x27;</span>).<span class="title function_">update</span>(text.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">4000</span>)).<span class="title function_">digest</span>(<span class="string">&#x27;hex&#x27;</span>).<span class="title function_">substring</span>(<span class="number">0</span>, <span class="number">16</span>);</span><br><span class="line">  <span class="keyword">return</span> <span class="string">`ai:summary:<span class="subst">$&#123;contentHash&#125;</span>`</span>;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>缓存键是<strong>正文清洗后的前 4000 字的 md5</strong>，不是文章 ID、不是 URL。</p><p>文章页能拿到摘要，是因为它自己在文章里，可以就地提取正文、算出这个指纹：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">文章页 → getArticleText() 清洗正文 → md5 → 查 Redis → 命中/生成 → 显示</span><br></pre></td></tr></table></figure><p>而首页只有标题和一句摘要，<strong>没有正文</strong>，算不出指纹，也就查不到。</p><p>顺带排掉两个误区：</p><ul><li><code>cache-admin.sh list</code> 里那个 <code>ID</code>（001、002……）是 <code>sort | nl</code> 每次现算的行号，不是持久标识，增删任何一条，后面全部漂移；</li><li>Redis 里根本没有”这篇文章对应哪条摘要”的映射，只有一串摘要正文和它们的 md5。</li></ul><h4 id="5-3-顺手排掉的一个隐性问题"><a href="#5-3-顺手排掉的一个隐性问题" class="headerlink" title="5.3 顺手排掉的一个隐性问题"></a>5.3 顺手排掉的一个隐性问题</h4><p>调试时发现同一个 URL，带 <code>Origin</code> 请求有时拿不到跨域头：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">curl -H <span class="string">&quot;Origin: https://blog.eucalyptus.cc&quot;</span> <span class="string">&quot;…/api/summary?key=p:83caee76&quot;</span>      <span class="comment"># 没有 ACAO</span></span><br><span class="line">curl -H <span class="string">&quot;Origin: https://blog.eucalyptus.cc&quot;</span> <span class="string">&quot;…/api/summary?key=p:83caee76&amp;cb=1&quot;</span> <span class="comment"># 有</span></span><br></pre></td></tr></table></figure><p>原因是宝塔的全局配置 <code>/www/server/nginx/conf/proxy.conf</code> 里开着：</p><figure class="highlight nginx"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="attribute">proxy_cache</span> cache_one;</span><br></pre></td></tr></table></figure><p>它给<strong>所有反代站点</strong>加了一层缓存，缓存键是 <code>$scheme$proxy_host$request_uri</code>，<strong>不区分 Origin</strong>。于是”第一次谁访问的”决定了这份缓存里有没有 <code>Access-Control-Allow-Origin</code>——浏览器第二次来就撞上空头，跨域失败。</p><p>解法是在响应里加一行，让 nginx 别缓存这条响应：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">res.<span class="title function_">set</span>(<span class="string">&#x27;X-Accel-Expires&#x27;</span>, <span class="string">&#x27;0&#x27;</span>);</span><br></pre></td></tr></table></figure><p><code>X-Accel-*</code> 是 nginx 认的控制头，<code>0</code> 表示不缓存。加上之后同样的测试就稳定了。</p><h4 id="5-4-最终方案：给每篇文章加一张”目录卡”"><a href="#5-4-最终方案：给每篇文章加一张”目录卡”" class="headerlink" title="5.4 最终方案：给每篇文章加一张”目录卡”"></a>5.4 最终方案：给每篇文章加一张”目录卡”</h4><p>既然键算不出来，那就<strong>在写摘要的时候，额外按文章标识存一份</strong>。</p><p>服务端只加两个地方：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 写入时（POST /api/ai-summary），如果带了 key，就多存一份</span></span><br><span class="line"><span class="keyword">const</span> alias = <span class="title function_">normalizeAliasKey</span>(req.<span class="property">body</span> &amp;&amp; req.<span class="property">body</span>.<span class="property">key</span>);   <span class="comment">// 只接受 p:&lt;字母数字&gt;</span></span><br><span class="line"><span class="keyword">await</span> redis.<span class="title function_">setex</span>(cacheKey, config.<span class="property">CACHE_TTL</span>, summary);</span><br><span class="line"><span class="keyword">await</span> <span class="title function_">saveAlias</span>(alias, summary);                             <span class="comment">// → ai:summary:p:&lt;abbrlink&gt;</span></span><br><span class="line"></span><br><span class="line"><span class="comment">// 新增只读接口，永远不触发生成</span></span><br><span class="line">app.<span class="title function_">get</span>(<span class="string">&#x27;/api/summary&#x27;</span>, <span class="title function_">async</span> (req, res) =&gt; &#123;</span><br><span class="line">  <span class="keyword">const</span> alias = <span class="title function_">normalizeAliasKey</span>(req.<span class="property">query</span>.<span class="property">key</span>);</span><br><span class="line">  <span class="keyword">if</span> (!alias) <span class="keyword">return</span> res.<span class="title function_">status</span>(<span class="number">400</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: <span class="string">&#x27;Bad key&#x27;</span> &#125;);</span><br><span class="line">  <span class="keyword">const</span> summary = <span class="keyword">await</span> redis.<span class="title function_">get</span>(<span class="string">`ai:summary:<span class="subst">$&#123;alias&#125;</span>`</span>);</span><br><span class="line">  res.<span class="title function_">set</span>(<span class="string">&#x27;X-Accel-Expires&#x27;</span>, <span class="string">&#x27;0&#x27;</span>);</span><br><span class="line">  res.<span class="title function_">set</span>(<span class="string">&#x27;Vary&#x27;</span>, <span class="string">&#x27;Origin&#x27;</span>);</span><br><span class="line">  res.<span class="title function_">json</span>(&#123; <span class="attr">summary</span>: summary || <span class="literal">null</span>, <span class="attr">cached</span>: <span class="title class_">Boolean</span>(summary) &#125;);</span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><p>文章页的请求体里带上 <code>abbrlink</code>：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">const</span> requestBody = &#123;</span><br><span class="line">  <span class="attr">text</span>: articleText.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">4000</span>),</span><br><span class="line">  <span class="attr">force</span>: forceRefresh</span><br><span class="line">&#125;;</span><br><span class="line"><span class="keyword">const</span> aliasKey = <span class="title function_">getAliasKey</span>();          <span class="comment">// → &#x27;p:83caee76&#x27;</span></span><br><span class="line"><span class="keyword">if</span> (aliasKey) requestBody.<span class="property">key</span> = aliasKey;</span><br></pre></td></tr></table></figure><p><code>abbrlink</code> 从 <code>GLOBAL_CONFIG_SITE</code> 里取，在 <code>head/config_site.pug</code> 注入：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">abbrlink: &#x27;!&#123;abbrlinkVal&#125;&#x27;,</span><br></pre></td></tr></table></figure><p>首页每个卡片只要认自己的 <code>data-abbrlink</code>，就能直接问：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="title function_">fetch</span>(<span class="variable constant_">API</span> + <span class="string">&#x27;?key=&#x27;</span> + <span class="built_in">encodeURIComponent</span>(<span class="string">&#x27;p:&#x27;</span> + abbrlink))</span><br></pre></td></tr></table></figure><p>完整的卡片脚本（3 并发、失败静默、命中才替换）：</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br></pre></td><td class="code"><pre><span class="line">(<span class="keyword">function</span> (<span class="params"></span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> <span class="variable constant_">API</span> = <span class="string">&#x27;https://abstract.eucalyptus.cc/api/summary&#x27;</span>;</span><br><span class="line">  <span class="keyword">const</span> cards = <span class="title class_">Array</span>.<span class="property"><span class="keyword">prototype</span></span>.<span class="property">slice</span>.<span class="title function_">call</span>(</span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">querySelectorAll</span>(<span class="string">&#x27;.recent-post-item.post-list-card[data-abbrlink]&#x27;</span>)</span><br><span class="line">  );</span><br><span class="line">  <span class="keyword">if</span> (!cards.<span class="property">length</span>) <span class="keyword">return</span>;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">let</span> cursor = <span class="number">0</span>;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">updateCard</span>(<span class="params">card</span>) &#123;</span><br><span class="line">    <span class="keyword">const</span> abbrlink = (card.<span class="title function_">getAttribute</span>(<span class="string">&#x27;data-abbrlink&#x27;</span>) || <span class="string">&#x27;&#x27;</span>).<span class="title function_">trim</span>();</span><br><span class="line">    <span class="keyword">const</span> content = card.<span class="title function_">querySelector</span>(<span class="string">&#x27;.recent-post-info &gt; .content&#x27;</span>);</span><br><span class="line">    <span class="keyword">if</span> (!abbrlink || !content) <span class="keyword">return</span> <span class="title class_">Promise</span>.<span class="title function_">resolve</span>();</span><br><span class="line"></span><br><span class="line">    <span class="keyword">return</span> <span class="title function_">fetch</span>(<span class="variable constant_">API</span> + <span class="string">&#x27;?key=&#x27;</span> + <span class="built_in">encodeURIComponent</span>(<span class="string">&#x27;p:&#x27;</span> + abbrlink), &#123; <span class="attr">credentials</span>: <span class="string">&#x27;omit&#x27;</span> &#125;)</span><br><span class="line">      .<span class="title function_">then</span>(<span class="function"><span class="params">res</span> =&gt;</span> res.<span class="property">ok</span> ? res.<span class="title function_">json</span>() : <span class="literal">null</span>)</span><br><span class="line">      .<span class="title function_">then</span>(<span class="function"><span class="params">data</span> =&gt;</span> &#123;</span><br><span class="line">        <span class="keyword">const</span> text = data &amp;&amp; <span class="keyword">typeof</span> data.<span class="property">summary</span> === <span class="string">&#x27;string&#x27;</span> ? data.<span class="property">summary</span>.<span class="title function_">trim</span>() : <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">        <span class="keyword">if</span> (!text) <span class="keyword">return</span>;</span><br><span class="line">        <span class="keyword">if</span> (text === (content.<span class="property">textContent</span> || <span class="string">&#x27;&#x27;</span>).<span class="title function_">trim</span>()) <span class="keyword">return</span>;</span><br><span class="line">        content.<span class="property">textContent</span> = text;</span><br><span class="line">        content.<span class="title function_">setAttribute</span>(<span class="string">&#x27;data-summary-source&#x27;</span>, <span class="string">&#x27;live&#x27;</span>);</span><br><span class="line">      &#125;)</span><br><span class="line">      .<span class="title function_">catch</span>(<span class="function">() =&gt;</span> &#123;&#125;);</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">next</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="keyword">if</span> (cursor &gt;= cards.<span class="property">length</span>) <span class="keyword">return</span> <span class="title class_">Promise</span>.<span class="title function_">resolve</span>();</span><br><span class="line">    <span class="keyword">return</span> <span class="title function_">updateCard</span>(cards[cursor++]).<span class="title function_">then</span>(next);</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; <span class="number">3</span>; i++) <span class="title function_">next</span>();</span><br><span class="line">&#125;)();</span><br></pre></td></tr></table></figure><p>注意这段脚本只是”<strong>升级</strong>“，不是”加载”：首屏渲染的还是构建时 <code>_data/ai_summary.json</code> 里那份，脚本只是拿最新值覆盖。所以接口挂了、跨域被挡、Redis 里没这条，<strong>页面都照常显示</strong>，只是看不到更新。</p><h3 id="六、结果"><a href="#六、结果" class="headerlink" title="六、结果"></a>六、结果</h3><ul><li>首页 10 张卡片，服务端渲染时就带着摘要，首屏不空；</li><li>脚本再发 10 个轻量 <code>GET</code>（3 并发），命中就把文字替换成 Redis 里的最新版本，并在元素上打一个 <code>data-summary-source=&quot;live&quot;</code> 的标记，方便验证；</li><li>现有 26 篇文章的别名已一次性写入（<code>ai:summary:p:&lt;abbrlink&gt;</code>，TTL 与正文缓存一致，30 天）；</li><li>新文章：第一次有人打开文章页，就会顺手把这张”目录卡”写好，首页下次刷新自动跟上。</li></ul><h2 id="后记"><a href="#后记" class="headerlink" title="后记"></a>后记</h2><p>这次改动最麻烦的不是 CSS，是”<strong>为什么首页拿不到摘要</strong>“这个问题。表面看是”接口不给我数据”，实际是<strong>键的设计</strong>：缓存按内容指纹编址，而首页手里只有文章标识。</p><p>补一层 <code>abbrlink → 摘要</code> 的别名，问题就没了。这类”看起来是权限问题、其实是寻址问题”的坑，值得记一笔。</p><p>几个能复用的经验：</p><ol><li><strong>给卡片加新样式，优先”加类名 + 新 CSS 文件”，而不是复制一份模板</strong>。模板会分叉，样式不会。</li><li><strong><code>width: 100%</code> 和 <code>margin</code> 一起用必然溢出</strong>，块级元素让它自己撑开就好。</li><li><strong>样式不生效先想缓存</strong>：Hexo 的 CSS 只认入口文件 mtime，改了被 <code>@import</code> 的局部文件必须 <code>clean</code>。</li><li><strong>静态兜底 + 动态升级</strong>是做”锦上添花”类功能的正确姿势：接口挂了页面不能挂。</li><li><strong>反代层的缓存会吃掉跨域头</strong>，<code>X-Accel-Expires: 0</code> 是最省事的开关。</li></ol><p>已知限制：摘要生成依赖模型额度，配额打满时会返回 <code>429 insufficient_quota</code>，此时候选文章的卡片会退回到构建时的快照——不影响阅读，只是不够新。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%96%87%E7%AB%A0%E5%8D%A1%E7%89%87%E6%A0%B7%E5%BC%8F/">文章卡片样式</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/10/25/3f7c1a92/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>AI 评论机器人 2.0：DSH 插件版</title>
      <link>https://blog.eucalyptus.cc/2026/10/18/69761bcb/</link>
      <guid>https://blog.eucalyptus.cc/2026/10/18/69761bcb/</guid>
      <pubDate>Sun, 18 Oct 2026 02:17:35 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;今年六月份的时候给博客搞了一个AI评论机器人，介绍了一套基于大模型能力为 Hexo</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>今年六月份的时候给博客搞了一个AI评论机器人，介绍了一套基于大模型能力为 Hexo 博客自动生成拟人化评论的系统，旨在解决个人博客评论区长期空白导致的冷启动困境。系统以独立 Python 脚本运行，不修改博客主题或 Twikoo 源码，通过读取本地数据库获取现有评论、调用 AI 服务生成评论与回复内容，并模拟真实用户的 UA、IP、Gravatar 头像等数据特征，使 AI 评论在数据层面与真实用户无异。系统采用分层隔离设计，按配置比例自动调度新评论或回复模式，支持批量处理与定时任务运行，可有效营造自然的社区讨论氛围。</p><div class='anzhiyu-tag-link'><a class="tag-Link"  href="/2026/06/08/16496380/">    <div class="tag-link-tips">站内地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://img.eucalyptus.cc/images/logo.png" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://img.eucalyptus.cc/images/logo.png" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">解决博客零评论困境：AI 评论机器人部署全记录</div>            <div class="tag-link-sitename">blog.eucalyptus.cc</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p>后来慢慢的荒废了…</p><p>最近有时间，将它改成了plugin（<font style="color:rgb(209, 215, 224) !important;">dsh-ai-bot-plugin</font>）部署到了我的dsh中,可以在dsh中可视化操作</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/1.avif"></p><hr><h2 id="dsh-ai-bot-plugin是什么"><a href="#dsh-ai-bot-plugin是什么" class="headerlink" title="dsh-ai-bot-plugin是什么"></a><font style="color:rgb(209, 215, 224) !important;">dsh-ai-bot-plugin</font>是什么</h2><p><strong>AI 评论机器人 2.0</strong> &#x3D; 机器人核心 + 数据面板 + DSH 插件。</p><ul><li><strong>机器人</strong>：从 Hexo <code>public/</code> 读取文章和正文摘要，从 Twikoo 读取评论，调用兼容 OpenAI Chat Completions 的模型生成新评论或回复，再提交回 Twikoo。</li><li><strong>面板</strong>：零前端依赖的本地控制台，查看评论热度、AI 占比、趋势、Token 用量和运行历史；可以发起任务、试运行、停止、下载日志，也能直接修改模型配置。</li><li><strong>DSH 插件</strong>：左侧栏「AI 评论」→ 右侧主区域页面。宿主自动拉起 Python 后端，通过 <code>/ai-bot</code> 同源代理加载，背景透明、亮&#x2F;暗主题跟随 DSH。</li></ul><p>适合自建 Hexo + Twikoo 的博客，用来冷启动评论区、自动回复，或者观察评论数据。</p><h2 id="2-0-亮点"><a href="#2-0-亮点" class="headerlink" title="2.0 亮点"></a>2.0 亮点</h2><ul><li><strong>DSH 原生页面</strong>：不是弹窗，也不是侧边抽屉；打开方式接近 DSH 自带插件页。</li><li><strong>模型可在面板里改</strong>：模型名、API 地址、Key 都能在「设置」编辑并测试连接，优先级高于环境变量。</li><li><strong>AI 台账防自回复</strong>：提交成功记录评论 id，下一轮精确排除自己的评论。</li><li><strong>主题跟随</strong>：DSH 切亮色&#x2F;暗色，面板同步切换；有皮肤壁纸时铺到面板背景。</li><li><strong>事件驱动刷新</strong>：打开页面、手动刷新、切回面板时更新，空闲不轮询，避免反复请求 Twikoo。</li><li><strong>CLI 与面板共用数据</strong>：运行记录、Token 用量、日志都在同一套本地状态里。</li></ul><h2 id="功能"><a href="#功能" class="headerlink" title="功能"></a>功能</h2><table><thead><tr><th>模块</th><th>能力</th></tr></thead><tbody><tr><td>机器人</td><td><code>mixed</code> &#x2F; <code>new</code> &#x2F; <code>reply</code> 三种模式；读取正文摘要；回复带真实文章标题和 <code>pid/rid</code>；支持 <code>--dry-run</code></td></tr><tr><td>面板</td><td>总览 &#x2F; 文章 &#x2F; 运行 &#x2F; 记录 &#x2F; 设置；趋势、评论构成、零评论文章、最近评论；搜索、筛选、多选、详情抽屉</td></tr><tr><td>任务</td><td>全部 &#x2F; 前 N 篇 &#x2F; 选中 &#x2F; 单篇；新评论比例、单篇回复上限；进度、实时日志、停止、日志下载</td></tr><tr><td>配置</td><td>面板内改模型 &#x2F; API 地址 &#x2F; Key；环境变量、DSH 凭据回退；连接测试</td></tr><tr><td>DSH</td><td>侧栏入口、主区域页面、同源代理、透明背景、主题&#x2F;壁纸跟随、宿主自动拉起后端</td></tr></tbody></table><h2 id="界面"><a href="#界面" class="headerlink" title="界面"></a>界面</h2><h3 id="总览"><a href="#总览" class="headerlink" title="总览"></a>总览</h3><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/2.avif"></p><p>顶部四张指标卡：文章总数（附带评论覆盖率）、可见评论（今日新增）、AI 评论数与占比、近 30 天模型调用次数，每张卡下面带一条迷你趋势线。往下左边是评论趋势，可在 30 &#x2F; 90 天之间切换，全部评论与 AI 评论两条线叠在一起（近期评论太少时会自动切到 90 天，避免图空着）；右边是评论构成环形图，分成 AI &#x2F; 真人 &#x2F; 隐藏。最下面是「零评论文章」和「最近评论」：前者按冷启动优先级列出还没人评论的文章，点「全部文章」跳到下一页；后者显示 Twikoo 上最新收到的评论和总条数。</p><h3 id="文章"><a href="#文章" class="headerlink" title="文章"></a>文章</h3><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/3.avif"></p><p>搜索框按标题或 URL 过滤，旁边的下拉可以只看有评论 &#x2F; 零评论 &#x2F; 含 AI 评论的文章。表格列出每篇的评论数、AI 评论数、摘要字数和最后评论时间；勾选若干篇后点「用选中文章运行」，就把任务范围限定在这几篇。点行尾的详情会从右侧滑出抽屉，里面是正文摘要、原文链接，以及「只处理这篇（回复）」的快捷入口。</p><h3 id="运行"><a href="#运行" class="headerlink" title="运行"></a>运行</h3><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/4.avif"></p><p>左半边是任务表单：模式（混合 &#x2F; 只发新评论 &#x2F; 只回复）、新评论比例滑杆（0% 全部回复，100% 全部发新评论）、单篇最多回复条数、范围（全部文章 &#x2F; 前 N 篇 &#x2F; 选中的文章），还有「试运行」开关——只调用模型生成内容、估算 token，不会往博客提交任何东西。右半边是实时输出：进度条、滚动日志、状态徽章和日志下载。任务跑在后台线程里，随时能点「停止」，结束后在下方汇总本次统计并写入「记录」。</p><h3 id="记录"><a href="#记录" class="headerlink" title="记录"></a>记录</h3><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/5.avif"></p><p>按时间倒序列出每次运行：模式、比例、覆盖文章数、新评论数、回复数、成功率、耗时和最终状态，点进去能看到当次的完整日志。命令行和定时任务的运行也写进同一张表，所以这里就是这台机器上所有评论操作的历史。</p><h3 id="设置"><a href="#设置" class="headerlink" title="设置"></a>设置</h3><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-10-18/6.avif"></p><p>上半部分是模型配置：模型名、API 地址、API Key 都能直接改，改完点「保存并测试」会立刻用新配置请求一次模型；保存后对面板和 CLI 同时生效，优先级高于环境变量。密钥落在本机数据目录的 <code>settings.json</code> 里，界面上只显示掩码，留空表示不修改。下半部分是运行环境（面板设置、环境变量、<code>config.py</code> 三层合并后的实际生效值）、最近 30 天的模型用量与消耗趋势，以及几条安全建议：端口不要暴露公网、反代记得加 HTTPS、cron 要加 <code>flock</code> 避免任务重叠。</p><p>个人项目，非 Twikoo &#x2F; DSH 官方项目，<font style="color:rgb(209, 215, 224) !important;">dsh-ai-bot-plugin插件还没有公开，有需要可以留言</font></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/CommentBot/">CommentBot</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/10/18/69761bcb/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL中的METHOD(认证方法)</title>
      <link>https://blog.eucalyptus.cc/2026/07/18/608bddc6/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/18/608bddc6/</guid>
      <pubDate>Sat, 18 Jul 2026 15:08:58 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在 PostgreSQL 的 &lt;code&gt;pg_hba.conf&lt;/code&gt; 文件中，&lt;code&gt;METHOD&lt;/code&gt;（认证方法）决定了服务器如何验证客户端的身份。&lt;/p&gt;
&lt;p&gt;PostgreSQL 支持多种认证方法，主要可以分为以下几类：&lt;/p&gt;
&lt;h3</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在 PostgreSQL 的 <code>pg_hba.conf</code> 文件中，<code>METHOD</code>（认证方法）决定了服务器如何验证客户端的身份。</p><p>PostgreSQL 支持多种认证方法，主要可以分为以下几类：</p><h3 id="基于密码的认证-Password-Based"><a href="#基于密码的认证-Password-Based" class="headerlink" title="基于密码的认证 (Password-Based)"></a>基于密码的认证 (Password-Based)</h3><p>这是最常用的方式，客户端需要提供密码。</p><table><thead><tr><th>方法</th><th>说明</th></tr></thead><tbody><tr><td>安全性</td><td>适用场景</td></tr><tr><td>scram-sha-256</td><td><strong>推荐</strong>。使用 SCRAM-SHA-256 挑战-响应机制。密码不以明文传输，也不存储哈希值，而是存储 Salted Hash。</td></tr><tr><td>最高 PG 10+ 默认首选</td><td><strong>生产环境首选</strong></td></tr><tr><td>md5</td><td>使用 MD5 哈希进行挑战-响应。比明文安全，但 MD5 已被认为不够强壮易受碰撞攻击。</td></tr><tr><td>中等</td><td>旧版本兼容或内部网络</td></tr><tr><td>password</td><td><strong>明文传输</strong>。密码以未加密形式通过网络发送。</td></tr><tr><td>极低</td><td><strong>严禁在生产环境使用</strong>，仅限 SSL 隧道内或测试</td></tr></tbody></table><p><strong>注意</strong>：从 PostgreSQL 14 开始，默认认证方法已改为 <code>scram-sha-256</code>。</p><h3 id="基于操作系统的认证-OS-Based"><a href="#基于操作系统的认证-OS-Based" class="headerlink" title="基于操作系统的认证 (OS-Based)"></a>基于操作系统的认证 (OS-Based)</h3><p>利用操作系统的用户身份进行映射，通常用于本地连接，<strong>无需输入数据库密码</strong>。</p><table><thead><tr><th>方法</th><th>说明</th><th>适用系统</th></tr></thead><tbody><tr><td>peer</td><td><strong>Linux&#x2F;Unix 专用</strong>。获取客户端的操作系统用户名，并检查它是否与请求的数据库用户名匹配。</td><td>Linux, macOS, Unix</td></tr><tr><td>ident</td><td><strong>通用</strong>。通过联系客户端机器上的 Ident 服务器来确定操作系统用户名。通常用于 TCP 连接。</td><td>Linux, Unix, Windows(较少用)</td></tr></tbody></table><p><strong>示例</strong>：如果 Linux 用户 <code>alice</code> 运行 <code>psql -U alice</code>，且配置为 <code>peer</code>，则直接登录，无需密码。</p><h3 id="无条件信任-拒绝-Trust-Reject"><a href="#无条件信任-拒绝-Trust-Reject" class="headerlink" title="无条件信任&#x2F;拒绝 (Trust&#x2F;Reject)"></a>无条件信任&#x2F;拒绝 (Trust&#x2F;Reject)</h3><table><thead><tr><th>方法</th><th>说明</th><th>风险</th></tr></thead><tbody><tr><td>trust</td><td><strong>无条件允许</strong>。只要连接建立成功，就允许访问，<strong>不需要任何密码</strong>。</td><td><strong>极高</strong>。任何能连接到该端口&#x2F;Socket 的人都可以登录。仅用于本地开发或完全隔离的内网。</td></tr><tr><td>reject</td><td><strong>无条件拒绝</strong>。立即关闭连接。通常用于在允许某些 IP 之前，先拒绝其他所有 IP（作为默认兜底规则）。</td><td>无（用于阻断）</td></tr></tbody></table><h3 id="外部认证集成-External-Integration"><a href="#外部认证集成-External-Integration" class="headerlink" title="外部认证集成 (External Integration)"></a>外部认证集成 (External Integration)</h3><p>与企业级身份管理系统集成。</p><table><thead><tr><th>方法</th><th>说明</th></tr></thead><tbody><tr><td>ldap</td><td>使用 LDAP 目录服务（如 Active Directory, OpenLDAP）进行认证。</td></tr><tr><td>radius</td><td>使用 RADIUS 服务器进行认证。</td></tr><tr><td>cert</td><td>使用 SSL 客户端证书进行认证。客户端必须提供有效的 SSL 证书，Common Name (CN) 需匹配数据库用户名。</td></tr><tr><td>pam</td><td>使用操作系统可插拔认证模块 (PAM) 进行认证。</td></tr><tr><td>bsd</td><td>使用 BSD 认证服务（较少见）。</td></tr><tr><td>gss &#x2F; sspi</td><td>使用 Kerberos GSSAPI (Unix) 或 SSPI (Windows) 进行单点登录 (SSO)。</td></tr></tbody></table><h3 id="常见场景推荐配置"><a href="#常见场景推荐配置" class="headerlink" title="常见场景推荐配置"></a>常见场景推荐配置</h3><h4 id="本地开发环境-最方便"><a href="#本地开发环境-最方便" class="headerlink" title="本地开发环境 (最方便)"></a>本地开发环境 (最方便)</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># &quot;local&quot; is for Unix domain socket connections only</span></span><br><span class="line"><span class="built_in">local</span>   all             all trust/peer</span><br></pre></td></tr></table></figure><h4 id="生产环境-最安全"><a href="#生产环境-最安全" class="headerlink" title="生产环境 (最安全)"></a>生产环境 (最安全)</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># &quot;local&quot; is for Unix domain socket connections only</span></span><br><span class="line"><span class="built_in">local</span> all             all md5</span><br><span class="line"></span><br><span class="line"><span class="comment"># IPv4 local connections:</span></span><br><span class="line">host all             all             0.0.0.0/0 md5</span><br><span class="line"></span><br><span class="line"><span class="comment"># IPv6 local connections:</span></span><br><span class="line">host all             all             ::1/128 scram-sha-256</span><br></pre></td></tr></table></figure><h4 id="企业内部网-平衡安全与便利"><a href="#企业内部网-平衡安全与便利" class="headerlink" title="企业内部网 (平衡安全与便利)"></a>企业内部网 (平衡安全与便利)</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 内网特定网段免密（需确保网络隔离）</span></span><br><span class="line">host all             all             192.168.1.0/24 trust</span><br><span class="line"></span><br><span class="line"><span class="comment"># 其他所有连接需要密码</span></span><br><span class="line">host all             all             0.0.0.0/0 scram-sha-256</span><br></pre></td></tr></table></figure><h3 id="总结建议"><a href="#总结建议" class="headerlink" title="总结建议"></a>总结建议</h3><ol><li><strong>首选</strong>：<code>scram-sha-256</code>（安全、标准）。</li><li><strong>本地运维</strong>：<code>peer</code>（Linux 下免密，安全且方便）。</li><li><strong>避免</strong>：<code>password</code>（明文传输，除非有 SSL）。</li><li><strong>慎用</strong>：<code>trust</code>（除非你非常清楚自己在做什么，且网络绝对安全）。</li></ol>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/18/608bddc6/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>pg_basebackup(物理备份)</title>
      <link>https://blog.eucalyptus.cc/2026/07/15/a6067988/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/15/a6067988/</guid>
      <pubDate>Wed, 15 Jul 2026 12:12:23 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;pg-basebackup（物理备份）&quot;&gt;&lt;a href=&quot;#pg-basebackup（物理备份）&quot; class=&quot;headerlink&quot; title=&quot;pg_basebackup（物理备份）&quot;&gt;&lt;/a&gt;pg_basebackup（物理备份）&lt;/h3&gt;&lt;h4</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="pg-basebackup（物理备份）"><a href="#pg-basebackup（物理备份）" class="headerlink" title="pg_basebackup（物理备份）"></a>pg_basebackup（物理备份）</h3><h4 id="常用参数速查"><a href="#常用参数速查" class="headerlink" title="常用参数速查"></a>常用参数速查</h4><table><thead><tr><th>参数</th><th>简写</th><th>说明</th><th>示例</th></tr></thead><tbody><tr><td>–pgdata&#x3D;DIRECTORY</td><td>-D</td><td>备份目标目录（必需）</td><td>-D &#x2F;backup&#x2F;base</td></tr><tr><td>–format&#x3D;p|t</td><td>-F</td><td>输出格式：plain&#x2F;tar</td><td></td></tr><tr><td>–wal-method&#x3D;METHOD</td><td>-X</td><td>WAL 处理方式</td><td>-Xs流复制</td></tr><tr><td>–checkpoint&#x3D;fast|spread</td><td></td><td>检查点模式</td><td></td></tr><tr><td>–progress</td><td>-P</td><td>显示进度</td><td>-P</td></tr><tr><td>–verbose</td><td>-v</td><td>详细输出</td><td>-v</td></tr><tr><td>–jobs&#x3D;NUM</td><td>-j</td><td>并行压缩&#x2F;传输</td><td>-j 4</td></tr><tr><td>–compress&#x3D;METHOD</td><td>-z</td><td>压缩方法</td><td>-z 9</td></tr><tr><td>–host&#x3D;HOSTNAME</td><td>-h</td><td>主机地址</td><td>-h 192.168.1.1</td></tr><tr><td>–port&#x3D;PORT</td><td>-p</td><td>端口</td><td>-p 5432</td></tr><tr><td>–username&#x3D;NAME</td><td>-U</td><td>用户名</td><td>-U rep</td></tr><tr><td>–no-password</td><td>-w</td><td>不提示密码</td><td>-w</td></tr><tr><td>–password</td><td>-W</td><td>强制提示密码</td><td>-W</td></tr></tbody></table><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br></pre></td><td class="code"><pre><span class="line">pg_basebackup takes a base backup of a running PostgreSQL server.</span><br><span class="line"></span><br><span class="line">Usage:</span><br><span class="line"></span><br><span class="line"> pg_basebackup [OPTION]...</span><br><span class="line"></span><br><span class="line">Options controlling the output:</span><br><span class="line"></span><br><span class="line"> -D, --pgdata=DIRECTORY receive base backup into directory</span><br><span class="line"></span><br><span class="line"> -F, --format=p|t output format (plain (default), tar)</span><br><span class="line"></span><br><span class="line"> -r, --max-rate=RATE maximum transfer rate to transfer data directory</span><br><span class="line"></span><br><span class="line"> (<span class="keyword">in</span> kB/s, or use suffix <span class="string">&quot;k&quot;</span> or <span class="string">&quot;M&quot;</span>)</span><br><span class="line"></span><br><span class="line"> -R, --write-recovery-conf</span><br><span class="line"></span><br><span class="line">                         write configuration <span class="keyword">for</span> replication</span><br><span class="line"></span><br><span class="line"> -t, --target=TARGET[:DETAIL]</span><br><span class="line"></span><br><span class="line"> backup target (<span class="keyword">if</span> other than client)</span><br><span class="line"></span><br><span class="line"> -T, --tablespace-mapping=OLDDIR=NEWDIR</span><br><span class="line"></span><br><span class="line"> relocate tablespace <span class="keyword">in</span> OLDDIR to NEWDIR</span><br><span class="line"></span><br><span class="line"> --waldir=WALDIR location <span class="keyword">for</span> the write-ahead <span class="built_in">log</span> directory</span><br><span class="line"></span><br><span class="line"> -X, --wal-method=none|fetch|stream</span><br><span class="line"></span><br><span class="line"> include required WAL files with specified method</span><br><span class="line"></span><br><span class="line"> -z, --gzip compress tar output</span><br><span class="line"></span><br><span class="line"> -Z, --compress=[&#123;client|server&#125;-]METHOD[:DETAIL]</span><br><span class="line"></span><br><span class="line"> compress on client or server as specified</span><br><span class="line"></span><br><span class="line"> -Z, --compress=none <span class="keyword">do</span> not compress tar output</span><br><span class="line"></span><br><span class="line">General options:</span><br><span class="line"></span><br><span class="line"> -c, --checkpoint=fast|spread</span><br><span class="line"></span><br><span class="line">                         <span class="built_in">set</span> fast or spread checkpointing</span><br><span class="line"></span><br><span class="line"> -C, --create-slot create replication slot</span><br><span class="line"></span><br><span class="line"> -l, --label=LABEL <span class="built_in">set</span> backup label</span><br><span class="line"></span><br><span class="line"> -n, --no-clean <span class="keyword">do</span> not clean up after errors</span><br><span class="line"></span><br><span class="line"> -N, --no-sync <span class="keyword">do</span> not <span class="built_in">wait</span> <span class="keyword">for</span> changes to be written safely to disk</span><br><span class="line"></span><br><span class="line"> -P, --progress show progress information</span><br><span class="line"></span><br><span class="line"> -S, --slot=SLOTNAME replication slot to use</span><br><span class="line"></span><br><span class="line"> -v, --verbose output verbose messages</span><br><span class="line"></span><br><span class="line"> -V, --version output version information, <span class="keyword">then</span> <span class="built_in">exit</span></span><br><span class="line"></span><br><span class="line"> --manifest-checksums=SHA&#123;224,256,384,512&#125;|CRC32C|NONE</span><br><span class="line"></span><br><span class="line">                         use algorithm <span class="keyword">for</span> manifest checksums</span><br><span class="line"></span><br><span class="line"> --manifest-force-encode</span><br><span class="line"></span><br><span class="line"> hex encode all file names <span class="keyword">in</span> manifest</span><br><span class="line"></span><br><span class="line"> --no-estimate-size <span class="keyword">do</span> not estimate backup size <span class="keyword">in</span> server side</span><br><span class="line"></span><br><span class="line"> --no-manifest suppress generation of backup manifest</span><br><span class="line"></span><br><span class="line"> --no-slot prevent creation of temporary replication slot</span><br><span class="line"></span><br><span class="line"> --no-verify-checksums</span><br><span class="line"></span><br><span class="line"> <span class="keyword">do</span> not verify checksums</span><br><span class="line"></span><br><span class="line"> -?, --<span class="built_in">help</span> show this <span class="built_in">help</span>, <span class="keyword">then</span> <span class="built_in">exit</span></span><br><span class="line"></span><br><span class="line">Connection options:</span><br><span class="line"></span><br><span class="line"> -d, --dbname=CONNSTR connection string</span><br><span class="line"></span><br><span class="line"> -h, --host=HOSTNAME database server host or socket directory</span><br><span class="line"></span><br><span class="line"> -p, --port=PORT database server port number</span><br><span class="line"></span><br><span class="line"> -s, --status-interval=INTERVAL</span><br><span class="line"></span><br><span class="line">                         <span class="keyword">time</span> between status packets sent to server (<span class="keyword">in</span> seconds)</span><br><span class="line"></span><br><span class="line"> -U, --username=NAME connect as specified database user</span><br><span class="line"></span><br><span class="line"> -w, --no-password never prompt <span class="keyword">for</span> password</span><br><span class="line"></span><br><span class="line"> -W, --password force password prompt (should happen automatically)</span><br><span class="line"></span><br><span class="line">Report bugs to &lt;pgsql-bugs@lists.postgresql.org&gt;.</span><br><span class="line"></span><br><span class="line">PostgreSQL home page: &lt;https://www.postgresql.org/&gt;</span><br></pre></td></tr></table></figure><h4 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h4><p>常用备份语法：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_basebackup -D /opt/pg_basebackup/$(<span class="built_in">date</span> +<span class="string">&quot;%Y%m%d_%H%M%S&quot;</span>) -Fp -Xs -P -v -U rep -h 192.168.0.3</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-15/img1.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_basebackup -D /opt/pg_basebackup/$(<span class="built_in">date</span> +<span class="string">&quot;%Y%m%d_%H%M%S&quot;</span>) -Ft -Xs -P -v -U rep -h 192.168.0.3</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-15/img2.avif"></p><p>backup_manifest</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-15/img3.avif"></p><h3 id="pg-dump"><a href="#pg-dump" class="headerlink" title="pg_dump"></a>pg_dump</h3><h4 id="常用参数速查-1"><a href="#常用参数速查-1" class="headerlink" title="常用参数速查"></a>常用参数速查</h4><table><thead><tr><th>参数</th><th>说明</th><th>示例</th></tr></thead><tbody><tr><td>-d, –dbname&#x3D;DBNAME</td><td>指定数据库</td><td>-d mydb</td></tr><tr><td>-U, –username&#x3D;NAME</td><td>用户名</td><td>-U postgres</td></tr><tr><td>-h, –host&#x3D;HOSTNAME</td><td>主机地址</td><td>-h 127.0.0.1</td></tr><tr><td>-p, –port&#x3D;PORT</td><td>端口</td><td>-p 5432</td></tr><tr><td>-f, –file&#x3D;FILENAME</td><td>输出文件（替代 &gt;）</td><td>-f backup.sql</td></tr><tr><td>-v, –verbose</td><td>详细输出</td><td>-v</td></tr><tr><td>-W, –password</td><td>强制提示密码</td><td>-W</td></tr><tr><td>-w, –no-password</td><td>从不提示密码</td><td>-w</td></tr></tbody></table><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br></pre></td><td class="code"><pre><span class="line">pg_dump dumps a database as a text file or to other formats.</span><br><span class="line"></span><br><span class="line">Usage:</span><br><span class="line"></span><br><span class="line"> pg_dump [OPTION]... [DBNAME]</span><br><span class="line"></span><br><span class="line">General options:</span><br><span class="line"></span><br><span class="line"> -f, --file=FILENAME output file or directory name/输出文件名或目录名</span><br><span class="line"></span><br><span class="line"> -F, --format=c|d|t|p output file format (custom, directory, tar,</span><br><span class="line"></span><br><span class="line"> plain text (default))</span><br><span class="line"></span><br><span class="line"> -j, --<span class="built_in">jobs</span>=NUM use this many parallel <span class="built_in">jobs</span> to dump</span><br><span class="line"></span><br><span class="line"> -v, --verbose verbose mode</span><br><span class="line"></span><br><span class="line"> -V, --version output version information, <span class="keyword">then</span> <span class="built_in">exit</span></span><br><span class="line"></span><br><span class="line"> -Z, --compress=METHOD[:DETAIL]</span><br><span class="line"></span><br><span class="line"> compress as specified</span><br><span class="line"></span><br><span class="line"> --lock-wait-timeout=TIMEOUT fail after waiting TIMEOUT <span class="keyword">for</span> a table lock</span><br><span class="line"></span><br><span class="line"> --no-sync <span class="keyword">do</span> not <span class="built_in">wait</span> <span class="keyword">for</span> changes to be written safely to disk</span><br><span class="line"></span><br><span class="line"> -?, --<span class="built_in">help</span> show this <span class="built_in">help</span>, <span class="keyword">then</span> <span class="built_in">exit</span></span><br><span class="line"></span><br><span class="line">Options controlling the output content:</span><br><span class="line"></span><br><span class="line"> -a, --data-only dump only the data, not the schema</span><br><span class="line"></span><br><span class="line"> -b, --large-objects include large objects <span class="keyword">in</span> dump</span><br><span class="line"></span><br><span class="line"> --blobs (same as --large-objects, deprecated)</span><br><span class="line"></span><br><span class="line"> -B, --no-large-objects exclude large objects <span class="keyword">in</span> dump</span><br><span class="line"></span><br><span class="line"> --no-blobs (same as --no-large-objects, deprecated)</span><br><span class="line"></span><br><span class="line"> -c, --clean clean (drop) database objects before recreating</span><br><span class="line"></span><br><span class="line"> -C, --create include commands to create database <span class="keyword">in</span> dump</span><br><span class="line"></span><br><span class="line"> -e, --extension=PATTERN dump the specified extension(s) only</span><br><span class="line"></span><br><span class="line"> -E, --encoding=ENCODING dump the data <span class="keyword">in</span> encoding ENCODING</span><br><span class="line"></span><br><span class="line"> -n, --schema=PATTERN dump the specified schema(s) only</span><br><span class="line"></span><br><span class="line"> -N, --exclude-schema=PATTERN <span class="keyword">do</span> NOT dump the specified schema(s)</span><br><span class="line"></span><br><span class="line"> -O, --no-owner skip restoration of object ownership <span class="keyword">in</span></span><br><span class="line"></span><br><span class="line"> plain-text format</span><br><span class="line"></span><br><span class="line"> -s, --schema-only dump only the schema, no data</span><br><span class="line"></span><br><span class="line"> -S, --superuser=NAME superuser user name to use <span class="keyword">in</span> plain-text format</span><br><span class="line"></span><br><span class="line"> -t, --table=PATTERN dump only the specified table(s)</span><br><span class="line"></span><br><span class="line"> -T, --exclude-table=PATTERN <span class="keyword">do</span> NOT dump the specified table(s)</span><br><span class="line"></span><br><span class="line"> -x, --no-privileges <span class="keyword">do</span> not dump privileges (grant/revoke)</span><br><span class="line"></span><br><span class="line"> --binary-upgrade <span class="keyword">for</span> use by upgrade utilities only</span><br><span class="line"></span><br><span class="line"> --column-inserts dump data as INSERT commands with column names</span><br><span class="line"></span><br><span class="line"> --disable-dollar-quoting <span class="built_in">disable</span> dollar quoting, use SQL standard quoting</span><br><span class="line"></span><br><span class="line"> --disable-triggers <span class="built_in">disable</span> triggers during data-only restore</span><br><span class="line"></span><br><span class="line"> --enable-row-security <span class="built_in">enable</span> row security (dump only content user has</span><br><span class="line"></span><br><span class="line">                               access to)</span><br><span class="line"></span><br><span class="line"> --exclude-table-and-children=PATTERN</span><br><span class="line"></span><br><span class="line"> <span class="keyword">do</span> NOT dump the specified table(s), including</span><br><span class="line"></span><br><span class="line"> child and partition tables</span><br><span class="line"></span><br><span class="line"> --exclude-table-data=PATTERN <span class="keyword">do</span> NOT dump data <span class="keyword">for</span> the specified table(s)</span><br><span class="line"></span><br><span class="line"> --exclude-table-data-and-children=PATTERN</span><br><span class="line"></span><br><span class="line"> <span class="keyword">do</span> NOT dump data <span class="keyword">for</span> the specified table(s),</span><br><span class="line"></span><br><span class="line"> including child and partition tables</span><br><span class="line"></span><br><span class="line"> --extra-float-digits=NUM override default setting <span class="keyword">for</span> extra_float_digits</span><br><span class="line"></span><br><span class="line"> --if-exists use IF EXISTS when dropping objects</span><br><span class="line"></span><br><span class="line"> --include-foreign-data=PATTERN</span><br><span class="line"></span><br><span class="line"> include data of foreign tables on foreign</span><br><span class="line"></span><br><span class="line"> servers matching PATTERN</span><br><span class="line"></span><br><span class="line"> --inserts dump data as INSERT commands, rather than COPY</span><br><span class="line"></span><br><span class="line"> --load-via-partition-root load partitions via the root table</span><br><span class="line"></span><br><span class="line"> --no-comments <span class="keyword">do</span> not dump comments</span><br><span class="line"></span><br><span class="line"> --no-publications <span class="keyword">do</span> not dump publications</span><br><span class="line"></span><br><span class="line"> --no-security-labels <span class="keyword">do</span> not dump security label assignments</span><br><span class="line"></span><br><span class="line"> --no-subscriptions <span class="keyword">do</span> not dump subscriptions</span><br><span class="line"></span><br><span class="line"> --no-table-access-method <span class="keyword">do</span> not dump table access methods</span><br><span class="line"></span><br><span class="line"> --no-tablespaces <span class="keyword">do</span> not dump tablespace assignments</span><br><span class="line"></span><br><span class="line"> --no-toast-compression <span class="keyword">do</span> not dump TOAST compression methods</span><br><span class="line"></span><br><span class="line"> --no-unlogged-table-data <span class="keyword">do</span> not dump unlogged table data</span><br><span class="line"></span><br><span class="line"> --on-conflict-do-nothing add ON CONFLICT DO NOTHING to INSERT commands</span><br><span class="line"></span><br><span class="line"> --quote-all-identifiers quote all identifiers, even <span class="keyword">if</span> not key words</span><br><span class="line"></span><br><span class="line"> --rows-per-insert=NROWS number of rows per INSERT; implies --inserts</span><br><span class="line"></span><br><span class="line"> --section=SECTION dump named section (pre-data, data, or post-data)</span><br><span class="line"></span><br><span class="line"> --serializable-deferrable <span class="built_in">wait</span> <span class="keyword">until</span> the dump can run without anomalies</span><br><span class="line"></span><br><span class="line"> --snapshot=SNAPSHOT use given snapshot <span class="keyword">for</span> the dump</span><br><span class="line"></span><br><span class="line"> --strict-names require table and/or schema include patterns to</span><br><span class="line"></span><br><span class="line"> match at least one entity each</span><br><span class="line"></span><br><span class="line"> --table-and-children=PATTERN dump only the specified table(s), including</span><br><span class="line"></span><br><span class="line"> child and partition tables</span><br><span class="line"></span><br><span class="line"> --use-set-session-authorization</span><br><span class="line"></span><br><span class="line">                               use SET SESSION AUTHORIZATION commands instead of</span><br><span class="line"></span><br><span class="line"> ALTER OWNER commands to <span class="built_in">set</span> ownership</span><br><span class="line"></span><br><span class="line">Connection options:</span><br><span class="line"></span><br><span class="line"> -d, --dbname=DBNAME database to dump</span><br><span class="line"></span><br><span class="line"> -h, --host=HOSTNAME database server host or socket directory</span><br><span class="line"></span><br><span class="line"> -p, --port=PORT database server port number</span><br><span class="line"></span><br><span class="line"> -U, --username=NAME connect as specified database user</span><br><span class="line"></span><br><span class="line"> -w, --no-password never prompt <span class="keyword">for</span> password</span><br><span class="line"></span><br><span class="line"> -W, --password force password prompt (should happen automatically)</span><br><span class="line"></span><br><span class="line"> --role=ROLENAME <span class="keyword">do</span> SET ROLE before dump</span><br><span class="line"></span><br><span class="line">If no database name is supplied, <span class="keyword">then</span> the PGDATABASE environment</span><br><span class="line"></span><br><span class="line">variable value is used.</span><br><span class="line"></span><br><span class="line">Report bugs to &lt;pgsql-bugs@lists.postgresql.org&gt;.</span><br><span class="line"></span><br><span class="line">PostgreSQL home page: &lt;https://www.postgresql.org/&gt;</span><br></pre></td></tr></table></figure><h4 id="示例-1"><a href="#示例-1" class="headerlink" title="示例"></a>示例</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_dump -U postgres -d demo1 &gt; $(<span class="built_in">date</span> +<span class="string">&quot;%Y%m%d_%H%M%S&quot;</span>).sql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-15/img4.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/15/a6067988/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>(1071, ‘Specified key was too long； max key length is 767 bytes‘)</title>
      <link>https://blog.eucalyptus.cc/2026/07/15/5c963531/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/15/5c963531/</guid>
      <pubDate>Wed, 15 Jul 2026 08:27:14 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;这个报错和ROW_FORMAT有关,在 MySQL 的 InnoDB 存储引擎中,ROW_FORMAT主要有4种格式,但在较旧的版本或特定语境下,常讨论的是前三种。以下是这四种格式的详细介绍和区别:&lt;/p&gt;
&lt;h5 id=&quot;REDUNDANT-冗余格式&quot;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>这个报错和ROW_FORMAT有关,在 MySQL 的 InnoDB 存储引擎中,ROW_FORMAT主要有4种格式,但在较旧的版本或特定语境下,常讨论的是前三种。以下是这四种格式的详细介绍和区别:</p><h5 id="REDUNDANT-冗余格式"><a href="#REDUNDANT-冗余格式" class="headerlink" title="REDUNDANT (冗余格式)"></a>REDUNDANT (冗余格式)</h5><p>来源:MySQL 5.0 之前的旧格式。</p><p>现状:不推荐使用,除非你需要迁移非常古老的数据库。</p><p>特点:</p><ul><li>为了向后兼容保留。</li><li>每个列都存储了长度前缀,即使定长字段也存。</li><li>缺点:占用空间大,性能较差。</li></ul><h5 id="COMPACT-紧凑格式-MySQL-5-0-5-7-默认"><a href="#COMPACT-紧凑格式-MySQL-5-0-5-7-默认" class="headerlink" title="COMPACT(紧凑格式) MySQL 5.0 - 5.7 默认"></a>COMPACT(紧凑格式) <strong>MySQL 5.0 - 5.7 默认</strong></h5><p>来源:MySQL 5.0 引入。</p><p>现状:在 MySQL 5.7 及之前是默认格式。现在依然广泛使用,但不如 DYNAMIC 灵活。</p><p>特点:</p><ul><li>去掉了 REDUNDANT中不必要的长度前缀。</li><li>NULL 值和长度为 0 的字段不占用存储空间 只占位标记 。</li><li>比 REDUNDANT更节省空间,CPU 开销更小。</li></ul><h5 id="DYNAMIC-动态格式-MySQL-5-7-8-0-默认"><a href="#DYNAMIC-动态格式-MySQL-5-7-8-0-默认" class="headerlink" title="DYNAMIC(动态格式)MySQL 5.7 &#x2F; 8.0 默认"></a>DYNAMIC(动态格式)<strong>MySQL 5.7 &#x2F; 8.0 默认</strong></h5><p>来源:MySQL 5.7 引入,8.0 成为默认值。</p><p>现状:现代 MySQL 的推荐默认格式。</p><ul><li>基于COMPACT格式改进。</li><li>关键区别:对于变长字段 如 VARCHAR, TEXT, BLOB ,如果数据太长无法完全存入主页面 Overflow Page ,DYNAMIC格式只会将前 20 字节 或更多,取决于实现 留在主页面,其余部分全部放到溢出页 Overflow Page 。</li><li>而 COMPACT格式会尝试将前 768 字节留在主页面。</li><li>优势:主页面能容纳更多的行索引记录,提高了缓冲池 Buffer Pool 的命中率,适合大字段较多的场景。</li></ul><h5 id="COMPRESSED-压缩格式"><a href="#COMPRESSED-压缩格式" class="headerlink" title="COMPRESSED(压缩格式)"></a>COMPRESSED(压缩格式)</h5><p>来源:MySQL 5.1 引入。</p><p>现状:适用于读多写少、磁盘空间紧张且 CPU 资源充足的场景。注意:在 MySQL 8.0.13 之后,官方已弃用此格式,建议改用表空间压缩或其他手段。</p><p>特点:</p><ul><li>基于 COMPACT格式。</li><li>使用 zlib 算法对数据和索引进行物理压缩。</li><li>可以显著减少磁盘占用和 I&#x2F;O,但会增加 CPU 负担 因为需要解压&#x2F;压缩 。</li><li>通常配合 KEY_BLOCK_SIZE使用。</li></ul><h5 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h5><table><thead><tr><th>REDUNDANT</th><th>COMPACT</th><th>DYNAMIC</th><th>COMPRESSED</th><th>特性</th></tr></thead><tbody><tr><td>引入版本</td><td>&lt; 5.0</td><td>5.0</td><td>5.7</td><td>5.1</td></tr><tr><td>默认状态</td><td>过时</td><td>5.7及以前默认</td><td>8.0 默认</td><td>需手动开启</td></tr><tr><td>大字段处理</td><td>全部存溢出页</td><td>前768字节在主页</td><td>仅前20字节在主页</td><td>压缩后存储</td></tr><tr><td>空间效率</td><td>低</td><td>中</td><td>高</td><td>最高 (但耗CPU)</td></tr><tr><td>性能</td><td>低</td><td>中</td><td>高 (缓存命中率高)</td><td>低 (CPU密集)</td></tr><tr><td>推荐程度</td><td>不推荐</td><td>可用</td><td>推荐</td><td>特定场景</td></tr></tbody></table><p>在 MySQL 5.6 及更早版本 或者手动设置了innodb_large_prefix OFF 中:</p><ul><li>COMPACT&#x2F; REDUNDANT格式限制:单个索引列的最大长度限制为 767 字节。</li><li>DYNAMIC &#x2F;COMPRESSED 格式限制:如果启用了innodb_large_prefix ON MySQL 5.7 默认开启 ,最大长度限制提升至 3072 字节。</li></ul><p>为什么会出现这个错误?最常见的情景是你在VARCHAR字段上创建索引,且使用了utf8mb4字符集。</p><ul><li>字符集计算:utf8mb4每个字符最多占用 4 个字节。</li><li>临界点计算:767 bytes&#x2F;4 bytes per char 191.75767 bytes&#x2F;4 bytes per char 191.75。所以,在COMPACT格式下,utf8mb4的 VARCHAR 字段如果长度超过 191,创建索引就会报错。</li></ul><p>例如下面的场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-07-15/img1.avif"></p><p>那有人可能会说这个idx_name不也才8个字符,为什么会超出限制呢?</p><p>这是一个非常经典的误解 这里有两个概念混淆了: 索引名的长度 和 索引列内容的长度 。报错 Specified key was too long指的不是索引的名字 idx_name 太长,而是你试图建立索引的那个字段 列 里的数据内容可能太长,超过了限制。</p><p>澄清概念</p><ul><li><p>idx_name:这是索引对象的名称。MySQL 对索引名的限制通常是64个字符。idx_name只有 8 个字符,完全没问题。</p></li><li><p>key length (报错中的 key):指的是被索引的那一列数据在索引树中占用的字节数。</p></li></ul><p>那有人可能又会说如果varchar(255)中我只存 abc 呢?VARCHAR确实是“弹性”的 变长 ,它只占用实际存储数据所需的字节数加上1-2个字节的长度前缀。如果里面存的是 abc ,它确实只占很少的空间。但是,索引 Index 的工作机制不同。索引 B Tree 是一个预分配结构。当 MySQL InnoDB 引擎创建索引时,它必须为索引中的每一个条目 Entry 预留足够的空间,以容纳该列可能出现的最大值。</p><p>在数据库底层:</p><ul><li>固定偏移量计算:InnoDB 需要知道索引记录中每一列的最大可能长度,以便快速计算下一条记录的起始位置。</li><li>页内布局:在一个 16KB MySQL 或 8KB PG 的数据页中,引擎需要确保即使所有行都填满最大长度,页面也不会溢出到无法管理的状态。</li></ul><p>因此,索引长度的限制是基于列定义的MAX LENGTH,而不是当前行的ACTUAL LENGTH 。</p><h3 id="解决方案"><a href="#解决方案" class="headerlink" title="解决方案"></a>解决方案</h3><h4 id="8-0"><a href="#8-0" class="headerlink" title="8.0"></a>8.0</h4><p>将row_format设置为dynamic即可</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> t1 row_format <span class="keyword">dynamic</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-07-15/img2.avif"></p><h3 id="5-6-5-7"><a href="#5-6-5-7" class="headerlink" title="5.6&#x2F;5.7"></a>5.6&#x2F;5.7</h3><p>将row_format设置为dynamic,并将innodb_large_prefix设置为ON,这2个条件必须都生效</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-07-15/img3.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/15/5c963531/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0+中引入的SET_USER_ID权限</title>
      <link>https://blog.eucalyptus.cc/2026/07/10/afa06306/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/10/afa06306/</guid>
      <pubDate>Fri, 10 Jul 2026 07:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;code&gt;SET_USER_ID&lt;/code&gt; 是 MySQL 8.0 引入的一个细粒度权限 Granular Privilege ,旨在解决“最小权限原则”与“指定 DEFINER”之间的矛盾。&lt;/p&gt;
&lt;p&gt;在 MySQL 5.7 及以前,如果你想创建一个</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><code>SET_USER_ID</code> 是 MySQL 8.0 引入的一个细粒度权限 Granular Privilege ,旨在解决“最小权限原则”与“指定 DEFINER”之间的矛盾。</p><p>在 MySQL 5.7 及以前,如果你想创建一个 <code>DEFINER</code> 为其他用户 非当前</p><p>然而,<code>SUPER</code> 权限过大,它包含了重启服务器、修改全局变量、杀死任意线程等高危操作。为了安全起见,云数据库 如阿里云 RDS、AWS Aurora 通常禁止给用户授予 <code>SUPER</code> 权限。</p><p>这就导致了一个困境:普通管理员无法创建指定其他用户为 DEFINER 的对象。</p><p>MySQL 8.0 引入 <code>SET_USER_ID</code>就是为了解决这个问题。</p><h3 id="SET-USER-ID-的核心作用"><a href="#SET-USER-ID-的核心作用" class="headerlink" title="SET_USER_ID 的核心作用"></a><code>SET_USER_ID</code> 的核心作用</h3><p>拥有 <code>SET_USER_ID</code> 权限的用户,可以执行以下操作:</p><ul><li>在创建存储过程、函数、视图、触发器时,指定任意其他用户作为 <code>DEFINER</code>。</li><li>使用 <code>SET ROLE</code> 语句切换角色。</li><li>本质上,它允许你“冒充”另一个用户的身份来定义对象,但不赋予你该用户的其他特权 如删除数据、重启服务等 。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-07-10/img1.avif"></p><h3 id="为什么需要它-场景举例"><a href="#为什么需要它-场景举例" class="headerlink" title="为什么需要它? 场景举例"></a>为什么需要它? 场景举例</h3><p>假设你是一个 DevOps 工程师,负责部署应用。</p><ul><li>应用代码中有一个存储过程 <code>proc_update_order</code>。</li><li>为了安全,这个存储过程应该以应用专用账号 <code>app_user</code> 的身份运行 即 <code>DEFINER &#39;app_user&#39; &#39;%&#39;</code> ,而不是以你的个人管理员账号 <code>admin_user</code> 运行。</li><li>在 MySQL 5.7 中:你需要 <code>SUPER</code> 权限才能创建 <code>DEFINER &#39;app_user&#39;</code> 的过程。但云厂商不给你 <code>SUPER</code>。</li><li>在 MySQL 8.0 中:DBA 可以只给你授予 <code>SET_USER_ID</code> 权限。你就可以合法地创建 <code>DEFINER &#39;app_user&#39;</code> 的过程,而无需拥有危险的 <code>SUPER</code> 权限。</li></ul><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><ul><li>在原生 MySQL 中,SET_USER_ID 是一个全局权限 Global Privilege</li><li>授予此权限需要 SUPER 权限执行</li><li>SET_USER_ID是 MySQL 8.0 引入</li></ul><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><p><code>SET_USER_ID</code> 是 MySQL 8.0 为了安全地替代 <code>SUPER</code> 权限中“指定 DEFINER”这一功能而设计的。它是一个好特性,但在当前的云数据库环境中,普及度和开放度依然有限。对于大多数开发者来说,避免硬编码 <code>DEFINER</code> 仍然是最稳妥、兼容性最好的做法。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/10/afa06306/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL中MVCC实现机制</title>
      <link>https://blog.eucalyptus.cc/2026/07/08/d92ff1f6/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/08/d92ff1f6/</guid>
      <pubDate>Wed, 08 Jul 2026 13:16:42 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;MVCC原理&quot;&gt;&lt;a href=&quot;#MVCC原理&quot; class=&quot;headerlink&quot; title=&quot;MVCC原理&quot;&gt;&lt;/a&gt;MVCC原理&lt;/h3&gt;&lt;p&gt;多版本并发控制（Multi-Version Concurrency</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="MVCC原理"><a href="#MVCC原理" class="headerlink" title="MVCC原理"></a>MVCC原理</h3><p>多版本并发控制（Multi-Version Concurrency Control，MVCC），是数据库中并发访问数据时保证数据一致性的一种方法。</p><p>在并发操作中，当正在写时，如果有用户在读，这时写可能只写了一半，如一行的前半部分刚写入，后半部分还没有写入，这时可能读的用户读取到的数据行的前半部分数据是新的，后半部分数据是原来的，这就导致了数据一致性问题。</p><p>解决这个问题的最简单的方法是使用读写锁，写的时候不允许读，正在读的时候也不允许写，但这种方法会导致读和写的操作不能并发执行。</p><p>于是，有人想到了一种能够让读写并发执行的方法，这种方法就是MVCC。</p><p>MVCC方法是写数据时，原数据并不删除，并发的读还能读到原数据，这样就不会有数据一致性问题了。</p><p>实现MVCC的方法有以下两种：</p><ul><li><p>第一种：写新数据时，把原数据移到一个单独的位置，如回滚段中，其他用户读数据时，从回滚段中把原数据读出来。</p></li><li><p>第二种：写新数据时，原数据不删除，而是把新数据插入进来。</p></li></ul><p>PostgreSQL数据库使用的是第二种方法，而Oracle数据库和MySQL数据库中的InnoDB引擎使用的是第一种方法。</p><h3 id="PostgreSQL中的多版本并发控制"><a href="#PostgreSQL中的多版本并发控制" class="headerlink" title="PostgreSQL中的多版本并发控制"></a>PostgreSQL中的多版本并发控制</h3><p>PostgreSQL中的多版本实现是通过把原数据留在数据文件中，新插入一条数据来实现多版本的功能的。</p><p>每张表上都有4个系统字段”xmin””xmax””cmin””cmax”，这4个字段就是为多版本的功能而添加的。</p><table><thead><tr><th>字段</th><th>类型</th><th>含义</th></tr></thead><tbody><tr><td>xmin</td><td>xid</td><td>插入该行的事务ID（行的”出生证明”）</td></tr><tr><td>xmax</td><td>xid</td><td>删除&#x2F;更新该行的事务ID（0表示未被删除）</td></tr><tr><td>cmin</td><td>cid</td><td>插入该行的命令序号（同一事务内的第几条语句）</td></tr><tr><td>cmax</td><td>cid</td><td>删除该行的命令序号（同一事务内）</td></tr><tr><td>ctid</td><td>tid</td><td>表示表内的物理位置（第一个数字表示数据行所在的物理块的物理块号，第二个数字表示数据行在物理块中的行号）</td></tr></tbody></table><p>xmin、xmax、cmin、cmax这4个字段在多版本实现中用于控制数据行是否对用户可见。</p><p>PostgreSQL将修改前后的数据存储在相同的结构中，分为以下几种情况：</p><ul><li>新插入一行时，将新插入行的xmin填写为当前的事务ID，xmax填”0”。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img1.avif"></p><ul><li>修改这一行时，实际上新插入一行，原数据行上的xmin不变，xmax改为当前的事务ID，新数据行上的xmin填为当前的事务ID，xmax填”0”。</li></ul><p>如下图所示，lp&#x3D;2 和 lp&#x3D;3 的 t_ctid 都是 (0,3)。这说明 UPDATE 操作产生的新旧版本共享同一个 ctid 槽位引用（新版本指向自身，旧版本的 t_ctid 在 UPDATE 时未被修改），但它们是两个独立的物理元组，通过 xmin&#x2F;xmax 形成版本链。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img2.avif"></p><p>通过 pageinspect 插件直接读取页面原始内容查看旧行数据：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line"> lp, <span class="comment">-- 行指针编号 (Line Pointer)</span></span><br><span class="line"> t_ctid, <span class="comment">-- 元组的 ctid</span></span><br><span class="line"> t_xmin, <span class="comment">-- 插入事务ID</span></span><br><span class="line"> t_xmax, <span class="comment">-- 删除/更新事务ID</span></span><br><span class="line"> t_infomask2, <span class="comment">-- 属性标志位（含 cmin/cmax）</span></span><br><span class="line"> t_hoff, <span class="comment">-- 头部长度</span></span><br><span class="line"> t_data <span class="comment">-- 原始用户数据（bytea 十六进制）</span></span><br><span class="line"><span class="keyword">FROM</span> heap_page_items(get_raw_page(<span class="string">&#x27;t1&#x27;</span>, <span class="number">0</span>));</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img3.avif"></p><ul><li>删除一行时，把被删除行上的xmax填写当前的事务ID，xmax不等于0不一定是死元组。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img4.avif"></p><p>从上面的叙述中就可以知道，xmin就是标记插入数据行的事务ID，而xmax就是标记删除数据行的事务ID。没有修改数据行的操作，因为修改数据行，实际上就是把原数据行上的xmax标记上自己的事务ID（相当于打上删除标记），然后再新插入一条记录。所以最新版本的数据即xmax为0的一条。</p><p>当两个事务同时访问记录时，通过参考xmin和xmax的标记判断记录的版本，根据版本号与自己当前的事务标识进行比较，确定自己的数据权限。</p><p>当删除数据时，记录并没有从数据块中被删除，空间也没有立即释放。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img6.avif"></p><p>PostgreSQL的多版本实现中首先要解决的是原数据的空间释放问题。</p><p>PostgreSQL通过运行Vaccum进程来回收之前的存储空间，默认PostgreSQL数据库中的AutoVacuum是打开的，也就是说，当一个表的更新量达到一定值时（<strong>死元组数&gt;50+(0.2×活行数</strong>），AutoVacuum自动回收空间。</p><p>当然也可以关闭AutoVacuum进程，然后在业务低峰期手动运行VACUUM命令来回收空间。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img7.avif"></p><p>在PostgreSQL中，若一个事务执行失败，在数据文件中该事务产生的数据并不会在事务回滚时被清理掉。为什么要这样做呢？为什么不在事务提交时把这些数据标记成有效，而在事务回滚时把这些数据标记成无效呢？</p><p>这是出于效率的考虑。</p><p>若事务提交或回滚时再次标记数据，那这些数据就有可能会被刷新到磁盘中，再次标记会导致另一次I&#x2F;O，从而降低性能。</p><p>那么如何知道这些数据是有效还是无效呢？</p><p>PostgreSQL通过记录事务的状态来实现。</p><p>数据行上记录了xmin和xmax，只需了解xmin和xmax对应的事务是成功提交还是回滚了，就可以知道这些数据行是否有效。</p><p>PostgreSQL把事务状态记录在pg_xact（旧版本中被称为pg_clog），在数据目录的pg_xact子目录下：</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img8.avif"></p><p>但是pg_xact是一个二进制文件目录不能直接查询，可以通过内置函数 txid_status()确定事务是提交还是回滚：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">committed: 事务已成功提交</span><br><span class="line">aborted: 事务已回滚（中止）</span><br><span class="line">in progress: 事务仍在运行中</span><br><span class="line">null: 事务 ID 太老，状态信息已被清理（见下文&quot;事务 ID 回卷&quot;）</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-08/img10.avif"></p><h3 id="PostgreSQL多版本的优劣分析"><a href="#PostgreSQL多版本的优劣分析" class="headerlink" title="PostgreSQL多版本的优劣分析"></a>PostgreSQL多版本的优劣分析</h3><p>Oracle数据库和MySQL数据库的InnoDB引擎也都实现了多版本的功能，但它们与PostgreSQL的实现方式是不一样的，在这两个数据库中，旧版本的数据并不记录在原先的数据块中，而是被记录在回滚段中，如果要读取旧版本的数据，需要根据回滚段的数据重构旧版本数据。</p><p>PostgreSQL的多版本机制与Java虚拟机的垃圾回收机制比较相像。</p><p>事务提交前，只需要访问原来的数据即可；提交后，系统更新元组的存储标识，直到Vaccum进程收回为止。</p><p>相对于InnoDB和Oracle，PostgreSQL的多版本的优势在于以下几点：</p><ul><li><p>事务回滚可以立即完成，无论事务进行了多少操作。</p></li><li><p>数据可以进行很多更新，不必像Oracle和InnoDB那样需要经常保证回滚段不会被用完，也不会像Oracle数据库那样，经常遇到”ORA-1555”错误的困扰。</p></li></ul><p>相对于InnoDB和Oracle，PostgreSQL的多版本的劣势在于以下几点：</p><ul><li><p>旧版本数据需要清理。PostgreSQL清理旧版本称为VACUUM，并提供了VACUUM命令进行清理。</p></li><li><p>旧版本的数据会导致查询更慢一些，因为旧版本的数据存储于数据文件中，查询时需要扫描更多的数据块。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/08/d92ff1f6/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL中的插件管理</title>
      <link>https://blog.eucalyptus.cc/2026/07/02/8e4ee321/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/02/8e4ee321/</guid>
      <pubDate>Thu, 02 Jul 2026 13:43:04 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;PG 内核本身不包含所有扩展的文件，许多发行版将扩展拆分为独立包，仅安装 postgresql-server 是不够的，启用插件之前需要在宿主机上安装 &lt;code&gt;*-contrib&lt;/code&gt; 软件包，但是安装 &lt;code&gt;*-contrib&lt;/code&gt;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>PG 内核本身不包含所有扩展的文件，许多发行版将扩展拆分为独立包，仅安装 postgresql-server 是不够的，启用插件之前需要在宿主机上安装 <code>*-contrib</code> 软件包，但是安装 <code>*-contrib</code> 软件包的话，需要使用到 pgdg 仓库，没有则需要先部署仓库：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">dnf install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-$(rpm -E %&#123;rhel&#125;)-x86_64/pgdg-redhat-repo-latest.noarch.rpm</span><br><span class="line"></span><br><span class="line">dnf install postgresql16-contrib</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img3.avif"></p><p>第三方插件需要单独安装，例如 postgis：</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img4.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">ls</span> /usr/pgsql-16/share/extension</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img5.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">dnf install -y postgis34_16</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-07-02/img7.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/02/8e4ee321/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL中的事务ID回卷和冻结</title>
      <link>https://blog.eucalyptus.cc/2026/07/02/d6aa4ae7/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/02/d6aa4ae7/</guid>
      <pubDate>Thu, 02 Jul 2026 13:42:42 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;事务 ID 回卷（Transaction ID Wraparound）是 PostgreSQL 中最严重、最致命的潜在故障之一。如果处理不当，它会导致数据库停止服务，甚至造成数据永久丢失。&lt;/p&gt;
&lt;p&gt;简单来说，这是因为 PostgreSQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>事务 ID 回卷（Transaction ID Wraparound）是 PostgreSQL 中最严重、最致命的潜在故障之一。如果处理不当，它会导致数据库停止服务，甚至造成数据永久丢失。</p><p>简单来说，这是因为 PostgreSQL 用来标记事务的”计数器”用完了，不得不从头开始数，从而导致新旧数据混淆。</p><h3 id="核心原理：32位整数的限制"><a href="#核心原理：32位整数的限制" class="headerlink" title="核心原理：32位整数的限制"></a>核心原理：32位整数的限制</h3><p>PostgreSQL 使用一个 32位无符号整数 (<code>xid</code>) 来标识每一个事务。</p><ul><li>最大值：2^32-1 ≈ 42.9亿。</li><li>含义：PG 最多只能容纳约 42 亿个事务。</li></ul><h3 id="为什么回卷会导致数据丢失？"><a href="#为什么回卷会导致数据丢失？" class="headerlink" title="为什么回卷会导致数据丢失？"></a>为什么回卷会导致数据丢失？</h3><p>PostgreSQL 依靠 MVCC（多版本并发控制）来判断哪行数据对当前事务可见。判断逻辑依赖于比较当前事务 ID 和数据行的创建&#x2F;删除事务 ID。</p><p>正常情况：</p><ul><li>当前事务 ID &#x3D; 100。</li><li>数据行 A 由事务 50 创建。</li><li>因为 100 &gt; 50，所以事务 100 能看到数据行 A。</li></ul><p>回卷发生时（灾难场景）：</p><p>假设事务 ID 已经跑到了 42 亿，然后回卷到了 10。</p><ul><li>旧数据：由事务 40 亿创建（在物理时间上是很久以前创建的，逻辑上应该是”过去”）。</li><li>当前事务：ID 为 10。</li><li>比较结果：PG 发现 10 &lt; 40亿。</li><li>错误判断：PG 会认为事务 40 亿是未来发生的事务！</li><li>后果：根据 MVCC 规则，当前事务不能看到”未来”的数据。于是，所有旧数据突然对查询不可见了！你的表看起来像是空了，或者数据错乱。</li></ul><h3 id="PostgreSQL-如何防止回卷？（Vacuum-Freeze）"><a href="#PostgreSQL-如何防止回卷？（Vacuum-Freeze）" class="headerlink" title="PostgreSQL 如何防止回卷？（Vacuum Freeze）"></a>PostgreSQL 如何防止回卷？（Vacuum Freeze）</h3><p>为了防止这种灾难，PostgreSQL 引入了一种机制叫”冻结”（Freezing）。</p><h4 id="什么是冻结？"><a href="#什么是冻结？" class="headerlink" title="什么是冻结？"></a>什么是冻结？</h4><p>当 <code>VACUUM</code> 进程运行时，它不仅清理死元组，还会检查那些非常古老的活元组。</p><ul><li>如果某个数据行的事务 ID 已经很老（比如超过 20 亿），VACUUM 会将该行的事务 ID 替换为一个特殊的常量：<code>FrozenXID</code>（通常设为 2）。</li><li>含义：<code>FrozenXID</code> 代表”这个数据在所有事务之前就已经存在了”。</li><li>效果：无论当前事务 ID 回卷到多少，<code>FrozenXID</code> (2) 永远小于任何正常事务 ID。因此，这些数据永远可见，不会再参与大小比较。</li></ul><h4 id="关键阈值："><a href="#关键阈值：" class="headerlink" title="关键阈值："></a>关键阈值：</h4><p>PG 设定了一个安全界限，通常是 20 亿个事务（<code>autovacuum_freeze_max_age</code>，默认 2亿，但内部保护机制在 20亿左右强制介入）。</p><ul><li>如果一个表中有数据行的年龄超过 20 亿事务未被冻结，PG 会发出警告。</li><li>如果超过 21.47 亿（2^31），PG 会强制停止所有写操作，并强制执行紧急 Vacuum Freeze，直到所有旧数据被冻结。此时数据库处于只读模式，业务完全中断。</li></ul><h3 id="如何监控事务-ID-年龄？"><a href="#如何监控事务-ID-年龄？" class="headerlink" title="如何监控事务 ID 年龄？"></a>如何监控事务 ID 年龄？</h3><p>你可以查询 <code>pg_stat_user_tables</code> 或 <code>pg_class</code> 来查看表的”年龄”（Age）。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line"> relname <span class="keyword">AS</span> table_name,</span><br><span class="line"> age(relfrozenxid) <span class="keyword">AS</span> transaction_age, <span class="comment">-- 事务年龄</span></span><br><span class="line"> mxid_age(relminmxid) <span class="keyword">AS</span> multixact_age <span class="comment">-- 多事务年龄</span></span><br><span class="line"><span class="keyword">FROM</span> pg_class</span><br><span class="line"><span class="keyword">WHERE</span> relkind <span class="operator">=</span> <span class="string">&#x27;r&#x27;</span> <span class="comment">-- 普通表</span></span><br><span class="line"><span class="keyword">ORDER</span> <span class="keyword">BY</span> age(relfrozenxid) <span class="keyword">DESC</span></span><br><span class="line">LIMIT <span class="number">10</span>;</span><br></pre></td></tr></table></figure><p><code>age</code> 含义：当前最新事务 ID 与该表最老未冻结事务 ID 的差值。</p><p>危险信号：</p><ul><li><code>age &gt; 10亿</code>：需要关注，检查 Autovacuum 是否正常工作。</li><li><code>age &gt; 15亿</code>：高危，建议手动执行 <code>VACUUM FREEZE</code>。</li><li><code>age &gt; 20亿</code>：紧急！数据库可能即将进入强制只读保护状态。</li></ul><h3 id="为什么会发生回卷危机？"><a href="#为什么会发生回卷危机？" class="headerlink" title="为什么会发生回卷危机？"></a>为什么会发生回卷危机？</h3><p>通常是因为 VACUUM 没有及时运行，导致旧数据没有被冻结。常见原因包括：</p><ol><li>Autovacuum 被禁用或配置错误：有人为了性能关掉了自动真空。</li><li>长事务阻塞：如你之前遇到的，长事务阻止了 VACUUM 清理和冻结旧数据。</li><li>高并发写入：事务产生速度极快，Autovacuum 跟不上节奏。</li><li>复制槽滞后：逻辑复制槽阻止了 WAL 日志的清理，进而影响 Vacuum。</li></ol><h3 id="解决方案与预防"><a href="#解决方案与预防" class="headerlink" title="解决方案与预防"></a>解决方案与预防</h3><h4 id="预防措施"><a href="#预防措施" class="headerlink" title="预防措施"></a>预防措施</h4><ol><li>保持 Autovacuum 开启：这是最重要的防线。</li><li>调整冻结参数：对于高频更新的大表，降低冻结阈值：</li></ol><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> my_table <span class="keyword">SET</span> (autovacuum_freeze_max_age <span class="operator">=</span> <span class="number">50000000</span>); <span class="comment">-- 5千万</span></span><br></pre></td></tr></table></figure><ol start="3"><li>避免长事务：长事务会阻止 Vacuum 冻结旧数据。</li><li>监控 Age：设置监控告警，当 <code>age(relfrozenxid)</code> 超过 10 亿时报警。</li></ol><h4 id="紧急处理（如果-Age-接近-20-亿）"><a href="#紧急处理（如果-Age-接近-20-亿）" class="headerlink" title="紧急处理（如果 Age 接近 20 亿）"></a>紧急处理（如果 Age 接近 20 亿）</h4><p>手动执行 Vacuum Freeze：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">VACUUM FREEZE VERBOSE my_table;</span><br></pre></td></tr></table></figure><ul><li>这会强制冻结所有旧数据，降低表的 Age。</li><li>注意：这会消耗大量 IO 和 CPU，可能在业务低峰期执行。</li></ul><p>如果数据库已进入只读保护：</p><ul><li>你必须等待强制 Vacuum 完成。这个过程可能非常漫长（几小时甚至几天，取决于表大小）。</li><li>在此期间，无法写入任何数据。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/02/d6aa4ae7/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL中的死元组（Dead tuple）</title>
      <link>https://blog.eucalyptus.cc/2026/07/02/fdc989e2/</link>
      <guid>https://blog.eucalyptus.cc/2026/07/02/fdc989e2/</guid>
      <pubDate>Thu, 02 Jul 2026 13:41:50 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h4 id=&quot;为什么会有死元组？（MVCC机制）&quot;&gt;&lt;a href=&quot;#为什么会有死元组？（MVCC机制）&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h4 id="为什么会有死元组？（MVCC机制）"><a href="#为什么会有死元组？（MVCC机制）" class="headerlink" title="为什么会有死元组？（MVCC机制）"></a>为什么会有死元组？（MVCC机制）</h4><p>PostgreSQL 使用 MVCC（多版本并发控制）来实现高并发和事务隔离。这与 MySQL (InnoDB) 的机制有很大不同。</p><p>当你执行 <code>UPDATE</code> 时：</p><ol><li>PG 不会直接修改原来的那一行数据。</li><li>PG 会将旧行标记为”死亡”（设置 <code>xmax</code> 事务ID）。</li><li>PG 会插入一个全新的行，包含更新后的数据。</li><li>结果：表中同时存在”旧版本（死元组）”和”新版本（活元组）”。</li></ol><p>当你执行 <code>DELETE</code> 时：</p><ol><li>PG 不会直接从磁盘移除该行。</li><li>PG 只是将该行标记为”死亡”（设置 <code>xmax</code> 事务ID）。</li><li>结果：该行变成了死元组，依然占据磁盘空间。</li></ol><p>为什么要这样做？为了事务隔离。</p><p>假设事务 A 正在读取某行数据，此时事务 B 更新了这行数据。</p><ul><li>如果 PG 直接覆盖了旧数据，事务 A 就会读到不一致的数据（违反了隔离性）。</li><li>通过保留旧版本（死元组），事务 A 可以继续读取它启动时看到的那个版本，而事务 B 读取新版本。互不干扰。</li></ul><h3 id="死元组的危害"><a href="#死元组的危害" class="headerlink" title="死元组的危害"></a>死元组的危害</h3><p>如果死元组不及时清理，会带来严重后果：</p><p><strong>表膨胀（Table Bloat）：</strong></p><ul><li>表文件越来越大，即使你只存了 1GB 的有效数据，表文件可能高达 10GB（全是死元组）。</li><li>导致磁盘空间浪费。</li></ul><p><strong>查询性能下降：</strong></p><ul><li>扫描表（Seq Scan）或索引时，PG 必须跳过大量的死元组。</li><li>索引也会变得庞大且碎片化，降低索引效率。</li></ul><p><strong>事务 ID 回卷风险（Transaction ID Wraparound）：</strong></p><ul><li>PG 使用 32 位整数存储事务 ID。如果死元组不被清理（冻结），事务 ID 用完后会发生回卷，导致数据丢失且数据库无法启动。这是 PG 最严重的故障之一。</li></ul><h3 id="死元组何时被清理？"><a href="#死元组何时被清理？" class="headerlink" title="死元组何时被清理？"></a>死元组何时被清理？</h3><p>死元组不会自动消失，必须由 <code>VACUUM</code> 进程来清理。</p><h4 id="清理的条件（Visibility-Map）"><a href="#清理的条件（Visibility-Map）" class="headerlink" title="清理的条件（Visibility Map）"></a>清理的条件（Visibility Map）</h4><p>VACUUM 只能清理那些对所有当前活跃事务都不可见的死元组。</p><ul><li>如果有一个长事务（Long-running Transaction）还在运行，并且它可能需要看到某个旧版本的数据，那么 VACUUM 不能删除那个死元组。</li><li>这就是你之前遇到 <code>dead row versions cannot be removed yet</code> 的原因。</li></ul><h4 id="清理的过程"><a href="#清理的过程" class="headerlink" title="清理的过程"></a>清理的过程</h4><ul><li><strong>标记可用</strong>：VACUUM 将死元组占用的空间标记为”空闲”，供后续的 <code>INSERT</code> 或 <code>UPDATE</code> 复用。</li><li><strong>更新可见性映射（Visibility Map）</strong>：记录哪些页面完全由活元组组成，加速后续查询。</li><li><strong>冻结事务 ID</strong>：防止事务 ID 回卷。</li></ul><p>注意：普通的 <code>VACUUM</code> 不会缩小表文件的大小（不会归还空间给操作系统），它只是让空间在内部可复用。只有 <code>VACUUM FULL</code> 才会真正缩小文件。</p><h3 id="如何监控死元组？"><a href="#如何监控死元组？" class="headerlink" title="如何监控死元组？"></a>如何监控死元组？</h3><p>你可以查询系统视图 <code>pg_stat_user_tables</code> 来查看表的死元组情况：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line"> relname <span class="keyword">AS</span> table_name,</span><br><span class="line"> n_live_tup <span class="keyword">AS</span> live_tuples, <span class="comment">-- 活元组数量</span></span><br><span class="line"> n_dead_tup <span class="keyword">AS</span> dead_tuples, <span class="comment">-- 死元组数量</span></span><br><span class="line">    last_vacuum, <span class="comment">-- 上次手动 vacuum 时间</span></span><br><span class="line">    last_autovacuum, <span class="comment">-- 上次自动 vacuum 时间</span></span><br><span class="line">    last_autoanalyze <span class="comment">-- 上次自动 analyze 时间</span></span><br><span class="line"><span class="keyword">FROM</span> pg_stat_user_tables</span><br><span class="line"><span class="keyword">ORDER</span> <span class="keyword">BY</span> n_dead_tup <span class="keyword">DESC</span>;</span><br></pre></td></tr></table></figure><ul><li>健康状态：<code>n_dead_tup</code> 应该接近 0，或者远小于 <code>n_live_tup</code>。</li><li>危险信号：如果 <code>n_dead_tup</code> 很大（例如几百万），且 <code>last_autovacuum</code> 是很久以前，说明 Autovacuum 失效或被阻塞，表正在严重膨胀。</li></ul><h3 id="如何处理过多的死元组？"><a href="#如何处理过多的死元组？" class="headerlink" title="如何处理过多的死元组？"></a>如何处理过多的死元组？</h3><h4 id="依赖-Autovacuum（默认推荐）"><a href="#依赖-Autovacuum（默认推荐）" class="headerlink" title="依赖 Autovacuum（默认推荐）"></a>依赖 Autovacuum（默认推荐）</h4><p>PostgreSQL 有一个后台进程叫 <code>autovacuum</code>，它会自动检测表的变动并触发 VACUUM。</p><p>调优建议：对于高频更新的表，可以单独调整其存储参数：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> ais41.recentships <span class="keyword">SET</span> (autovacuum_vacuum_scale_factor <span class="operator">=</span> <span class="number">0.05</span>);</span><br></pre></td></tr></table></figure><p>（默认是 0.2，即 20% 的死元组才触发；改为 0.05 表示 5% 就触发，更频繁地清理。）</p><h4 id="杀死长事务"><a href="#杀死长事务" class="headerlink" title="杀死长事务"></a>杀死长事务</h4><p>如前所述，长事务会阻止 VACUUM 清理死元组。</p><p>查找并终止长时间运行的事务：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> pg_terminate_backend(pid)</span><br><span class="line"><span class="keyword">FROM</span> pg_stat_activity</span><br><span class="line"><span class="keyword">WHERE</span> state <span class="operator">!=</span> <span class="string">&#x27;idle&#x27;</span></span><br><span class="line">  <span class="keyword">AND</span> now() <span class="operator">-</span> xact_start <span class="operator">&gt;</span> <span class="type">interval</span> <span class="string">&#x27;10 minutes&#x27;</span>;</span><br></pre></td></tr></table></figure><h4 id="手动-VACUUM"><a href="#手动-VACUUM" class="headerlink" title="手动 VACUUM"></a>手动 VACUUM</h4><p>如果 Autovacuum 跟不上节奏，可以手动执行：</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">VACUUM VERBOSE ais41.recentships;</span><br></pre></td></tr></table></figure><h4 id="重建表（极端情况）"><a href="#重建表（极端情况）" class="headerlink" title="重建表（极端情况）"></a>重建表（极端情况）</h4><p>如果表已经极度膨胀（例如 90% 都是死元组），普通 VACUUM 效率太低。</p><ul><li>使用 <code>VACUUM FULL</code>（锁表，慎用）。</li><li>或使用 <code>pg_repack</code> 插件（在线重组，推荐生产环境使用）。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/07/02/fdc989e2/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>基于 Node.js + 大模型的 AI 客服系统</title>
      <link>https://blog.eucalyptus.cc/2026/06/28/1133165e/</link>
      <guid>https://blog.eucalyptus.cc/2026/06/28/1133165e/</guid>
      <pubDate>Sun, 28 Jun 2026 11:26:54 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;引言&quot;&gt;&lt;a href=&quot;#引言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="引言"><a href="#引言" class="headerlink" title="引言"></a>引言</h2><ul><li>痛点引入：博客文章越来越多，读者找不到想看的内容；评论区冷清，互动少；自己没时间回复每一条留言。</li><li>解决方案：给博客装一个 AI 智能助手，24 小时在线，能聊天、能搜文章、能回答问题。</li></ul><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-28/1.avif"></p><h2 id="项目介绍"><a href="#项目介绍" class="headerlink" title="项目介绍"></a>项目介绍</h2><p>核心功能：</p><ul><li>智能对话（基于大语言模型）</li><li>博客文章搜索与推荐</li><li>FAQ 知识库自动匹配</li><li>支持多模型切换（聊天&#x2F;图像生成）</li><li>限流保护，防止滥用</li></ul><p>技术栈：Node.js + Express + Axios + 大模型 API</p><h2 id="关键技术实现"><a href="#关键技术实现" class="headerlink" title="关键技术实现"></a>关键技术实现</h2><h3 id="文章索引与搜索"><a href="#文章索引与搜索" class="headerlink" title="文章索引与搜索"></a>文章索引与搜索</h3><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 从 Hexo 的 _posts 目录读取文章</span></span><br><span class="line"><span class="comment">// 解析 front-matter（标题、日期、标签、分类）</span></span><br><span class="line"><span class="comment">// 构建可搜索的文章对象数组</span></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">POSTS_DIR</span> = <span class="string">&#x27;/www/wwwroot/myblog/source/_posts&#x27;</span>;</span><br></pre></td></tr></table></figure><p>亮点：直接读取源文件，无需数据库，部署简单。</p><h3 id="FAQ-知识库设计"><a href="#FAQ-知识库设计" class="headerlink" title="FAQ 知识库设计"></a>FAQ 知识库设计</h3><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// JSON 格式存储常见问题</span></span><br><span class="line"><span class="comment">// 关键词匹配 + 评分机制</span></span><br><span class="line"><span class="comment">// 匹配成功直接返回，无需调用大模型（省钱+快速）</span></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">FAQ_FILE</span> = path.<span class="title function_">join</span>(__dirname, <span class="string">&#x27;faq.json&#x27;</span>);</span><br></pre></td></tr></table></figure><p>亮点：80% 的常见问题走 FAQ，只有复杂问题才调用大模型。</p><h3 id="多模型支持"><a href="#多模型支持" class="headerlink" title="多模型支持"></a>多模型支持</h3><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 支持聊天模型 + 图像生成模型</span></span><br><span class="line"><span class="comment">// 用户可切换模型</span></span><br><span class="line"><span class="comment">// 统一接口封装</span></span><br><span class="line">#ai-chatbot-input-area</span><br><span class="line">  #ai-chatbot-model-menu</span><br><span class="line">    div.<span class="property">ai</span>-chatbot-model-<span class="title function_">item</span>(data-model=<span class="string">&quot;sensenova-6.7-flash-lite&quot;</span> data-type=<span class="string">&quot;chat&quot;</span> onclick=<span class="string">&quot;selectModel(&#x27;sensenova-6.7-flash-lite&#x27;, &#x27;Sensenova 6.7 Lite&#x27;, &#x27;chat&#x27;)&quot;</span>)</span><br><span class="line">      span <span class="title class_">Sensenova</span> <span class="number">6.7</span> <span class="title class_">Lite</span></span><br><span class="line">      span.<span class="property">ai</span>-chatbot-model-desc 文本对话</span><br><span class="line">    div.<span class="property">ai</span>-chatbot-model-<span class="title function_">item</span>(data-model=<span class="string">&quot;sensenova-u1-fast&quot;</span> data-type=<span class="string">&quot;image&quot;</span> onclick=<span class="string">&quot;selectModel(&#x27;sensenova-u1-fast&#x27;, &#x27;Sensenova U1&#x27;, &#x27;image&#x27;)&quot;</span>)</span><br><span class="line">      span <span class="title class_">Sensenova</span> <span class="variable constant_">U1</span></span><br><span class="line">      span.<span class="property">ai</span>-chatbot-model-desc 图像生成</span><br><span class="line">    div.<span class="property">ai</span>-chatbot-model-<span class="title function_">item</span>(data-model=<span class="string">&quot;deepseek-v4-flash&quot;</span> data-type=<span class="string">&quot;chat&quot;</span> onclick=<span class="string">&quot;selectModel(&#x27;deepseek-v4-flash&#x27;, &#x27;DeepSeek V4&#x27;, &#x27;chat&#x27;)&quot;</span>)</span><br><span class="line">      span <span class="title class_">DeepSeek</span> <span class="variable constant_">V4</span></span><br><span class="line">      span.<span class="property">ai</span>-chatbot-model-desc 深度对话</span><br></pre></td></tr></table></figure><h3 id="限流与安全防护"><a href="#限流与安全防护" class="headerlink" title="限流与安全防护"></a>限流与安全防护</h3><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// IP 级别：60 秒内最多 20 次请求</span></span><br><span class="line"><span class="comment">// 防止 API Key 被刷爆</span></span><br><span class="line"><span class="comment">// 错误处理与降级</span></span><br><span class="line"><span class="keyword">function</span> <span class="title function_">getClientIP</span>(<span class="params">req</span>) &#123;</span><br><span class="line">  <span class="keyword">return</span> req.<span class="property">headers</span>[<span class="string">&#x27;x-forwarded-for&#x27;</span>]?.<span class="title function_">split</span>(<span class="string">&#x27;,&#x27;</span>)[<span class="number">0</span>]?.<span class="title function_">trim</span>() || </span><br><span class="line">         req.<span class="property">connection</span>?.<span class="property">remoteAddress</span> || </span><br><span class="line">         req.<span class="property">socket</span>?.<span class="property">remoteAddress</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">RATE_LIMIT</span> = &#123;&#125;; </span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">RATE_LIMIT_WINDOW</span> = <span class="number">60000</span>;</span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">RATE_LIMIT_MAX</span> = <span class="number">20</span>;      </span><br></pre></td></tr></table></figure><hr><h2 id="前端集成"><a href="#前端集成" class="headerlink" title="前端集成"></a>前端集成</h2><ul><li>聊天窗口的 UI 设计</li><li>位置控制</li><li>与 Hexo 主题的融合</li><li>调用后端 API 的 JavaScript 代码</li></ul><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 发送消息到后端</span></span><br><span class="line"><span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">sendMessage</span>(<span class="params">message</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="string">&#x27;https://your-api.com/api/chat&#x27;</span>, &#123;</span><br><span class="line">    <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>,</span><br><span class="line">    <span class="attr">headers</span>: &#123; <span class="string">&#x27;Content-Type&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span> &#125;,</span><br><span class="line">    <span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(&#123; message, <span class="attr">history</span>: chatHistory &#125;)</span><br><span class="line">  &#125;);</span><br><span class="line">  <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">  <span class="keyword">return</span> data.<span class="property">reply</span>;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><hr><h2 id="部署与运维"><a href="#部署与运维" class="headerlink" title="部署与运维"></a>部署与运维</h2><h3 id="部署方式"><a href="#部署方式" class="headerlink" title="部署方式"></a>部署方式</h3><table><thead><tr><th>方式</th><th>适用场景</th><th>命令</th></tr></thead><tbody><tr><td>本地开发</td><td>调试测试</td><td>node server.js</td></tr><tr><td>服务器部署</td><td>生产环境</td><td>pm2 start server.js</td></tr></tbody></table><h3 id="环境变量配置"><a href="#环境变量配置" class="headerlink" title="环境变量配置"></a>环境变量配置</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">API_KEY=your-api-key</span><br><span class="line">BOT_NAME=AI助手</span><br><span class="line">BOT_AVATAR=https://your-avatar-url</span><br><span class="line">SERVICE_PORT=5004</span><br></pre></td></tr></table></figure><h3 id="自动重启与监控"><a href="#自动重启与监控" class="headerlink" title="自动重启与监控"></a>自动重启与监控</h3><ul><li>使用 <code>pm2</code> 进程管理</li><li>配合 Nginx 反向代理</li><li>日志轮转</li></ul><hr><h2 id="效果展示"><a href="#效果展示" class="headerlink" title="效果展示"></a>效果展示</h2><h3 id="对话示例"><a href="#对话示例" class="headerlink" title="对话示例"></a>对话示例</h3><p>用户：推荐一些MySQL相关的文章<br>用户：你是谁  </p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-28/2.avif"></p><p>用户：樱花纷飞的放学路上，两个身影隔着三米的距离一前一后走着。女生抱着书包，马尾辫随着步伐轻轻晃动，耳朵尖泛着可疑的红。男生双手插兜，假装在看远处的天空，却每隔几秒就用余光偷瞄前面的背影。一阵风吹过，樱花瓣纷纷扬扬落在两人之间，像一条粉色的河。画面定格在女生突然停下脚步、男生差点撞上去的刹那，两人错愕的对视中，一片花瓣恰好停在女生的睫毛上。背景虚化，前景花瓣清晰，浪漫氛围拉满。</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-28/3.avif"></p><h3 id="性能数据"><a href="#性能数据" class="headerlink" title="性能数据"></a>性能数据</h3><ul><li>平均响应时间：~500ms（FAQ）&#x2F; ~2s（大模型）</li><li>支持并发：取决于 API 限额</li><li>文章索引：自动加载，无需手动更新</li></ul><h2 id="遇到的问题与解决方案"><a href="#遇到的问题与解决方案" class="headerlink" title="遇到的问题与解决方案"></a>遇到的问题与解决方案</h2><table><thead><tr><th>问题</th><th>解决方案</th></tr></thead><tbody><tr><td>大模型 API 费用高</td><td>FAQ 优先匹配，减少 API 调用</td></tr><tr><td>文章更新后索引不同步</td><td>提供 &#x2F;api&#x2F;reload 接口手动刷新</td></tr><tr><td>前端样式与主题冲突</td><td>使用 CSS 变量，适配 Anzhiyu 主题</td></tr><tr><td>响应慢</td><td>增加 timeout 处理，超时返回友好提示</td></tr></tbody></table><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><ul><li>项目价值：让博客从”静态展示”变成”动态交互”</li><li>学习收获：Node.js 服务开发、大模型 API 调用、全文检索思路</li><li>体验地址：<a href="https://blog.eucalyptus.cc/">blog.eucalyptus.cc</a></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/ChatBot/">ChatBot</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/06/28/1133165e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Go + Redis：本地部署高性能图片主色调提取服务</title>
      <link>https://blog.eucalyptus.cc/2026/06/10/5046db3d/</link>
      <guid>https://blog.eucalyptus.cc/2026/06/10/5046db3d/</guid>
      <pubDate>Wed, 10 Jun 2026 11:32:58 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;部署 &lt;code&gt;img2color-go&lt;/code&gt; 所需的环境非常轻量，主要包含的核心组件&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;go语言环境编译用（Go 1.21+ (建议最新稳定版)。）&lt;/li&gt;
&lt;li&gt;docker拉起redis容器缓存用（Docker 20.10+,</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>部署 <code>img2color-go</code> 所需的环境非常轻量，主要包含的核心组件</p><ul><li>go语言环境编译用（Go 1.21+ (建议最新稳定版)。）</li><li>docker拉起redis容器缓存用（Docker 20.10+, Docker Compose V2。）</li></ul><h2 id="拉起Redis容器做缓存"><a href="#拉起Redis容器做缓存" class="headerlink" title="拉起Redis容器做缓存"></a>拉起Redis容器做缓存</h2><p>在 <code>/val/lib/docker/redis-img2color</code>目录下创建 <code>docker-compose.yml</code>：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">services:</span><br><span class="line">  redis-img2color:</span><br><span class="line">    image: redis:7-alpine</span><br><span class="line">    container_name: redis-img2color</span><br><span class="line">    restart: always</span><br><span class="line">    ports:</span><br><span class="line">      - &quot;127.0.0.1:6380:6379&quot;</span><br><span class="line">    volumes:</span><br><span class="line">      - /val/lib/docker/redis-img2color:/data</span><br><span class="line">    command: redis-server --appendonly yes</span><br></pre></td></tr></table></figure><p>执行启动：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker compose up -d</span><br></pre></td></tr></table></figure><h2 id="克隆代码"><a href="#克隆代码" class="headerlink" title="克隆代码"></a>克隆代码</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">git clone https://github.com/anzhiyu-c/img2color-go.git</span><br><span class="line">cd img2color-go</span><br></pre></td></tr></table></figure><h2 id="修改包名：api-img2color-go"><a href="#修改包名：api-img2color-go" class="headerlink" title="修改包名：api&#x2F;img2color.go"></a>修改包名：api&#x2F;img2color.go</h2><h3 id="为什么要改？"><a href="#为什么要改？" class="headerlink" title="为什么要改？"></a>为什么要改？</h3><ul><li>原代码 (<code>package handler</code>)：这是为 Vercel&#x2F;Serverless 环境设计的“库”模式，它没有 <code>main</code> 函数入口，直接 <code>go build</code> 会报错或者生成无法直接运行的库</li><li>修改后 (<code>package main</code>)：这告诉 Go 编译器这是一个独立的可执行程序。配合我们添加的 <code>main</code> 函数（或原有的入口逻辑），才能编译出一个可以在服务器上直接运行的二进制文件 (<code>img2color-server</code>)。</li></ul><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"># 将 api/img2color.go 第一行的 package handler 替换为 package main</span><br><span class="line">sed -i &#x27;1s/package handler/package main/&#x27; api/img2color.go</span><br><span class="line"></span><br><span class="line"># 验证一下是否修改成功</span><br><span class="line">head -n 1 api/img2color.go</span><br></pre></td></tr></table></figure><h2 id="配置环境变量"><a href="#配置环境变量" class="headerlink" title="配置环境变量"></a>配置环境变量</h2><p>创建&#x2F;修改 <code>.env</code> 文件：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">PORT=9000</span><br><span class="line">REDIS_ADDRESS=127.0.0.1:6380</span><br><span class="line">REDIS_PASSWORD=</span><br><span class="line">USE_REDIS_CACHE=true</span><br><span class="line">REDIS_DB=0</span><br><span class="line">USE_MONGODB=false</span><br><span class="line">MONGO_URI=</span><br><span class="line">MONGO_DB=</span><br><span class="line">ALLOWED_REFERERS=</span><br></pre></td></tr></table></figure><h2 id="编译-Go-程序"><a href="#编译-Go-程序" class="headerlink" title="编译 Go 程序"></a>编译 Go 程序</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">cd /opt/img2color-go</span><br><span class="line">go mod tidy</span><br><span class="line">go build -o img2color-server ./api/</span><br><span class="line">chmod +x img2color-server</span><br></pre></td></tr></table></figure><h2 id="配置-Systemd-服务"><a href="#配置-Systemd-服务" class="headerlink" title="配置 Systemd 服务"></a>配置 Systemd 服务</h2><p>创建 <code>/etc/systemd/system/img2color.service</code>：</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line">[Unit]</span><br><span class="line">Description=img2color-go Service</span><br><span class="line">After=network.target docker.service</span><br><span class="line"></span><br><span class="line">[Service]</span><br><span class="line">Type=simple</span><br><span class="line">User=root</span><br><span class="line">WorkingDirectory=/opt/img2color-go</span><br><span class="line">ExecStart=/opt/img2color-go/img2color-server</span><br><span class="line">Restart=on-failure</span><br><span class="line"></span><br><span class="line">[Install]</span><br><span class="line">WantedBy=multi-user.target</span><br></pre></td></tr></table></figure><h2 id="启动并验证"><a href="#启动并验证" class="headerlink" title="启动并验证"></a>启动并验证</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"># 重载配置并启动</span><br><span class="line">sudo systemctl daemon-reload</span><br><span class="line">sudo systemctl enable --now img2color</span><br><span class="line"></span><br><span class="line"># 查看日志确认连接成功</span><br><span class="line">sudo journalctl -u img2color -f</span><br></pre></td></tr></table></figure><h2 id="最终测试"><a href="#最终测试" class="headerlink" title="最终测试"></a>最终测试</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">curl &quot;http://127.0.0.1:9000/api?img=https://avatars.githubusercontent.com/u/9919?v=4&quot;</span><br></pre></td></tr></table></figure><h2 id="反向代理"><a href="#反向代理" class="headerlink" title="反向代理"></a>反向代理</h2><p>后续可以配置个反向代理将ip+port换成域名，这里不做过多赘述</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Redis/">Redis</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/06/10/5046db3d/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>解决博客零评论困境：AI 评论机器人部署全记录</title>
      <link>https://blog.eucalyptus.cc/2026/06/08/16496380/</link>
      <guid>https://blog.eucalyptus.cc/2026/06/08/16496380/</guid>
      <pubDate>Mon, 08 Jun 2026 11:19:18 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>写博客的人大多有过这种体验：精心打磨一篇文章发布后，评论区却长期空白。对读者而言，”零评论”往往意味着内容无人问津，反而降低了互动意愿；对博主来说，手动维护评论既耗时又难以持续，尤其是当站点积累了数十篇甚至上百篇文章后，逐篇补充评论几乎成了不可能完成的任务。</p><p>我目前维护的个人博客基于 Hexo 框架，使用 anzhiyu 主题，评论系统选用 Twikoo 并通过 Docker 独立部署。随着文章数量增加，我逐渐意识到需要一个自动化的方案来解决评论冷启动问题——不是批量注册马甲账号刷量，而是让 AI 以真实读者的视角参与讨论，生成有实质内容、角度各异的评论，从而营造自然的社区氛围。</p><p>这个方案的核心思路是：利用大模型能力生成拟人化评论内容，同时通过模拟真实用户的浏览器 UA、IP 地址、Gravatar 头像等细节，让 AI 评论在数据层面与真实用户无异。系统不修改 Hexo 主题或 Twikoo 源码，而是以独立 Python 脚本的形式运行，通过读取 Twikoo 本地数据库获取现有评论，再经 HTTPS 接口提交新评论或回复。</p><p>本文将完整记录该系统的部署过程，从环境准备、模块配置到定时任务运行，力求每一步都可复现。Twikoo 本身的部署已有大量文档，此处不再赘述；代码实现仅展示关键结构与思路，具体细节可根据实际需求调整补充</p><h2 id="代码架构"><a href="#代码架构" class="headerlink" title="代码架构"></a>代码架构</h2><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">ai_bot/                          # Python 包</span><br><span class="line">├── __init__.py                  # 空文件，标记包</span><br><span class="line">├── config.py                    # 配置中心（API密钥、URL、比例）</span><br><span class="line">├── ai_service.py                # AI生成服务（昵称、评论、回复）</span><br><span class="line">├── twikoo_client.py             # Twikoo交互层（读db、写接口）</span><br><span class="line">├── auto_comment.py              # 新评论逻辑</span><br><span class="line">├── reply_bot.py                 # 回复评论逻辑</span><br><span class="line">└── main.py                      # 入口调度（CLI、批量、比例控制）</span><br></pre></td></tr></table></figure><h3 id="关键设计"><a href="#关键设计" class="headerlink" title="关键设计"></a>关键设计</h3><p><strong>分层隔离</strong></p><ul><li><code>ai_service</code> 只负责内容生成，不感知 Twikoo</li><li><code>twikoo_client</code> 只负责数据读写，不感知 AI</li><li><code>main</code> 负责编排，业务逻辑下沉到 <code>auto_comment</code> &#x2F; <code>reply_bot</code></li></ul><p><strong>双通道读写</strong></p><ul><li>读：直接解析本地 <code>db.json.0</code>，绕过 API 限制</li><li>写：HTTS POST 到 Twikoo 容器，复用官方接口</li></ul><p><strong>状态外置</strong></p><ul><li>角度轮换记录 <code>USED_ANGLES</code> 放内存（非持久，重启清空）</li><li>配置全放 <code>config.py</code>，支持环境变量注入</li></ul><h3 id="相关代码"><a href="#相关代码" class="headerlink" title="相关代码"></a>相关代码</h3><p>下述代码统一放在博客根目录下的一个文件中，例如新建 ai_bot</p><h4 id="config-py"><a href="#config-py" class="headerlink" title="config.py"></a>config.py</h4><p><code>config.py</code> 作为配置中心模块，集中管理 AI 接口密钥、Twikoo 服务地址、评论策略比例等全局参数，全部支持通过环境变量注入，实现配置与代码分离，便于不同环境快速切换。</p><p>SENSENOVA_API_URL这个需要使用自己模型的URL调用地址，SENSENOVA_MODEL切换模型，TWIKOO_URL可以使用域名或IP+PORT</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#!/usr/bin/env python3</span></span><br><span class="line"><span class="comment"># -*- coding: utf-8 -*-</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> os</span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== 日日新 SenseNova 配置 ==========</span></span><br><span class="line">SENSENOVA_API_KEY = os.getenv(<span class="string">&quot;OPENAI_API_KEY&quot;</span>, <span class="string">&quot;sk-your-sensenova-key&quot;</span>)</span><br><span class="line">SENSENOVA_API_URL = <span class="string">&quot;https://token.sensenova.cn/v1/chat/completions&quot;</span></span><br><span class="line">SENSENOVA_MODEL = <span class="string">&quot;deepseek-v4-flash&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># Twikoo 配置</span></span><br><span class="line">TWIKOO_URL = <span class="string">&quot;http://localhost:8080&quot;</span>  </span><br><span class="line">SITE_URL = <span class="string">&quot;https://blog.eucalyptus.cc&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== AI 评论策略配置 ==========</span></span><br><span class="line"><span class="comment"># 新评论 vs 回复评论的比例（0-100）</span></span><br><span class="line"><span class="comment"># 例如：NEW_COMMENT_RATIO = 70 表示 70% 概率发新评论，30% 概率回复</span></span><br><span class="line">NEW_COMMENT_RATIO = <span class="number">70</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 日志</span></span><br><span class="line">LOG_DIR = <span class="string">&quot;/var/log/ai-bot&quot;</span></span><br><span class="line">os.makedirs(LOG_DIR, exist_ok=<span class="literal">True</span>)</span><br></pre></td></tr></table></figure><p>OPENAI_API_KEY环境变量配置并持久化</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 写入 ~/.bashrc</span></span><br><span class="line">echo <span class="string">&#x27;export OPENAI_API_KEY=&quot;sk-your-actual-sensenova-key&quot;&#x27;</span> &gt;&gt; ~/.bashrc</span><br><span class="line"></span><br><span class="line"><span class="comment"># 立即生效</span></span><br><span class="line">source ~/.bashrc</span><br></pre></td></tr></table></figure><h4 id="ai-service-py"><a href="#ai-service-py" class="headerlink" title="ai_service.py"></a>ai_service.py</h4><p><code>ai_service.py</code> 作为 AI 生成服务模块，封装 SenseNova 大模型 API 调用，提供昵称生成、评论生成、回复生成三个核心接口；通过预设多角度评论池与角色扮演策略，结合温度参数和长度随机控制，确保输出内容拟人化且避免重复，同时维护已用角度记录实现单篇文章内的评论多样性。</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#!/usr/bin/env python3</span></span><br><span class="line"><span class="comment"># -*- coding: utf-8 -*-</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> requests</span><br><span class="line"><span class="keyword">import</span> random</span><br><span class="line"><span class="keyword">from</span> typing <span class="keyword">import</span> <span class="type">Optional</span></span><br><span class="line"><span class="keyword">from</span> .config <span class="keyword">import</span> SENSENOVA_API_KEY, SENSENOVA_API_URL, SENSENOVA_MODEL</span><br><span class="line"></span><br><span class="line"><span class="comment"># 评论角度池</span></span><br><span class="line">COMMENT_ANGLES = [</span><br><span class="line">    <span class="string">&quot;技术实现角度，提出疑问或建议&quot;</span>,</span><br><span class="line">    <span class="string">&quot;个人经验角度，分享相关经历&quot;</span>,</span><br><span class="line">    <span class="string">&quot;应用场景角度，讨论实际使用&quot;</span>,</span><br><span class="line">    <span class="string">&quot;学习收获角度，表达感谢和启发&quot;</span>,</span><br><span class="line">    <span class="string">&quot;问题反馈角度，指出可能的坑&quot;</span>,</span><br><span class="line">    <span class="string">&quot;扩展思考角度，提出延伸问题&quot;</span>,</span><br><span class="line">    <span class="string">&quot;情感共鸣角度，表达认同和感受&quot;</span>,</span><br><span class="line">]</span><br><span class="line"></span><br><span class="line"><span class="comment"># 角色设定池</span></span><br><span class="line">COMMENT_ROLES = [</span><br><span class="line">    <span class="string">&quot;技术小白，刚入门，有很多疑问&quot;</span>,</span><br><span class="line">    <span class="string">&quot;有经验的开发者，喜欢分享经验&quot;</span>,</span><br><span class="line">    <span class="string">&quot;学生党，正在学习相关技术&quot;</span>,</span><br><span class="line">    <span class="string">&quot;职场老鸟，关注实际应用&quot;</span>,</span><br><span class="line">    <span class="string">&quot;爱好者，喜欢折腾新技术&quot;</span>,</span><br><span class="line">    <span class="string">&quot;博主同行，交流心得&quot;</span>,</span><br><span class="line">]</span><br><span class="line"></span><br><span class="line"><span class="comment"># 记录已用角度（内存中，重启会清空）</span></span><br><span class="line">USED_ANGLES = &#123;&#125;</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">generate_nick</span>() -&gt; <span class="built_in">str</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;AI 生成随机昵称&quot;&quot;&quot;</span></span><br><span class="line">    prompt = <span class="string">&quot;&quot;&quot;你是一个中文网名生成器，请生成一个2-4个字的博客读者昵称。</span></span><br><span class="line"><span class="string">要求：</span></span><br><span class="line"><span class="string">- 像真实的中文网名，有生活气息</span></span><br><span class="line"><span class="string">- 可以是：技术向、文艺向、幽默向、日常向</span></span><br><span class="line"><span class="string">- 不要英文，不要符号</span></span><br><span class="line"><span class="string">- 直接输出昵称，不要解释</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">示例：代码诗人、深夜咖啡、佛系码农、探索者、路过人间、技术小白&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">    headers = &#123;</span><br><span class="line">        <span class="string">&quot;Authorization&quot;</span>: <span class="string">f&quot;Bearer <span class="subst">&#123;SENSENOVA_API_KEY&#125;</span>&quot;</span>,</span><br><span class="line">        <span class="string">&quot;Content-Type&quot;</span>: <span class="string">&quot;application/json&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    data = &#123;</span><br><span class="line">        <span class="string">&quot;model&quot;</span>: SENSENOVA_MODEL,</span><br><span class="line">        <span class="string">&quot;messages&quot;</span>: [&#123;<span class="string">&quot;role&quot;</span>: <span class="string">&quot;user&quot;</span>, <span class="string">&quot;content&quot;</span>: prompt&#125;],</span><br><span class="line">        <span class="string">&quot;temperature&quot;</span>: <span class="number">1.2</span>,</span><br><span class="line">        <span class="string">&quot;max_tokens&quot;</span>: <span class="number">20</span>,</span><br><span class="line">        <span class="string">&quot;reasoning_effort&quot;</span>: <span class="string">&quot;none&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">try</span>:</span><br><span class="line">        resp = requests.post(SENSENOVA_API_URL, headers=headers, json=data, timeout=<span class="number">10</span>)</span><br><span class="line">        result = resp.json()</span><br><span class="line">        nick = result[<span class="string">&#x27;choices&#x27;</span>][<span class="number">0</span>][<span class="string">&#x27;message&#x27;</span>][<span class="string">&#x27;content&#x27;</span>].strip()</span><br><span class="line">        nick = nick.replace(<span class="string">&quot;\&quot;&quot;</span>, <span class="string">&quot;&quot;</span>).replace(<span class="string">&quot;&#x27;&quot;</span>, <span class="string">&quot;&quot;</span>).replace(<span class="string">&quot;：&quot;</span>, <span class="string">&quot;&quot;</span>).replace(<span class="string">&quot;:&quot;</span>, <span class="string">&quot;&quot;</span>).strip()</span><br><span class="line">        <span class="keyword">return</span> nick[:<span class="number">10</span>]</span><br><span class="line">    <span class="keyword">except</span> Exception <span class="keyword">as</span> e:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;昵称生成失败: <span class="subst">&#123;e&#125;</span>&quot;</span>)</span><br><span class="line">        fallback = [<span class="string">&quot;技术小白&quot;</span>, <span class="string">&quot;路过读者&quot;</span>, <span class="string">&quot;前端爱好者&quot;</span>, <span class="string">&quot;博主粉丝&quot;</span>, <span class="string">&quot;学习中的猫&quot;</span>, <span class="string">&quot;代码搬运工&quot;</span>, <span class="string">&quot;夜猫子程序员&quot;</span>, <span class="string">&quot;探索者&quot;</span>]</span><br><span class="line">        <span class="keyword">return</span> random.choice(fallback)</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">generate_comment</span>(<span class="params">title: <span class="built_in">str</span>, content: <span class="built_in">str</span>, url: <span class="built_in">str</span> = <span class="string">&quot;&quot;</span></span>) -&gt; <span class="type">Optional</span>[<span class="built_in">str</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;生成文章评论，支持多角度和角色&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">    <span class="comment"># 选择未用过的角度</span></span><br><span class="line">    used = USED_ANGLES.get(url, [])</span><br><span class="line">    available = [a <span class="keyword">for</span> a <span class="keyword">in</span> COMMENT_ANGLES <span class="keyword">if</span> a <span class="keyword">not</span> <span class="keyword">in</span> used]</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> available:</span><br><span class="line">        <span class="comment"># 所有角度用完，重置</span></span><br><span class="line">        available = COMMENT_ANGLES</span><br><span class="line">        USED_ANGLES[url] = []</span><br><span class="line"></span><br><span class="line">    angle = random.choice(available)</span><br><span class="line">    USED_ANGLES[url] = USED_ANGLES.get(url, []) + [angle]</span><br><span class="line"></span><br><span class="line">    <span class="comment"># 随机角色</span></span><br><span class="line">    role = random.choice(COMMENT_ROLES)</span><br><span class="line"></span><br><span class="line">    <span class="comment"># 随机长度要求</span></span><br><span class="line">    length_req = random.choice([</span><br><span class="line">        <span class="string">&quot;简短有力，30-50字&quot;</span>,</span><br><span class="line">        <span class="string">&quot;中等长度，50-80字&quot;</span>,</span><br><span class="line">        <span class="string">&quot;稍微详细，80-100字&quot;</span>,</span><br><span class="line">    ])</span><br><span class="line"></span><br><span class="line">    prompt = <span class="string">f&quot;&quot;&quot;你是一位<span class="subst">&#123;role&#125;</span>，请根据以下文章生成一条评论。</span></span><br><span class="line"><span class="string">要求：</span></span><br><span class="line"><span class="string">- 从&quot;<span class="subst">&#123;angle&#125;</span>&quot;出发</span></span><br><span class="line"><span class="string">- <span class="subst">&#123;length_req&#125;</span></span></span><br><span class="line"><span class="string">- 像真实人类一样，有个人观点</span></span><br><span class="line"><span class="string">- 不要太过正式，口语化一点</span></span><br><span class="line"><span class="string">- 避免和之前评论重复的内容</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">文章标题：<span class="subst">&#123;title&#125;</span></span></span><br><span class="line"><span class="string">文章内容摘要：<span class="subst">&#123;content[:<span class="number">500</span>]&#125;</span>&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">    headers = &#123;</span><br><span class="line">        <span class="string">&quot;Authorization&quot;</span>: <span class="string">f&quot;Bearer <span class="subst">&#123;SENSENOVA_API_KEY&#125;</span>&quot;</span>,</span><br><span class="line">        <span class="string">&quot;Content-Type&quot;</span>: <span class="string">&quot;application/json&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    data = &#123;</span><br><span class="line">        <span class="string">&quot;model&quot;</span>: SENSENOVA_MODEL,</span><br><span class="line">        <span class="string">&quot;messages&quot;</span>: [&#123;<span class="string">&quot;role&quot;</span>: <span class="string">&quot;user&quot;</span>, <span class="string">&quot;content&quot;</span>: prompt&#125;],</span><br><span class="line">        <span class="string">&quot;temperature&quot;</span>: <span class="number">1.5</span>,  <span class="comment"># 提高随机性</span></span><br><span class="line">        <span class="string">&quot;max_tokens&quot;</span>: <span class="number">150</span>,</span><br><span class="line">        <span class="string">&quot;reasoning_effort&quot;</span>: <span class="string">&quot;none&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">try</span>:</span><br><span class="line">        resp = requests.post(SENSENOVA_API_URL, headers=headers, json=data, timeout=<span class="number">30</span>)</span><br><span class="line">        result = resp.json()</span><br><span class="line">        <span class="keyword">return</span> result[<span class="string">&#x27;choices&#x27;</span>][<span class="number">0</span>][<span class="string">&#x27;message&#x27;</span>][<span class="string">&#x27;content&#x27;</span>].strip()</span><br><span class="line">    <span class="keyword">except</span> Exception <span class="keyword">as</span> e:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;AI 生成失败: <span class="subst">&#123;e&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">None</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">generate_reply</span>(<span class="params">comment_text: <span class="built_in">str</span>, article_title: <span class="built_in">str</span></span>) -&gt; <span class="type">Optional</span>[<span class="built_in">str</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;生成回复评论，使用读者角度&quot;&quot;&quot;</span></span><br><span class="line">    </span><br><span class="line">    prompt = <span class="string">f&quot;&quot;&quot;你是一位博客读者，正在回复这篇文章下的评论。</span></span><br><span class="line"><span class="string">要求：</span></span><br><span class="line"><span class="string">- 以读者身份回复，不是博主/作者</span></span><br><span class="line"><span class="string">- 像真实读者一样，分享自己的看法、经验或疑问</span></span><br><span class="line"><span class="string">- 可以表示认同、补充观点、提出相关问题</span></span><br><span class="line"><span class="string">- 语气自然、口语化，像朋友聊天</span></span><br><span class="line"><span class="string">- 不要说&quot;作为作者&quot;、&quot;我会写&quot;、&quot;我的文章&quot;等博主口吻</span></span><br><span class="line"><span class="string">- 可以说&quot;我也遇到过&quot;、&quot;同感&quot;、&quot;学到了&quot;、&quot;想问下&quot;等读者常用语</span></span><br><span class="line"><span class="string">- 长度适中，50-100字左右</span></span><br><span class="line"><span class="string">- ⚠️ 重要：不要@任何人，直接回复即可，不要出现@用户名</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">文章标题：<span class="subst">&#123;article_title&#125;</span></span></span><br><span class="line"><span class="string">你要回复的评论：<span class="subst">&#123;comment_text[:<span class="number">300</span>]&#125;</span>&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">    headers = &#123;</span><br><span class="line">        <span class="string">&quot;Authorization&quot;</span>: <span class="string">f&quot;Bearer <span class="subst">&#123;SENSENOVA_API_KEY&#125;</span>&quot;</span>,</span><br><span class="line">        <span class="string">&quot;Content-Type&quot;</span>: <span class="string">&quot;application/json&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    data = &#123;</span><br><span class="line">        <span class="string">&quot;model&quot;</span>: SENSENOVA_MODEL,</span><br><span class="line">        <span class="string">&quot;messages&quot;</span>: [&#123;<span class="string">&quot;role&quot;</span>: <span class="string">&quot;user&quot;</span>, <span class="string">&quot;content&quot;</span>: prompt&#125;],</span><br><span class="line">        <span class="string">&quot;temperature&quot;</span>: <span class="number">1.2</span>,</span><br><span class="line">        <span class="string">&quot;max_tokens&quot;</span>: <span class="number">150</span>,</span><br><span class="line">        <span class="string">&quot;reasoning_effort&quot;</span>: <span class="string">&quot;none&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">try</span>:</span><br><span class="line">        resp = requests.post(SENSENOVA_API_URL, headers=headers, json=data, timeout=<span class="number">30</span>)</span><br><span class="line">        result = resp.json()</span><br><span class="line">        reply = result[<span class="string">&#x27;choices&#x27;</span>][<span class="number">0</span>][<span class="string">&#x27;message&#x27;</span>][<span class="string">&#x27;content&#x27;</span>].strip()</span><br><span class="line">        </span><br><span class="line">        <span class="comment"># 过滤掉 AI 可能生成的 @用户名</span></span><br><span class="line">        <span class="keyword">import</span> re</span><br><span class="line">        reply = re.sub(<span class="string">r&#x27;@\w+\s*&#x27;</span>, <span class="string">&#x27;&#x27;</span>, reply).strip()</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">return</span> reply</span><br><span class="line">    <span class="keyword">except</span> Exception <span class="keyword">as</span> e:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;AI 生成回复失败: <span class="subst">&#123;e&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">None</span></span><br><span class="line"></span><br><span class="line">        </span><br></pre></td></tr></table></figure><h4 id="twikoo-client-py"><a href="#twikoo-client-py" class="headerlink" title="twikoo_client.py"></a>twikoo_client.py</h4><p><code>twikoo_client.py</code> 作为 Twikoo 交互层模块，采用双通道设计实现评论数据的读写操作：读取通道直接解析本地 <code>db.json.0</code> 文件获取完整评论列表，写入通道通过 HTTP POST 向 Twikoo 容器提交新评论或回复；同时负责拟人化字段构造（UA、IP、邮箱等）及 URL 编码兼容处理，确保数据层面与真实用户无异。</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># twikoo_client.py</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> requests</span><br><span class="line"><span class="keyword">import</span> random</span><br><span class="line"><span class="keyword">import</span> json</span><br><span class="line"><span class="keyword">import</span> os</span><br><span class="line"><span class="keyword">import</span> urllib.parse</span><br><span class="line"><span class="keyword">from</span> typing <span class="keyword">import</span> <span class="type">Optional</span>, <span class="type">Dict</span>, <span class="type">List</span></span><br><span class="line"><span class="keyword">from</span> .config <span class="keyword">import</span> TWIKOO_URL, SITE_URL</span><br><span class="line"></span><br><span class="line"><span class="comment"># 真实用户 UA 池</span></span><br><span class="line">USER_AGENTS = [</span><br><span class="line">    <span class="string">&quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36&quot;</span>,</span><br><span class="line">    <span class="string">&quot;Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36&quot;</span>,</span><br><span class="line">    <span class="string">&quot;Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/121.0&quot;</span>,</span><br><span class="line">    <span class="string">&quot;Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.1 Safari/605.1.15&quot;</span>,</span><br><span class="line">    <span class="string">&quot;Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36&quot;</span>,</span><br><span class="line">]</span><br><span class="line"></span><br><span class="line"><span class="comment"># 真实 IP 池（国内常见）</span></span><br><span class="line">IP_POOL = [</span><br><span class="line">    <span class="string">&quot;223.104.212.1&quot;</span>, <span class="string">&quot;183.192.123.45&quot;</span>, <span class="string">&quot;117.136.62.89&quot;</span>,</span><br><span class="line">    <span class="string">&quot;120.197.198.2&quot;</span>, <span class="string">&quot;183.60.235.1&quot;</span>, <span class="string">&quot;113.96.201.23&quot;</span>,</span><br><span class="line">    <span class="string">&quot;116.22.29.1&quot;</span>, <span class="string">&quot;125.220.157.89&quot;</span>, <span class="string">&quot;42.236.10.1&quot;</span></span><br><span class="line">]</span><br><span class="line"></span><br><span class="line"><span class="comment"># Twikoo 本地数据库路径</span></span><br><span class="line">DB_PATH = <span class="string">&quot;/var/lib/docker/twikoo/data/db.json.0&quot;</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">_get_comments_from_db</span>(<span class="params">url: <span class="built_in">str</span></span>) -&gt; <span class="type">List</span>[<span class="type">Dict</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;从 Twikoo 本地 db.json 读取评论&quot;&quot;&quot;</span></span><br><span class="line">    comments = []</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> os.path.exists(DB_PATH):</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;数据库文件不存在: <span class="subst">&#123;DB_PATH&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> comments</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">try</span>:</span><br><span class="line">        <span class="keyword">with</span> <span class="built_in">open</span>(DB_PATH, <span class="string">&#x27;r&#x27;</span>, encoding=<span class="string">&#x27;utf-8&#x27;</span>) <span class="keyword">as</span> f:</span><br><span class="line">            <span class="keyword">for</span> line <span class="keyword">in</span> f:</span><br><span class="line">                line = line.strip()</span><br><span class="line">                <span class="keyword">if</span> <span class="keyword">not</span> line:</span><br><span class="line">                    <span class="keyword">continue</span></span><br><span class="line">                <span class="keyword">try</span>:</span><br><span class="line">                    doc = json.loads(line)</span><br><span class="line">                    doc_url = doc.get(<span class="string">&quot;url&quot;</span>, <span class="string">&quot;&quot;</span>)</span><br><span class="line">                    </span><br><span class="line">                    <span class="comment"># 匹配 url（同时支持编码和未编码）</span></span><br><span class="line">                    urls_match = (</span><br><span class="line">                        doc_url == url <span class="keyword">or</span> </span><br><span class="line">                        doc_url == urllib.parse.unquote(url) <span class="keyword">or</span></span><br><span class="line">                        urllib.parse.unquote(doc_url) == url</span><br><span class="line">                    )</span><br><span class="line">                    </span><br><span class="line">                    <span class="keyword">if</span> <span class="keyword">not</span> urls_match:</span><br><span class="line">                        <span class="keyword">continue</span></span><br><span class="line">                    </span><br><span class="line">                    <span class="comment"># 排除垃圾评论和已删除</span></span><br><span class="line">                    <span class="keyword">if</span> doc.get(<span class="string">&quot;isSpam&quot;</span>, <span class="literal">False</span>) <span class="keyword">or</span> doc.get(<span class="string">&quot;status&quot;</span>) == <span class="string">&quot;deleted&quot;</span>:</span><br><span class="line">                        <span class="keyword">continue</span></span><br><span class="line">                    </span><br><span class="line">                    <span class="comment"># 统一字段格式</span></span><br><span class="line">                    comment = &#123;</span><br><span class="line">                        <span class="string">&quot;_id&quot;</span>: doc.get(<span class="string">&quot;_id&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;id&quot;</span>: doc.get(<span class="string">&quot;id&quot;</span>) <span class="keyword">or</span> doc.get(<span class="string">&quot;_id&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;nick&quot;</span>: doc.get(<span class="string">&quot;nick&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;mail&quot;</span>: doc.get(<span class="string">&quot;mail&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;mailMd5&quot;</span>: doc.get(<span class="string">&quot;mailMd5&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;link&quot;</span>: doc.get(<span class="string">&quot;link&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;ua&quot;</span>: doc.get(<span class="string">&quot;ua&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;ip&quot;</span>: doc.get(<span class="string">&quot;ip&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;master&quot;</span>: doc.get(<span class="string">&quot;master&quot;</span>, <span class="literal">False</span>),</span><br><span class="line">                        <span class="string">&quot;url&quot;</span>: doc_url,</span><br><span class="line">                        <span class="string">&quot;href&quot;</span>: doc.get(<span class="string">&quot;href&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;comment&quot;</span>: doc.get(<span class="string">&quot;comment&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;rid&quot;</span>: doc.get(<span class="string">&quot;rid&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;pid&quot;</span>: doc.get(<span class="string">&quot;pid&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">                        <span class="string">&quot;isSpam&quot;</span>: doc.get(<span class="string">&quot;isSpam&quot;</span>, <span class="literal">False</span>),</span><br><span class="line">                        <span class="string">&quot;created&quot;</span>: doc.get(<span class="string">&quot;created&quot;</span>, <span class="number">0</span>),</span><br><span class="line">                        <span class="string">&quot;updated&quot;</span>: doc.get(<span class="string">&quot;updated&quot;</span>, <span class="number">0</span>),</span><br><span class="line">                    &#125;</span><br><span class="line">                    comments.append(comment)</span><br><span class="line">                <span class="keyword">except</span> json.JSONDecodeError:</span><br><span class="line">                    <span class="keyword">continue</span></span><br><span class="line">    <span class="keyword">except</span> Exception <span class="keyword">as</span> e:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;读取数据库失败: <span class="subst">&#123;e&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;从数据库读取到 <span class="subst">&#123;<span class="built_in">len</span>(comments)&#125;</span> 条评论&quot;</span>)</span><br><span class="line">    <span class="keyword">return</span> comments</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">get_comments</span>(<span class="params">url: <span class="built_in">str</span>, limit: <span class="built_in">int</span> = <span class="number">100</span></span>) -&gt; <span class="type">List</span>[<span class="type">Dict</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;获取评论列表 - 直接读本地数据库&quot;&quot;&quot;</span></span><br><span class="line">    <span class="keyword">return</span> _get_comments_from_db(url)</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">submit_comment</span>(<span class="params">url: <span class="built_in">str</span>, comment: <span class="built_in">str</span>, nick: <span class="built_in">str</span>, mail: <span class="built_in">str</span>, pid: <span class="built_in">str</span> = <span class="string">&quot;&quot;</span>, rid: <span class="built_in">str</span> = <span class="string">&quot;&quot;</span></span>) -&gt; <span class="built_in">bool</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;提交评论到 Twikoo，支持回复&quot;&quot;&quot;</span></span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 1. 移除 SITE_URL 前缀</span></span><br><span class="line">    <span class="keyword">if</span> url.startswith(SITE_URL):</span><br><span class="line">        url = url.replace(SITE_URL, <span class="string">&quot;&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 2. 确保格式正确</span></span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> url.startswith(<span class="string">&quot;/&quot;</span>):</span><br><span class="line">        url = <span class="string">&quot;/&quot;</span> + url</span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> url.endswith(<span class="string">&quot;/&quot;</span>):</span><br><span class="line">        url = url + <span class="string">&quot;/&quot;</span></span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 3. 先完全解码，再重新编码（防止双重编码）</span></span><br><span class="line">    url = urllib.parse.unquote(url)</span><br><span class="line">    parts = url.split(<span class="string">&#x27;/&#x27;</span>)</span><br><span class="line">    encoded_parts = [urllib.parse.quote(part, safe=<span class="string">&#x27;&#x27;</span>) <span class="keyword">for</span> part <span class="keyword">in</span> parts]</span><br><span class="line">    url = <span class="string">&#x27;/&#x27;</span>.join(encoded_parts)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 4. 构造 href</span></span><br><span class="line">    href = SITE_URL + url</span><br><span class="line">    </span><br><span class="line">    ua = random.choice(USER_AGENTS)</span><br><span class="line">    fake_ip = random.choice(IP_POOL)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 5. 构造 payload</span></span><br><span class="line">    <span class="comment"># 关键修复：顶级评论不要传 pid/rid 字段（而不是传空字符串）</span></span><br><span class="line">    payload = &#123;</span><br><span class="line">        <span class="string">&quot;event&quot;</span>: <span class="string">&quot;COMMENT_SUBMIT&quot;</span>,</span><br><span class="line">        <span class="string">&quot;url&quot;</span>: url,</span><br><span class="line">        <span class="string">&quot;href&quot;</span>: href,</span><br><span class="line">        <span class="string">&quot;comment&quot;</span>: comment,</span><br><span class="line">        <span class="string">&quot;nick&quot;</span>: nick,</span><br><span class="line">        <span class="string">&quot;mail&quot;</span>: mail,</span><br><span class="line">        <span class="string">&quot;link&quot;</span>: <span class="string">&quot;&quot;</span>,</span><br><span class="line">        <span class="string">&quot;ua&quot;</span>: ua,</span><br><span class="line">        <span class="string">&quot;ip&quot;</span>: fake_ip,</span><br><span class="line">        <span class="string">&quot;isSpam&quot;</span>: <span class="literal">False</span>,  <span class="comment"># 显式设置，必须和手动评论一致</span></span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 只有回复时才添加 pid 和 rid</span></span><br><span class="line">    <span class="keyword">if</span> pid:</span><br><span class="line">        payload[<span class="string">&quot;pid&quot;</span>] = pid</span><br><span class="line">    <span class="keyword">if</span> rid:</span><br><span class="line">        payload[<span class="string">&quot;rid&quot;</span>] = rid</span><br><span class="line">    </span><br><span class="line">    headers = &#123;</span><br><span class="line">        <span class="string">&quot;Content-Type&quot;</span>: <span class="string">&quot;application/json&quot;</span>,</span><br><span class="line">        <span class="string">&quot;User-Agent&quot;</span>: ua,</span><br><span class="line">        <span class="string">&quot;X-Forwarded-For&quot;</span>: fake_ip,</span><br><span class="line">        <span class="string">&quot;X-Real-IP&quot;</span>: fake_ip</span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">try</span>:</span><br><span class="line">        resp = requests.post(TWIKOO_URL, json=payload, headers=headers, timeout=<span class="number">10</span>)</span><br><span class="line">        result = resp.json()</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  Twikoo 返回: <span class="subst">&#123;result&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  提交 URL: <span class="subst">&#123;url&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  Payload: <span class="subst">&#123;json.dumps(payload, ensure_ascii=<span class="literal">False</span>)&#125;</span>&quot;</span>)  <span class="comment"># 调试用</span></span><br><span class="line">        <span class="keyword">return</span> <span class="string">&quot;id&quot;</span> <span class="keyword">in</span> result <span class="keyword">or</span> result.get(<span class="string">&quot;code&quot;</span>) == <span class="number">0</span></span><br><span class="line">    <span class="keyword">except</span> Exception <span class="keyword">as</span> e:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;提交失败: <span class="subst">&#123;e&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">check_ai_comment_exists</span>(<span class="params">url: <span class="built_in">str</span></span>) -&gt; <span class="built_in">bool</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;检查是否已有 AI 评论（通过 UA 识别）&quot;&quot;&quot;</span></span><br><span class="line">    comments = get_comments(url)</span><br><span class="line">    <span class="keyword">for</span> c <span class="keyword">in</span> comments:</span><br><span class="line">        ua = c.get(<span class="string">&quot;ua&quot;</span>, <span class="string">&quot;&quot;</span>)</span><br><span class="line">        <span class="keyword">if</span> ua <span class="keyword">in</span> USER_AGENTS:</span><br><span class="line">            <span class="keyword">return</span> <span class="literal">True</span></span><br><span class="line">    <span class="keyword">return</span> <span class="literal">False</span></span><br></pre></td></tr></table></figure><h4 id="auto-comment-py"><a href="#auto-comment-py" class="headerlink" title="auto_comment.py"></a>auto_comment.py</h4><p><code>auto_comment.py</code> 作为新评论逻辑模块，负责组装并提交单篇文章的首条 AI 评论：依次调用 AI 服务生成评论内容、随机昵称和邮箱，构造完整的 Twikoo 评论数据包，最终通过客户端提交；内置可选的去重检查机制，避免同一篇文章被重复评论。</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#!/usr/bin/env python3</span></span><br><span class="line"><span class="comment"># -*- coding: utf-8 -*-</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> random</span><br><span class="line"><span class="keyword">from</span> .ai_service <span class="keyword">import</span> generate_comment, generate_nick</span><br><span class="line"><span class="keyword">from</span> .twikoo_client <span class="keyword">import</span> submit_comment, check_ai_comment_exists</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">generate_mail</span>() -&gt; <span class="built_in">str</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;生成邮箱，Twikoo 自动显示 Gravatar 头像&quot;&quot;&quot;</span></span><br><span class="line">    seed = random.randint(<span class="number">1000</span>, <span class="number">9999</span>)</span><br><span class="line">    <span class="keyword">return</span> <span class="string">f&quot;user<span class="subst">&#123;seed&#125;</span>@example.com&quot;</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">process_article</span>(<span class="params">url: <span class="built_in">str</span>, title: <span class="built_in">str</span>, content: <span class="built_in">str</span></span>) -&gt; <span class="built_in">bool</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;处理单篇文章：发新评论&quot;&quot;&quot;</span></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;处理: <span class="subst">&#123;title&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 检查是否已有 AI 评论（可选，如果想多次评论可以注释掉）</span></span><br><span class="line">    <span class="comment"># if check_ai_comment_exists(url):</span></span><br><span class="line">    <span class="comment">#     print(&quot;  已有 AI 评论，跳过&quot;)</span></span><br><span class="line">    <span class="comment">#     return False</span></span><br><span class="line">    </span><br><span class="line">    comment_text = generate_comment(title, content, url)</span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> comment_text:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">&quot;  AI 生成失败&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  生成: <span class="subst">&#123;comment_text[:<span class="number">50</span>]&#125;</span>...&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    nick = generate_nick()</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  昵称: <span class="subst">&#123;nick&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    mail = generate_mail()</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  邮箱: <span class="subst">&#123;mail&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> submit_comment(url, comment_text, nick, mail):</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  ✅ 提交成功&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">True</span></span><br><span class="line">    <span class="keyword">else</span>:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  ❌ 提交失败&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br></pre></td></tr></table></figure><h4 id="reply-bot-py"><a href="#reply-bot-py" class="headerlink" title="reply_bot.py"></a>reply_bot.py</h4><p><code>reply_bot.py</code> 作为回复评论逻辑模块，负责筛选并回复文章下现有评论：读取 Twikoo 本地数据库获取未回复评论列表（排除 AI 自身评论），调用 AI 服务生成针对性回复内容，正确设置 <code>pid</code> 和 <code>rid</code> 字段确保回复层级关系准确，实现模拟真实读者间的互动对话。</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># reply_bot.py</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> random</span><br><span class="line"><span class="keyword">from</span> typing <span class="keyword">import</span> <span class="type">List</span>, <span class="type">Dict</span></span><br><span class="line"><span class="keyword">from</span> .ai_service <span class="keyword">import</span> generate_reply, generate_nick  <span class="comment"># 导入 generate_nick</span></span><br><span class="line"><span class="keyword">from</span> .twikoo_client <span class="keyword">import</span> get_comments, submit_comment</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">get_unreplied_comments</span>(<span class="params">url: <span class="built_in">str</span>, bot_nicks: <span class="type">List</span>[<span class="built_in">str</span>]</span>) -&gt; <span class="type">List</span>[<span class="type">Dict</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;获取未回复的评论（排除自己的评论）&quot;&quot;&quot;</span></span><br><span class="line">    comments = get_comments(url)</span><br><span class="line">    </span><br><span class="line">    unreplied = []</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 收集所有被回复的评论 ID（用 pid）</span></span><br><span class="line">    replied_ids = <span class="built_in">set</span>()</span><br><span class="line">    <span class="keyword">for</span> c <span class="keyword">in</span> comments:</span><br><span class="line">        pid = c.get(<span class="string">&quot;pid&quot;</span>)</span><br><span class="line">        <span class="keyword">if</span> pid:</span><br><span class="line">            replied_ids.add(pid)</span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;已被回复的评论ID: <span class="subst">&#123;replied_ids&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">for</span> comment <span class="keyword">in</span> comments:</span><br><span class="line">        <span class="comment"># 获取评论 ID（优先 _id）</span></span><br><span class="line">        comment_id = comment.get(<span class="string">&quot;_id&quot;</span>) <span class="keyword">or</span> comment.get(<span class="string">&quot;id&quot;</span>)</span><br><span class="line">        nick = comment.get(<span class="string">&quot;nick&quot;</span>, <span class="string">&quot;unknown&quot;</span>)</span><br><span class="line">        </span><br><span class="line">        <span class="comment"># 跳过自己的评论</span></span><br><span class="line">        <span class="keyword">if</span> nick <span class="keyword">in</span> bot_nicks:</span><br><span class="line">            <span class="keyword">continue</span></span><br><span class="line">        </span><br><span class="line">        <span class="comment"># 检查是否已被回复</span></span><br><span class="line">        <span class="keyword">if</span> comment_id <span class="keyword">and</span> comment_id <span class="keyword">in</span> replied_ids:</span><br><span class="line">            <span class="keyword">continue</span></span><br><span class="line">        </span><br><span class="line">        unreplied.append(comment)</span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;发现 <span class="subst">&#123;<span class="built_in">len</span>(unreplied)&#125;</span> 条未回复评论&quot;</span>)</span><br><span class="line">    <span class="keyword">return</span> unreplied</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">reply_to_comment</span>(<span class="params">parent_comment: <span class="type">Dict</span>, article_title: <span class="built_in">str</span></span>) -&gt; <span class="built_in">bool</span>:</span><br><span class="line">    parent_nick = parent_comment.get(<span class="string">&quot;nick&quot;</span>, <span class="string">&quot;网友&quot;</span>)</span><br><span class="line">    parent_text = parent_comment.get(<span class="string">&quot;comment&quot;</span>, <span class="string">&quot;&quot;</span>)[:<span class="number">30</span>]</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;回复 [<span class="subst">&#123;parent_nick&#125;</span>]: <span class="subst">&#123;parent_text&#125;</span>...&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 生成回复内容</span></span><br><span class="line">    reply_text = generate_reply(</span><br><span class="line">        comment_text=parent_comment.get(<span class="string">&quot;comment&quot;</span>, <span class="string">&quot;&quot;</span>),</span><br><span class="line">        article_title=article_title</span><br><span class="line">    )</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> reply_text:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">&quot;  回复生成失败&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  回复: <span class="subst">&#123;reply_text[:<span class="number">50</span>]&#125;</span>...&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 随机生成昵称</span></span><br><span class="line">    reply_nick = generate_nick()</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  昵称: <span class="subst">&#123;reply_nick&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 获取父评论ID</span></span><br><span class="line">    parent_id = parent_comment.get(<span class="string">&quot;_id&quot;</span>) <span class="keyword">or</span> parent_comment.get(<span class="string">&quot;id&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 获取父评论的 rid</span></span><br><span class="line">    parent_rid = parent_comment.get(<span class="string">&quot;rid&quot;</span>, <span class="string">&quot;&quot;</span>)</span><br><span class="line">    <span class="keyword">if</span> parent_rid:</span><br><span class="line">        <span class="comment"># 父评论本身是回复，继承其 rid</span></span><br><span class="line">        root_id = parent_rid</span><br><span class="line">    <span class="keyword">else</span>:</span><br><span class="line">        <span class="comment"># 父评论是顶级评论，rid 就是父评论自己的 id</span></span><br><span class="line">        root_id = parent_id</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 提交回复（不加 @，Twikoo 前端自动显示）</span></span><br><span class="line">    result = submit_comment(</span><br><span class="line">        url=parent_comment.get(<span class="string">&quot;url&quot;</span>, <span class="string">&quot;/&quot;</span>),</span><br><span class="line">        comment=reply_text,</span><br><span class="line">        nick=reply_nick,</span><br><span class="line">        mail=<span class="string">f&quot;ai-reply-<span class="subst">&#123;random.randint(<span class="number">1000</span>,<span class="number">9999</span>)&#125;</span>@example.com&quot;</span>,</span><br><span class="line">        pid=parent_id,</span><br><span class="line">        rid=root_id,</span><br><span class="line">    )</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">return</span> result</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">run_reply_bot</span>(<span class="params">url: <span class="built_in">str</span>, bot_nicks: <span class="type">List</span>[<span class="built_in">str</span>], max_reply: <span class="built_in">int</span> = <span class="number">3</span></span>):</span><br><span class="line">    <span class="string">&quot;&quot;&quot;运行回复机器人&quot;&quot;&quot;</span></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;检查文章: <span class="subst">&#123;url&#125;</span>&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    unreplied = get_unreplied_comments(url, bot_nicks)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 随机打乱顺序</span></span><br><span class="line">    random.shuffle(unreplied)</span><br><span class="line">    </span><br><span class="line">    <span class="comment"># 取前 max_reply 条</span></span><br><span class="line">    to_reply = unreplied[:max_reply]</span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;选择回复 <span class="subst">&#123;<span class="built_in">len</span>(to_reply)&#125;</span>/<span class="subst">&#123;<span class="built_in">len</span>(unreplied)&#125;</span> 条评论&quot;</span>)</span><br><span class="line">    </span><br><span class="line">    success = <span class="number">0</span></span><br><span class="line">    <span class="keyword">for</span> comment <span class="keyword">in</span> to_reply:</span><br><span class="line">        <span class="keyword">if</span> reply_to_comment(comment, <span class="string">&quot;文章标题&quot;</span>):</span><br><span class="line">            success += <span class="number">1</span></span><br><span class="line">    </span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;完成: 回复 <span class="subst">&#123;success&#125;</span>/<span class="subst">&#123;<span class="built_in">len</span>(to_reply)&#125;</span> 条评论&quot;</span>)</span><br><span class="line">    <span class="keyword">return</span> success</span><br></pre></td></tr></table></figure><h4 id="main-py"><a href="#main-py" class="headerlink" title="main.py"></a>main.py</h4><p><code>main.py</code> 作为入口调度模块，负责整合全系统运行流程：自动扫描 Hexo 生成目录发现文章列表，按配置比例随机调度新评论或回复模式，提供 CLI 参数支持单篇&#x2F;批量&#x2F;范围选择及临时比例覆盖，最终输出执行统计报告，是日常定时任务调用的唯一入口。</p><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#!/usr/bin/env python3</span></span><br><span class="line"><span class="comment"># -*- coding: utf-8 -*-</span></span><br><span class="line"><span class="string">&quot;&quot;&quot;</span></span><br><span class="line"><span class="string">AI 博客评论机器人 - 智能模式</span></span><br><span class="line"><span class="string">按配置比例随机选择发新评论或回复现有评论</span></span><br><span class="line"><span class="string">&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">import</span> sys</span><br><span class="line"><span class="keyword">import</span> argparse</span><br><span class="line"><span class="keyword">import</span> os</span><br><span class="line"><span class="keyword">import</span> re</span><br><span class="line"><span class="keyword">import</span> urllib.parse</span><br><span class="line"><span class="keyword">import</span> random</span><br><span class="line"><span class="keyword">from</span> typing <span class="keyword">import</span> <span class="type">List</span>, <span class="type">Dict</span></span><br><span class="line"><span class="keyword">from</span> .reply_bot <span class="keyword">import</span> run_reply_bot</span><br><span class="line"><span class="keyword">from</span> .ai_service <span class="keyword">import</span> generate_comment, generate_nick</span><br><span class="line"><span class="keyword">from</span> .twikoo_client <span class="keyword">import</span> submit_comment</span><br><span class="line"><span class="keyword">from</span> .config <span class="keyword">import</span> NEW_COMMENT_RATIO</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== 文章加载 ==========</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">get_hexo_articles</span>(<span class="params">public_dir: <span class="built_in">str</span> = <span class="string">&quot;/www/wwwroot/myblog/public&quot;</span></span>) -&gt; <span class="type">List</span>[<span class="type">Dict</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;从 Hexo 生成目录获取文章列表&quot;&quot;&quot;</span></span><br><span class="line">    articles = []</span><br><span class="line">    <span class="keyword">for</span> root, dirs, files <span class="keyword">in</span> os.walk(public_dir):</span><br><span class="line">        rel_path = os.path.relpath(root, public_dir)</span><br><span class="line">        <span class="keyword">if</span> <span class="keyword">not</span> re.<span class="keyword">match</span>(<span class="string">r&#x27;^\d&#123;4&#125;/\d&#123;2&#125;/\d&#123;2&#125;/&#x27;</span>, rel_path):</span><br><span class="line">            <span class="keyword">continue</span></span><br><span class="line">        <span class="keyword">if</span> <span class="string">&quot;index.html&quot;</span> <span class="keyword">not</span> <span class="keyword">in</span> files:</span><br><span class="line">            <span class="keyword">continue</span></span><br><span class="line">        url = <span class="string">f&quot;/<span class="subst">&#123;rel_path&#125;</span>/&quot;</span></span><br><span class="line">        dir_name = os.path.basename(rel_path)</span><br><span class="line">        title = urllib.parse.unquote(dir_name)</span><br><span class="line">        articles.append(&#123;<span class="string">&quot;url&quot;</span>: url, <span class="string">&quot;title&quot;</span>: title, <span class="string">&quot;content&quot;</span>: <span class="string">&quot;&quot;</span>&#125;)</span><br><span class="line">    <span class="keyword">return</span> articles</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">load_articles</span>() -&gt; <span class="type">List</span>[<span class="type">Dict</span>]:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;加载文章列表&quot;&quot;&quot;</span></span><br><span class="line">    articles = get_hexo_articles()</span><br><span class="line">    <span class="keyword">if</span> articles:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;自动获取到 <span class="subst">&#123;<span class="built_in">len</span>(articles)&#125;</span> 篇文章&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> articles</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">&quot;自动获取失败&quot;</span>)</span><br><span class="line">    <span class="keyword">return</span> []</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== 新评论 ==========</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">generate_mail</span>() -&gt; <span class="built_in">str</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;生成随机邮箱&quot;&quot;&quot;</span></span><br><span class="line">    <span class="keyword">return</span> <span class="string">f&quot;user<span class="subst">&#123;random.randint(<span class="number">1000</span>, <span class="number">9999</span>)&#125;</span>@example.com&quot;</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">process_new_comment</span>(<span class="params">url: <span class="built_in">str</span>, title: <span class="built_in">str</span>, content: <span class="built_in">str</span> = <span class="string">&quot;&quot;</span></span>) -&gt; <span class="built_in">bool</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;发新评论&quot;&quot;&quot;</span></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;处理: <span class="subst">&#123;title&#125;</span>&quot;</span>)</span><br><span class="line"></span><br><span class="line">    comment_text = generate_comment(title, content, url)</span><br><span class="line">    <span class="keyword">if</span> <span class="keyword">not</span> comment_text:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">&quot;  AI 生成失败&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br><span class="line"></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  生成: <span class="subst">&#123;comment_text[:<span class="number">50</span>]&#125;</span>...&quot;</span>)</span><br><span class="line"></span><br><span class="line">    nick = generate_nick()</span><br><span class="line">    mail = generate_mail()</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  昵称: <span class="subst">&#123;nick&#125;</span>&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;  邮箱: <span class="subst">&#123;mail&#125;</span>&quot;</span>)</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> submit_comment(url, comment_text, nick, mail):</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  ✅ 提交成功&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">True</span></span><br><span class="line">    <span class="keyword">else</span>:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;  ❌ 提交失败&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span> <span class="literal">False</span></span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== 智能调度 ==========</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">process_article_smart</span>(<span class="params">article: <span class="type">Dict</span>, bot_nicks: <span class="type">List</span>[<span class="built_in">str</span>], max_reply: <span class="built_in">int</span> = <span class="number">3</span></span>) -&gt; <span class="type">Dict</span>:</span><br><span class="line">    <span class="string">&quot;&quot;&quot;智能处理：随机选择发新评论或回复&quot;&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">    url = article[<span class="string">&quot;url&quot;</span>]</span><br><span class="line">    title = article[<span class="string">&quot;title&quot;</span>]</span><br><span class="line">    is_new = random.randint(<span class="number">1</span>, <span class="number">100</span>) &lt;= NEW_COMMENT_RATIO</span><br><span class="line"></span><br><span class="line">    result = &#123;</span><br><span class="line">        <span class="string">&quot;url&quot;</span>: url, <span class="string">&quot;title&quot;</span>: title,</span><br><span class="line">        <span class="string">&quot;mode&quot;</span>: <span class="string">&quot;new&quot;</span> <span class="keyword">if</span> is_new <span class="keyword">else</span> <span class="string">&quot;reply&quot;</span>,</span><br><span class="line">        <span class="string">&quot;success&quot;</span>: <span class="literal">False</span>, <span class="string">&quot;detail&quot;</span>: <span class="string">&quot;&quot;</span></span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> is_new:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;\n📝 [<span class="subst">&#123;title&#125;</span>] 随机选择：发新评论&quot;</span>)</span><br><span class="line">        success = process_new_comment(url, title, article.get(<span class="string">&quot;content&quot;</span>, <span class="string">&quot;&quot;</span>))</span><br><span class="line">        result[<span class="string">&quot;success&quot;</span>] = success</span><br><span class="line">        result[<span class="string">&quot;detail&quot;</span>] = <span class="string">&quot;新评论提交成功&quot;</span> <span class="keyword">if</span> success <span class="keyword">else</span> <span class="string">&quot;新评论提交失败&quot;</span></span><br><span class="line">    <span class="keyword">else</span>:</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;\n💬 [<span class="subst">&#123;title&#125;</span>] 随机选择：回复评论&quot;</span>)</span><br><span class="line">        count = run_reply_bot(url, bot_nicks, max_reply=max_reply)</span><br><span class="line">        result[<span class="string">&quot;success&quot;</span>] = count &gt; <span class="number">0</span></span><br><span class="line">        result[<span class="string">&quot;detail&quot;</span>] = <span class="string">f&quot;回复了 <span class="subst">&#123;count&#125;</span> 条评论&quot;</span></span><br><span class="line"></span><br><span class="line">    <span class="keyword">return</span> result</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">run_smart</span>(<span class="params">articles: <span class="type">List</span>[<span class="type">Dict</span>], bot_nicks: <span class="type">List</span>[<span class="built_in">str</span>] = <span class="literal">None</span>, max_reply: <span class="built_in">int</span> = <span class="number">3</span></span>):</span><br><span class="line">    <span class="string">&quot;&quot;&quot;批量智能处理&quot;&quot;&quot;</span></span><br><span class="line">    <span class="keyword">if</span> bot_nicks <span class="keyword">is</span> <span class="literal">None</span>:</span><br><span class="line">        bot_nicks = [<span class="string">&quot;AI助手&quot;</span>, <span class="string">&quot;博主助手&quot;</span>]</span><br><span class="line"></span><br><span class="line">    stats = &#123;<span class="string">&quot;new&quot;</span>: <span class="number">0</span>, <span class="string">&quot;reply&quot;</span>: <span class="number">0</span>, <span class="string">&quot;new_ok&quot;</span>: <span class="number">0</span>, <span class="string">&quot;reply_ok&quot;</span>: <span class="number">0</span>&#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">for</span> article <span class="keyword">in</span> articles:</span><br><span class="line">        r = process_article_smart(article, bot_nicks, max_reply)</span><br><span class="line">        stats[r[<span class="string">&quot;mode&quot;</span>]] += <span class="number">1</span></span><br><span class="line">        <span class="keyword">if</span> r[<span class="string">&quot;success&quot;</span>]:</span><br><span class="line">            stats[<span class="string">f&quot;<span class="subst">&#123;r[<span class="string">&#x27;mode&#x27;</span>]&#125;</span>_ok&quot;</span>] += <span class="number">1</span></span><br><span class="line"></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;\n<span class="subst">&#123;<span class="string">&#x27;=&#x27;</span>*<span class="number">50</span>&#125;</span>&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">&quot;📊 执行统计&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;<span class="subst">&#123;<span class="string">&#x27;=&#x27;</span>*<span class="number">50</span>&#125;</span>&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;总文章: <span class="subst">&#123;<span class="built_in">len</span>(articles)&#125;</span>&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;新评论: <span class="subst">&#123;stats[<span class="string">&#x27;new&#x27;</span>]&#125;</span> 篇 (成功 <span class="subst">&#123;stats[<span class="string">&#x27;new_ok&#x27;</span>]&#125;</span>)&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;回  复: <span class="subst">&#123;stats[<span class="string">&#x27;reply&#x27;</span>]&#125;</span> 篇 (成功 <span class="subst">&#123;stats[<span class="string">&#x27;reply_ok&#x27;</span>]&#125;</span>)&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;设置比例: <span class="subst">&#123;NEW_COMMENT_RATIO&#125;</span>%&quot;</span>)</span><br><span class="line">    actual = <span class="built_in">round</span>(stats[<span class="string">&#x27;new&#x27;</span>]/<span class="built_in">len</span>(articles)*<span class="number">100</span>, <span class="number">1</span>) <span class="keyword">if</span> articles <span class="keyword">else</span> <span class="number">0</span></span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;实际比例: <span class="subst">&#123;actual&#125;</span>%&quot;</span>)</span><br><span class="line">    <span class="built_in">print</span>(<span class="string">f&quot;<span class="subst">&#123;<span class="string">&#x27;=&#x27;</span>*<span class="number">50</span>&#125;</span>&quot;</span>)</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment"># ========== CLI ==========</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">def</span> <span class="title function_">main</span>():</span><br><span class="line">    parser = argparse.ArgumentParser(description=<span class="string">&quot;AI Blog Bot&quot;</span>)</span><br><span class="line">    parser.add_argument(<span class="string">&quot;command&quot;</span>, choices=[<span class="string">&quot;run&quot;</span>, <span class="string">&quot;list&quot;</span>])</span><br><span class="line">    parser.add_argument(<span class="string">&quot;--id&quot;</span>, <span class="built_in">type</span>=<span class="built_in">str</span>, <span class="built_in">help</span>=<span class="string">&quot;文章序号，如 12 或 1,3,5-10&quot;</span>)</span><br><span class="line">    parser.add_argument(<span class="string">&quot;--count&quot;</span>, <span class="built_in">type</span>=<span class="built_in">int</span>, default=<span class="number">3</span>, <span class="built_in">help</span>=<span class="string">&quot;回复上限（默认3）&quot;</span>)</span><br><span class="line">    parser.add_argument(<span class="string">&quot;--ratio&quot;</span>, <span class="built_in">type</span>=<span class="built_in">int</span>, <span class="built_in">help</span>=<span class="string">&quot;临时新评论比例 1-100&quot;</span>)</span><br><span class="line"></span><br><span class="line">    args = parser.parse_args()</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> args.command == <span class="string">&quot;list&quot;</span>:</span><br><span class="line">        articles = load_articles()</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;\n<span class="subst">&#123;<span class="string">&#x27;序号&#x27;</span>:&lt;<span class="number">6</span>&#125;</span><span class="subst">&#123;<span class="string">&#x27;标题&#x27;</span>:&lt;<span class="number">40</span>&#125;</span><span class="subst">&#123;<span class="string">&#x27;URL&#x27;</span>&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">&quot;-&quot;</span> * <span class="number">80</span>)</span><br><span class="line">        <span class="keyword">for</span> i, a <span class="keyword">in</span> <span class="built_in">enumerate</span>(articles, <span class="number">1</span>):</span><br><span class="line">            <span class="built_in">print</span>(<span class="string">f&quot;<span class="subst">&#123;i:&lt;<span class="number">6</span>&#125;</span><span class="subst">&#123;a[<span class="string">&#x27;title&#x27;</span>][:<span class="number">38</span>]:&lt;<span class="number">40</span>&#125;</span><span class="subst">&#123;a[<span class="string">&#x27;url&#x27;</span>][:<span class="number">50</span>]&#125;</span>&quot;</span>)</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;\n共 <span class="subst">&#123;<span class="built_in">len</span>(articles)&#125;</span> 篇&quot;</span>)</span><br><span class="line">        <span class="keyword">return</span></span><br><span class="line"></span><br><span class="line">    <span class="comment"># 临时覆盖比例</span></span><br><span class="line">    <span class="keyword">if</span> args.ratio <span class="keyword">is</span> <span class="keyword">not</span> <span class="literal">None</span>:</span><br><span class="line">        <span class="keyword">global</span> NEW_COMMENT_RATIO</span><br><span class="line">        NEW_COMMENT_RATIO = <span class="built_in">max</span>(<span class="number">1</span>, <span class="built_in">min</span>(<span class="number">100</span>, args.ratio))</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;临时比例: <span class="subst">&#123;NEW_COMMENT_RATIO&#125;</span>%&quot;</span>)</span><br><span class="line"></span><br><span class="line">    bot_nicks = [<span class="string">&quot;AI助手&quot;</span>, <span class="string">&quot;博主助手&quot;</span>]</span><br><span class="line">    articles = load_articles()</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> args.<span class="built_in">id</span>:</span><br><span class="line">        selected = []</span><br><span class="line">        <span class="keyword">for</span> part <span class="keyword">in</span> args.<span class="built_in">id</span>.split(<span class="string">&#x27;,&#x27;</span>):</span><br><span class="line">            <span class="keyword">if</span> <span class="string">&#x27;-&#x27;</span> <span class="keyword">in</span> part:</span><br><span class="line">                s, e = <span class="built_in">map</span>(<span class="built_in">int</span>, part.split(<span class="string">&#x27;-&#x27;</span>))</span><br><span class="line">                selected.extend([articles[i-<span class="number">1</span>] <span class="keyword">for</span> i <span class="keyword">in</span> <span class="built_in">range</span>(s, e+<span class="number">1</span>) <span class="keyword">if</span> <span class="number">1</span> &lt;= i &lt;= <span class="built_in">len</span>(articles)])</span><br><span class="line">            <span class="keyword">else</span>:</span><br><span class="line">                i = <span class="built_in">int</span>(part)</span><br><span class="line">                <span class="keyword">if</span> <span class="number">1</span> &lt;= i &lt;= <span class="built_in">len</span>(articles):</span><br><span class="line">                    selected.append(articles[i-<span class="number">1</span>])</span><br><span class="line">        <span class="built_in">print</span>(<span class="string">f&quot;处理 <span class="subst">&#123;<span class="built_in">len</span>(selected)&#125;</span> 篇&quot;</span>)</span><br><span class="line">        run_smart(selected, bot_nicks, max_reply=args.count)</span><br><span class="line">    <span class="keyword">else</span>:</span><br><span class="line">        run_smart(articles, bot_nicks, max_reply=args.count)</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="keyword">if</span> __name__ == <span class="string">&quot;__main__&quot;</span>:</span><br><span class="line">    main()</span><br></pre></td></tr></table></figure><h2 id="使用方法"><a href="#使用方法" class="headerlink" title="使用方法"></a>使用方法</h2><h3 id="基础用法"><a href="#基础用法" class="headerlink" title="基础用法"></a>基础用法</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#查看文章列表</span></span><br><span class="line">python -m ai_bot.main list</span><br><span class="line"></span><br><span class="line"><span class="comment"># 处理单篇文章（按配置比例随机选择模式）</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 3</span><br><span class="line"></span><br><span class="line"><span class="comment"># 处理多篇</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 1,3,5</span><br><span class="line"></span><br><span class="line"><span class="comment"># 处理范围</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 1-10</span><br></pre></td></tr></table></figure><h3 id="模式控制"><a href="#模式控制" class="headerlink" title="模式控制"></a>模式控制</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 强制发新评论（100% 概率）</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 3 --ratio 100</span><br><span class="line"></span><br><span class="line"><span class="comment"># 强制回复模式（0% 概率发新评论）</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 3 --ratio 0</span><br><span class="line"></span><br><span class="line"><span class="comment"># 回复模式下，最多回复 5 条现有评论</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 3 --ratio 0 --count 5</span><br></pre></td></tr></table></figure><h3 id="批量处理"><a href="#批量处理" class="headerlink" title="批量处理"></a>批量处理</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 全部文章（按默认比例）</span></span><br><span class="line">python -m ai_bot.main run</span><br><span class="line"></span><br><span class="line"><span class="comment"># 指定范围 + 强制新评论</span></span><br><span class="line">python -m ai_bot.main run --<span class="built_in">id</span> 5-20 --ratio 100</span><br></pre></td></tr></table></figure><h3 id="相关参数"><a href="#相关参数" class="headerlink" title="相关参数"></a>相关参数</h3><table><thead><tr><th>参数</th><th>必填</th><th>默认值</th><th>说明</th></tr></thead><tbody><tr><td><code>--id</code></td><td>否</td><td>全部</td><td>文章序号，如 3 &#x2F; 1,3 &#x2F; 5-10</td></tr><tr><td><code>--ratio</code></td><td>否</td><td>配置值</td><td>临时覆盖新评论比例，1-100</td></tr><tr><td><code>--count</code></td><td>否</td><td>3</td><td>回复模式下单篇最大回复数</td></tr></tbody></table><h2 id="后续扩展"><a href="#后续扩展" class="headerlink" title="后续扩展"></a>后续扩展</h2><p><strong>AI 互动机器人</strong>：注册固定昵称（如 <code>@小助手</code>），访客可在评论区 <code>@</code> 主动提问，AI 实时检测触发词并回复，支持多轮对话，从单向评论输出升级为双向互动助手。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/CommentBot/">CommentBot</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/06/08/16496380/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>从 Ollama 到云端：Hexo AI 摘要的多平台进化之路</title>
      <link>https://blog.eucalyptus.cc/2026/06/01/45224c9f/</link>
      <guid>https://blog.eucalyptus.cc/2026/06/01/45224c9f/</guid>
      <pubDate>Mon, 01 Jun 2026 05:16:37 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h1 id=&quot;从-Ollama-到云端：Hexo-AI-摘要的多平台进化之路&quot;&gt;&lt;a href=&quot;#从-Ollama-到云端：Hexo-AI-摘要的多平台进化之路&quot; class=&quot;headerlink&quot; title=&quot;从 Ollama 到云端：Hexo AI</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h1 id="从-Ollama-到云端：Hexo-AI-摘要的多平台进化之路"><a href="#从-Ollama-到云端：Hexo-AI-摘要的多平台进化之路" class="headerlink" title="从 Ollama 到云端：Hexo AI 摘要的多平台进化之路"></a>从 Ollama 到云端：Hexo AI 摘要的多平台进化之路</h1><blockquote><p>之前我写了《使用 Ollama 为 Hexo 博客部署 AI 文章摘要》，介绍了本地部署大模型生成摘要的方案。运行一段时间后，发现几个问题：3B 模型效果一般，更大的模型又吃资源；生成速度慢，用户体验不佳；服务器配置有限，经常卡顿。于是，我重新设计了一套架构：保留前端交互，后端加入代理层，支持多个云端 API，并用 Redis 缓存加速。本文分享这个升级过程。</p></blockquote><div class='anzhiyu-tag-link'><a class="tag-Link"  href="/2026/05/16/83caee76/">    <div class="tag-link-tips">站内地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://img.eucalyptus.cc/images/logo.png" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://img.eucalyptus.cc/images/logo.png" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">使用 Ollama 为 Hexo 博客部署 AI 文章摘要</div>            <div class="tag-link-sitename">本站文章</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div> <h2 id="Ollama-方案的局限"><a href="#Ollama-方案的局限" class="headerlink" title="Ollama 方案的局限"></a>Ollama 方案的局限</h2><p>之前的架构：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">前端 JS → Ollama API (本地 11434 端口)</span><br></pre></td></tr></table></figure><p>遇到的问题：</p><table><thead><tr><th>问题</th><th>说明</th></tr></thead><tbody><tr><td>模型效果</td><td>qwen2.5:3b 摘要质量一般，7b 又太慢</td></tr><tr><td>资源占用</td><td>8G 内存服务器，跑模型容易卡死</td></tr><tr><td>生成速度</td><td>本地生成一次摘要要 5-20 秒</td></tr><tr><td>维护成本</td><td>需要定期更新模型，管理模型文件</td></tr></tbody></table><h2 id="新架构设计"><a href="#新架构设计" class="headerlink" title="新架构设计"></a>新架构设计</h2><p>升级后的架构：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">前端 JS → Nginx → Node.js 代理 → Redis 缓存 / 云端 API</span><br><span class="line">              ↑</span><br><span class="line">         静态文件 (Hexo)</span><br></pre></td></tr></table></figure><p>核心变化：</p><ol><li><strong>加入代理层</strong>：前端不再直接调 AI API，而是通过代理转发</li><li><strong>支持多平台</strong>：日日新、DeepSeek、Ollama 自由切换</li><li><strong>Redis 缓存</strong>：相同文章直接返回缓存，不重复调用 API</li><li><strong>Key 安全</strong>：API Key 放在服务器，前端不可见</li></ol><h2 id="部署"><a href="#部署" class="headerlink" title="部署"></a>部署</h2><h3 id="Docker拉起Redis-容器编排"><a href="#Docker拉起Redis-容器编排" class="headerlink" title="Docker拉起Redis(容器编排)"></a>Docker拉起Redis(容器编排)</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 创建目录</span></span><br><span class="line"><span class="built_in">mkdir</span> -p /opt/redis/data</span><br><span class="line"><span class="built_in">cd</span> /opt/redis</span><br><span class="line"></span><br><span class="line"><span class="comment"># 创建 docker-compose.yml</span></span><br><span class="line"><span class="built_in">cat</span> &gt; docker-compose.yml &lt;&lt; <span class="string">&#x27;EOF&#x27;</span></span><br><span class="line">version: <span class="string">&#x27;3.8&#x27;</span></span><br><span class="line">services:</span><br><span class="line">  redis:</span><br><span class="line">    image: redis:7-alpine</span><br><span class="line">    container_name: redis-ai</span><br><span class="line">    restart: always</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;127.0.0.1:6379:6379&quot;</span></span><br><span class="line">    volumes:</span><br><span class="line">      - /var/lib/docker//redis:/data</span><br><span class="line">    <span class="built_in">command</span>: redis-server --appendonly <span class="built_in">yes</span></span><br><span class="line">EOF</span><br><span class="line"></span><br><span class="line"><span class="comment"># 启动</span></span><br><span class="line">docker-compose up -d</span><br><span class="line"></span><br><span class="line"><span class="comment"># 验证</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli ping</span><br></pre></td></tr></table></figure><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-01/1.avif"></p><h3 id="部署AI代理"><a href="#部署AI代理" class="headerlink" title="部署AI代理"></a>部署AI代理</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 创建目录</span></span><br><span class="line"><span class="built_in">mkdir</span> -p /opt/ai-proxy</span><br><span class="line"><span class="built_in">cd</span> /opt/ai-proxy</span><br><span class="line"></span><br><span class="line"><span class="comment"># 初始化</span></span><br><span class="line">npm init -y</span><br><span class="line">npm install express node-fetch ioredis</span><br><span class="line"></span><br><span class="line"><span class="comment"># 创建 index.js（代理代码）</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 启动</span></span><br><span class="line">pm2 start index.js --name ai-proxy</span><br><span class="line">pm2 save</span><br><span class="line">pm2 startup</span><br></pre></td></tr></table></figure><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">const</span> express = <span class="built_in">require</span>(<span class="string">&#x27;express&#x27;</span>);</span><br><span class="line"><span class="keyword">const</span> fetch = <span class="built_in">require</span>(<span class="string">&#x27;node-fetch&#x27;</span>);</span><br><span class="line"><span class="keyword">const</span> <span class="title class_">Redis</span> = <span class="built_in">require</span>(<span class="string">&#x27;ioredis&#x27;</span>);</span><br><span class="line"><span class="keyword">const</span> crypto = <span class="built_in">require</span>(<span class="string">&#x27;crypto&#x27;</span>);</span><br><span class="line"></span><br><span class="line"><span class="keyword">const</span> app = <span class="title function_">express</span>();</span><br><span class="line"></span><br><span class="line"><span class="comment">// Redis 连接</span></span><br><span class="line"><span class="keyword">const</span> redis = <span class="keyword">new</span> <span class="title class_">Redis</span>(&#123;</span><br><span class="line">  <span class="attr">host</span>: <span class="string">&#x27;127.0.0.1&#x27;</span>,</span><br><span class="line">  <span class="attr">port</span>: <span class="number">6379</span>,</span><br><span class="line">  <span class="attr">db</span>: <span class="number">0</span></span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line">redis.<span class="title function_">on</span>(<span class="string">&#x27;connect&#x27;</span>, <span class="function">() =&gt;</span> <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">&#x27;[Redis] Connected&#x27;</span>));</span><br><span class="line">redis.<span class="title function_">on</span>(<span class="string">&#x27;error&#x27;</span>, <span class="function">(<span class="params">err</span>) =&gt;</span> <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[Redis] Error:&#x27;</span>, err));</span><br><span class="line"></span><br><span class="line"><span class="comment">// 缓存时间：7天（秒）</span></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">CACHE_TTL</span> = <span class="number">7</span> * <span class="number">24</span> * <span class="number">60</span> * <span class="number">60</span>;</span><br><span class="line"></span><br><span class="line"><span class="comment">// 只用内容哈希生成缓存 key</span></span><br><span class="line"><span class="keyword">function</span> <span class="title function_">getCacheKey</span>(<span class="params">text</span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> contentHash = crypto.<span class="title function_">createHash</span>(<span class="string">&#x27;md5&#x27;</span>).<span class="title function_">update</span>(text.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">4000</span>)).<span class="title function_">digest</span>(<span class="string">&#x27;hex&#x27;</span>).<span class="title function_">substring</span>(<span class="number">0</span>, <span class="number">16</span>);</span><br><span class="line">  <span class="keyword">return</span> <span class="string">`ai:summary:<span class="subst">$&#123;contentHash&#125;</span>`</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">app.<span class="title function_">use</span>(express.<span class="title function_">json</span>());</span><br><span class="line"></span><br><span class="line">app.<span class="title function_">use</span>(<span class="function">(<span class="params">req, res, next</span>) =&gt;</span> &#123;</span><br><span class="line">  <span class="keyword">const</span> allowedOrigins = [<span class="string">&#x27;https://blog.eucalyptus.cc&#x27;</span>];</span><br><span class="line">  <span class="keyword">const</span> origin = req.<span class="property">headers</span>.<span class="property">origin</span>;</span><br><span class="line">  </span><br><span class="line">  <span class="keyword">if</span> (allowedOrigins.<span class="title function_">includes</span>(origin)) &#123;</span><br><span class="line">    res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Origin&#x27;</span>, origin);</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Methods&#x27;</span>, <span class="string">&#x27;POST, OPTIONS&#x27;</span>);</span><br><span class="line">  res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Headers&#x27;</span>, <span class="string">&#x27;Content-Type, Authorization&#x27;</span>);</span><br><span class="line">  </span><br><span class="line">  <span class="keyword">if</span> (req.<span class="property">method</span> === <span class="string">&#x27;OPTIONS&#x27;</span>) <span class="keyword">return</span> res.<span class="title function_">sendStatus</span>(<span class="number">200</span>);</span><br><span class="line">  <span class="title function_">next</span>();</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line">app.<span class="title function_">post</span>(<span class="string">&#x27;/api/ai-summary&#x27;</span>, <span class="title function_">async</span> (req, res) =&gt; &#123;</span><br><span class="line">  <span class="keyword">const</span> &#123; text &#125; = req.<span class="property">body</span> || &#123;&#125;;</span><br><span class="line">  </span><br><span class="line">  <span class="keyword">if</span> (!text || text.<span class="property">length</span> &lt; <span class="number">50</span>) &#123;</span><br><span class="line">    <span class="keyword">return</span> res.<span class="title function_">status</span>(<span class="number">400</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: <span class="string">&#x27;Text too short&#x27;</span> &#125;);</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="keyword">const</span> cacheKey = <span class="title function_">getCacheKey</span>(text);</span><br><span class="line">  </span><br><span class="line">  <span class="keyword">try</span> &#123;</span><br><span class="line">    <span class="comment">// 1. 查 Redis 缓存</span></span><br><span class="line">    <span class="keyword">const</span> cached = <span class="keyword">await</span> redis.<span class="title function_">get</span>(cacheKey);</span><br><span class="line">    <span class="keyword">if</span> (cached) &#123;</span><br><span class="line">      <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">&#x27;[Cache] Hit:&#x27;</span>, cacheKey);</span><br><span class="line">      <span class="keyword">return</span> res.<span class="title function_">json</span>(&#123; <span class="attr">summary</span>: cached, <span class="attr">cached</span>: <span class="literal">true</span> &#125;);</span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">&#x27;[Cache] Miss:&#x27;</span>, cacheKey);</span><br><span class="line">    </span><br><span class="line">    <span class="comment">// 2. 调日日新 API</span></span><br><span class="line">    <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="string">&#x27;https://token.sensenova.cn/v1/chat/completions&#x27;</span>, &#123;</span><br><span class="line">      <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>,</span><br><span class="line">      <span class="attr">headers</span>: &#123;</span><br><span class="line">        <span class="string">&#x27;Authorization&#x27;</span>: <span class="string">&#x27;Bearer 输入自己的key&#x27;</span>,</span><br><span class="line">        <span class="string">&#x27;Content-Type&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span></span><br><span class="line">      &#125;,</span><br><span class="line">      <span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(&#123;</span><br><span class="line">        <span class="attr">model</span>: <span class="string">&#x27;deepseek-v4-flash&#x27;</span>,</span><br><span class="line">        <span class="attr">messages</span>: [</span><br><span class="line">          &#123;</span><br><span class="line">            <span class="attr">role</span>: <span class="string">&#x27;system&#x27;</span>,</span><br><span class="line">            <span class="attr">content</span>: <span class="string">&#x27;请为以下文章生成一段简洁的摘要，突出核心内容。&#x27;</span></span><br><span class="line">          &#125;,</span><br><span class="line">          &#123;</span><br><span class="line">            <span class="attr">role</span>: <span class="string">&#x27;user&#x27;</span>,</span><br><span class="line">            <span class="attr">content</span>: text.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">4000</span>)</span><br><span class="line">          &#125;</span><br><span class="line">        ],</span><br><span class="line">        <span class="attr">max_tokens</span>: <span class="number">200</span>,</span><br><span class="line">        <span class="attr">temperature</span>: <span class="number">0.3</span></span><br><span class="line">      &#125;)</span><br><span class="line">    &#125;);</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> (!response.<span class="property">ok</span>) &#123;</span><br><span class="line">      <span class="keyword">const</span> error = <span class="keyword">await</span> response.<span class="title function_">text</span>();</span><br><span class="line">      <span class="keyword">return</span> res.<span class="title function_">status</span>(response.<span class="property">status</span>).<span class="title function_">json</span>(&#123; error &#125;);</span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">    <span class="keyword">const</span> summary = data.<span class="property">choices</span>?.[<span class="number">0</span>]?.<span class="property">message</span>?.<span class="property">content</span>?.<span class="title function_">trim</span>();</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> (!summary) &#123;</span><br><span class="line">      <span class="keyword">return</span> res.<span class="title function_">status</span>(<span class="number">500</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: <span class="string">&#x27;Empty summary&#x27;</span> &#125;);</span><br><span class="line">    &#125;</span><br><span class="line">    </span><br><span class="line">    <span class="comment">// 3. 写入 Redis 缓存</span></span><br><span class="line">    <span class="keyword">await</span> redis.<span class="title function_">setex</span>(cacheKey, <span class="variable constant_">CACHE_TTL</span>, summary);</span><br><span class="line">    <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">&#x27;[Cache] Saved:&#x27;</span>, cacheKey);</span><br><span class="line">    </span><br><span class="line">    res.<span class="title function_">json</span>(&#123; summary, <span class="attr">cached</span>: <span class="literal">false</span> &#125;);</span><br><span class="line">    </span><br><span class="line">  &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">    <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[AI Proxy] Error:&#x27;</span>, err.<span class="property">message</span>);</span><br><span class="line">    res.<span class="title function_">status</span>(<span class="number">500</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: err.<span class="property">message</span> &#125;);</span><br><span class="line">  &#125;</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">PORT</span> = <span class="number">3000</span>;</span><br><span class="line">app.<span class="title function_">listen</span>(<span class="variable constant_">PORT</span>, <span class="string">&#x27;127.0.0.1&#x27;</span>, <span class="function">() =&gt;</span> &#123;</span><br><span class="line">  <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">`AI Proxy running on http://127.0.0.1:<span class="subst">$&#123;PORT&#125;</span>`</span>);</span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-01/2.avif"></p><h3 id="Nginx反向代理"><a href="#Nginx反向代理" class="headerlink" title="Nginx反向代理"></a>Nginx反向代理</h3><p>这里直接再宝塔面板中配置</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/AI/2026-06-01/3.avif"></p><h3 id="前端集成"><a href="#前端集成" class="headerlink" title="前端集成"></a>前端集成</h3><p>这里不在做过多缀述，参考之前的文章即可，但是需要修改ai-summary.js代码</p><div class='anzhiyu-tag-link'><a class="tag-Link"  href="/2026/05/16/83caee76/">    <div class="tag-link-tips">站内地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://img.eucalyptus.cc/images/logo.png" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://img.eucalyptus.cc/images/logo.png" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">使用 Ollama 为 Hexo 博客部署 AI 文章摘要</div>            <div class="tag-link-sitename">本站文章</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br><span class="line">252</span><br><span class="line">253</span><br><span class="line">254</span><br><span class="line">255</span><br><span class="line">256</span><br><span class="line">257</span><br><span class="line">258</span><br><span class="line">259</span><br><span class="line">260</span><br><span class="line">261</span><br><span class="line">262</span><br><span class="line">263</span><br><span class="line">264</span><br><span class="line">265</span><br><span class="line">266</span><br><span class="line">267</span><br><span class="line">268</span><br><span class="line">269</span><br><span class="line">270</span><br><span class="line">271</span><br><span class="line">272</span><br><span class="line">273</span><br><span class="line">274</span><br><span class="line">275</span><br><span class="line">276</span><br><span class="line">277</span><br><span class="line">278</span><br><span class="line">279</span><br><span class="line">280</span><br><span class="line">281</span><br><span class="line">282</span><br><span class="line">283</span><br><span class="line">284</span><br><span class="line">285</span><br><span class="line">286</span><br><span class="line">287</span><br><span class="line">288</span><br><span class="line">289</span><br><span class="line">290</span><br><span class="line">291</span><br><span class="line">292</span><br><span class="line">293</span><br><span class="line">294</span><br><span class="line">295</span><br><span class="line">296</span><br><span class="line">297</span><br><span class="line">298</span><br><span class="line">299</span><br><span class="line">300</span><br><span class="line">301</span><br><span class="line">302</span><br><span class="line">303</span><br><span class="line">304</span><br><span class="line">305</span><br><span class="line">306</span><br><span class="line">307</span><br><span class="line">308</span><br><span class="line">309</span><br><span class="line">310</span><br><span class="line">311</span><br><span class="line">312</span><br><span class="line">313</span><br><span class="line">314</span><br><span class="line">315</span><br><span class="line">316</span><br><span class="line">317</span><br><span class="line">318</span><br><span class="line">319</span><br><span class="line">320</span><br><span class="line">321</span><br><span class="line">322</span><br><span class="line">323</span><br><span class="line">324</span><br><span class="line">325</span><br><span class="line">326</span><br><span class="line">327</span><br><span class="line">328</span><br><span class="line">329</span><br><span class="line">330</span><br><span class="line">331</span><br><span class="line">332</span><br><span class="line">333</span><br><span class="line">334</span><br><span class="line">335</span><br><span class="line">336</span><br><span class="line">337</span><br><span class="line">338</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/**</span></span><br><span class="line"><span class="comment"> * 安知鱼主题 AI 摘要 - 代理版（无前端缓存）</span></span><br><span class="line"><span class="comment"> */</span></span><br><span class="line">(<span class="keyword">function</span>(<span class="params"></span>) &#123;</span><br><span class="line">  <span class="string">&#x27;use strict&#x27;</span>;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">const</span> <span class="variable constant_">CONFIG</span> = &#123;</span><br><span class="line">    <span class="attr">apiUrl</span>: <span class="string">&#x27;https://ai.eucalyptus.cc/api/ai-summary&#x27;</span>,</span><br><span class="line">    <span class="attr">typeSpeed</span>: <span class="number">35</span>,</span><br><span class="line">    <span class="attr">maxSummaryLength</span>: <span class="number">1000</span>,</span><br><span class="line">    <span class="attr">retryCount</span>: <span class="number">1</span></span><br><span class="line">  &#125;;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">let</span> isProcessing = <span class="literal">false</span>;</span><br><span class="line">  <span class="keyword">let</span> typeWriterTimer = <span class="literal">null</span>;</span><br><span class="line">  <span class="keyword">let</span> abortController = <span class="literal">null</span>;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">waitForElement</span>(<span class="params">selector, timeout = <span class="number">3000</span></span>) &#123;</span><br><span class="line">    <span class="keyword">return</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function">(<span class="params">resolve, reject</span>) =&gt;</span> &#123;</span><br><span class="line">      <span class="keyword">const</span> element = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(selector);</span><br><span class="line">      <span class="keyword">if</span> (element) <span class="keyword">return</span> <span class="title function_">resolve</span>(element);</span><br><span class="line">      <span class="keyword">const</span> observer = <span class="keyword">new</span> <span class="title class_">MutationObserver</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">        <span class="keyword">const</span> el = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(selector);</span><br><span class="line">        <span class="keyword">if</span> (el) &#123; observer.<span class="title function_">disconnect</span>(); <span class="title function_">resolve</span>(el); &#125;</span><br><span class="line">      &#125;);</span><br><span class="line">      observer.<span class="title function_">observe</span>(<span class="variable language_">document</span>.<span class="property">body</span>, &#123; <span class="attr">childList</span>: <span class="literal">true</span>, <span class="attr">subtree</span>: <span class="literal">true</span> &#125;);</span><br><span class="line">      <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> &#123; observer.<span class="title function_">disconnect</span>(); <span class="title function_">reject</span>(<span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">`Timeout waiting for <span class="subst">$&#123;selector&#125;</span>`</span>)); &#125;, timeout);</span><br><span class="line">    &#125;);</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">escapeHtml</span>(<span class="params">text</span>) &#123;</span><br><span class="line">    <span class="keyword">if</span> (!text) <span class="keyword">return</span> <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">    <span class="keyword">const</span> div = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&#x27;div&#x27;</span>);</span><br><span class="line">    div.<span class="property">textContent</span> = text;</span><br><span class="line">    <span class="keyword">return</span> div.<span class="property">innerHTML</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">typeWriter</span>(<span class="params">element, text, speed = CONFIG.typeSpeed</span>) &#123;</span><br><span class="line">    <span class="keyword">return</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function">(<span class="params">resolve</span>) =&gt;</span> &#123;</span><br><span class="line">      <span class="keyword">if</span> (typeWriterTimer) &#123; <span class="built_in">clearInterval</span>(typeWriterTimer); typeWriterTimer = <span class="literal">null</span>; &#125;</span><br><span class="line">      <span class="keyword">let</span> index = <span class="number">0</span>;</span><br><span class="line">      element.<span class="property">textContent</span> = <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">      typeWriterTimer = <span class="built_in">setInterval</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">        <span class="keyword">if</span> (index &lt; text.<span class="property">length</span>) &#123; </span><br><span class="line">          element.<span class="property">textContent</span> += text.<span class="title function_">charAt</span>(index); </span><br><span class="line">          index++; </span><br><span class="line">        &#125; <span class="keyword">else</span> &#123; </span><br><span class="line">          <span class="built_in">clearInterval</span>(typeWriterTimer); </span><br><span class="line">          typeWriterTimer = <span class="literal">null</span>; </span><br><span class="line">          <span class="title function_">resolve</span>(); </span><br><span class="line">        &#125;</span><br><span class="line">      &#125;, speed);</span><br><span class="line">    &#125;);</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">getArticleText</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="keyword">const</span> selectors = [</span><br><span class="line">      <span class="string">&#x27;#article-container .post-content&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;#article-container #post&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.post-content&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;article .entry-content&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;#post-content&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.article-content&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.markdown-body&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;#content article&#x27;</span></span><br><span class="line">    ];</span><br><span class="line"></span><br><span class="line">    <span class="keyword">let</span> article = <span class="literal">null</span>;</span><br><span class="line">    <span class="keyword">for</span> (<span class="keyword">const</span> sel <span class="keyword">of</span> selectors) &#123;</span><br><span class="line">      article = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(sel);</span><br><span class="line">      <span class="keyword">if</span> (article &amp;&amp; article.<span class="property">innerText</span>.<span class="title function_">trim</span>().<span class="property">length</span> &gt; <span class="number">200</span>) <span class="keyword">break</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> (!article) &#123; </span><br><span class="line">      <span class="variable language_">console</span>.<span class="title function_">warn</span>(<span class="string">&#x27;[AI Summary] Article content not found.&#x27;</span>); </span><br><span class="line">      <span class="keyword">return</span> <span class="string">&#x27;&#x27;</span>; </span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> clone = article.<span class="title function_">cloneNode</span>(<span class="literal">true</span>);</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> removeSelectors = [</span><br><span class="line">      <span class="string">&#x27;h1&#x27;</span>, <span class="string">&#x27;h2.post-title&#x27;</span>, <span class="string">&#x27;.post-title&#x27;</span>, <span class="string">&#x27;.page-title&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.post-meta&#x27;</span>, <span class="string">&#x27;.meta&#x27;</span>, <span class="string">&#x27;.entry-meta&#x27;</span>, <span class="string">&#x27;.article-meta&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.post-date&#x27;</span>, <span class="string">&#x27;.post-time&#x27;</span>, <span class="string">&#x27;.published&#x27;</span>, <span class="string">&#x27;.updated&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.author&#x27;</span>, <span class="string">&#x27;.byline&#x27;</span>, <span class="string">&#x27;.post-author&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.post-tags&#x27;</span>, <span class="string">&#x27;.tags&#x27;</span>, <span class="string">&#x27;.tag-cloud&#x27;</span>, <span class="string">&#x27;.post-categories&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;.categories&#x27;</span>, <span class="string">&#x27;.post-category&#x27;</span>, <span class="string">&#x27;.article-tags&#x27;</span>,</span><br><span class="line">      <span class="string">&#x27;nav&#x27;</span>, <span class="string">&#x27;.nav&#x27;</span>, <span class="string">&#x27;.breadcrumb&#x27;</span>, <span class="string">&#x27;.crumbs&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;aside&#x27;</span>, <span class="string">&#x27;.sidebar&#x27;</span>, <span class="string">&#x27;.widget&#x27;</span>, <span class="string">&#x27;.toc&#x27;</span>, <span class="string">&#x27;#toc&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;header&#x27;</span>, <span class="string">&#x27;.post-header&#x27;</span>, <span class="string">&#x27;.entry-header&#x27;</span>, <span class="string">&#x27;.article-header&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;footer&#x27;</span>, <span class="string">&#x27;.post-footer&#x27;</span>, <span class="string">&#x27;.entry-footer&#x27;</span>, <span class="string">&#x27;.article-footer&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;#post-comment&#x27;</span>, <span class="string">&#x27;.comments&#x27;</span>, <span class="string">&#x27;.comment-area&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.share&#x27;</span>, <span class="string">&#x27;.social-share&#x27;</span>, <span class="string">&#x27;.reward&#x27;</span>, <span class="string">&#x27;.donate&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-copyright&#x27;</span>, <span class="string">&#x27;.copyright&#x27;</span>, <span class="string">&#x27;.license&#x27;</span>, <span class="string">&#x27;.declaration&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.relatedPosts&#x27;</span>, <span class="string">&#x27;.related-posts&#x27;</span>, <span class="string">&#x27;.related&#x27;</span>, <span class="string">&#x27;.recommend&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.anzhiyu-ai-summary&#x27;</span>, <span class="string">&#x27;#ai-summary&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;script&#x27;</span>, <span class="string">&#x27;style&#x27;</span>, <span class="string">&#x27;pre&#x27;</span>, <span class="string">&#x27;code&#x27;</span>, <span class="string">&#x27;table&#x27;</span>, </span><br><span class="line">            <span class="string">&#x27;img&#x27;</span>, <span class="string">&#x27;figure&#x27;</span>, <span class="string">&#x27;figcaption&#x27;</span>, <span class="string">&#x27;svg&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;blockquote&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.ads-wrap&#x27;</span>, <span class="string">&#x27;.ad&#x27;</span>, <span class="string">&#x27;.advertisement&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.highlight&#x27;</span>, <span class="string">&#x27;.mermaid&#x27;</span>, <span class="string">&#x27;.katex&#x27;</span>, <span class="string">&#x27;.mathjax&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.pagination&#x27;</span>, <span class="string">&#x27;.pager&#x27;</span>, <span class="string">&#x27;.page-nav&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.notice&#x27;</span>, <span class="string">&#x27;.alert&#x27;</span>, <span class="string">&#x27;.tips&#x27;</span>, <span class="string">&#x27;.warning&#x27;</span></span><br><span class="line">        ];</span><br><span class="line">        </span><br><span class="line">        removeSelectors.<span class="title function_">forEach</span>(<span class="function"><span class="params">sel</span> =&gt;</span> &#123;</span><br><span class="line">            clone.<span class="title function_">querySelectorAll</span>(sel).<span class="title function_">forEach</span>(<span class="function"><span class="params">el</span> =&gt;</span> el.<span class="title function_">remove</span>());</span><br><span class="line">        &#125;);</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">let</span> text = clone.<span class="property">innerText</span></span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/[*#\-_`~\[\]()&gt;|]/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\b[A-Z]&#123;5,&#125;\b/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\d&#123;4&#125;[年/-]\d&#123;1,2&#125;[月/-]\d&#123;1,2&#125;[日]?/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/[^\u4e00-\u9fa5a-zA-Z0-9，。！？；：&quot;&quot;&#x27;&#x27;（）【】《》.,;:!?&#x27;&quot;()\[\]&lt;&gt;、\-—\n]/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">trim</span>();</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">if</span> (text.<span class="property">length</span> &lt; <span class="number">100</span>) &#123;</span><br><span class="line">            <span class="variable language_">console</span>.<span class="title function_">warn</span>(<span class="string">&#x27;[AI Summary] Content too short, trying fallback...&#x27;</span>);</span><br><span class="line">            <span class="keyword">const</span> paragraphs = <span class="title class_">Array</span>.<span class="title function_">from</span>(<span class="variable language_">document</span>.<span class="title function_">querySelectorAll</span>(<span class="string">&#x27;p&#x27;</span>));</span><br><span class="line">            <span class="keyword">const</span> longestP = paragraphs</span><br><span class="line">                .<span class="title function_">filter</span>(<span class="function"><span class="params">p</span> =&gt;</span> &#123;</span><br><span class="line">                    <span class="keyword">const</span> t = p.<span class="property">innerText</span>.<span class="title function_">trim</span>();</span><br><span class="line">                    <span class="keyword">return</span> t.<span class="property">length</span> &gt; <span class="number">50</span> &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;标签&#x27;</span>) &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;分类&#x27;</span>) &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;作者&#x27;</span>);</span><br><span class="line">                &#125;)</span><br><span class="line">                .<span class="title function_">sort</span>(<span class="function">(<span class="params">a, b</span>) =&gt;</span> b.<span class="property">innerText</span>.<span class="property">length</span> - a.<span class="property">innerText</span>.<span class="property">length</span>)</span><br><span class="line">                .<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">10</span>);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (longestP.<span class="property">length</span> &gt; <span class="number">0</span>) &#123;</span><br><span class="line">                text = longestP.<span class="title function_">map</span>(<span class="function"><span class="params">p</span> =&gt;</span> p.<span class="property">innerText</span>).<span class="title function_">join</span>(<span class="string">&#x27; &#x27;</span>);</span><br><span class="line">                text = text.<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>).<span class="title function_">trim</span>();</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">return</span> text;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">callSummaryAPI</span>(<span class="params">text, retry = <span class="number">0</span></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (abortController) abortController.<span class="title function_">abort</span>();</span><br><span class="line">        abortController = <span class="keyword">new</span> <span class="title class_">AbortController</span>();</span><br><span class="line">        <span class="keyword">const</span> timeoutId = <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> abortController.<span class="title function_">abort</span>(), <span class="number">120000</span>);</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="variable constant_">CONFIG</span>.<span class="property">apiUrl</span>, &#123;</span><br><span class="line">                <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>,</span><br><span class="line">                <span class="attr">headers</span>: &#123; </span><br><span class="line">                    <span class="string">&#x27;Content-Type&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span></span><br><span class="line">                &#125;,</span><br><span class="line">                <span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(&#123;</span><br><span class="line">                    <span class="attr">text</span>: text.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">4000</span>)</span><br><span class="line">                &#125;),</span><br><span class="line">                <span class="attr">signal</span>: abortController.<span class="property">signal</span></span><br><span class="line">            &#125;);</span><br><span class="line">            </span><br><span class="line">            <span class="built_in">clearTimeout</span>(timeoutId);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!response.<span class="property">ok</span>) &#123;</span><br><span class="line">                <span class="keyword">const</span> errorText = <span class="keyword">await</span> response.<span class="title function_">text</span>();</span><br><span class="line">                <span class="keyword">throw</span> <span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">`HTTP <span class="subst">$&#123;response.status&#125;</span>: <span class="subst">$&#123;errorText&#125;</span>`</span>);</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">            <span class="keyword">let</span> summary = data.<span class="property">summary</span> || <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!summary) <span class="keyword">throw</span> <span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">&#x27;Empty response&#x27;</span>);</span><br><span class="line">            </span><br><span class="line">            summary = summary</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*(摘要|总结|概括)[：:]\s*/i</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*[&quot;&#x27;]?|[&quot;&#x27;]?\s*$/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/\*\*/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*[-*]\s+/gm</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^#&#123;1,6&#125;\s+/gm</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/这篇文章主要(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/本文主要(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/该文章(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/此文章(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/综上所述[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/总之[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/总而言之[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">trim</span>();</span><br><span class="line"></span><br><span class="line">            <span class="keyword">if</span> (!<span class="regexp">/^本文(主要)?介绍了/</span>.<span class="title function_">test</span>(summary)) &#123;</span><br><span class="line">                summary = <span class="string">&#x27;本文介绍了&#x27;</span> + summary.<span class="title function_">replace</span>(<span class="regexp">/^[，。！？\s]+/</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">            &#125;</span><br><span class="line"></span><br><span class="line">            <span class="keyword">const</span> sentences = summary.<span class="title function_">split</span>(<span class="regexp">/[。！？.!?]/</span>).<span class="title function_">filter</span>(<span class="function"><span class="params">s</span> =&gt;</span> s.<span class="title function_">trim</span>());</span><br><span class="line">            <span class="keyword">if</span> (sentences.<span class="property">length</span> &gt; <span class="number">3</span>) &#123;</span><br><span class="line">                summary = sentences.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">3</span>).<span class="title function_">join</span>(<span class="string">&#x27;。&#x27;</span>) + <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (summary.<span class="property">length</span> &gt; <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span>) &#123;</span><br><span class="line">                summary = summary.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span>);</span><br><span class="line">                <span class="keyword">const</span> lastPunct = <span class="title class_">Math</span>.<span class="title function_">max</span>(</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;。&#x27;</span>),</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;！&#x27;</span>),</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;？&#x27;</span>)</span><br><span class="line">                );</span><br><span class="line">                <span class="keyword">if</span> (lastPunct &gt; <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span> * <span class="number">0.7</span>) &#123;</span><br><span class="line">                    summary = summary.<span class="title function_">slice</span>(<span class="number">0</span>, lastPunct + <span class="number">1</span>);</span><br><span class="line">                &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">                    summary = summary.<span class="title function_">replace</span>(<span class="regexp">/[^。！？]*$/</span>, <span class="string">&#x27;&#x27;</span>) + <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">                &#125;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!<span class="regexp">/[。！？.!?]$/</span>.<span class="title function_">test</span>(summary)) &#123;</span><br><span class="line">                summary += <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">return</span> summary;</span><br><span class="line">            </span><br><span class="line">        &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">            <span class="built_in">clearTimeout</span>(timeoutId);</span><br><span class="line">            <span class="keyword">if</span> (retry &lt; <span class="variable constant_">CONFIG</span>.<span class="property">retryCount</span>) &#123;</span><br><span class="line">                <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">`[AI Summary] Retrying... (<span class="subst">$&#123;retry + <span class="number">1</span>&#125;</span>/<span class="subst">$&#123;CONFIG.retryCount&#125;</span>)`</span>);</span><br><span class="line">                <span class="keyword">await</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function"><span class="params">r</span> =&gt;</span> <span class="built_in">setTimeout</span>(r, <span class="number">2000</span>));</span><br><span class="line">                <span class="keyword">return</span> <span class="title function_">callSummaryAPI</span>(text, retry + <span class="number">1</span>);</span><br><span class="line">            &#125;</span><br><span class="line">            <span class="keyword">throw</span> err;</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">renderContainer</span>(<span class="params">targetContainer, isLoading = <span class="literal">false</span>, content = <span class="string">&#x27;&#x27;</span></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (!targetContainer) <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">const</span> loadingHtml = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;span class=&quot;ai-loading-inline&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;svg class=&quot;ai-loading-svg&quot; width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 50 50&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;circle cx=&quot;25&quot; cy=&quot;25&quot; r=&quot;20&quot; fill=&quot;none&quot; stroke=&quot;currentColor&quot; stroke-width=&quot;3&quot; </span></span><br><span class="line"><span class="string">                        stroke-linecap=&quot;round&quot; stroke-dasharray=&quot;80&quot; stroke-dashoffset=&quot;60&quot;&gt;</span></span><br><span class="line"><span class="string">                        &lt;animateTransform attributeName=&quot;transform&quot; type=&quot;rotate&quot; from=&quot;0 25 25&quot; to=&quot;360 25 25&quot; dur=&quot;1s&quot; repeatCount=&quot;indefinite&quot;/&gt;</span></span><br><span class="line"><span class="string">                    &lt;/circle&gt;</span></span><br><span class="line"><span class="string">                &lt;/svg&gt;</span></span><br><span class="line"><span class="string">                &lt;span class=&quot;ai-loading-dots&quot;&gt;AI 正在分析文章&lt;/span&gt;</span></span><br><span class="line"><span class="string">            &lt;/span&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">        </span><br><span class="line">        targetContainer.<span class="property">innerHTML</span> = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;div class=&quot;ai-content&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-header&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;i class=&quot;eucalyptus icon-bilibili&quot;&gt;&lt;/i&gt;&lt;span class=&quot;ai-titles&quot;&gt;AI 摘要&lt;/span&gt;&lt;span class=&quot;ai-badge&quot;&gt;AGENT&lt;/span&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-text-box&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p id=&quot;ai-summary-text&quot;&gt;<span class="subst">$&#123;isLoading ? loadingHtml : escapeHtml(content)&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            &lt;/div&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">        <span class="keyword">return</span> targetContainer.<span class="title function_">querySelector</span>(<span class="string">&#x27;#ai-summary-text&#x27;</span>);</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">renderError</span>(<span class="params">targetContainer, message</span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (!targetContainer) <span class="keyword">return</span>;</span><br><span class="line">        targetContainer.<span class="property">innerHTML</span> = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;div class=&quot;ai-content&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-header&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;i class=&quot;eucalyptus icon-bilibili&quot;&gt;&lt;/i&gt;&lt;span class=&quot;ai-titles&quot;&gt;AI 摘要&lt;/span&gt;&lt;span class=&quot;ai-badge&quot;&gt;AGENT&lt;/span&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-text-box&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p style=&quot;color: #999;&quot;&gt;<span class="subst">$&#123;escapeHtml(message)&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            &lt;/div&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">bootstrap</span>(<span class="params"></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (abortController) &#123;</span><br><span class="line">            abortController.<span class="title function_">abort</span>();</span><br><span class="line">            abortController = <span class="literal">null</span>;</span><br><span class="line">        &#125;</span><br><span class="line">        <span class="keyword">if</span> (typeWriterTimer) &#123; </span><br><span class="line">            <span class="built_in">clearInterval</span>(typeWriterTimer); </span><br><span class="line">            typeWriterTimer = <span class="literal">null</span>; </span><br><span class="line">        &#125;</span><br><span class="line">        isProcessing = <span class="literal">false</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">if</span> (<span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;ai-summary&#x27;</span>)) &#123;</span><br><span class="line">            <span class="built_in">setTimeout</span>(initAISummary, <span class="number">100</span>);</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">initAISummary</span>(<span class="params"></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (isProcessing) <span class="keyword">return</span>;</span><br><span class="line">        isProcessing = <span class="literal">true</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> container = <span class="keyword">await</span> <span class="title function_">waitForElement</span>(<span class="string">&#x27;#ai-summary&#x27;</span>);</span><br><span class="line">            <span class="keyword">const</span> text = <span class="title function_">getArticleText</span>();</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!text || text.<span class="property">length</span> &lt; <span class="number">50</span>) &#123;</span><br><span class="line">                <span class="title function_">renderContainer</span>(container, <span class="literal">false</span>, <span class="string">&#x27;本文篇幅较短，暂无详细摘要。&#x27;</span>);</span><br><span class="line">                isProcessing = <span class="literal">false</span>;</span><br><span class="line">                <span class="keyword">return</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="title function_">renderContainer</span>(container, <span class="literal">true</span>);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">let</span> summary;</span><br><span class="line">            <span class="keyword">try</span> &#123; </span><br><span class="line">                summary = <span class="keyword">await</span> <span class="title function_">callSummaryAPI</span>(text); </span><br><span class="line">            &#125;</span><br><span class="line">            <span class="keyword">catch</span> (err) &#123; </span><br><span class="line">                <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[AI Summary] API failed:&#x27;</span>, err); </span><br><span class="line">                <span class="title function_">renderError</span>(container, <span class="string">`AI 服务暂时不可用：<span class="subst">$&#123;err.message&#125;</span>`</span>); </span><br><span class="line">                isProcessing = <span class="literal">false</span>; </span><br><span class="line">                <span class="keyword">return</span>; </span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> textEl = <span class="title function_">renderContainer</span>(container, <span class="literal">false</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">            <span class="keyword">await</span> <span class="title function_">typeWriter</span>(textEl, summary);</span><br><span class="line">            </span><br><span class="line">        &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">            <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[AI Summary] Init Error:&#x27;</span>, err);</span><br><span class="line">            <span class="keyword">const</span> container = <span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;ai-summary&#x27;</span>);</span><br><span class="line">            <span class="keyword">if</span> (container) <span class="title function_">renderError</span>(container, <span class="string">&#x27;初始化失败&#x27;</span>);</span><br><span class="line">        &#125; <span class="keyword">finally</span> &#123; </span><br><span class="line">            isProcessing = <span class="literal">false</span>; </span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> (<span class="variable language_">document</span>.<span class="property">readyState</span> === <span class="string">&#x27;loading&#x27;</span>) &#123;</span><br><span class="line">        <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;DOMContentLoaded&#x27;</span>, bootstrap);</span><br><span class="line">    &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">        <span class="title function_">bootstrap</span>();</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pjax:complete&#x27;</span>, bootstrap);</span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;turbolinks:load&#x27;</span>, bootstrap);</span><br><span class="line"></span><br><span class="line">    <span class="keyword">let</span> lastUrl = location.<span class="property">pathname</span>;</span><br><span class="line">    <span class="keyword">new</span> <span class="title class_">MutationObserver</span>(<span class="function">() =&gt;</span> &#123; </span><br><span class="line">        <span class="keyword">const</span> url = location.<span class="property">pathname</span>; </span><br><span class="line">        <span class="keyword">if</span> (url !== lastUrl) &#123; </span><br><span class="line">            lastUrl = url; </span><br><span class="line">            <span class="title function_">bootstrap</span>(); </span><br><span class="line">        &#125; </span><br><span class="line">    &#125;).<span class="title function_">observe</span>(<span class="variable language_">document</span>, &#123; <span class="attr">subtree</span>: <span class="literal">true</span>, <span class="attr">childList</span>: <span class="literal">true</span> &#125;);</span><br><span class="line"></span><br><span class="line">&#125;)();</span><br></pre></td></tr></table></figure><h3 id="重新构建Hexo"><a href="#重新构建Hexo" class="headerlink" title="重新构建Hexo"></a>重新构建Hexo</h3><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">hexo clean</span><br><span class="line">hexo generate</span><br></pre></td></tr></table></figure><h3 id="查看Redis缓存"><a href="#查看Redis缓存" class="headerlink" title="查看Redis缓存"></a>查看Redis缓存</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#查看所有 AI 摘要缓存</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli KEYS <span class="string">&quot;ai:summary:*&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#查看缓存数量</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli DBSIZE</span><br><span class="line"></span><br><span class="line"><span class="comment">#查看某个缓存内容</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli GET <span class="string">&quot;ai:summary:具体的hash值&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#查看缓存剩余过期时间（秒）</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli TTL <span class="string">&quot;ai:summary:具体的hash值&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#查看缓存详细信息（长度、类型等）</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli DEBUG OBJECT <span class="string">&quot;ai:summary:具体的hash值&quot;</span></span><br></pre></td></tr></table></figure><h3 id="删除Redis缓存"><a href="#删除Redis缓存" class="headerlink" title="删除Redis缓存"></a>删除Redis缓存</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#删除单个缓存</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli DEL <span class="string">&quot;ai:summary:具体的hash值&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#批量删除所有 AI 摘要缓存</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli EVAL <span class="string">&quot;return redis.call(&#x27;del&#x27;, unpack(redis.call(&#x27;keys&#x27;, &#x27;ai:summary:*&#x27;)))&quot;</span> 0</span><br><span class="line"></span><br><span class="line"><span class="comment">#删除所有缓存（慎用）</span></span><br><span class="line">docker <span class="built_in">exec</span> redis-ai redis-cli FLUSHDB</span><br></pre></td></tr></table></figure><h3 id="进入Redis-CLI交互式模式"><a href="#进入Redis-CLI交互式模式" class="headerlink" title="进入Redis CLI交互式模式"></a>进入Redis CLI交互式模式</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">exec</span> -it redis-ai redis-cli</span><br><span class="line"></span><br><span class="line"><span class="comment"># 然后可以执行各种命令</span></span><br><span class="line">127.0.0.1:6379&gt; KEYS ai:summary:*</span><br><span class="line">127.0.0.1:6379&gt; GET ai:summary:5bc22daf2d8a9026</span><br><span class="line">127.0.0.1:6379&gt; TTL ai:summary:5bc22daf2d8a9026</span><br><span class="line">127.0.0.1:6379&gt; DEL ai:summary:5bc22daf2d8a9026</span><br><span class="line">127.0.0.1:6379&gt; <span class="built_in">exit</span></span><br></pre></td></tr></table></figure><h2 id="效果对比"><a href="#效果对比" class="headerlink" title="效果对比"></a>效果对比</h2><table><thead><tr><th>指标</th><th>Ollama (3b)</th><th>新方案 (日日新)</th></tr></thead><tbody><tr><td>生成速度</td><td>5-10 秒</td><td>1-3 秒</td></tr><tr><td>摘要质量</td><td>一般</td><td>较好</td></tr><tr><td>资源占用</td><td>500MB-1GB 内存</td><td>20MB 内存</td></tr><tr><td>并发能力</td><td>单用户</td><td>多用户共享缓存</td></tr><tr><td>成本</td><td>免费</td><td>按 API 调用计费</td></tr></tbody></table><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><p>从 Ollama 到云端代理，解决了三个核心问题：</p><ol><li><strong>质量</strong>：云端大模型效果优于本地小模型</li><li><strong>速度</strong>：缓存命中时直接返回，无需等待生成</li><li><strong>成本</strong>：缓存减少重复调用，降低 API 费用</li></ol><p>对于 2C4G 的服务器，这套方案更轻量、更稳定。如果服务器资源充足，Ollama 仍是免费的不错选择。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Ollama/">Ollama</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/06/01/45224c9f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Ollama访问限制</title>
      <link>https://blog.eucalyptus.cc/2026/05/21/58b7f64e/</link>
      <guid>https://blog.eucalyptus.cc/2026/05/21/58b7f64e/</guid>
      <pubDate>Thu, 21 May 2026 15:43:41 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;Nginx-Basic-Auth认证&quot;&gt;&lt;a href=&quot;#Nginx-Basic-Auth认证&quot; class=&quot;headerlink&quot; title=&quot;Nginx+Basic Auth认证&quot;&gt;&lt;/a&gt;Nginx+Basic Auth认证&lt;/h2&gt;&lt;h3</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="Nginx-Basic-Auth认证"><a href="#Nginx-Basic-Auth认证" class="headerlink" title="Nginx+Basic Auth认证"></a>Nginx+Basic Auth认证</h2><h3 id="生成密码文件"><a href="#生成密码文件" class="headerlink" title="生成密码文件"></a>生成密码文件</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 安装工具</span></span><br><span class="line">yum install httpd-tools -y</span><br><span class="line"></span><br><span class="line"><span class="comment"># 创建密码文件（用户名 admin）</span></span><br><span class="line">htpasswd -c /www/server/pass/ollama.pass admin</span><br><span class="line"></span><br><span class="line"><span class="comment"># 输入密码，比如 MySecurePass123</span></span><br></pre></td></tr></table></figure><h3 id="修改nginx配置文件"><a href="#修改nginx配置文件" class="headerlink" title="修改nginx配置文件"></a>修改nginx配置文件</h3><p>在之前配置ollama的反向代理的nginx配置文件中设置Basic Auth认证实现访问限制</p><figure class="highlight nginx"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#BASICAUTH START</span></span><br><span class="line"><span class="attribute">auth_basic</span> <span class="string">&quot;Ollama API Auth&quot;</span>;</span><br><span class="line"><span class="attribute">auth_basic_user_file</span> /www/server/pass/ollama.pass;</span><br><span class="line"><span class="comment">#BASICAUTH END</span></span><br></pre></td></tr></table></figure><h3 id="重启nginx"><a href="#重启nginx" class="headerlink" title="重启nginx"></a>重启nginx</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">nginx -t</span><br><span class="line">systemctl reload nginx</span><br></pre></td></tr></table></figure><h3 id="测试"><a href="#测试" class="headerlink" title="测试"></a>测试</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 不带认证 → 401 Unauthorized</span></span><br><span class="line">curl https://ollama.eucalyptus.cc/api/tags</span><br><span class="line"></span><br><span class="line"><span class="comment"># 带认证 → 成功</span></span><br><span class="line">curl https://admin:MySecurePass123@ollama.eucalyptus.cc/api/tags</span><br></pre></td></tr></table></figure><h2 id="后端Node-js代理"><a href="#后端Node-js代理" class="headerlink" title="后端Node.js代理"></a>后端Node.js代理</h2><p>但是这样的话再前端调用的时候需要把账号和密码写到前端js中，还是有泄露的风险，这时我们可以使用后端代理。前端 JS 直接调用后端代理，后端代理内部带 Basic Auth 访问 Ollama。</p><p>架构图</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">用户浏览器 → Hexo 博客页面 → JS 调用 https://ollama.eucalyptus.cc</span><br><span class="line">                                              ↓</span><br><span class="line">                                    ECS Nginx (无认证，或简单限流)</span><br><span class="line">                                              ↓</span><br><span class="line">                                    Node.js 代理 (localhost:3001)</span><br><span class="line">                                              ↓</span><br><span class="line">                                    带 Basic Auth 调 Ollama (127.0.0.1:11434)</span><br><span class="line">                                              ↓</span><br><span class="line">                                    frps → frp隧道 → 本地虚拟机 Ollama</span><br></pre></td></tr></table></figure><h3 id="部署步骤"><a href="#部署步骤" class="headerlink" title="部署步骤"></a>部署步骤</h3><h4 id="ecs安装node-js"><a href="#ecs安装node-js" class="headerlink" title="ecs安装node.js"></a>ecs安装node.js</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># CentOS 7</span></span><br><span class="line">curl -fsSL https://rpm.nodesource.com/setup_18.x | bash -</span><br><span class="line">yum install -y nodejs</span><br><span class="line"></span><br><span class="line"><span class="comment"># 验证</span></span><br><span class="line">node -v</span><br><span class="line">npm -v</span><br></pre></td></tr></table></figure><h4 id="创建代理服务"><a href="#创建代理服务" class="headerlink" title="创建代理服务"></a>创建代理服务</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> -p /opt/ollama-proxy</span><br><span class="line"><span class="built_in">cd</span> /opt/ollama-proxy</span><br><span class="line">npm init -y</span><br><span class="line">npm install express node-fetch@2</span><br></pre></td></tr></table></figure><h4 id="创建proxy-js"><a href="#创建proxy-js" class="headerlink" title="创建proxy.js"></a>创建proxy.js</h4><p>记得配置CORS，不然会出现跨域访问的问题</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">const</span> express = <span class="built_in">require</span>(<span class="string">&#x27;express&#x27;</span>);</span><br><span class="line"><span class="keyword">const</span> fetch = <span class="built_in">require</span>(<span class="string">&#x27;node-fetch&#x27;</span>);</span><br><span class="line"></span><br><span class="line"><span class="keyword">const</span> app = <span class="title function_">express</span>();</span><br><span class="line"></span><br><span class="line"><span class="comment">// ========== CORS 中间件 ==========</span></span><br><span class="line">app.<span class="title function_">use</span>(<span class="function">(<span class="params">req, res, next</span>) =&gt;</span> &#123;</span><br><span class="line">    res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Origin&#x27;</span>, <span class="string">&#x27;https://blog.eucalyptus.cc&#x27;</span>);</span><br><span class="line">    res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Methods&#x27;</span>, <span class="string">&#x27;GET, POST, OPTIONS&#x27;</span>);</span><br><span class="line">    res.<span class="title function_">header</span>(<span class="string">&#x27;Access-Control-Allow-Headers&#x27;</span>, <span class="string">&#x27;Origin, X-Requested-With, Content-Type, Accept, Authorization&#x27;</span>);</span><br><span class="line">    </span><br><span class="line">    <span class="keyword">if</span> (req.<span class="property">method</span> === <span class="string">&#x27;OPTIONS&#x27;</span>) &#123;</span><br><span class="line">        <span class="keyword">return</span> res.<span class="title function_">sendStatus</span>(<span class="number">204</span>);</span><br><span class="line">    &#125;</span><br><span class="line">    <span class="title function_">next</span>();</span><br><span class="line">&#125;);</span><br><span class="line"><span class="comment">// =================================</span></span><br><span class="line"></span><br><span class="line">app.<span class="title function_">use</span>(express.<span class="title function_">json</span>(&#123; <span class="attr">limit</span>: <span class="string">&#x27;10mb&#x27;</span> &#125;));</span><br><span class="line"></span><br><span class="line"><span class="comment">// Ollama 配置</span></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">OLLAMA_HOST</span> = <span class="string">&#x27;http://127.0.0.1:11434&#x27;</span>;</span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">AUTH_USER</span> = <span class="string">&#x27;admin&#x27;</span>;</span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">AUTH_PASS</span> = <span class="string">&#x27;MySecurePass123&#x27;</span>;</span><br><span class="line"></span><br><span class="line"><span class="comment">// 生成 Basic Auth 头</span></span><br><span class="line"><span class="keyword">const</span> basicAuth = <span class="string">&#x27;Basic &#x27;</span> + <span class="title class_">Buffer</span>.<span class="title function_">from</span>(<span class="string">`<span class="subst">$&#123;AUTH_USER&#125;</span>:<span class="subst">$&#123;AUTH_PASS&#125;</span>`</span>).<span class="title function_">toString</span>(<span class="string">&#x27;base64&#x27;</span>);</span><br><span class="line"></span><br><span class="line"><span class="comment">// 健康检查</span></span><br><span class="line">app.<span class="title function_">get</span>(<span class="string">&#x27;/health&#x27;</span>, <span class="function">(<span class="params">req, res</span>) =&gt;</span> &#123;</span><br><span class="line">    res.<span class="title function_">json</span>(&#123; <span class="attr">status</span>: <span class="string">&#x27;ok&#x27;</span> &#125;);</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="comment">// 代理 /api/generate</span></span><br><span class="line">app.<span class="title function_">post</span>(<span class="string">&#x27;/api/generate&#x27;</span>, <span class="title function_">async</span> (req, res) =&gt; &#123;</span><br><span class="line">    <span class="keyword">try</span> &#123;</span><br><span class="line">        <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="string">`<span class="subst">$&#123;OLLAMA_HOST&#125;</span>/api/generate`</span>, &#123;</span><br><span class="line">            <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>,</span><br><span class="line">            <span class="attr">headers</span>: &#123;</span><br><span class="line">                <span class="string">&#x27;Content-Type&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span>,</span><br><span class="line">                <span class="string">&#x27;Authorization&#x27;</span>: basicAuth</span><br><span class="line">            &#125;,</span><br><span class="line">            <span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(req.<span class="property">body</span>),</span><br><span class="line">            <span class="attr">timeout</span>: <span class="number">60000</span></span><br><span class="line">        &#125;);</span><br><span class="line"></span><br><span class="line">        <span class="keyword">if</span> (!response.<span class="property">ok</span>) &#123;</span><br><span class="line">            <span class="keyword">const</span> text = <span class="keyword">await</span> response.<span class="title function_">text</span>();</span><br><span class="line">            <span class="keyword">return</span> res.<span class="title function_">status</span>(response.<span class="property">status</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: text &#125;);</span><br><span class="line">        &#125;</span><br><span class="line"></span><br><span class="line">        <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">        res.<span class="title function_">json</span>(data);</span><br><span class="line"></span><br><span class="line">    &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">        <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;Proxy error:&#x27;</span>, err);</span><br><span class="line">        res.<span class="title function_">status</span>(<span class="number">500</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: err.<span class="property">message</span> &#125;);</span><br><span class="line">    &#125;</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="comment">// 代理 /api/tags</span></span><br><span class="line">app.<span class="title function_">get</span>(<span class="string">&#x27;/api/tags&#x27;</span>, <span class="title function_">async</span> (req, res) =&gt; &#123;</span><br><span class="line">    <span class="keyword">try</span> &#123;</span><br><span class="line">        <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="string">`<span class="subst">$&#123;OLLAMA_HOST&#125;</span>/api/tags`</span>, &#123;</span><br><span class="line">            <span class="attr">headers</span>: &#123; <span class="string">&#x27;Authorization&#x27;</span>: basicAuth &#125;</span><br><span class="line">        &#125;);</span><br><span class="line">        <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">        res.<span class="title function_">json</span>(data);</span><br><span class="line">    &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">        res.<span class="title function_">status</span>(<span class="number">500</span>).<span class="title function_">json</span>(&#123; <span class="attr">error</span>: err.<span class="property">message</span> &#125;);</span><br><span class="line">    &#125;</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="keyword">const</span> <span class="variable constant_">PORT</span> = <span class="number">3001</span>;</span><br><span class="line">app.<span class="title function_">listen</span>(<span class="variable constant_">PORT</span>, <span class="string">&#x27;127.0.0.1&#x27;</span>, <span class="function">() =&gt;</span> &#123;</span><br><span class="line">    <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">`Ollama proxy running on http://127.0.0.1:<span class="subst">$&#123;PORT&#125;</span>`</span>);</span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><h4 id="用PM2守护进程"><a href="#用PM2守护进程" class="headerlink" title="用PM2守护进程"></a>用PM2守护进程</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line">npm install -g pm2</span><br><span class="line"></span><br><span class="line"><span class="comment"># 启动</span></span><br><span class="line">pm2 start proxy.js --name ollama-proxy</span><br><span class="line"></span><br><span class="line"><span class="comment"># 开机自启</span></span><br><span class="line">pm2 startup</span><br><span class="line">pm2 save</span><br><span class="line"></span><br><span class="line"><span class="comment"># 查看状态</span></span><br><span class="line">pm2 status</span><br><span class="line">pm2 logs ollama-proxy</span><br></pre></td></tr></table></figure><h4 id="修改ollama反向代理nginx的配置文件"><a href="#修改ollama反向代理nginx的配置文件" class="headerlink" title="修改ollama反向代理nginx的配置文件"></a>修改ollama反向代理nginx的配置文件</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#PROXY-CONF-START</span></span><br><span class="line">location ^~ / &#123;</span><br><span class="line">  proxy_pass http://127.0.0.1:3001;   <span class="comment"># 改成代理端口</span></span><br><span class="line">  proxy_set_header Host <span class="variable">$http_host</span>;</span><br><span class="line">  proxy_set_header X-Real-IP <span class="variable">$remote_addr</span>;</span><br><span class="line">  proxy_set_header X-Real-Port <span class="variable">$remote_port</span>;</span><br><span class="line">  proxy_set_header X-Forwarded-For <span class="variable">$proxy_add_x_forwarded_for</span>;</span><br><span class="line">  proxy_set_header X-Forwarded-Proto <span class="variable">$scheme</span>;</span><br><span class="line">  proxy_set_header X-Forwarded-Host <span class="variable">$host</span>;</span><br><span class="line">  proxy_set_header X-Forwarded-Port <span class="variable">$server_port</span>;</span><br><span class="line">  proxy_set_header REMOTE-HOST <span class="variable">$remote_addr</span>;</span><br><span class="line">  </span><br><span class="line">  proxy_connect_timeout 60s;</span><br><span class="line">  proxy_send_timeout 600s;</span><br><span class="line">  proxy_read_timeout 600s;</span><br><span class="line">  proxy_http_version 1.1;</span><br><span class="line">  proxy_set_header Upgrade <span class="variable">$http_upgrade</span>;</span><br><span class="line">  proxy_set_header Connection <span class="variable">$connection_upgrade</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="comment">#PROXY-CONF-END</span></span><br></pre></td></tr></table></figure><h4 id="重启nginx-1"><a href="#重启nginx-1" class="headerlink" title="重启nginx"></a>重启nginx</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">nginx -t</span><br><span class="line">systemctl reload nginx</span><br></pre></td></tr></table></figure><h4 id="测试验证"><a href="#测试验证" class="headerlink" title="测试验证"></a>测试验证</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 测试代理健康</span></span><br><span class="line">curl http://127.0.0.1:3001/health</span><br><span class="line"></span><br><span class="line"><span class="comment"># 测试生成</span></span><br><span class="line">curl -X POST http://127.0.0.1:3001/api/generate \</span><br><span class="line">  -H <span class="string">&quot;Content-Type: application/json&quot;</span> \</span><br><span class="line">  -d <span class="string">&#x27;&#123;&quot;model&quot;:&quot;qwen2.5:0.5b&quot;,&quot;prompt&quot;:&quot;你好&quot;,&quot;stream&quot;:false&#125;&#x27;</span></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Ollama/">Ollama</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/05/21/58b7f64e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>frp 配置反向代理实现 内网穿透</title>
      <link>https://blog.eucalyptus.cc/2026/05/20/21482fcd/</link>
      <guid>https://blog.eucalyptus.cc/2026/05/20/21482fcd/</guid>
      <pubDate>Wed, 20 May 2026 14:30:10 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是内网穿透&quot;&gt;&lt;a href=&quot;#什么是内网穿透&quot; class=&quot;headerlink&quot; title=&quot;什么是内网穿透&quot;&gt;&lt;/a&gt;什么是内网穿透&lt;/h2&gt;&lt;h3 id=&quot;核心原理&quot;&gt;&lt;a href=&quot;#核心原理&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是内网穿透"><a href="#什么是内网穿透" class="headerlink" title="什么是内网穿透"></a>什么是内网穿透</h2><h3 id="核心原理"><a href="#核心原理" class="headerlink" title="核心原理"></a>核心原理</h3><p>你的本地设备（如家里的电脑、公司的服务器）通常通过路由器&#x2F;NAT设备上网，只拥有（如192.168.x.x）。外网无法直接访问这些内网IP，因为：</p><ul><li>路由器有防火墙功能，会拦截外部主动发起的连接</li><li>内网IP在公网上不可路由</li></ul><p><strong>内网穿透就是打通这个”墙”，让外网流量能够到达内网设备。</strong></p><h3 id="常见实现方式"><a href="#常见实现方式" class="headerlink" title="常见实现方式"></a>常见实现方式</h3><table><thead><tr><th>方式</th><th>原理</th><th>例子</th></tr></thead><tbody><tr><td><strong>反向代理</strong></td><td>内网主动连接公网服务器，建立隧道，流量通过隧道转发</td><td>FRP、Ngrok、花生壳</td></tr><tr><td><strong>VPN&#x2F;虚拟组网</strong></td><td>组建虚拟局域网，让外网设备获得内网身份</td><td>WireGuard、ZeroTier、Tailscale</td></tr><tr><td><strong>DDNS+端口映射</strong></td><td>如果有公网IP，直接做路由器端口转发</td><td>路由器设置虚拟服务器</td></tr><tr><td><strong>云服务器中转</strong></td><td>数据先发到云服务器，再转发到内网</td><td>自建转发服务</td></tr></tbody></table><h2 id="配置方案"><a href="#配置方案" class="headerlink" title="配置方案"></a>配置方案</h2><p>本文章需要配置的是 实现内网穿透：</p><ul><li><strong>frps</strong>（服务端）：部署在有公网IP的ECS上（如阿里云）</li><li><strong>frpc</strong>（客户端）：部署在本地CentOS虚拟机中</li><li><strong>流程</strong>：本地frpc主动连接ECS上的frps → 建立加密隧道 → 外网用户访问ECS的端口 → frps通过隧道转发给frpc → 到达本地服务</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">[外网用户] → [ECS公网IP:7500] → [frps] ═══隧道═══ [frpc] → [本地Ollama:11434]</span><br></pre></td></tr></table></figure><h3 id="下载并安装frps（ECS-本地Centos虚拟机）"><a href="#下载并安装frps（ECS-本地Centos虚拟机）" class="headerlink" title="下载并安装frps（ECS+本地Centos虚拟机）"></a>下载并安装frps（ECS+本地Centos虚拟机）</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#下载</span></span><br><span class="line">wget https://github.com/fatedier/frp/releases/download/v0.61.0/frp_0.61.0_linux_amd64.tar.gz</span><br><span class="line"><span class="comment">#解压</span></span><br><span class="line">tar -zxvf frp_0.61.0_linux_amd64.tar.gz</span><br><span class="line"><span class="built_in">cd</span> frp_0.61.0_linux_amd64</span><br></pre></td></tr></table></figure><h3 id="编写服务端配置文件frps-toml（ECS）"><a href="#编写服务端配置文件frps-toml（ECS）" class="headerlink" title="编写服务端配置文件frps.toml（ECS）"></a>编写服务端配置文件frps.toml（ECS）</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> &gt; frpc.toml &lt;&lt; <span class="string">&#x27;EOF&#x27;</span></span><br><span class="line"><span class="comment"># 服务端监听地址（0.0.0.0表示监听所有网卡）</span></span><br><span class="line">bindAddr = <span class="string">&quot;0.0.0.0&quot;</span></span><br><span class="line"><span class="comment"># 服务端监听端口（frpc会连接这个端口）</span></span><br><span class="line">bindPort = 7000</span><br><span class="line"></span><br><span class="line"><span class="comment"># 身份验证（必须设置，防止被他人滥用）</span></span><br><span class="line">auth.method = <span class="string">&quot;token&quot;</span></span><br><span class="line">auth.token = <span class="string">&quot;your_secure_token_here&quot;</span>  <span class="comment"># 改成复杂密码</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># Web 管理面板（可选，用于查看连接状态）</span></span><br><span class="line">webServer.addr = <span class="string">&quot;0.0.0.0&quot;</span></span><br><span class="line">webServer.port = 7500</span><br><span class="line">webServer.user = <span class="string">&quot;admin&quot;</span></span><br><span class="line">webServer.password = <span class="string">&quot;admin123&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 允许代理的端口范围（根据你的服务调整）</span></span><br><span class="line">allowPorts = [</span><br><span class="line">  &#123; start = 6000, end = 7000 &#125;</span><br><span class="line">]</span><br><span class="line"></span><br><span class="line">EOF</span><br></pre></td></tr></table></figure><p>auth.token可以使用openssl生成</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 生成32位随机字符串</span></span><br><span class="line">openssl rand -<span class="built_in">base64</span> 32</span><br><span class="line"></span><br><span class="line"><span class="comment"># 示例输出：</span></span><br><span class="line"><span class="comment"># W8vX2kLmN9pQr4StUv3WxYz5AbCdEfGhIjKlMnOpQr=</span></span><br></pre></td></tr></table></figure><h3 id="放开ecs上安全组和防火墙的相应端口"><a href="#放开ecs上安全组和防火墙的相应端口" class="headerlink" title="放开ecs上安全组和防火墙的相应端口"></a>放开ecs上安全组和防火墙的相应端口</h3><h4 id="安全组"><a href="#安全组" class="headerlink" title="安全组"></a>安全组</h4><table><thead><tr><th>端口</th><th>用途</th><th>授权对象</th></tr></thead><tbody><tr><td>7000</td><td>frp服务端通信端口</td><td>0.0.0.0&#x2F;0</td></tr><tr><td>7500</td><td>Web管理面板（可选）</td><td>0.0.0.0</td></tr><tr><td>6000-7000</td><td>代理端口范围</td><td>0.0.0.0&#x2F;0</td></tr></tbody></table><h4 id="防火墙"><a href="#防火墙" class="headerlink" title="防火墙"></a>防火墙</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> firewall-cmd --permanent --add-port=7000/tcp</span><br><span class="line"><span class="built_in">sudo</span> firewall-cmd --permanent --add-port=7500/tcp</span><br><span class="line"><span class="built_in">sudo</span> firewall-cmd --permanent --add-port=6000-7000/tcp</span><br><span class="line"><span class="built_in">sudo</span> firewall-cmd --reload</span><br></pre></td></tr></table></figure><h3 id="启动fprs"><a href="#启动fprs" class="headerlink" title="启动fprs"></a>启动fprs</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 前台启动（测试用）</span></span><br><span class="line">./frps -c ./frps.toml</span><br><span class="line"></span><br><span class="line"><span class="comment"># 后台启动（生产用）</span></span><br><span class="line"><span class="built_in">nohup</span> ./frps -c ./frps.toml &gt; frps.log 2&gt;&amp;1 &amp;</span><br><span class="line"></span><br><span class="line"><span class="comment"># 查看日志</span></span><br><span class="line"><span class="built_in">tail</span> -f frps.log</span><br></pre></td></tr></table></figure><h3 id="编写客户端配置文件frpc-toml（本地Centos虚拟机）"><a href="#编写客户端配置文件frpc-toml（本地Centos虚拟机）" class="headerlink" title="编写客户端配置文件frpc.toml（本地Centos虚拟机）"></a>编写客户端配置文件frpc.toml（本地Centos虚拟机）</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> &gt; frps.toml &lt;&lt; <span class="string">&#x27;EOF&#x27;</span></span><br><span class="line"><span class="comment"># 服务端地址（ECS的公网IP）</span></span><br><span class="line">serverAddr = <span class="string">&quot;x.x.x.x&quot;</span>  <span class="comment"># 你的ECS公网IP</span></span><br><span class="line">serverPort = 7000</span><br><span class="line"></span><br><span class="line"><span class="comment"># 身份验证（必须与服务端一致）</span></span><br><span class="line">auth.method = <span class="string">&quot;token&quot;</span></span><br><span class="line">auth.token = <span class="string">&quot;your_secure_token_here&quot;</span>  <span class="comment"># 必须和服务端相同</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 给这个客户端起个名字</span></span><br><span class="line">user = <span class="string">&quot;local-ollama&quot;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 代理配置：将本地Ollama暴露到公网</span></span><br><span class="line">[[proxies]]</span><br><span class="line">name = <span class="string">&quot;ollama&quot;</span></span><br><span class="line"><span class="built_in">type</span> = <span class="string">&quot;tcp&quot;</span></span><br><span class="line">localIP = <span class="string">&quot;127.0.0.1&quot;</span></span><br><span class="line">localPort = 11434          <span class="comment"># 本地Ollama端口</span></span><br><span class="line">remotePort = 6000          <span class="comment"># 公网访问端口（ECS的6000端口）</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 可选：再暴露SSH</span></span><br><span class="line">[[proxies]]</span><br><span class="line">name = <span class="string">&quot;ssh&quot;</span></span><br><span class="line"><span class="built_in">type</span> = <span class="string">&quot;tcp&quot;</span></span><br><span class="line">localIP = <span class="string">&quot;127.0.0.1&quot;</span></span><br><span class="line">localPort = 22</span><br><span class="line">remotePort = 6001</span><br><span class="line"></span><br><span class="line">EOF</span><br></pre></td></tr></table></figure><h3 id="启动frpc"><a href="#启动frpc" class="headerlink" title="启动frpc"></a>启动frpc</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 前台启动（测试）</span></span><br><span class="line">./frpc -c ./frpc.toml</span><br><span class="line"></span><br><span class="line"><span class="comment"># 后台启动</span></span><br><span class="line"><span class="built_in">nohup</span> ./frpc -c ./frpc.toml &gt; frpc.log 2&gt;&amp;1 &amp;</span><br><span class="line"></span><br><span class="line"><span class="comment"># 查看日志</span></span><br><span class="line"><span class="built_in">tail</span> -f frpc.log</span><br></pre></td></tr></table></figure><h2 id="测试（ollama）"><a href="#测试（ollama）" class="headerlink" title="测试（ollama）"></a>测试（ollama）</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 直接访问本地Ollama</span></span><br><span class="line">curl http://127.0.0.1:11434/api/tags  </span><br><span class="line"></span><br><span class="line"><span class="comment"># 通过FRP访问</span></span><br><span class="line">curl http://ECS公网IP:6000/api/tags  </span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/%E5%86%85%E7%BD%91%E7%A9%BF%E9%80%8F/">内网穿透</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/frp/">frp</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/05/20/21482fcd/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>使用 Ollama 为 Hexo 博客部署 AI 文章摘要</title>
      <link>https://blog.eucalyptus.cc/2026/05/16/83caee76/</link>
      <guid>https://blog.eucalyptus.cc/2026/05/16/83caee76/</guid>
      <pubDate>Sat, 16 May 2026 09:43:12 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h1 id=&quot;使用-Ollama-为-Hexo-博客部署-AI-文章摘要&quot;&gt;&lt;a href=&quot;#使用-Ollama-为-Hexo-博客部署-AI-文章摘要&quot; class=&quot;headerlink&quot; title=&quot;使用 Ollama 为 Hexo 博客部署 AI</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h1 id="使用-Ollama-为-Hexo-博客部署-AI-文章摘要"><a href="#使用-Ollama-为-Hexo-博客部署-AI-文章摘要" class="headerlink" title="使用 Ollama 为 Hexo 博客部署 AI 文章摘要"></a>使用 Ollama 为 Hexo 博客部署 AI 文章摘要</h1><h2 id="架构概述"><a href="#架构概述" class="headerlink" title="架构概述"></a>架构概述</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">┌─────────────────┐      ┌─────────────────┐      ┌─────────────────┐</span><br><span class="line">│   用户浏览器     │ ──→  │  Hexo 服务器    │ ──→  │  Ollama 服务器  │</span><br><span class="line">│                 │      │  (Nginx 代理)   │      │  (192.168.0.2)│</span><br><span class="line">│  blog.mingliang │      │  192.168.1.2 │      │   :11434        │</span><br><span class="line">│     star.com    │      │                 │      │                 │</span><br><span class="line">└─────────────────┘      └─────────────────┘      └─────────────────┘</span><br><span class="line">        ↑                                              ↑</span><br><span class="line">        └──────────── 仅允许 192.168.1.2 访问 ──────┘</span><br></pre></td></tr></table></figure><hr><h2 id="Ollama-服务端部署"><a href="#Ollama-服务端部署" class="headerlink" title="Ollama 服务端部署"></a>Ollama 服务端部署</h2><h3 id="1-拉起ollama的容器并设置环境变量防止CORS跨域访问"><a href="#1-拉起ollama的容器并设置环境变量防止CORS跨域访问" class="headerlink" title="1. 拉起ollama的容器并设置环境变量防止CORS跨域访问"></a>1. 拉起ollama的容器并设置环境变量防止CORS跨域访问</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">docker run -d \</span><br><span class="line">  -v ollama:/root/.ollama \</span><br><span class="line">  -p 11434:11434 \</span><br><span class="line">  -e OLLAMA_ORIGINS=<span class="string">&quot;https://blog.eucalyptus.cc,https://eucalyptus.cc,http://localhost,https://localhost&quot;</span> \</span><br><span class="line">  -e OLLAMA_HOST=<span class="string">&quot;0.0.0.0:11434&quot;</span> \</span><br><span class="line">  --name ollama \</span><br><span class="line">  ollama/ollama</span><br></pre></td></tr></table></figure><h3 id="2-为ollama下载qwen2-5-0-5b模型"><a href="#2-为ollama下载qwen2-5-0-5b模型" class="headerlink" title="2. 为ollama下载qwen2.5:0.5b模型"></a>2. 为ollama下载qwen2.5:0.5b模型</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">exec</span> ollama ollama pull qwen2.5:0.5b</span><br></pre></td></tr></table></figure><h3 id="3-安全加固：配置防火墙"><a href="#3-安全加固：配置防火墙" class="headerlink" title="3. 安全加固：配置防火墙"></a>3. 安全加固：配置防火墙</h3><p>在阿里云安全组中配置：</p><ul><li>入方向 <code>11434</code> 端口：授权对象 <code>192.168.1.2</code></li><li>删除所有 <code>0.0.0.0/0</code> 访问 11434 的规则</li></ul><hr><h2 id="Hexo-服务器配置反向代理"><a href="#Hexo-服务器配置反向代理" class="headerlink" title="Hexo 服务器配置反向代理"></a>Hexo 服务器配置反向代理</h2><p>在 Hexo 服务器（<code>192.168.1.2</code>）的 Nginx 中配置：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">代理目录：/</span><br><span class="line">目标：url地址 http://192.168.0.2:11434</span><br><span class="line">发送域名：<span class="variable">$http_host</span></span><br></pre></td></tr></table></figure><p><strong>为何需要反向代理？</strong></p><ul><li>浏览器直接请求 Ollama 存在 CORS 限制</li><li>通过同域名代理，前端无跨域问题</li><li>隐藏真实 Ollama IP，增强安全性</li></ul><hr><h2 id="Hexo-主题集成"><a href="#Hexo-主题集成" class="headerlink" title="Hexo 主题集成"></a>Hexo 主题集成</h2><h3 id="1-添加挂载点"><a href="#1-添加挂载点" class="headerlink" title="1. 添加挂载点"></a>1. 添加挂载点</h3><p>编辑 <code>/www/wwwroot/myblog/themes/anzhiyu/layout/post.pug</code>，插入：</p><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">...</span><br><span class="line"></span><br><span class="line">//- AI 摘要区域（由 ai-summary.js 动态渲染）</span><br><span class="line">#ai-summary.anzhiyu-ai-summary</span><br><span class="line"></span><br><span class="line">!=page.content</span><br><span class="line"></span><br><span class="line">...</span><br></pre></td></tr></table></figure><h3 id="2-前端核心代码"><a href="#2-前端核心代码" class="headerlink" title="2. 前端核心代码"></a>2. 前端核心代码</h3><p><code>ai-summary.js</code> —— 纯前端 Ollama 调用，支持打字机效果和本地缓存：</p><ul><li>自动提取文章正文，过滤代码块、图片等干扰内容</li><li>调用 Ollama <code>/api/generate</code> 接口生成摘要</li><li><strong>localStorage 缓存</strong>：同篇文章 7 天内不再重复请求</li><li><strong>打字机效果</strong>：逐字输出，增强交互体验</li><li>适配 PJAX&#x2F;Turbolinks 无刷新页面切换</li></ul><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br><span class="line">252</span><br><span class="line">253</span><br><span class="line">254</span><br><span class="line">255</span><br><span class="line">256</span><br><span class="line">257</span><br><span class="line">258</span><br><span class="line">259</span><br><span class="line">260</span><br><span class="line">261</span><br><span class="line">262</span><br><span class="line">263</span><br><span class="line">264</span><br><span class="line">265</span><br><span class="line">266</span><br><span class="line">267</span><br><span class="line">268</span><br><span class="line">269</span><br><span class="line">270</span><br><span class="line">271</span><br><span class="line">272</span><br><span class="line">273</span><br><span class="line">274</span><br><span class="line">275</span><br><span class="line">276</span><br><span class="line">277</span><br><span class="line">278</span><br><span class="line">279</span><br><span class="line">280</span><br><span class="line">281</span><br><span class="line">282</span><br><span class="line">283</span><br><span class="line">284</span><br><span class="line">285</span><br><span class="line">286</span><br><span class="line">287</span><br><span class="line">288</span><br><span class="line">289</span><br><span class="line">290</span><br><span class="line">291</span><br><span class="line">292</span><br><span class="line">293</span><br><span class="line">294</span><br><span class="line">295</span><br><span class="line">296</span><br><span class="line">297</span><br><span class="line">298</span><br><span class="line">299</span><br><span class="line">300</span><br><span class="line">301</span><br><span class="line">302</span><br><span class="line">303</span><br><span class="line">304</span><br><span class="line">305</span><br><span class="line">306</span><br><span class="line">307</span><br><span class="line">308</span><br><span class="line">309</span><br><span class="line">310</span><br><span class="line">311</span><br><span class="line">312</span><br><span class="line">313</span><br><span class="line">314</span><br><span class="line">315</span><br><span class="line">316</span><br><span class="line">317</span><br><span class="line">318</span><br><span class="line">319</span><br><span class="line">320</span><br><span class="line">321</span><br><span class="line">322</span><br><span class="line">323</span><br><span class="line">324</span><br><span class="line">325</span><br><span class="line">326</span><br><span class="line">327</span><br><span class="line">328</span><br><span class="line">329</span><br><span class="line">330</span><br><span class="line">331</span><br><span class="line">332</span><br><span class="line">333</span><br><span class="line">334</span><br><span class="line">335</span><br><span class="line">336</span><br><span class="line">337</span><br><span class="line">338</span><br><span class="line">339</span><br><span class="line">340</span><br><span class="line">341</span><br><span class="line">342</span><br><span class="line">343</span><br><span class="line">344</span><br><span class="line">345</span><br><span class="line">346</span><br><span class="line">347</span><br><span class="line">348</span><br><span class="line">349</span><br><span class="line">350</span><br><span class="line">351</span><br><span class="line">352</span><br><span class="line">353</span><br><span class="line">354</span><br><span class="line">355</span><br><span class="line">356</span><br><span class="line">357</span><br><span class="line">358</span><br><span class="line">359</span><br><span class="line">360</span><br><span class="line">361</span><br><span class="line">362</span><br><span class="line">363</span><br><span class="line">364</span><br><span class="line">365</span><br><span class="line">366</span><br><span class="line">367</span><br><span class="line">368</span><br><span class="line">369</span><br><span class="line">370</span><br><span class="line">371</span><br><span class="line">372</span><br><span class="line">373</span><br><span class="line">374</span><br><span class="line">375</span><br><span class="line">376</span><br><span class="line">377</span><br><span class="line">378</span><br><span class="line">379</span><br><span class="line">380</span><br><span class="line">381</span><br><span class="line">382</span><br><span class="line">383</span><br><span class="line">384</span><br><span class="line">385</span><br><span class="line">386</span><br><span class="line">387</span><br><span class="line">388</span><br><span class="line">389</span><br><span class="line">390</span><br><span class="line">391</span><br><span class="line">392</span><br><span class="line">393</span><br><span class="line">394</span><br><span class="line">395</span><br><span class="line">396</span><br><span class="line">397</span><br><span class="line">398</span><br><span class="line">399</span><br><span class="line">400</span><br><span class="line">401</span><br><span class="line">402</span><br><span class="line">403</span><br><span class="line">404</span><br><span class="line">405</span><br><span class="line">406</span><br><span class="line">407</span><br><span class="line">408</span><br><span class="line">409</span><br><span class="line">410</span><br><span class="line">411</span><br><span class="line">412</span><br><span class="line">413</span><br><span class="line">414</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/**</span></span><br><span class="line"><span class="comment"> *  AI 摘要 - Ollama 直连版 </span></span><br><span class="line"><span class="comment"> */</span></span><br><span class="line">(<span class="keyword">function</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="string">&#x27;use strict&#x27;</span>;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> <span class="variable constant_">CONFIG</span> = &#123;</span><br><span class="line">        <span class="attr">apiUrl</span>: <span class="string">&#x27;https://ollama.eucalyptus.cc/api/generate&#x27;</span>,</span><br><span class="line">        <span class="attr">model</span>: <span class="string">&#x27;qwen2.5:3b&#x27;</span>,</span><br><span class="line">        <span class="attr">typeSpeed</span>: <span class="number">35</span>,</span><br><span class="line">        <span class="attr">maxSummaryLength</span>: <span class="number">500</span>,</span><br><span class="line">        <span class="attr">retryCount</span>: <span class="number">1</span></span><br><span class="line">    &#125;;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> <span class="variable constant_">FRONTEND_CACHE_KEY</span> = <span class="string">&#x27;ai_summary_frontend_v7&#x27;</span>;</span><br><span class="line">    <span class="keyword">const</span> <span class="variable constant_">FRONTEND_CACHE_MAX_AGE</span> = <span class="number">7</span> * <span class="number">24</span> * <span class="number">60</span> * <span class="number">60</span> * <span class="number">1000</span>;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">let</span> isProcessing = <span class="literal">false</span>;</span><br><span class="line">    <span class="keyword">let</span> typeWriterTimer = <span class="literal">null</span>;</span><br><span class="line">    <span class="keyword">let</span> abortController = <span class="literal">null</span>;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">waitForElement</span>(<span class="params">selector, timeout = <span class="number">3000</span></span>) &#123;</span><br><span class="line">        <span class="keyword">return</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function">(<span class="params">resolve, reject</span>) =&gt;</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> element = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(selector);</span><br><span class="line">            <span class="keyword">if</span> (element) <span class="keyword">return</span> <span class="title function_">resolve</span>(element);</span><br><span class="line">            <span class="keyword">const</span> observer = <span class="keyword">new</span> <span class="title class_">MutationObserver</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">                <span class="keyword">const</span> el = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(selector);</span><br><span class="line">                <span class="keyword">if</span> (el) &#123; observer.<span class="title function_">disconnect</span>(); <span class="title function_">resolve</span>(el); &#125;</span><br><span class="line">            &#125;);</span><br><span class="line">            observer.<span class="title function_">observe</span>(<span class="variable language_">document</span>.<span class="property">body</span>, &#123; <span class="attr">childList</span>: <span class="literal">true</span>, <span class="attr">subtree</span>: <span class="literal">true</span> &#125;);</span><br><span class="line">            <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> &#123; observer.<span class="title function_">disconnect</span>(); <span class="title function_">reject</span>(<span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">`Timeout waiting for <span class="subst">$&#123;selector&#125;</span>`</span>)); &#125;, timeout);</span><br><span class="line">        &#125;);</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">escapeHtml</span>(<span class="params">text</span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (!text) <span class="keyword">return</span> <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">        <span class="keyword">const</span> div = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&#x27;div&#x27;</span>);</span><br><span class="line">        div.<span class="property">textContent</span> = text;</span><br><span class="line">        <span class="keyword">return</span> div.<span class="property">innerHTML</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">typeWriter</span>(<span class="params">element, text, speed = CONFIG.typeSpeed</span>) &#123;</span><br><span class="line">        <span class="keyword">return</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function">(<span class="params">resolve</span>) =&gt;</span> &#123;</span><br><span class="line">            <span class="keyword">if</span> (typeWriterTimer) &#123; <span class="built_in">clearInterval</span>(typeWriterTimer); typeWriterTimer = <span class="literal">null</span>; &#125;</span><br><span class="line">            <span class="keyword">let</span> index = <span class="number">0</span>;</span><br><span class="line">            element.<span class="property">textContent</span> = <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">            typeWriterTimer = <span class="built_in">setInterval</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">                <span class="keyword">if</span> (index &lt; text.<span class="property">length</span>) &#123; </span><br><span class="line">                    element.<span class="property">textContent</span> += text.<span class="title function_">charAt</span>(index); </span><br><span class="line">                    index++; </span><br><span class="line">                &#125; <span class="keyword">else</span> &#123; </span><br><span class="line">                    <span class="built_in">clearInterval</span>(typeWriterTimer); </span><br><span class="line">                    typeWriterTimer = <span class="literal">null</span>; </span><br><span class="line">                    <span class="title function_">resolve</span>(); </span><br><span class="line">                &#125;</span><br><span class="line">            &#125;, speed);</span><br><span class="line">        &#125;);</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">getFrontendCache</span>(<span class="params">path</span>) &#123;</span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> data = <span class="variable language_">localStorage</span>.<span class="title function_">getItem</span>(<span class="variable constant_">FRONTEND_CACHE_KEY</span>);</span><br><span class="line">            <span class="keyword">if</span> (!data) <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">            <span class="keyword">const</span> cache = <span class="title class_">JSON</span>.<span class="title function_">parse</span>(data);</span><br><span class="line">            <span class="keyword">const</span> item = cache[path];</span><br><span class="line">            <span class="keyword">if</span> (!item) <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">            <span class="keyword">if</span> (<span class="title class_">Date</span>.<span class="title function_">now</span>() - item.<span class="property">time</span> &gt; <span class="variable constant_">FRONTEND_CACHE_MAX_AGE</span>) &#123;</span><br><span class="line">                <span class="keyword">delete</span> cache[path];</span><br><span class="line">                <span class="variable language_">localStorage</span>.<span class="title function_">setItem</span>(<span class="variable constant_">FRONTEND_CACHE_KEY</span>, <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(cache));</span><br><span class="line">                <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            <span class="keyword">return</span> item.<span class="property">summary</span>;</span><br><span class="line">        &#125; <span class="keyword">catch</span> &#123;</span><br><span class="line">            <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">setFrontendCache</span>(<span class="params">path, summary</span>) &#123;</span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> data = <span class="variable language_">localStorage</span>.<span class="title function_">getItem</span>(<span class="variable constant_">FRONTEND_CACHE_KEY</span>);</span><br><span class="line">            <span class="keyword">const</span> cache = data ? <span class="title class_">JSON</span>.<span class="title function_">parse</span>(data) : &#123;&#125;;</span><br><span class="line">            cache[path] = &#123; summary, <span class="attr">time</span>: <span class="title class_">Date</span>.<span class="title function_">now</span>() &#125;;</span><br><span class="line">            <span class="variable language_">localStorage</span>.<span class="title function_">setItem</span>(<span class="variable constant_">FRONTEND_CACHE_KEY</span>, <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(cache));</span><br><span class="line">        &#125; <span class="keyword">catch</span> &#123;&#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">getArticleText</span>(<span class="params"></span>) &#123;</span><br><span class="line">        <span class="keyword">const</span> selectors = [</span><br><span class="line">            <span class="string">&#x27;#article-container .post-content&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;#article-container #post&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-content&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;article .entry-content&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;#post-content&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.article-content&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.markdown-body&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;#content article&#x27;</span></span><br><span class="line">        ];</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">let</span> article = <span class="literal">null</span>;</span><br><span class="line">        <span class="keyword">for</span> (<span class="keyword">const</span> sel <span class="keyword">of</span> selectors) &#123;</span><br><span class="line">            article = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(sel);</span><br><span class="line">            <span class="keyword">if</span> (article &amp;&amp; article.<span class="property">innerText</span>.<span class="title function_">trim</span>().<span class="property">length</span> &gt; <span class="number">200</span>) <span class="keyword">break</span>;</span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">if</span> (!article) &#123; </span><br><span class="line">            <span class="variable language_">console</span>.<span class="title function_">warn</span>(<span class="string">&#x27;[AI Summary] Article content not found.&#x27;</span>); </span><br><span class="line">            <span class="keyword">return</span> <span class="string">&#x27;&#x27;</span>; </span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">const</span> clone = article.<span class="title function_">cloneNode</span>(<span class="literal">true</span>);</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">const</span> removeSelectors = [</span><br><span class="line">            <span class="string">&#x27;h1&#x27;</span>, <span class="string">&#x27;h2.post-title&#x27;</span>, <span class="string">&#x27;.post-title&#x27;</span>, <span class="string">&#x27;.page-title&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-meta&#x27;</span>, <span class="string">&#x27;.meta&#x27;</span>, <span class="string">&#x27;.entry-meta&#x27;</span>, <span class="string">&#x27;.article-meta&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-date&#x27;</span>, <span class="string">&#x27;.post-time&#x27;</span>, <span class="string">&#x27;.published&#x27;</span>, <span class="string">&#x27;.updated&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.author&#x27;</span>, <span class="string">&#x27;.byline&#x27;</span>, <span class="string">&#x27;.post-author&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-tags&#x27;</span>, <span class="string">&#x27;.tags&#x27;</span>, <span class="string">&#x27;.tag-cloud&#x27;</span>, <span class="string">&#x27;.post-categories&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.categories&#x27;</span>, <span class="string">&#x27;.post-category&#x27;</span>, <span class="string">&#x27;.article-tags&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;nav&#x27;</span>, <span class="string">&#x27;.nav&#x27;</span>, <span class="string">&#x27;.breadcrumb&#x27;</span>, <span class="string">&#x27;.crumbs&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;aside&#x27;</span>, <span class="string">&#x27;.sidebar&#x27;</span>, <span class="string">&#x27;.widget&#x27;</span>, <span class="string">&#x27;.toc&#x27;</span>, <span class="string">&#x27;#toc&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;header&#x27;</span>, <span class="string">&#x27;.post-header&#x27;</span>, <span class="string">&#x27;.entry-header&#x27;</span>, <span class="string">&#x27;.article-header&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;footer&#x27;</span>, <span class="string">&#x27;.post-footer&#x27;</span>, <span class="string">&#x27;.entry-footer&#x27;</span>, <span class="string">&#x27;.article-footer&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;#post-comment&#x27;</span>, <span class="string">&#x27;.comments&#x27;</span>, <span class="string">&#x27;.comment-area&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.share&#x27;</span>, <span class="string">&#x27;.social-share&#x27;</span>, <span class="string">&#x27;.reward&#x27;</span>, <span class="string">&#x27;.donate&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.post-copyright&#x27;</span>, <span class="string">&#x27;.copyright&#x27;</span>, <span class="string">&#x27;.license&#x27;</span>, <span class="string">&#x27;.declaration&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.relatedPosts&#x27;</span>, <span class="string">&#x27;.related-posts&#x27;</span>, <span class="string">&#x27;.related&#x27;</span>, <span class="string">&#x27;.recommend&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.anzhiyu-ai-summary&#x27;</span>, <span class="string">&#x27;#ai-summary&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;script&#x27;</span>, <span class="string">&#x27;style&#x27;</span>, <span class="string">&#x27;pre&#x27;</span>, <span class="string">&#x27;code&#x27;</span>, <span class="string">&#x27;table&#x27;</span>, </span><br><span class="line">            <span class="string">&#x27;img&#x27;</span>, <span class="string">&#x27;figure&#x27;</span>, <span class="string">&#x27;figcaption&#x27;</span>, <span class="string">&#x27;svg&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;blockquote&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.ads-wrap&#x27;</span>, <span class="string">&#x27;.ad&#x27;</span>, <span class="string">&#x27;.advertisement&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.highlight&#x27;</span>, <span class="string">&#x27;.mermaid&#x27;</span>, <span class="string">&#x27;.katex&#x27;</span>, <span class="string">&#x27;.mathjax&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.pagination&#x27;</span>, <span class="string">&#x27;.pager&#x27;</span>, <span class="string">&#x27;.page-nav&#x27;</span>,</span><br><span class="line">            <span class="string">&#x27;.notice&#x27;</span>, <span class="string">&#x27;.alert&#x27;</span>, <span class="string">&#x27;.tips&#x27;</span>, <span class="string">&#x27;.warning&#x27;</span></span><br><span class="line">        ];</span><br><span class="line">        </span><br><span class="line">        removeSelectors.<span class="title function_">forEach</span>(<span class="function"><span class="params">sel</span> =&gt;</span> &#123;</span><br><span class="line">            clone.<span class="title function_">querySelectorAll</span>(sel).<span class="title function_">forEach</span>(<span class="function"><span class="params">el</span> =&gt;</span> el.<span class="title function_">remove</span>());</span><br><span class="line">        &#125;);</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">let</span> text = clone.<span class="property">innerText</span></span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/[*#\-_`~\[\]()&gt;|]/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\b[A-Z]&#123;5,&#125;\b/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\d&#123;4&#125;[年/-]\d&#123;1,2&#125;[月/-]\d&#123;1,2&#125;[日]?/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/[^\u4e00-\u9fa5a-zA-Z0-9，。！？；：&quot;&quot;&#x27;&#x27;（）【】《》.,;:!?&#x27;&quot;()\[\]&lt;&gt;、\-—\n]/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>)</span><br><span class="line">            .<span class="title function_">trim</span>();</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">if</span> (text.<span class="property">length</span> &lt; <span class="number">100</span>) &#123;</span><br><span class="line">            <span class="variable language_">console</span>.<span class="title function_">warn</span>(<span class="string">&#x27;[AI Summary] Content too short, trying fallback...&#x27;</span>);</span><br><span class="line">            <span class="keyword">const</span> paragraphs = <span class="title class_">Array</span>.<span class="title function_">from</span>(<span class="variable language_">document</span>.<span class="title function_">querySelectorAll</span>(<span class="string">&#x27;p&#x27;</span>));</span><br><span class="line">            <span class="keyword">const</span> longestP = paragraphs</span><br><span class="line">                .<span class="title function_">filter</span>(<span class="function"><span class="params">p</span> =&gt;</span> &#123;</span><br><span class="line">                    <span class="keyword">const</span> t = p.<span class="property">innerText</span>.<span class="title function_">trim</span>();</span><br><span class="line">                    <span class="keyword">return</span> t.<span class="property">length</span> &gt; <span class="number">50</span> &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;标签&#x27;</span>) &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;分类&#x27;</span>) &amp;&amp; !t.<span class="title function_">includes</span>(<span class="string">&#x27;作者&#x27;</span>);</span><br><span class="line">                &#125;)</span><br><span class="line">                .<span class="title function_">sort</span>(<span class="function">(<span class="params">a, b</span>) =&gt;</span> b.<span class="property">innerText</span>.<span class="property">length</span> - a.<span class="property">innerText</span>.<span class="property">length</span>)</span><br><span class="line">                .<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">10</span>);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (longestP.<span class="property">length</span> &gt; <span class="number">0</span>) &#123;</span><br><span class="line">                text = longestP.<span class="title function_">map</span>(<span class="function"><span class="params">p</span> =&gt;</span> p.<span class="property">innerText</span>).<span class="title function_">join</span>(<span class="string">&#x27; &#x27;</span>);</span><br><span class="line">                text = text.<span class="title function_">replace</span>(<span class="regexp">/\s+/g</span>, <span class="string">&#x27; &#x27;</span>).<span class="title function_">trim</span>();</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">return</span> text;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">callSummaryAPI</span>(<span class="params">text, retry = <span class="number">0</span></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (abortController) abortController.<span class="title function_">abort</span>();</span><br><span class="line">        abortController = <span class="keyword">new</span> <span class="title class_">AbortController</span>();</span><br><span class="line">        <span class="keyword">const</span> timeoutId = <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> abortController.<span class="title function_">abort</span>(), <span class="number">120000</span>);</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="comment">// ========== 优化后的提示词 ==========</span></span><br><span class="line">            <span class="keyword">const</span> prompt = <span class="string">`你是一个专业的博客文章摘要生成助手。</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">请阅读以下文章，用一段话概括其核心内容。</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">要求：</span></span><br><span class="line"><span class="string">- 自然流畅，像人写的读后感</span></span><br><span class="line"><span class="string">- 开头用&quot;本文介绍了&quot;或&quot;本文主要介绍了&quot;</span></span><br><span class="line"><span class="string">- 不要分点，不要列条目</span></span><br><span class="line"><span class="string">- 不要复述标题、作者、日期、标签等元信息</span></span><br><span class="line"><span class="string">- 不要输出 markdown 格式（如 **、-、# 等）</span></span><br><span class="line"><span class="string">- 不要包含&quot;摘要：&quot;&quot;总结：&quot;&quot;综上所述&quot;等前缀</span></span><br><span class="line"><span class="string">- 直接输出正文</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">文章内容：</span></span><br><span class="line"><span class="string">&quot;&quot;&quot;</span></span><br><span class="line"><span class="string"><span class="subst">$&#123;text.slice(<span class="number">0</span>, <span class="number">4000</span>)&#125;</span></span></span><br><span class="line"><span class="string">&quot;&quot;&quot;</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">概括：`</span>;</span><br><span class="line">            <span class="comment">// ====================================</span></span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> response = <span class="keyword">await</span> <span class="title function_">fetch</span>(<span class="variable constant_">CONFIG</span>.<span class="property">apiUrl</span>, &#123;</span><br><span class="line">                <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>,</span><br><span class="line">                <span class="attr">headers</span>: &#123; <span class="string">&#x27;Content-Type&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span> &#125;,</span><br><span class="line">                <span class="attr">body</span>: <span class="title class_">JSON</span>.<span class="title function_">stringify</span>(&#123;</span><br><span class="line">                    <span class="attr">model</span>: <span class="variable constant_">CONFIG</span>.<span class="property">model</span>,</span><br><span class="line">                    <span class="attr">prompt</span>: prompt,</span><br><span class="line">                    <span class="attr">stream</span>: <span class="literal">false</span>,</span><br><span class="line">                    <span class="attr">options</span>: &#123;</span><br><span class="line">                        <span class="attr">temperature</span>: <span class="number">0.3</span>,</span><br><span class="line">                        <span class="attr">num_predict</span>: <span class="number">800</span></span><br><span class="line">                    &#125;</span><br><span class="line">                &#125;),</span><br><span class="line">                <span class="attr">signal</span>: abortController.<span class="property">signal</span></span><br><span class="line">            &#125;);</span><br><span class="line">            <span class="built_in">clearTimeout</span>(timeoutId);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!response.<span class="property">ok</span>) &#123;</span><br><span class="line">                <span class="keyword">const</span> errorText = <span class="keyword">await</span> response.<span class="title function_">text</span>();</span><br><span class="line">                <span class="keyword">throw</span> <span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">`HTTP <span class="subst">$&#123;response.status&#125;</span>: <span class="subst">$&#123;errorText&#125;</span>`</span>);</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> data = <span class="keyword">await</span> response.<span class="title function_">json</span>();</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">let</span> summary = data.<span class="property">response</span> || <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">            <span class="keyword">if</span> (!summary) <span class="keyword">throw</span> <span class="keyword">new</span> <span class="title class_">Error</span>(<span class="string">&#x27;Empty response&#x27;</span>);</span><br><span class="line">            </span><br><span class="line">            <span class="comment">// ========== 清理输出 ==========</span></span><br><span class="line">            summary = summary</span><br><span class="line">                <span class="comment">// 去掉纯前缀词（不要删&quot;本文介绍了&quot;）</span></span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*(摘要|总结|概括)[：:]\s*/i</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*[&quot;&#x27;]?|[&quot;&#x27;]?\s*$/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                <span class="comment">// 去掉 markdown</span></span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/\*\*/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^\s*[-*]\s+/gm</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/^#&#123;1,6&#125;\s+/gm</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                <span class="comment">// 统一&quot;本文介绍了&quot;格式</span></span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/这篇文章主要(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/本文主要(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/该文章(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/此文章(介绍|讲述|讨论|分析)了/g</span>, <span class="string">&#x27;本文介绍了&#x27;</span>)</span><br><span class="line">                <span class="comment">// 去掉常见废话</span></span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/综上所述[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/总之[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">replace</span>(<span class="regexp">/总而言之[，。]/g</span>, <span class="string">&#x27;&#x27;</span>)</span><br><span class="line">                .<span class="title function_">trim</span>();</span><br><span class="line"></span><br><span class="line">            <span class="comment">// 确保以&quot;本文介绍了&quot;开头</span></span><br><span class="line">            <span class="keyword">if</span> (!<span class="regexp">/^本文(主要)?介绍了/</span>.<span class="title function_">test</span>(summary)) &#123;</span><br><span class="line">                summary = <span class="string">&#x27;本文介绍了&#x27;</span> + summary.<span class="title function_">replace</span>(<span class="regexp">/^[，。！？\s]+/</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">            &#125;</span><br><span class="line"></span><br><span class="line">            <span class="comment">// 句子太多时取前3句，避免太长</span></span><br><span class="line">            <span class="keyword">const</span> sentences = summary.<span class="title function_">split</span>(<span class="regexp">/[。！？.!?]/</span>).<span class="title function_">filter</span>(<span class="function"><span class="params">s</span> =&gt;</span> s.<span class="title function_">trim</span>());</span><br><span class="line">            <span class="keyword">if</span> (sentences.<span class="property">length</span> &gt; <span class="number">3</span>) &#123;</span><br><span class="line">                summary = sentences.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="number">3</span>).<span class="title function_">join</span>(<span class="string">&#x27;。&#x27;</span>) + <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="comment">// 显示长度截断（语义完整）</span></span><br><span class="line">            <span class="keyword">if</span> (summary.<span class="property">length</span> &gt; <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span>) &#123;</span><br><span class="line">                summary = summary.<span class="title function_">slice</span>(<span class="number">0</span>, <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span>);</span><br><span class="line">                <span class="keyword">const</span> lastPunct = <span class="title class_">Math</span>.<span class="title function_">max</span>(</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;。&#x27;</span>),</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;！&#x27;</span>),</span><br><span class="line">                    summary.<span class="title function_">lastIndexOf</span>(<span class="string">&#x27;？&#x27;</span>)</span><br><span class="line">                );</span><br><span class="line">                <span class="keyword">if</span> (lastPunct &gt; <span class="variable constant_">CONFIG</span>.<span class="property">maxSummaryLength</span> * <span class="number">0.7</span>) &#123;</span><br><span class="line">                    summary = summary.<span class="title function_">slice</span>(<span class="number">0</span>, lastPunct + <span class="number">1</span>);</span><br><span class="line">                &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">                    summary = summary.<span class="title function_">replace</span>(<span class="regexp">/[^。！？]*$/</span>, <span class="string">&#x27;&#x27;</span>) + <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">                &#125;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!<span class="regexp">/[。！？.!?]$/</span>.<span class="title function_">test</span>(summary)) &#123;</span><br><span class="line">                summary += <span class="string">&#x27;。&#x27;</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">return</span> summary;</span><br><span class="line">            </span><br><span class="line">        &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">            <span class="built_in">clearTimeout</span>(timeoutId);</span><br><span class="line">            <span class="keyword">if</span> (retry &lt; <span class="variable constant_">CONFIG</span>.<span class="property">retryCount</span>) &#123;</span><br><span class="line">                <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">`[AI Summary] Retrying... (<span class="subst">$&#123;retry + <span class="number">1</span>&#125;</span>/<span class="subst">$&#123;CONFIG.retryCount&#125;</span>)`</span>);</span><br><span class="line">                <span class="keyword">await</span> <span class="keyword">new</span> <span class="title class_">Promise</span>(<span class="function"><span class="params">r</span> =&gt;</span> <span class="built_in">setTimeout</span>(r, <span class="number">2000</span>));</span><br><span class="line">                <span class="keyword">return</span> <span class="title function_">callSummaryAPI</span>(text, retry + <span class="number">1</span>);</span><br><span class="line">            &#125;</span><br><span class="line">            <span class="keyword">throw</span> err;</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">renderContainer</span>(<span class="params">targetContainer, isLoading = <span class="literal">false</span>, content = <span class="string">&#x27;&#x27;</span></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (!targetContainer) <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">const</span> loadingHtml = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;span class=&quot;ai-loading-inline&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;svg class=&quot;ai-loading-svg&quot; width=&quot;16&quot; height=&quot;16&quot; viewBox=&quot;0 0 50 50&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;circle cx=&quot;25&quot; cy=&quot;25&quot; r=&quot;20&quot; fill=&quot;none&quot; stroke=&quot;currentColor&quot; stroke-width=&quot;3&quot; </span></span><br><span class="line"><span class="string">                        stroke-linecap=&quot;round&quot; stroke-dasharray=&quot;80&quot; stroke-dashoffset=&quot;60&quot;&gt;</span></span><br><span class="line"><span class="string">                        &lt;animateTransform attributeName=&quot;transform&quot; type=&quot;rotate&quot; from=&quot;0 25 25&quot; to=&quot;360 25 25&quot; dur=&quot;1s&quot; repeatCount=&quot;indefinite&quot;/&gt;</span></span><br><span class="line"><span class="string">                    &lt;/circle&gt;</span></span><br><span class="line"><span class="string">                &lt;/svg&gt;</span></span><br><span class="line"><span class="string">                &lt;span class=&quot;ai-loading-dots&quot;&gt;AI 正在分析文章&lt;/span&gt;</span></span><br><span class="line"><span class="string">            &lt;/span&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">        </span><br><span class="line">        targetContainer.<span class="property">innerHTML</span> = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;div class=&quot;ai-content&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-header&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;i class=&quot;eucalyptus icon-bilibili&quot;&gt;&lt;/i&gt;&lt;span class=&quot;ai-titles&quot;&gt;AI 摘要&lt;/span&gt;&lt;span class=&quot;ai-badge&quot;&gt;AGENT&lt;/span&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-text-box&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p id=&quot;ai-summary-text&quot;&gt;<span class="subst">$&#123;isLoading ? loadingHtml : escapeHtml(content)&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            &lt;/div&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">        <span class="keyword">return</span> targetContainer.<span class="title function_">querySelector</span>(<span class="string">&#x27;#ai-summary-text&#x27;</span>);</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">renderError</span>(<span class="params">targetContainer, message</span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (!targetContainer) <span class="keyword">return</span>;</span><br><span class="line">        targetContainer.<span class="property">innerHTML</span> = <span class="string">`</span></span><br><span class="line"><span class="string">            &lt;div class=&quot;ai-content&quot;&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-header&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;i class=&quot;eucalyptus icon-bilibili&quot;&gt;&lt;/i&gt;&lt;span class=&quot;ai-titles&quot;&gt;AI 摘要&lt;/span&gt;&lt;span class=&quot;ai-badge&quot;&gt;AGENT&lt;/span&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;ai-text-box&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p style=&quot;color: #999;&quot;&gt;<span class="subst">$&#123;escapeHtml(message)&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            &lt;/div&gt;</span></span><br><span class="line"><span class="string">        `</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">function</span> <span class="title function_">bootstrap</span>(<span class="params"></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (abortController) &#123;</span><br><span class="line">            abortController.<span class="title function_">abort</span>();</span><br><span class="line">            abortController = <span class="literal">null</span>;</span><br><span class="line">        &#125;</span><br><span class="line">        <span class="keyword">if</span> (typeWriterTimer) &#123; </span><br><span class="line">            <span class="built_in">clearInterval</span>(typeWriterTimer); </span><br><span class="line">            typeWriterTimer = <span class="literal">null</span>; </span><br><span class="line">        &#125;</span><br><span class="line">        isProcessing = <span class="literal">false</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">if</span> (<span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;ai-summary&#x27;</span>)) &#123;</span><br><span class="line">            <span class="built_in">setTimeout</span>(initAISummary, <span class="number">100</span>);</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">async</span> <span class="keyword">function</span> <span class="title function_">initAISummary</span>(<span class="params"></span>) &#123;</span><br><span class="line">        <span class="keyword">if</span> (isProcessing) <span class="keyword">return</span>;</span><br><span class="line">        isProcessing = <span class="literal">true</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">try</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> container = <span class="keyword">await</span> <span class="title function_">waitForElement</span>(<span class="string">&#x27;#ai-summary&#x27;</span>);</span><br><span class="line">            <span class="keyword">const</span> text = <span class="title function_">getArticleText</span>();</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (!text || text.<span class="property">length</span> &lt; <span class="number">50</span>) &#123;</span><br><span class="line">                <span class="title function_">renderContainer</span>(container, <span class="literal">false</span>, <span class="string">&#x27;本文篇幅较短，暂无详细摘要。&#x27;</span>);</span><br><span class="line">                isProcessing = <span class="literal">false</span>;</span><br><span class="line">                <span class="keyword">return</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> cacheKey = <span class="variable language_">window</span>.<span class="property">location</span>.<span class="property">pathname</span>;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> frontendCached = <span class="title function_">getFrontendCache</span>(cacheKey);</span><br><span class="line">            <span class="keyword">if</span> (frontendCached) &#123;</span><br><span class="line">                <span class="keyword">const</span> textEl = <span class="title function_">renderContainer</span>(container, <span class="literal">false</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">                <span class="keyword">await</span> <span class="title function_">typeWriter</span>(textEl, frontendCached);</span><br><span class="line">                isProcessing = <span class="literal">false</span>;</span><br><span class="line">                <span class="keyword">return</span>;</span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="title function_">renderContainer</span>(container, <span class="literal">true</span>);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">let</span> summary;</span><br><span class="line">            <span class="keyword">try</span> &#123; </span><br><span class="line">                summary = <span class="keyword">await</span> <span class="title function_">callSummaryAPI</span>(text); </span><br><span class="line">            &#125;</span><br><span class="line">            <span class="keyword">catch</span> (err) &#123; </span><br><span class="line">                <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[AI Summary] API failed:&#x27;</span>, err); </span><br><span class="line">                <span class="title function_">renderError</span>(container, <span class="string">`AI 服务暂时不可用：<span class="subst">$&#123;err.message&#125;</span>`</span>); </span><br><span class="line">                isProcessing = <span class="literal">false</span>; </span><br><span class="line">                <span class="keyword">return</span>; </span><br><span class="line">            &#125;</span><br><span class="line">            </span><br><span class="line">            <span class="title function_">setFrontendCache</span>(cacheKey, summary);</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> textEl = <span class="title function_">renderContainer</span>(container, <span class="literal">false</span>, <span class="string">&#x27;&#x27;</span>);</span><br><span class="line">            <span class="keyword">await</span> <span class="title function_">typeWriter</span>(textEl, summary);</span><br><span class="line">            </span><br><span class="line">        &#125; <span class="keyword">catch</span> (err) &#123;</span><br><span class="line">            <span class="variable language_">console</span>.<span class="title function_">error</span>(<span class="string">&#x27;[AI Summary] Init Error:&#x27;</span>, err);</span><br><span class="line">            <span class="keyword">const</span> container = <span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;ai-summary&#x27;</span>);</span><br><span class="line">            <span class="keyword">if</span> (container) <span class="title function_">renderError</span>(container, <span class="string">&#x27;初始化失败&#x27;</span>);</span><br><span class="line">        &#125; <span class="keyword">finally</span> &#123; </span><br><span class="line">            isProcessing = <span class="literal">false</span>; </span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> (<span class="variable language_">document</span>.<span class="property">readyState</span> === <span class="string">&#x27;loading&#x27;</span>) &#123;</span><br><span class="line">        <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;DOMContentLoaded&#x27;</span>, bootstrap);</span><br><span class="line">    &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">        <span class="title function_">bootstrap</span>();</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pjax:complete&#x27;</span>, bootstrap);</span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;turbolinks:load&#x27;</span>, bootstrap);</span><br><span class="line"></span><br><span class="line">    <span class="keyword">let</span> lastUrl = location.<span class="property">pathname</span>;</span><br><span class="line">    <span class="keyword">new</span> <span class="title class_">MutationObserver</span>(<span class="function">() =&gt;</span> &#123; </span><br><span class="line">        <span class="keyword">const</span> url = location.<span class="property">pathname</span>; </span><br><span class="line">        <span class="keyword">if</span> (url !== lastUrl) &#123; </span><br><span class="line">            lastUrl = url; </span><br><span class="line">            <span class="title function_">bootstrap</span>(); </span><br><span class="line">        &#125; </span><br><span class="line">    &#125;).<span class="title function_">observe</span>(<span class="variable language_">document</span>, &#123; <span class="attr">subtree</span>: <span class="literal">true</span>, <span class="attr">childList</span>: <span class="literal">true</span> &#125;);</span><br><span class="line"></span><br><span class="line">&#125;)();</span><br></pre></td></tr></table></figure><p><code>ai-summary.css</code> —— 固定配色方案，支持明暗模式切换：</p><ul><li>白天模式：浅灰背景 + 白色正文框</li><li>暗色模式：深色背景 + 深色正文框</li><li>机器人图标 + 状态指示器（绿色呼吸灯）</li><li>移动端自适应</li></ul><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/* ============================================</span></span><br><span class="line"><span class="comment">   AI 摘要样式 - 固定配色方案</span></span><br><span class="line"><span class="comment">   ============================================ */</span></span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 白天模式 ========== */</span></span><br><span class="line"><span class="selector-class">.anzhiyu-ai-summary</span> &#123;</span><br><span class="line">  <span class="attribute">position</span>: relative;</span><br><span class="line">  <span class="attribute">margin</span>: <span class="number">20px</span> <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">12px</span>;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#f5f5f7</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#1d1d1f</span>;</span><br><span class="line">  <span class="attribute">overflow</span>: hidden;</span><br><span class="line">  <span class="attribute">font-family</span>: -apple-system, BlinkMacSystemFont, <span class="string">&quot;Segoe UI&quot;</span>, Roboto, <span class="string">&quot;Helvetica Neue&quot;</span>, Arial, sans-serif;</span><br><span class="line">  <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">4px</span> <span class="number">12px</span> <span class="built_in">rgba</span>(<span class="number">0</span>, <span class="number">0</span>, <span class="number">0</span>, <span class="number">0.06</span>);</span><br><span class="line">  <span class="attribute">border</span>: <span class="number">1px</span> solid <span class="number">#e8e8ed</span>;</span><br><span class="line">  <span class="attribute">transition</span>: all <span class="number">0.3s</span> ease;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.anzhiyu-ai-summary</span><span class="selector-pseudo">:hover</span> &#123;</span><br><span class="line">  <span class="attribute">transform</span>: <span class="built_in">translateY</span>(-<span class="number">2px</span>);</span><br><span class="line">  <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">8px</span> <span class="number">24px</span> <span class="built_in">rgba</span>(<span class="number">0</span>, <span class="number">0</span>, <span class="number">0</span>, <span class="number">0.1</span>);</span><br><span class="line">  <span class="attribute">border-color</span>: <span class="number">#d2d2d7</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 内容区域 */</span></span><br><span class="line"><span class="selector-class">.ai-content</span> &#123;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">20px</span> <span class="number">24px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 头部区域 */</span></span><br><span class="line"><span class="selector-class">.ai-header</span> &#123;</span><br><span class="line">  <span class="attribute">display</span>: flex;</span><br><span class="line">  <span class="attribute">align-items</span>: center;</span><br><span class="line">  <span class="attribute">gap</span>: <span class="number">10px</span>;</span><br><span class="line">  <span class="attribute">margin-bottom</span>: <span class="number">16px</span>;</span><br><span class="line">  <span class="attribute">padding-bottom</span>: <span class="number">12px</span>;</span><br><span class="line">  <span class="attribute">border-bottom</span>: <span class="number">1px</span> solid <span class="number">#e8e8ed</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 机器人图标 */</span></span><br><span class="line"><span class="selector-class">.ai-robot</span> &#123;</span><br><span class="line">  <span class="attribute">flex-shrink</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">vertical-align</span>: middle;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 左侧标签 - AI 摘要 */</span></span><br><span class="line"><span class="selector-class">.ai-titles</span> &#123;</span><br><span class="line">  <span class="attribute">flex-shrink</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">16px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>: <span class="number">800</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#1d1d1f</span>;</span><br><span class="line">  <span class="attribute">letter-spacing</span>: <span class="number">0.5px</span>;</span><br><span class="line">  <span class="attribute">white-space</span>: nowrap;</span><br><span class="line">  <span class="attribute">background</span>: none;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">0</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 右侧标签 - Eucalyptus AGENT */</span></span><br><span class="line"><span class="selector-class">.ai-badge</span> &#123;</span><br><span class="line">  <span class="attribute">margin-left</span>: auto;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">12px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>: <span class="number">500</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#86868b</span>;</span><br><span class="line">  <span class="attribute">letter-spacing</span>: <span class="number">0.8px</span>;</span><br><span class="line">  <span class="attribute">white-space</span>: nowrap;</span><br><span class="line">  <span class="attribute">background</span>: none;</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">position</span>: relative;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 小圆点装饰 */</span></span><br><span class="line"><span class="selector-class">.ai-badge</span><span class="selector-pseudo">::before</span> &#123;</span><br><span class="line">  <span class="attribute">content</span>: <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  <span class="attribute">display</span>: inline-block;</span><br><span class="line">  <span class="attribute">width</span>: <span class="number">6px</span>;</span><br><span class="line">  <span class="attribute">height</span>: <span class="number">6px</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">50%</span>;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#34c759</span>;</span><br><span class="line">  <span class="attribute">margin-right</span>: <span class="number">6px</span>;</span><br><span class="line">  <span class="attribute">vertical-align</span>: middle;</span><br><span class="line">  <span class="attribute">animation</span>: pulse <span class="number">2s</span> ease-in-out infinite;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">@keyframes</span> pulse &#123;</span><br><span class="line">  <span class="number">0%</span>, <span class="number">100%</span> &#123; <span class="attribute">opacity</span>: <span class="number">1</span>; <span class="attribute">transform</span>: <span class="built_in">scale</span>(<span class="number">1</span>); &#125;</span><br><span class="line">  <span class="number">50%</span> &#123; <span class="attribute">opacity</span>: <span class="number">0.6</span>; <span class="attribute">transform</span>: <span class="built_in">scale</span>(<span class="number">0.8</span>); &#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 摘要文本框 */</span></span><br><span class="line"><span class="selector-class">.ai-text-box</span> &#123;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">16px</span> <span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#ffffff</span>;</span><br><span class="line">  <span class="attribute">border</span>: <span class="number">1px</span> solid <span class="number">#e8e8ed</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">10px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">15px</span>;</span><br><span class="line">  <span class="attribute">line-height</span>: <span class="number">1.8</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#3a3a3c</span>;</span><br><span class="line">  <span class="attribute">text-align</span>: justify;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-text-box</span> <span class="selector-tag">p</span> &#123;</span><br><span class="line">  <span class="attribute">margin</span>: <span class="number">0</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ============================================</span></span><br><span class="line"><span class="comment">   加载状态</span></span><br><span class="line"><span class="comment">   ============================================ */</span></span><br><span class="line"><span class="selector-class">.ai-loading</span> &#123;</span><br><span class="line">  <span class="attribute">display</span>: flex;</span><br><span class="line">  <span class="attribute">align-items</span>: center;</span><br><span class="line">  <span class="attribute">gap</span>: <span class="number">12px</span>;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">10px</span> <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#1d1d1f</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">14px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-loading</span> <span class="selector-tag">i</span> &#123;</span><br><span class="line">  <span class="attribute">animation</span>: spin <span class="number">1s</span> linear infinite;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">@keyframes</span> spin &#123;</span><br><span class="line">  <span class="selector-tag">from</span> &#123; <span class="attribute">transform</span>: <span class="built_in">rotate</span>(<span class="number">0deg</span>); &#125;</span><br><span class="line">  <span class="selector-tag">to</span> &#123; <span class="attribute">transform</span>: <span class="built_in">rotate</span>(<span class="number">360deg</span>); &#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ============================================</span></span><br><span class="line"><span class="comment">   暗色模式</span></span><br><span class="line"><span class="comment">   ============================================ */</span></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.anzhiyu-ai-summary</span> &#123;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#1c1c1e</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#ffffff</span>;</span><br><span class="line">  <span class="attribute">border-color</span>: <span class="number">#2c2c2e</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">4px</span> <span class="number">12px</span> <span class="built_in">rgba</span>(<span class="number">0</span>, <span class="number">0</span>, <span class="number">0</span>, <span class="number">0.3</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.anzhiyu-ai-summary</span><span class="selector-pseudo">:hover</span> &#123;</span><br><span class="line">  <span class="attribute">border-color</span>: <span class="number">#3a3a3c</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">8px</span> <span class="number">24px</span> <span class="built_in">rgba</span>(<span class="number">0</span>, <span class="number">0</span>, <span class="number">0</span>, <span class="number">0.4</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-header</span> &#123;</span><br><span class="line">  <span class="attribute">border-bottom-color</span>: <span class="number">#2c2c2e</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-titles</span> &#123;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#ffffff</span>;</span><br><span class="line">  <span class="attribute">background</span>: none;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-badge</span> &#123;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#8e8e93</span>;</span><br><span class="line">  <span class="attribute">background</span>: none;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-badge</span><span class="selector-pseudo">::before</span> &#123;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#30d158</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-text-box</span> &#123;</span><br><span class="line">  <span class="attribute">background</span>: <span class="number">#2c2c2e</span>;</span><br><span class="line">  <span class="attribute">border-color</span>: <span class="number">#3a3a3c</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#ffffff</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-loading</span> &#123;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#ffffff</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-loading-inline</span> &#123;</span><br><span class="line">  <span class="attribute">display</span>: flex;</span><br><span class="line">  <span class="attribute">align-items</span>: center;</span><br><span class="line">  <span class="attribute">gap</span>: <span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#86868b</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">14px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-loading-inline</span> <span class="selector-tag">i</span> &#123;</span><br><span class="line">  <span class="attribute">animation</span>: spin <span class="number">1s</span> linear infinite;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;dark&quot;</span>]</span> <span class="selector-class">.ai-loading-inline</span> &#123;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#8e8e93</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment">/* AI 摘要加载动画 */</span></span><br><span class="line"><span class="selector-class">.ai-loading-inline</span> &#123;</span><br><span class="line">  <span class="attribute">display</span>: inline-flex;</span><br><span class="line">  <span class="attribute">align-items</span>: center;</span><br><span class="line">  <span class="attribute">gap</span>: <span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#999</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">14px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-loading-svg</span> &#123;</span><br><span class="line">  <span class="attribute">animation</span>: ai-loading-rotate <span class="number">1s</span> linear infinite;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#999</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">@keyframes</span> ai-loading-rotate &#123;</span><br><span class="line">  <span class="selector-tag">from</span> &#123; <span class="attribute">transform</span>: <span class="built_in">rotate</span>(<span class="number">0deg</span>); &#125;</span><br><span class="line">  <span class="selector-tag">to</span> &#123; <span class="attribute">transform</span>: <span class="built_in">rotate</span>(<span class="number">360deg</span>); &#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 文字后面的点动画 */</span></span><br><span class="line"><span class="selector-class">.ai-loading-dots</span><span class="selector-pseudo">::after</span> &#123;</span><br><span class="line">  <span class="attribute">content</span>: <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  <span class="attribute">animation</span>: ai-loading-dots <span class="number">1.5s</span> <span class="built_in">steps</span>(<span class="number">4</span>, end) infinite;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">@keyframes</span> ai-loading-dots &#123;</span><br><span class="line">  <span class="number">0%</span> &#123; <span class="attribute">content</span>: <span class="string">&#x27;&#x27;</span>; &#125;</span><br><span class="line">  <span class="number">25%</span> &#123; <span class="attribute">content</span>: <span class="string">&#x27;.&#x27;</span>; &#125;</span><br><span class="line">  <span class="number">50%</span> &#123; <span class="attribute">content</span>: <span class="string">&#x27;..&#x27;</span>; &#125;</span><br><span class="line">  <span class="number">75%</span> &#123; <span class="attribute">content</span>: <span class="string">&#x27;...&#x27;</span>; &#125;</span><br><span class="line">  <span class="number">100%</span> &#123; <span class="attribute">content</span>: <span class="string">&#x27;&#x27;</span>; &#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.ai-header</span> <span class="selector-class">.icon-bilibili</span> &#123;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">margin-right</span>: <span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">vertical-align</span>: middle;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ============================================</span></span><br><span class="line"><span class="comment">   移动端适配</span></span><br><span class="line"><span class="comment">   ============================================ */</span></span><br><span class="line"><span class="keyword">@media</span> (<span class="attribute">max-width</span>: <span class="number">768px</span>) &#123;</span><br><span class="line">  <span class="selector-class">.anzhiyu-ai-summary</span> &#123;</span><br><span class="line">    <span class="attribute">margin</span>: <span class="number">16px</span> -<span class="number">16px</span>;</span><br><span class="line">    <span class="attribute">border-radius</span>: <span class="number">0</span>;</span><br><span class="line">    <span class="attribute">border-left</span>: none;</span><br><span class="line">    <span class="attribute">border-right</span>: none;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.ai-content</span> &#123;</span><br><span class="line">    <span class="attribute">padding</span>: <span class="number">16px</span> <span class="number">20px</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.ai-badge</span> &#123;</span><br><span class="line">    <span class="attribute">display</span>: none;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.ai-text-box</span> &#123;</span><br><span class="line">    <span class="attribute">padding</span>: <span class="number">12px</span> <span class="number">14px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-引入资源文件"><a href="#3-引入资源文件" class="headerlink" title="3. 引入资源文件"></a>3. 引入资源文件</h3><p>在主题布局中引入 CSS 和 JS：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">inject:</span></span><br><span class="line">  <span class="attr">head:</span></span><br><span class="line">    <span class="comment"># 自定义css</span></span><br><span class="line">    <span class="bullet">-</span> <span class="string">&lt;link</span> <span class="string">rel=&quot;stylesheet&quot;</span> <span class="string">href=&quot;/cdn/css/ai-summary.css&quot;&gt;</span></span><br><span class="line"> </span><br><span class="line">  <span class="attr">bottom:</span></span><br><span class="line">    <span class="comment"># 自定义js</span></span><br><span class="line">    <span class="bullet">-</span> <span class="string">&lt;script</span> <span class="string">defer</span> <span class="string">src=&quot;/cdn/js/ai-summary.js&quot;&gt;&lt;/script&gt;</span></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/AI/">AI</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Ollama/">Ollama</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/05/16/83caee76/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的PITR</title>
      <link>https://blog.eucalyptus.cc/2026/05/15/f30196cf/</link>
      <guid>https://blog.eucalyptus.cc/2026/05/15/f30196cf/</guid>
      <pubDate>Fri, 15 May 2026 06:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;2026-04-09 03:34:12 目标库&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img1.avif&quot;&gt;&lt;/p&gt;
&lt;p&gt;2026-04-09 11:35:20</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>2026-04-09 03:34:12 目标库</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img1.avif"></p><p>2026-04-09 11:35:20 源库</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img2.avif"></p><p>源库进行全量备份</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img3.avif"></p><p>导入目标库恢复</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img4.avif"></p><p>在源库删除demo3创建demo4</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img5.avif"></p><p>解析binlog查看时间</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img6.avif"></p><p>接下来需要将目标库恢复至demo3被删除的状态</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">mysqlbinlog \</span><br><span class="line"><span class="comment">--skip-gtids \</span></span><br><span class="line"><span class="comment">--start-datetime 2026-04-09 11:42:30 \</span></span><br><span class="line"><span class="comment">--stop-datetime 2026-04-09 11:042:37 \</span></span><br><span class="line"><span class="comment">--verbose \</span></span><br><span class="line"><span class="comment">--base64-output DECODE-ROWS \</span></span><br><span class="line"><span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span>d6e147809ebe<span class="operator">-</span>bin<span class="number">.000002</span> \</span><br><span class="line"><span class="operator">&gt;</span> <span class="operator">/</span>opt<span class="operator">/</span>demo.sql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img7.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-15/img8.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/05/15/f30196cf/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Replication with More Columns on Source or Replica</title>
      <link>https://blog.eucalyptus.cc/2026/05/10/13b0354f/</link>
      <guid>https://blog.eucalyptus.cc/2026/05/10/13b0354f/</guid>
      <pubDate>Sun, 10 May 2026 02:15:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><a href="https://dev.mysql.com/doc/mysql-replication-excerpt/5.7/en/replication-features-more-columns.html">https://dev.mysql.com/doc/mysql-replication-excerpt/5.7/en/replication-features-more-columns.html</a></p><h3 id="5-7-44"><a href="#5-7-44" class="headerlink" title="5.7.44"></a>5.7.44</h3><h4 id="测试验证"><a href="#测试验证" class="headerlink" title="测试验证"></a>测试验证</h4><h5 id="源表中有更多列-以下表定义有效且能正确复制"><a href="#源表中有更多列-以下表定义有效且能正确复制" class="headerlink" title="源表中有更多列,以下表定义有效且能正确复制"></a>源表中有更多列,以下表定义有效且能正确复制</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>, c3 <span class="type">INT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img1.avif"></p><h5 id="以下表定义将引发错误-因为表中两个版本共有的列在副本上的定义顺序与在源上的定义顺序不同"><a href="#以下表定义将引发错误-因为表中两个版本共有的列在副本上的定义顺序与在源上的定义顺序不同" class="headerlink" title="以下表定义将引发错误,因为表中两个版本共有的列在副本上的定义顺序与在源上的定义顺序不同"></a>以下表定义将引发错误,因为表中两个版本共有的列在副本上的定义顺序与在源上的定义顺序不同</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>, c3 <span class="type">INT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c2 <span class="type">INT</span>, c1 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img2.avif"></p><p>不一定会导致复制中断,但是source和replica上相同列的数据可能会出现不一致</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img3.avif"></p><h5 id="下表定义也会引发错误-因为源表上额外列的定义出现在两个表版本共有的列定义之前"><a href="#下表定义也会引发错误-因为源表上额外列的定义出现在两个表版本共有的列定义之前" class="headerlink" title="下表定义也会引发错误,因为源表上额外列的定义出现在两个表版本共有的列定义之前"></a>下表定义也会引发错误,因为源表上额外列的定义出现在两个表版本共有的列定义之前</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c3 <span class="type">INT</span>, c1 <span class="type">INT</span>, c2 <span class="type">INT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p>不一定会导致复制中断,但是source和replica上相同列的数据可能会出现不一致</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img4.avif"></p><h5 id="以下表定义失败-因为与源版本相比-副本的表版本包含额外的列-并且这两个版本的表对公共列c2使用了不同的数据类型"><a href="#以下表定义失败-因为与源版本相比-副本的表版本包含额外的列-并且这两个版本的表对公共列c2使用了不同的数据类型" class="headerlink" title="以下表定义失败,因为与源版本相比,副本的表版本包含额外的列,并且这两个版本的表对公共列c2使用了不同的数据类型"></a>以下表定义失败,因为与源版本相比,副本的表版本包含额外的列,并且这两个版本的表对公共列c2使用了不同的数据类型</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">BIGINT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>, c3 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p>大概率会导致复制中断,</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img6.avif"></p><h4 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h4><p><strong>source和replica之间列的多少和顺序,并不 一定会导致复制中断,但是一定会出现数据不一致。source和replica之间的列的数据类型不同,一定会导致复制中断。</strong></p><h3 id="8-0-37"><a href="#8-0-37" class="headerlink" title="8.0.37"></a>8.0.37</h3><h4 id="测试验证-1"><a href="#测试验证-1" class="headerlink" title="测试验证"></a>测试验证</h4><h5 id="下表定义也会引发错误-因为源表上额外列的定义出现在两个表版本共有的列定义之前-1"><a href="#下表定义也会引发错误-因为源表上额外列的定义出现在两个表版本共有的列定义之前-1" class="headerlink" title="下表定义也会引发错误,因为源表上额外列的定义出现在两个表版本共有的列定义之前"></a>下表定义也会引发错误,因为源表上额外列的定义出现在两个表版本共有的列定义之前</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c3 <span class="type">INT</span>, c1 <span class="type">INT</span>, c2 <span class="type">INT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p>不一定会导致复制中断,但是source和replica上相同列的数据可能会出现不一致</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img7.avif"></p><h5 id="以下表定义失败-因为与源版本相比-副本的表版本包含额外的列-并且这两个版本的表对公共列c2使用了不同的数据类型-1"><a href="#以下表定义失败-因为与源版本相比-副本的表版本包含额外的列-并且这两个版本的表对公共列c2使用了不同的数据类型-1" class="headerlink" title="以下表定义失败,因为与源版本相比,副本的表版本包含额外的列,并且这两个版本的表对公共列c2使用了不同的数据类型"></a>以下表定义失败,因为与源版本相比,副本的表版本包含额外的列,并且这两个版本的表对公共列c2使用了不同的数据类型</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">source<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">BIGINT</span>);</span><br><span class="line">replica<span class="operator">&gt;</span> <span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>, c2 <span class="type">INT</span>, c3 <span class="type">INT</span>);</span><br></pre></td></tr></table></figure><p>大概率会导致复制中断,</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-05-10/img9.avif"></p><h4 id="总结-1"><a href="#总结-1" class="headerlink" title="总结"></a>总结</h4><p><strong>source和replica之间列的多少和顺序,并不 一定会导致复制中断,但是一定会出现数据不一致。source和replica之间的列的数据类型不同,一定会导致复制中断。</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/05/10/13b0354f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>新添文章卡片样式</title>
      <link>https://blog.eucalyptus.cc/2026/04/13/6fe15434/</link>
      <guid>https://blog.eucalyptus.cc/2026/04/13/6fe15434/</guid>
      <pubDate>Mon, 13 Apr 2026 06:19:46 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;这份教程，记录了我为 AnZhiYu</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>这份教程，记录了我为 AnZhiYu 主题添加横向卡片样式的全部过程。代码不多，但每一处都仔细调整过：斜切的视觉平衡、移动端的适配、分页后的稳定性……甚至强迫自己解决了偶数页布局错乱的 bug。</p><p>代码不是束缚，是自由的工具。愿你的博客，也能长出属于自己的姿态。</p><h2 id="正文"><a href="#正文" class="headerlink" title="正文"></a>正文</h2><p>文件路径分布</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line">blog/                          # Hexo 博客根目录</span><br><span class="line">├── themes/</span><br><span class="line">│   └── anzhiyu/                    # AnZhiYu 主题目录</span><br><span class="line">│       ├── layout/                 # 布局模板目录</span><br><span class="line">│       │   ├── includes/           # 包含组件目录</span><br><span class="line">│       │   │   └── mixins/         # mixins 组件目录</span><br><span class="line">│       │   │       └── post-ui-horizontal.pug    # ← 横向卡片 Pug 模板</span><br><span class="line">│       │   └── index.pug           # ← 首页布局文件（调用横向卡片）</span><br><span class="line">│       └── ...                     # 其他主题文件</span><br><span class="line">├── source/                         # 源文件目录（会被复制到 public）</span><br><span class="line">│   └── cdn/                        # CDN 资源目录</span><br><span class="line">│       └── css/</span><br><span class="line">│           └── horizontal-card.css # ← 横向卡片样式文件（你提供的 CSS）</span><br><span class="line">└── ...                             # 其他博客文件</span><br></pre></td></tr></table></figure><p>新建post-ui-horizontal.pug</p><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br></pre></td><td class="code"><pre><span class="line">mixin <span class="title function_">postUIHorizontal</span>()</span><br><span class="line">  - <span class="keyword">let</span> maxDate = <span class="number">0</span></span><br><span class="line">  each item <span class="keyword">in</span> site.<span class="property">posts</span>.<span class="property">data</span></span><br><span class="line">    <span class="keyword">if</span> item.<span class="property">date</span> &gt; maxDate</span><br><span class="line">      - maxDate = item.<span class="property">date</span></span><br><span class="line"></span><br><span class="line">  .<span class="property">horizontal</span>-post-list</span><br><span class="line">    each article, index <span class="keyword">in</span> page.<span class="property">posts</span>.<span class="property">data</span></span><br><span class="line">      - <span class="keyword">let</span> link = article.<span class="property">link</span> || article.<span class="property">path</span></span><br><span class="line">      - <span class="keyword">let</span> title = article.<span class="property">title</span> || <span class="title function_">_p</span>(<span class="string">&#x27;no_title&#x27;</span>)</span><br><span class="line">      - <span class="keyword">let</span> post_cover = article.<span class="property">cover</span></span><br><span class="line">      - <span class="keyword">let</span> desc = article.<span class="property">description</span> || article.<span class="property">excerpt</span> || <span class="string">&#x27;&#x27;</span></span><br><span class="line">      - <span class="keyword">let</span> category = article.<span class="property">categories</span>.<span class="property">data</span>[<span class="number">0</span>]</span><br><span class="line">      - <span class="keyword">let</span> dateStr = <span class="title function_">date</span>(article.<span class="property">date</span>, <span class="string">&#x27;MM-DD&#x27;</span>)</span><br><span class="line">      - <span class="keyword">let</span> wc = <span class="title function_">wordcount</span>(article.<span class="property">content</span>)</span><br><span class="line">      - <span class="keyword">const</span> new_post = <span class="title function_">is_current</span>(<span class="string">&#x27;/&#x27;</span>) &amp;&amp; (maxDate === article.<span class="property">date</span>)</span><br><span class="line">      <span class="comment">// 判断左右位置：偶数左边，奇数右边</span></span><br><span class="line">      - <span class="keyword">let</span> isLeft = index % <span class="number">2</span> === <span class="number">0</span></span><br><span class="line">      </span><br><span class="line">      article.<span class="property">recent</span>-post-item.<span class="property">horizontal</span>-<span class="title function_">card</span>(<span class="keyword">class</span>=isLeft ? <span class="string">&#x27;image-right&#x27;</span> : <span class="string">&#x27;image-left&#x27;</span> onclick=<span class="string">`pjax.loadUrl(&#x27;<span class="subst">$&#123;url_for(link)&#125;</span>&#x27;)`</span>)</span><br><span class="line">        <span class="comment">// 图片在左（奇数卡片）</span></span><br><span class="line">        <span class="keyword">if</span> !isLeft &amp;&amp; post_cover &amp;&amp; theme.<span class="property">cover</span>.<span class="property">index_enable</span></span><br><span class="line">          .<span class="property">post</span>-cover</span><br><span class="line">            <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) title=title)</span><br><span class="line">              img.<span class="title function_">post_bg</span>(src=<span class="title function_">url_for</span>(post_cover) onerror=<span class="string">`this.onerror=null;this.src=&#x27;`</span>+ <span class="title function_">url_for</span>(theme.<span class="property">error_img</span>.<span class="property">post_page</span>) + <span class="string">`&#x27;`</span> alt=title loading=<span class="string">&quot;lazy&quot;</span>)</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 无图片占位（奇数卡片）</span></span><br><span class="line">        <span class="keyword">if</span> !isLeft &amp;&amp; !(post_cover &amp;&amp; theme.<span class="property">cover</span>.<span class="property">index_enable</span>)</span><br><span class="line">          .<span class="property">post</span>-cover.<span class="property">no</span>-image</span><br><span class="line">            <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) title=title)</span><br><span class="line">              .<span class="property">cover</span>-placeholder</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 内容区</span></span><br><span class="line">        .<span class="property">post</span>-content</span><br><span class="line">          .<span class="property">post</span>-content-top</span><br><span class="line">            .<span class="property">post</span>-tips</span><br><span class="line">              <span class="keyword">if</span> (<span class="title function_">is_home</span>() &amp;&amp; (article.<span class="property">top</span> || article.<span class="property">sticky</span> &gt; <span class="number">0</span>))</span><br><span class="line">                span.<span class="property">article</span>-meta.<span class="property">sticky</span>-warp</span><br><span class="line">                  i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-thumbtack.<span class="property">sticky</span></span><br><span class="line">                  span.<span class="property">sticky</span>= <span class="title function_">_p</span>(<span class="string">&#x27;sticky&#x27;</span>)</span><br><span class="line">            </span><br><span class="line">            a.<span class="property">post</span>-<span class="title function_">title</span>(href=<span class="title function_">url_for</span>(link) title=title)= title</span><br><span class="line"></span><br><span class="line">          .<span class="property">post</span>-meta-wrap</span><br><span class="line">            <span class="keyword">if</span> (theme.<span class="property">post_meta</span>.<span class="property">page</span>.<span class="property">date_type</span>)</span><br><span class="line">              span.<span class="property">post</span>-meta-date</span><br><span class="line">                <span class="keyword">if</span> (theme.<span class="property">post_meta</span>.<span class="property">page</span>.<span class="property">date_type</span> === <span class="string">&#x27;both&#x27;</span>)</span><br><span class="line">                  i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-calendar-<span class="title function_">alt</span>(style=<span class="string">`<span class="subst">$&#123;theme.post_meta.page.date_format===<span class="string">&quot;simple&quot;</span> ? <span class="string">&quot;display:none&quot;</span>:<span class="string">&quot;&quot;</span>&#125;</span>`</span>)</span><br><span class="line">                  span.<span class="property">article</span>-meta-label=<span class="title function_">_p</span>(<span class="string">&#x27;post.created&#x27;</span>)</span><br><span class="line">                  time.<span class="property">post</span>-meta-date-<span class="title function_">created</span>(datetime=<span class="title function_">date_xml</span>(article.<span class="property">date</span>) title=<span class="title function_">_p</span>(<span class="string">&#x27;post.created&#x27;</span>) + <span class="string">&#x27; &#x27;</span> + <span class="title function_">full_date</span>(article.<span class="property">date</span>) time=<span class="title function_">full_date</span>(article.<span class="property">date</span>))=<span class="title function_">date</span>(article.<span class="property">date</span>, config.<span class="property">date_format</span>)</span><br><span class="line">                  span.<span class="property">article</span>-meta-separator</span><br><span class="line">                  i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-<span class="title function_">history</span>(style=<span class="string">`font-size: 15px; <span class="subst">$&#123;theme.post_meta.page.date_format===<span class="string">&quot;simple&quot;</span> ? <span class="string">&quot;display:none&quot;</span>:<span class="string">&quot;&quot;</span>&#125;</span>`</span>)</span><br><span class="line">                  span.<span class="property">article</span>-meta-label=<span class="title function_">_p</span>(<span class="string">&#x27;post.updated&#x27;</span>)</span><br><span class="line">                  time.<span class="property">post</span>-meta-date-<span class="title function_">updated</span>(datetime=<span class="title function_">date_xml</span>(article.<span class="property">updated</span>) title=<span class="title function_">_p</span>(<span class="string">&#x27;post.updated&#x27;</span>) + <span class="string">&#x27; &#x27;</span> + <span class="title function_">full_date</span>(article.<span class="property">updated</span>) time=<span class="title function_">full_date</span>(article.<span class="property">updated</span>))=<span class="title function_">date</span>(article.<span class="property">updated</span>, config.<span class="property">date_format</span>)</span><br><span class="line">                <span class="keyword">else</span></span><br><span class="line">                  - <span class="keyword">let</span> data_type_updated = theme.<span class="property">post_meta</span>.<span class="property">page</span>.<span class="property">date_type</span> === <span class="string">&#x27;updated&#x27;</span></span><br><span class="line">                  - <span class="keyword">let</span> date_type = data_type_updated ? <span class="string">&#x27;updated&#x27;</span> : <span class="string">&#x27;date&#x27;</span></span><br><span class="line">                  - <span class="keyword">let</span> date_type_other = data_type_updated ? <span class="string">&#x27;date&#x27;</span> : <span class="string">&#x27;updated&#x27;</span></span><br><span class="line">                  - <span class="keyword">let</span> date_icon = data_type_updated ? <span class="string">&#x27;anzhiyu-icon-history&#x27;</span> :<span class="string">&#x27;anzhiyu-icon-calendar-days&#x27;</span></span><br><span class="line">                  - <span class="keyword">let</span> date_title = data_type_updated ? <span class="title function_">_p</span>(<span class="string">&#x27;post.updated&#x27;</span>) : <span class="title function_">_p</span>(<span class="string">&#x27;post.created&#x27;</span>)</span><br><span class="line">                  - <span class="keyword">let</span> date_title_other = data_type_updated ? <span class="title function_">_p</span>(<span class="string">&#x27;post.created&#x27;</span>) : <span class="title function_">_p</span>(<span class="string">&#x27;post.updated&#x27;</span>)</span><br><span class="line">                  i.<span class="title function_">anzhiyufont</span>(<span class="keyword">class</span>=date_icon style=<span class="string">`font-size: 15px; <span class="subst">$&#123;theme.post_meta.page.date_format===<span class="string">&quot;simple&quot;</span> ? <span class="string">&quot;display:none&quot;</span>:<span class="string">&quot;&quot;</span>&#125;</span>`</span>)</span><br><span class="line">                  span.<span class="property">article</span>-meta-label=date_title</span><br><span class="line">                  <span class="title function_">time</span>(datetime=<span class="title function_">date_xml</span>(article[date_type]) title=date_title + <span class="string">&#x27; &#x27;</span> + <span class="title function_">full_date</span>(article[date_type])  time=<span class="title function_">full_date</span>(article[date_type]))=<span class="title function_">date</span>(article[date_type], config.<span class="property">date_format</span>)</span><br><span class="line">                  <span class="title function_">time</span>(datetime=<span class="title function_">date_xml</span>(article[date_type_other]), <span class="keyword">class</span>=<span class="string">&quot;time_hidden&quot;</span>, title=date_title_other + <span class="string">&#x27; &#x27;</span> + <span class="title function_">full_date</span>(article[date_type_other]) time=<span class="title function_">full_date</span>(article[date_type_other]))=<span class="title function_">date</span>(article[date_type_other], config.<span class="property">date_format</span>)</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> (theme.<span class="property">post_meta</span>.<span class="property">page</span>.<span class="property">tags</span> &amp;&amp; article.<span class="property">tags</span>.<span class="property">data</span>.<span class="property">length</span> &gt; <span class="number">0</span>)</span><br><span class="line">              span.<span class="property">article</span>-meta.<span class="property">tags</span></span><br><span class="line">                each item, index <span class="keyword">in</span> article.<span class="property">tags</span>.<span class="property">data</span></span><br><span class="line">                  <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(item.<span class="property">path</span>) event.<span class="property">cancelbubble</span> onclick=<span class="string">&quot;window.event.cancelBubble=true;&quot;</span>).<span class="property">article</span>-meta__tags</span><br><span class="line">                    span </span><br><span class="line">                      i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-hashtag</span><br><span class="line">                      =item.<span class="property">name</span></span><br><span class="line">            </span><br><span class="line">            mixin countBlockHorizontal</span><br><span class="line">              - needLoadCountJs = <span class="literal">true</span></span><br><span class="line">              span.<span class="property">article</span>-meta</span><br><span class="line">                span.<span class="property">article</span>-meta-separator</span><br><span class="line">                i.<span class="property">eucalyptus</span>.<span class="property">icon</span>-comments</span><br><span class="line">                <span class="keyword">if</span> block</span><br><span class="line">                  block</span><br><span class="line">                span.<span class="property">article</span>-meta-label= <span class="string">&#x27; &#x27;</span> + <span class="title function_">_p</span>(<span class="string">&#x27;card_post_count&#x27;</span>)</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">if</span> theme.<span class="property">comments</span>.<span class="property">card_post_count</span></span><br><span class="line">              <span class="keyword">case</span> theme.<span class="property">comments</span>.<span class="property">use</span>[<span class="number">0</span>]</span><br><span class="line">                when <span class="string">&#x27;Valine&#x27;</span></span><br><span class="line">                  +countBlockHorizontal</span><br><span class="line">                    <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) + <span class="string">&#x27;#post-comment&#x27;</span>)</span><br><span class="line">                      span.<span class="property">valine</span>-comment-<span class="title function_">count</span>(data-xid=<span class="title function_">url_for</span>(link))</span><br><span class="line">                        i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-spinner.<span class="property">anzhiyu</span>-spin</span><br><span class="line">                when <span class="string">&#x27;Waline&#x27;</span></span><br><span class="line">                  +countBlockHorizontal</span><br><span class="line">                    <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) + <span class="string">&#x27;#post-comment&#x27;</span>)</span><br><span class="line">                      span.<span class="property">waline</span>-comment-<span class="title function_">count</span>(id=<span class="title function_">url_for</span>(link))</span><br><span class="line">                        i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-spinner.<span class="property">anzhiyu</span>-spin</span><br><span class="line">                when <span class="string">&#x27;Twikoo&#x27;</span></span><br><span class="line">                  +countBlockHorizontal</span><br><span class="line">                    a.<span class="property">twikoo</span>-<span class="title function_">count</span>(href=<span class="title function_">url_for</span>(link) + <span class="string">&#x27;#post-comment&#x27;</span> tabindex=<span class="string">&quot;-1&quot;</span>)</span><br><span class="line">                      i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-spinner.<span class="property">anzhiyu</span>-spin</span><br><span class="line">                when <span class="string">&#x27;Artalk&#x27;</span></span><br><span class="line">                  +countBlockHorizontal</span><br><span class="line">                    <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) + <span class="string">&#x27;#post-comment&#x27;</span>)</span><br><span class="line">                      span.<span class="property">artalk</span>-<span class="title function_">count</span>(data-page-key=<span class="title function_">url_for</span>(link))</span><br><span class="line">                        i.<span class="property">anzhiyufont</span>.<span class="property">anzhiyu</span>-icon-spinner.<span class="property">anzhiyu</span>-spin</span><br><span class="line"></span><br><span class="line">          <span class="keyword">case</span> theme.<span class="property">index_post_content</span>.<span class="property">method</span></span><br><span class="line">            when <span class="literal">false</span></span><br><span class="line">              - <span class="keyword">break</span></span><br><span class="line">            when <span class="number">1</span></span><br><span class="line">              .<span class="property">post</span>-desc!= article.<span class="property">description</span></span><br><span class="line">            when <span class="number">2</span></span><br><span class="line">              <span class="keyword">if</span> article.<span class="property">description</span></span><br><span class="line">                .<span class="property">post</span>-desc!= article.<span class="property">description</span></span><br><span class="line">              <span class="keyword">else</span></span><br><span class="line">                - <span class="keyword">const</span> content = <span class="title function_">strip_html</span>(article.<span class="property">content</span>)</span><br><span class="line">                - <span class="keyword">let</span> expert = content.<span class="title function_">substring</span>(<span class="number">0</span>, theme.<span class="property">index_post_content</span>.<span class="property">length</span>) </span><br><span class="line">                - content.<span class="property">length</span> &gt; theme.<span class="property">index_post_content</span>.<span class="property">length</span> ? expert += <span class="string">&#x27; ...&#x27;</span> : <span class="string">&#x27;&#x27;</span></span><br><span class="line">                .<span class="property">post</span>-desc!= expert</span><br><span class="line">            <span class="keyword">default</span></span><br><span class="line">              - <span class="keyword">const</span> content = <span class="title function_">strip_html</span>(article.<span class="property">content</span>)</span><br><span class="line">              - <span class="keyword">let</span> expert = content.<span class="title function_">substring</span>(<span class="number">0</span>, theme.<span class="property">index_post_content</span>.<span class="property">length</span>) </span><br><span class="line">              - content.<span class="property">length</span> &gt; theme.<span class="property">index_post_content</span>.<span class="property">length</span> ? expert += <span class="string">&#x27; ...&#x27;</span> : <span class="string">&#x27;&#x27;</span></span><br><span class="line">              .<span class="property">post</span>-desc!= expert</span><br><span class="line"></span><br><span class="line">        <span class="comment">// 图片在右（偶数卡片）</span></span><br><span class="line">        <span class="keyword">if</span> isLeft &amp;&amp; post_cover &amp;&amp; theme.<span class="property">cover</span>.<span class="property">index_enable</span></span><br><span class="line">          .<span class="property">post</span>-cover</span><br><span class="line">            <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) title=title)</span><br><span class="line">              img.<span class="title function_">post_bg</span>(src=<span class="title function_">url_for</span>(post_cover) onerror=<span class="string">`this.onerror=null;this.src=&#x27;`</span>+ <span class="title function_">url_for</span>(theme.<span class="property">error_img</span>.<span class="property">post_page</span>) + <span class="string">`&#x27;`</span> alt=title loading=<span class="string">&quot;lazy&quot;</span>)</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 无图片占位（偶数卡片）</span></span><br><span class="line">        <span class="keyword">if</span> isLeft &amp;&amp; !(post_cover &amp;&amp; theme.<span class="property">cover</span>.<span class="property">index_enable</span>)</span><br><span class="line">          .<span class="property">post</span>-cover.<span class="property">no</span>-image</span><br><span class="line">            <span class="title function_">a</span>(href=<span class="title function_">url_for</span>(link) title=title)</span><br><span class="line">              .<span class="property">cover</span>-placeholder</span><br><span class="line"></span><br><span class="line">      <span class="keyword">if</span> theme.<span class="property">ad</span> &amp;&amp; theme.<span class="property">ad</span>.<span class="property">index</span></span><br><span class="line">        <span class="keyword">if</span> (index + <span class="number">1</span>) % <span class="number">3</span> == <span class="number">0</span></span><br><span class="line">          .<span class="property">horizontal</span>-card.<span class="property">ads</span>-wrap!=theme.<span class="property">ad</span>.<span class="property">index</span></span><br></pre></td></tr></table></figure><p>修改index.pug</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line">extends includes/layout.pug</span><br><span class="line"></span><br><span class="line">block content</span><br><span class="line">  include ./includes/mixins/post-ui.pug</span><br><span class="line">  </span><br><span class="line">  // 关键：include 必须在顶层，不能放在 if 里面</span><br><span class="line">  include ./includes/mixins/post-ui-horizontal.pug</span><br><span class="line">  </span><br><span class="line">  #recent-posts.recent-posts</span><br><span class="line">    include includes/categoryGroup.pug</span><br><span class="line">    </span><br><span class="line">    if theme.home_card_style === &#x27;horizontal&#x27;</span><br><span class="line">      +postUIHorizontal()</span><br><span class="line">    else</span><br><span class="line">      +postUI</span><br><span class="line">    </span><br><span class="line">    include includes/pagination.pug</span><br></pre></td></tr></table></figure><p>新建horizontal-card.css</p><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/* ========== 变量定义 ========== */</span></span><br><span class="line"><span class="selector-pseudo">:root</span> &#123;</span><br><span class="line">    <span class="attr">--card-bg</span>: <span class="number">#1a1a2e</span>;</span><br><span class="line">    <span class="attr">--card-bg-alt</span>: <span class="number">#16213e</span>;</span><br><span class="line">    <span class="attr">--theme-color</span>: <span class="number">#e94560</span>;</span><br><span class="line">    <span class="attr">--skew-width</span>: <span class="number">60px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 基础卡片样式 ========== */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span> &#123;</span><br><span class="line">    <span class="attribute">display</span>: flex;</span><br><span class="line">    <span class="attribute">flex-direction</span>: row;</span><br><span class="line">    <span class="attribute">width</span>: <span class="number">100%</span>;</span><br><span class="line">    <span class="attribute">height</span>: <span class="number">260px</span>;</span><br><span class="line">    <span class="attribute">border-radius</span>: <span class="number">16px</span>;</span><br><span class="line">    <span class="attribute">overflow</span>: hidden;</span><br><span class="line">    <span class="attribute">background</span>: <span class="built_in">var</span>(--card-bg);</span><br><span class="line">    <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">8px</span> <span class="number">32px</span> <span class="built_in">rgba</span>(<span class="number">0</span>,<span class="number">0</span>,<span class="number">0</span>,<span class="number">0.3</span>);</span><br><span class="line">    <span class="attribute">transition</span>: all <span class="number">0.4s</span> ease;</span><br><span class="line">    <span class="attribute">cursor</span>: pointer;</span><br><span class="line">    <span class="attribute">position</span>: relative;</span><br><span class="line">    <span class="attribute">margin-bottom</span>: <span class="number">32px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-pseudo">:hover</span> &#123;</span><br><span class="line">    <span class="attribute">transform</span>: <span class="built_in">translateY</span>(-<span class="number">6px</span>);</span><br><span class="line">    <span class="attribute">box-shadow</span>: <span class="number">0</span> <span class="number">16px</span> <span class="number">48px</span> <span class="built_in">rgba</span>(<span class="number">233</span>, <span class="number">69</span>, <span class="number">96</span>, <span class="number">0.15</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 内容区域基础 ========== */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-content</span> &#123;</span><br><span class="line">    <span class="attribute">width</span>: <span class="built_in">calc</span>(<span class="number">58%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">flex</span>: <span class="number">0</span> <span class="number">0</span> <span class="built_in">calc</span>(<span class="number">58%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">max-width</span>: <span class="built_in">calc</span>(<span class="number">58%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">padding</span>: <span class="number">32px</span> <span class="number">40px</span>;</span><br><span class="line">    <span class="attribute">display</span>: flex;</span><br><span class="line">    <span class="attribute">flex-direction</span>: column;</span><br><span class="line">    <span class="attribute">justify-content</span>: space-between;</span><br><span class="line">    <span class="attribute">position</span>: relative;</span><br><span class="line">    <span class="attribute">z-index</span>: <span class="number">2</span>;</span><br><span class="line">    <span class="attribute">min-width</span>: <span class="number">0</span>;</span><br><span class="line">    <span class="attribute">overflow</span>: hidden;</span><br><span class="line">    <span class="attribute">box-sizing</span>: border-box;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-title</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">1.6rem</span>;</span><br><span class="line">    <span class="attribute">font-weight</span>: <span class="number">700</span>;</span><br><span class="line">    <span class="attribute">line-height</span>: <span class="number">1.3</span>;</span><br><span class="line">    <span class="attribute">display</span>: -webkit-box;</span><br><span class="line">    -webkit-<span class="selector-tag">line</span>-clamp: <span class="number">2</span>;</span><br><span class="line">    -webkit-<span class="attribute">box-orient</span>: vertical;</span><br><span class="line">    <span class="attribute">overflow</span>: hidden;</span><br><span class="line">    <span class="attribute">margin-bottom</span>: <span class="number">4px</span>;</span><br><span class="line">    <span class="attribute">word-break</span>: break-word;</span><br><span class="line">    <span class="attribute">overflow-wrap</span>: break-word;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-desc</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">1rem</span>;</span><br><span class="line">    <span class="attribute">line-height</span>: <span class="number">1.8</span>;</span><br><span class="line">    <span class="attribute">display</span>: -webkit-box;</span><br><span class="line">    -webkit-<span class="selector-tag">line</span>-clamp: <span class="number">2</span>;</span><br><span class="line">    -webkit-<span class="attribute">box-orient</span>: vertical;</span><br><span class="line">    <span class="attribute">overflow</span>: hidden;</span><br><span class="line">    <span class="attribute">margin-top</span>: <span class="number">12px</span>;</span><br><span class="line">    <span class="attribute">word-break</span>: break-word;</span><br><span class="line">    <span class="attribute">overflow-wrap</span>: break-word;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 图片区域基础 ========== */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-cover</span> &#123;</span><br><span class="line">    <span class="attribute">width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">flex</span>: <span class="number">0</span> <span class="number">0</span> <span class="built_in">calc</span>(<span class="number">42%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">max-width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> - <span class="number">0px</span>);</span><br><span class="line">    <span class="attribute">min-width</span>: <span class="number">320px</span>;</span><br><span class="line">    <span class="attribute">height</span>: <span class="number">100%</span>;</span><br><span class="line">    <span class="attribute">position</span>: relative;</span><br><span class="line">    <span class="attribute">overflow</span>: hidden;</span><br><span class="line">    <span class="attribute">box-sizing</span>: border-box;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-cover</span> <span class="selector-tag">img</span> &#123;</span><br><span class="line">    <span class="attribute">width</span>: <span class="number">100%</span>;</span><br><span class="line">    <span class="attribute">height</span>: <span class="number">100%</span>;</span><br><span class="line">    <span class="attribute">object-fit</span>: cover;</span><br><span class="line">    <span class="attribute">transition</span>: transform <span class="number">0.6s</span> ease;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-pseudo">:hover</span> <span class="selector-class">.post-cover</span> <span class="selector-tag">img</span> &#123;</span><br><span class="line">    <span class="attribute">transform</span>: <span class="built_in">scale</span>(<span class="number">1.1</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 图片在右边 + 斜切线 ========== */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> &#123;</span><br><span class="line">    <span class="attribute">background</span>: <span class="built_in">linear-gradient</span>(<span class="number">135deg</span>, <span class="built_in">var</span>(--card-bg) <span class="number">0%</span>, <span class="built_in">var</span>(--card-bg-alt) <span class="number">100%</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> <span class="selector-class">.post-content</span> &#123;</span><br><span class="line">    <span class="attribute">order</span>: <span class="number">1</span>;</span><br><span class="line">    <span class="attribute">padding-right</span>: <span class="number">80px</span>;</span><br><span class="line">    <span class="attribute">clip-path</span>: <span class="built_in">polygon</span>(</span><br><span class="line">        <span class="number">0</span> <span class="number">0</span>, </span><br><span class="line">        <span class="built_in">calc</span>(<span class="number">100%</span> - <span class="built_in">var</span>(--skew-width)) <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">100%</span>, </span><br><span class="line">        <span class="number">0</span> <span class="number">100%</span></span><br><span class="line">    );</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> <span class="selector-class">.post-cover</span> &#123;</span><br><span class="line">    <span class="attribute">order</span>: <span class="number">2</span>;</span><br><span class="line">    <span class="attribute">clip-path</span>: <span class="built_in">polygon</span>(</span><br><span class="line">        <span class="built_in">var</span>(--skew-width) <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">100%</span>, </span><br><span class="line">        <span class="number">0</span> <span class="number">100%</span></span><br><span class="line">    );</span><br><span class="line">    <span class="attribute">margin-left</span>: <span class="built_in">calc</span>(<span class="built_in">var</span>(--skew-width) * -<span class="number">1</span>);</span><br><span class="line">    <span class="attribute">margin-right</span>: <span class="built_in">calc</span>(<span class="built_in">var</span>(--skew-width) * -<span class="number">1</span>);</span><br><span class="line">    <span class="attribute">width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">    <span class="attribute">flex</span>: <span class="number">0</span> <span class="number">0</span> <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">    <span class="attribute">max-width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 图片在左边 + 斜切线 ========== */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span> &#123;</span><br><span class="line">    <span class="attribute">background</span>: <span class="built_in">linear-gradient</span>(<span class="number">225deg</span>, <span class="built_in">var</span>(--card-bg) <span class="number">0%</span>, <span class="built_in">var</span>(--card-bg-alt) <span class="number">100%</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span> <span class="selector-class">.post-content</span> &#123;</span><br><span class="line">    <span class="attribute">order</span>: <span class="number">2</span>;</span><br><span class="line">    <span class="attribute">padding-left</span>: <span class="number">80px</span>;</span><br><span class="line">    <span class="attribute">clip-path</span>: <span class="built_in">polygon</span>(</span><br><span class="line">        <span class="built_in">var</span>(--skew-width) <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">100%</span>, </span><br><span class="line">        <span class="number">0</span> <span class="number">100%</span></span><br><span class="line">    );</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span> <span class="selector-class">.post-cover</span> &#123;</span><br><span class="line">    <span class="attribute">order</span>: <span class="number">1</span>;</span><br><span class="line">    <span class="attribute">clip-path</span>: <span class="built_in">polygon</span>(</span><br><span class="line">        <span class="number">0</span> <span class="number">0</span>, </span><br><span class="line">        <span class="built_in">calc</span>(<span class="number">100%</span> - <span class="built_in">var</span>(--skew-width)) <span class="number">0</span>, </span><br><span class="line">        <span class="number">100%</span> <span class="number">100%</span>, </span><br><span class="line">        <span class="number">0</span> <span class="number">100%</span></span><br><span class="line">    );</span><br><span class="line">    <span class="attribute">margin-right</span>: <span class="built_in">calc</span>(<span class="built_in">var</span>(--skew-width) * -<span class="number">1</span>);</span><br><span class="line">    <span class="attribute">margin-left</span>: <span class="built_in">calc</span>(<span class="built_in">var</span>(--skew-width) * -<span class="number">1</span>);</span><br><span class="line">    <span class="attribute">width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">    <span class="attribute">flex</span>: <span class="number">0</span> <span class="number">0</span> <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">    <span class="attribute">max-width</span>: <span class="built_in">calc</span>(<span class="number">42%</span> + <span class="built_in">var</span>(--skew-width)) <span class="meta">!important</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 第一张卡片距离顶部增加间距 */</span></span><br><span class="line"><span class="selector-class">.horizontal-card</span><span class="selector-pseudo">:first-child</span> &#123;</span><br><span class="line">    <span class="attribute">margin-top</span>: <span class="number">32px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========== 响应式适配 ========== */</span></span><br><span class="line"><span class="keyword">@media</span> screen <span class="keyword">and</span> (<span class="attribute">max-width</span>: <span class="number">768px</span>) &#123;</span><br><span class="line">    <span class="selector-class">.horizontal-card</span>,</span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span>,</span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> &#123;</span><br><span class="line">        <span class="attribute">flex-direction</span>: column;</span><br><span class="line">        <span class="attribute">height</span>: auto;</span><br><span class="line">        <span class="attribute">margin-bottom</span>: <span class="number">28px</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="selector-class">.horizontal-card</span> <span class="selector-class">.post-content</span>,</span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span> <span class="selector-class">.post-content</span>,</span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> <span class="selector-class">.post-content</span> &#123;</span><br><span class="line">        <span class="attribute">width</span>: <span class="number">100%</span>;</span><br><span class="line">        <span class="attribute">flex</span>: none;</span><br><span class="line">        <span class="attribute">max-width</span>: <span class="number">100%</span>;</span><br><span class="line">        <span class="attribute">padding</span>: <span class="number">24px</span>;</span><br><span class="line">        <span class="attribute">order</span>: <span class="number">2</span>;</span><br><span class="line">        <span class="attribute">clip-path</span>: none;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-left</span> <span class="selector-class">.post-cover</span>,</span><br><span class="line">    <span class="selector-class">.horizontal-card</span><span class="selector-class">.image-right</span> <span class="selector-class">.post-cover</span> &#123;</span><br><span class="line">        <span class="attribute">width</span>: <span class="number">100%</span> <span class="meta">!important</span>;</span><br><span class="line">        <span class="attribute">flex</span>: none <span class="meta">!important</span>;</span><br><span class="line">        <span class="attribute">max-width</span>: <span class="number">100%</span> <span class="meta">!important</span>;</span><br><span class="line">        <span class="attribute">min-width</span>: auto;</span><br><span class="line">        <span class="attribute">height</span>: <span class="number">220px</span>;</span><br><span class="line">        <span class="attribute">order</span>: <span class="number">1</span>;</span><br><span class="line">        <span class="attribute">margin</span>: <span class="number">0</span> <span class="meta">!important</span>;</span><br><span class="line">        <span class="attribute">clip-path</span>: <span class="built_in">polygon</span>(<span class="number">0</span> <span class="number">0</span>, <span class="number">100%</span> <span class="number">0</span>, <span class="number">100%</span> <span class="number">85%</span>, <span class="number">0</span> <span class="number">100%</span>);</span><br><span class="line">    &#125;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>_config.anzhiyu.yml调用自定义horizontal-card.css</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">inject:</span></span><br><span class="line">  <span class="attr">head:</span></span><br><span class="line">    <span class="comment"># 自定义css</span></span><br><span class="line">    <span class="string">...</span></span><br><span class="line">    <span class="bullet">-</span> <span class="string">&lt;link</span> <span class="string">rel=&quot;stylesheet&quot;</span> <span class="string">href=&quot;/cdn/css/horizontal-card.css&quot;&gt;</span></span><br></pre></td></tr></table></figure><p>_config.anzhiyu.yml中使用新的文章卡片样式，建议添加article_double_row之后</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="string">...</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 首页双栏显示</span></span><br><span class="line"><span class="attr">article_double_row:</span> <span class="literal">true</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 文章卡片样式: default | horizontal</span></span><br><span class="line"><span class="attr">home_card_style:</span> <span class="string">horizontal</span></span><br><span class="line"></span><br><span class="line"><span class="string">...</span></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%96%87%E7%AB%A0%E5%8D%A1%E7%89%87%E6%A0%B7%E5%BC%8F/">文章卡片样式</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/04/13/6fe15434/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>侧边栏添加访客信息</title>
      <link>https://blog.eucalyptus.cc/2026/04/12/378d6ae1/</link>
      <guid>https://blog.eucalyptus.cc/2026/04/12/378d6ae1/</guid>
      <pubDate>Sun, 12 Apr 2026 15:15:45 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>博客是写在网上的日记，但总有人悄悄路过。</p><p>侧边栏那个小小的卡片，它会尝试获取你的大致位置（不精确到门牌号，只是城市和距离），然后告诉博主：你离我多少公里，此刻是早安、午安还是晚安。</p><p>代码不多，但花了不少心思：多 API 降级、PJAX 兼容、距离计算、时间问候……甚至为了不泄露隐私，全程只使用公开的 IP 地理服务。</p><p>如果你是安知鱼主题的用户，可以直接照搬；如果你用其他主题，改改选择器也能用。</p><h2 id="正文"><a href="#正文" class="headerlink" title="正文"></a>正文</h2><p>文件路径</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line">blog/</span><br><span class="line">├── themes/</span><br><span class="line">│   └── anzhiyu/                    </span><br><span class="line">│       ├── layout/                 </span><br><span class="line">│       │   ├── includes/           </span><br><span class="line">│       │   │   └── widget/         </span><br><span class="line">│       │   │       └── card_welcome.pug </span><br><span class="line">│       │   │       └── index.pug                      </span><br><span class="line">├── source/                        </span><br><span class="line">│   └── cdn/                        </span><br><span class="line">│       └── css/</span><br><span class="line">│       │   └── welcome.css</span><br><span class="line">│       └── js/</span><br><span class="line">│           └── welcome.js</span><br><span class="line">└── ...                             </span><br></pre></td></tr></table></figure><p><font style="color:#000000;background-color:rgba(255, 255, 255, 0.05);">新建card_welcome.pug</font></p><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="selector-class">.card-widget</span><span class="selector-class">.card-welcome</span></span><br><span class="line">  <span class="selector-class">.card-content</span></span><br><span class="line">    <span class="selector-class">.item-headline</span></span><br><span class="line">      <span class="selector-tag">i</span><span class="selector-class">.fas</span><span class="selector-class">.fa-map-marker-alt</span></span><br><span class="line">    <span class="selector-id">#welcome-info</span>(style=&quot;<span class="attribute">min-height</span>: <span class="number">100px</span>; <span class="attribute">display</span>: flex; <span class="attribute">align-items</span>: center; <span class="attribute">justify-content</span>: center;&quot;)</span><br><span class="line">      <span class="selector-class">.loading-spinner</span></span><br><span class="line">        <span class="selector-tag">i</span><span class="selector-class">.fas</span><span class="selector-class">.fa-spinner</span><span class="selector-class">.fa-spin</span></span><br><span class="line">        |  正在定位...</span><br></pre></td></tr></table></figure><p>修改index.pug</p><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br></pre></td><td class="code"><pre><span class="line">#aside-content.<span class="property">aside</span>-content</span><br><span class="line">  <span class="comment">//- post</span></span><br><span class="line">  <span class="keyword">if</span> <span class="title function_">is_post</span>()</span><br><span class="line">    - <span class="keyword">const</span> tocStyle = page.<span class="property">toc_style_simple</span></span><br><span class="line">    - <span class="keyword">const</span> tocStyleVal = tocStyle === <span class="literal">true</span> || tocStyle === <span class="literal">false</span> ? tocStyle : theme.<span class="property">toc</span>.<span class="property">style_simple</span></span><br><span class="line">    <span class="keyword">if</span> showToc &amp;&amp; tocStyleVal</span><br><span class="line">      .<span class="property">sticky_layout</span></span><br><span class="line">        include ./card_post_toc.<span class="property">pug</span></span><br><span class="line">    <span class="keyword">else</span></span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_author&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_announcement&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      </span><br><span class="line">      <span class="comment">// 添加访客信息卡片（公告下面）</span></span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_welcome&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      </span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_weixin&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_top_self&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      .<span class="property">sticky_layout</span></span><br><span class="line">        <span class="keyword">if</span> showToc</span><br><span class="line">          include ./card_post_toc.<span class="property">pug</span></span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_recent_post&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_ad&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">  <span class="keyword">else</span></span><br><span class="line">    <span class="comment">//- page</span></span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_author&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_announcement&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">    </span><br><span class="line">    <span class="comment">// 添加访客信息卡片（公告下面）</span></span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_welcome&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">    </span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_weixin&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_top_self&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">    !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_categories&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)  </span><br><span class="line"></span><br><span class="line">    .<span class="property">sticky_layout</span></span><br><span class="line">      <span class="keyword">if</span> showToc</span><br><span class="line">        include ./card_post_toc.<span class="property">pug</span></span><br><span class="line">      .<span class="property">card</span>-widget</span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_ad&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_tags&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_archives&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">        !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_webinfo&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br><span class="line">      !=<span class="title function_">partial</span>(<span class="string">&#x27;includes/widget/card_bottom_self&#x27;</span>, &#123;&#125;, &#123;<span class="attr">cache</span>: <span class="literal">true</span>&#125;)</span><br></pre></td></tr></table></figure><p>新建welcome.js</p><figure class="highlight javascript"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">// 使用 IIFE 避免全局污染</span></span><br><span class="line">(<span class="keyword">function</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="comment">// 标记是否已经获取过 IP 信息（当前会话内只获取一次即可）</span></span><br><span class="line">    <span class="keyword">let</span> ipInfoLoaded = <span class="literal">false</span>;</span><br><span class="line">    <span class="keyword">let</span> cachedHTML = <span class="literal">null</span>;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> <span class="title function_">fetchIpInfo</span> = <span class="keyword">async</span> (<span class="params"></span>) =&gt; &#123;</span><br><span class="line">        <span class="keyword">const</span> welcomeInfo = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(<span class="string">&#x27;#welcome-info&#x27;</span>);</span><br><span class="line">        <span class="keyword">if</span> (!welcomeInfo) <span class="keyword">return</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 如果已经加载过，直接恢复缓存的内容</span></span><br><span class="line">        <span class="keyword">if</span> (ipInfoLoaded &amp;&amp; cachedHTML) &#123;</span><br><span class="line">            welcomeInfo.<span class="property">innerHTML</span> = cachedHTML;</span><br><span class="line">            <span class="keyword">return</span>;</span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 显示加载状态</span></span><br><span class="line">        welcomeInfo.<span class="property">innerHTML</span> = <span class="string">&#x27;&lt;div class=&quot;loading&quot;&gt;&lt;i class=&quot;fas fa-spinner fa-spin&quot;&gt;&lt;/i&gt; 定位中...&lt;/div&gt;&#x27;</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 备用 API 列表（ipinfo.io 在国内可能被拦截，放在后面）</span></span><br><span class="line">        <span class="keyword">const</span> apis = [</span><br><span class="line">            &#123; </span><br><span class="line">                <span class="attr">url</span>: <span class="string">&#x27;https://api.ip.sb/geoip&#x27;</span>, </span><br><span class="line">                <span class="attr">parser</span>: <span class="function">(<span class="params">d</span>) =&gt;</span> (&#123;</span><br><span class="line">                    <span class="attr">country</span>: d.<span class="property">country</span>,</span><br><span class="line">                    <span class="attr">region</span>: d.<span class="property">region</span>,</span><br><span class="line">                    <span class="attr">city</span>: d.<span class="property">city</span>,</span><br><span class="line">                    <span class="attr">loc</span>: d.<span class="property">latitude</span> &amp;&amp; d.<span class="property">longitude</span> ? <span class="string">`<span class="subst">$&#123;d.latitude&#125;</span>,<span class="subst">$&#123;d.longitude&#125;</span>`</span> : <span class="literal">null</span></span><br><span class="line">                &#125;)</span><br><span class="line">            &#125;,</span><br><span class="line">            &#123;</span><br><span class="line">                <span class="attr">url</span>: <span class="string">&#x27;https://ipapi.co/json/&#x27;</span>,</span><br><span class="line">                <span class="attr">parser</span>: <span class="function">(<span class="params">d</span>) =&gt;</span> (&#123;</span><br><span class="line">                    <span class="attr">country</span>: d.<span class="property">country_code</span>,</span><br><span class="line">                    <span class="attr">region</span>: d.<span class="property">region</span>,</span><br><span class="line">                    <span class="attr">city</span>: d.<span class="property">city</span>,</span><br><span class="line">                    <span class="attr">loc</span>: d.<span class="property">latitude</span> &amp;&amp; d.<span class="property">longitude</span> ? <span class="string">`<span class="subst">$&#123;d.latitude&#125;</span>,<span class="subst">$&#123;d.longitude&#125;</span>`</span> : <span class="literal">null</span></span><br><span class="line">                &#125;)</span><br><span class="line">            &#125;,</span><br><span class="line">            &#123;</span><br><span class="line">                <span class="attr">url</span>: <span class="string">&#x27;https://ipinfo.io/json&#x27;</span>,</span><br><span class="line">                <span class="attr">parser</span>: <span class="function">(<span class="params">d</span>) =&gt;</span> (&#123;</span><br><span class="line">                    <span class="attr">country</span>: d.<span class="property">country</span>,</span><br><span class="line">                    <span class="attr">region</span>: d.<span class="property">region</span>,</span><br><span class="line">                    <span class="attr">city</span>: d.<span class="property">city</span>,</span><br><span class="line">                    <span class="attr">loc</span>: d.<span class="property">loc</span></span><br><span class="line">                &#125;)</span><br><span class="line">            &#125;</span><br><span class="line">        ];</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">let</span> data = <span class="literal">null</span>;</span><br><span class="line">        </span><br><span class="line">        <span class="keyword">for</span> (<span class="keyword">const</span> api <span class="keyword">of</span> apis) &#123;</span><br><span class="line">            <span class="keyword">try</span> &#123;</span><br><span class="line">                <span class="keyword">const</span> controller = <span class="keyword">new</span> <span class="title class_">AbortController</span>();</span><br><span class="line">                <span class="keyword">const</span> timeout = <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> controller.<span class="title function_">abort</span>(), <span class="number">3000</span>);</span><br><span class="line">                </span><br><span class="line">                <span class="keyword">const</span> res = <span class="keyword">await</span> <span class="title function_">fetch</span>(api.<span class="property">url</span>, &#123; </span><br><span class="line">                    <span class="attr">signal</span>: controller.<span class="property">signal</span>,</span><br><span class="line">                    <span class="attr">headers</span>: &#123; <span class="string">&#x27;Accept&#x27;</span>: <span class="string">&#x27;application/json&#x27;</span> &#125;</span><br><span class="line">                &#125;);</span><br><span class="line">                <span class="built_in">clearTimeout</span>(timeout);</span><br><span class="line">                </span><br><span class="line">                <span class="keyword">if</span> (res.<span class="property">ok</span>) &#123;</span><br><span class="line">                    <span class="keyword">const</span> raw = <span class="keyword">await</span> res.<span class="title function_">json</span>();</span><br><span class="line">                    data = api.<span class="title function_">parser</span>(raw);</span><br><span class="line">                    <span class="keyword">break</span>;</span><br><span class="line">                &#125;</span><br><span class="line">            &#125; <span class="keyword">catch</span> (e) &#123;</span><br><span class="line">                <span class="keyword">continue</span>;</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;</span><br><span class="line">        </span><br><span class="line">        <span class="comment">// 渲染内容</span></span><br><span class="line">        <span class="keyword">if</span> (data) &#123;</span><br><span class="line">            <span class="keyword">const</span> &#123; country, region, city, loc &#125; = data;</span><br><span class="line">            <span class="keyword">const</span> [lat, lng] = loc ? loc.<span class="title function_">split</span>(<span class="string">&#x27;,&#x27;</span>).<span class="title function_">map</span>(<span class="title class_">Number</span>) : [];</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> myLat = <span class="number">31.707754</span>;</span><br><span class="line">            <span class="keyword">const</span> myLng = <span class="number">119.825873</span>;</span><br><span class="line">            <span class="keyword">const</span> dist = (lat &amp;&amp; lng) ? <span class="title function_">calculateDistance</span>(lng, lat, myLng, myLat) : <span class="literal">null</span>;</span><br><span class="line">            </span><br><span class="line">            <span class="keyword">const</span> location = country === <span class="string">&quot;CN&quot;</span> || country === <span class="string">&quot;China&quot;</span> </span><br><span class="line">                ? <span class="string">`<span class="subst">$&#123;region || <span class="string">&#x27;&#x27;</span>&#125;</span> <span class="subst">$&#123;city || <span class="string">&#x27;&#x27;</span>&#125;</span>`</span>.<span class="title function_">trim</span>() </span><br><span class="line">                : (country || <span class="string">&#x27;地球&#x27;</span>);</span><br><span class="line">            </span><br><span class="line">            cachedHTML = <span class="string">`</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;welcome-content&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p&gt;欢迎来自 &lt;span class=&quot;location&quot;&gt;<span class="subst">$&#123;location || <span class="string">&#x27;神秘星球&#x27;</span>&#125;</span>&lt;/span&gt; 的道友 💖&lt;/p&gt;</span></span><br><span class="line"><span class="string">                    <span class="subst">$&#123;dist ? <span class="string">`&lt;p&gt;距博主约 &lt;span class=&quot;distance&quot;&gt;<span class="subst">$&#123;dist&#125;</span>&lt;/span&gt; 公里&lt;/p&gt;`</span> : <span class="string">&#x27;&#x27;</span>&#125;</span></span></span><br><span class="line"><span class="string">                    &lt;p class=&quot;greeting&quot;&gt;<span class="subst">$&#123;getTimeGreeting()&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            `</span>;</span><br><span class="line">            ipInfoLoaded = <span class="literal">true</span>;</span><br><span class="line">            welcomeInfo.<span class="property">innerHTML</span> = cachedHTML;</span><br><span class="line">        &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">            cachedHTML = <span class="string">`</span></span><br><span class="line"><span class="string">                &lt;div class=&quot;welcome-content&quot;&gt;</span></span><br><span class="line"><span class="string">                    &lt;p&gt;🎉 欢迎来到我的博客！&lt;/p&gt;</span></span><br><span class="line"><span class="string">                    &lt;p class=&quot;greeting&quot;&gt;<span class="subst">$&#123;getTimeGreeting()&#125;</span>&lt;/p&gt;</span></span><br><span class="line"><span class="string">                &lt;/div&gt;</span></span><br><span class="line"><span class="string">            `</span>;</span><br><span class="line">            ipInfoLoaded = <span class="literal">true</span>;</span><br><span class="line">            welcomeInfo.<span class="property">innerHTML</span> = cachedHTML;</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> <span class="title function_">calculateDistance</span> = (<span class="params">lng1, lat1, lng2, lat2</span>) =&gt; &#123;</span><br><span class="line">        <span class="keyword">if</span> (!lat1 || !lng1 || !lat2 || !lng2) <span class="keyword">return</span> <span class="literal">null</span>;</span><br><span class="line">        <span class="keyword">const</span> R = <span class="number">6371</span>;</span><br><span class="line">        <span class="keyword">const</span> rad = <span class="title class_">Math</span>.<span class="property">PI</span> / <span class="number">180</span>;</span><br><span class="line">        <span class="keyword">const</span> dLat = (lat2 - lat1) * rad;</span><br><span class="line">        <span class="keyword">const</span> dLon = (lng2 - lng1) * rad;</span><br><span class="line">        <span class="keyword">const</span> a = <span class="title class_">Math</span>.<span class="title function_">sin</span>(dLat/<span class="number">2</span>) ** <span class="number">2</span> + <span class="title class_">Math</span>.<span class="title function_">cos</span>(lat1 * rad) * <span class="title class_">Math</span>.<span class="title function_">cos</span>(lat2 * rad) * <span class="title class_">Math</span>.<span class="title function_">sin</span>(dLon/<span class="number">2</span>) ** <span class="number">2</span>;</span><br><span class="line">        <span class="keyword">return</span> <span class="title class_">Math</span>.<span class="title function_">round</span>(R * <span class="number">2</span> * <span class="title class_">Math</span>.<span class="title function_">atan2</span>(<span class="title class_">Math</span>.<span class="title function_">sqrt</span>(a), <span class="title class_">Math</span>.<span class="title function_">sqrt</span>(<span class="number">1</span>-a)));</span><br><span class="line">    &#125;;</span><br><span class="line"></span><br><span class="line">    <span class="keyword">const</span> <span class="title function_">getTimeGreeting</span> = (<span class="params"></span>) =&gt; &#123;</span><br><span class="line">        <span class="keyword">const</span> hour = <span class="keyword">new</span> <span class="title class_">Date</span>().<span class="title function_">getHours</span>();</span><br><span class="line">        <span class="keyword">if</span> (hour &lt; <span class="number">6</span>) <span class="keyword">return</span> <span class="string">&quot;It&#x27;s late, pay attention to rest 🌙&quot;</span>;</span><br><span class="line">        <span class="keyword">if</span> (hour &lt; <span class="number">12</span>) <span class="keyword">return</span> <span class="string">&quot;Good morning, start your day. ☀️&quot;</span>;</span><br><span class="line">        <span class="keyword">if</span> (hour &lt; <span class="number">18</span>) <span class="keyword">return</span> <span class="string">&quot;Good afternoon. Good work. ☕&quot;</span>;</span><br><span class="line">        <span class="keyword">return</span> <span class="string">&quot;Good evening. May you have a good mood. 🌆&quot;</span>;</span><br><span class="line">    &#125;;</span><br><span class="line"></span><br><span class="line">    <span class="comment">// ===== 初始化策略 =====</span></span><br><span class="line">    </span><br><span class="line">    <span class="comment">// 1. 首次加载</span></span><br><span class="line">    <span class="keyword">if</span> (<span class="variable language_">document</span>.<span class="property">readyState</span> === <span class="string">&#x27;loading&#x27;</span>) &#123;</span><br><span class="line">        <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;DOMContentLoaded&#x27;</span>, fetchIpInfo);</span><br><span class="line">    &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">        <span class="title function_">fetchIpInfo</span>();</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="comment">// 2. 安知鱼主题 PJAX 事件（关键）</span></span><br><span class="line">    <span class="comment">// 安知鱼使用 pjax:complete，但 footer 不刷新，所以需要手动恢复内容</span></span><br><span class="line">    <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;pjax:complete&#x27;</span>, <span class="function">() =&gt;</span> &#123;</span><br><span class="line">        <span class="comment">// PJAX 完成后，检查 welcome-info 是否存在</span></span><br><span class="line">        <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> welcomeInfo = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(<span class="string">&#x27;#welcome-info&#x27;</span>);</span><br><span class="line">            <span class="keyword">if</span> (welcomeInfo) &#123;</span><br><span class="line">                <span class="keyword">if</span> (cachedHTML &amp;&amp; ipInfoLoaded) &#123;</span><br><span class="line">                    <span class="comment">// 已经有缓存，直接恢复</span></span><br><span class="line">                    welcomeInfo.<span class="property">innerHTML</span> = cachedHTML;</span><br><span class="line">                &#125; <span class="keyword">else</span> &#123;</span><br><span class="line">                    <span class="comment">// 首次或缓存丢失，重新获取</span></span><br><span class="line">                    <span class="title function_">fetchIpInfo</span>();</span><br><span class="line">                &#125;</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;, <span class="number">100</span>); <span class="comment">// 延迟确保 DOM 已更新</span></span><br><span class="line">    &#125;);</span><br><span class="line"></span><br><span class="line">    <span class="comment">// 3. 浏览器前进/后退按钮</span></span><br><span class="line">    <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;popstate&#x27;</span>, <span class="function">() =&gt;</span> &#123;</span><br><span class="line">        <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">            <span class="keyword">const</span> welcomeInfo = <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(<span class="string">&#x27;#welcome-info&#x27;</span>);</span><br><span class="line">            <span class="keyword">if</span> (welcomeInfo &amp;&amp; cachedHTML &amp;&amp; ipInfoLoaded) &#123;</span><br><span class="line">                welcomeInfo.<span class="property">innerHTML</span> = cachedHTML;</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;, <span class="number">100</span>);</span><br><span class="line">    &#125;);</span><br><span class="line"></span><br><span class="line">&#125;)();</span><br></pre></td></tr></table></figure><p>新建welcome.css</p><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br></pre></td><td class="code"><pre><span class="line"><span class="selector-class">.card-welcome</span> <span class="selector-class">.item-headline</span> <span class="selector-tag">i</span> &#123;</span><br><span class="line">    <span class="attribute">color</span>: <span class="number">#4dabf7</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-id">#welcome-info</span> &#123;</span><br><span class="line">    <span class="attribute">color</span>: <span class="built_in">var</span>(--anzhiyu-fontcolor);</span><br><span class="line">    <span class="attribute">text-align</span>: center;</span><br><span class="line">    <span class="attribute">padding</span>: <span class="number">15px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-id">#welcome-info</span> <span class="selector-class">.loading</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">14px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-id">#welcome-info</span> <span class="selector-class">.loading</span> <span class="selector-tag">i</span> &#123;</span><br><span class="line">    <span class="attribute">margin-right</span>: <span class="number">8px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-class">.welcome-content</span> <span class="selector-class">.location</span> &#123;</span><br><span class="line">    <span class="attribute">color</span>: <span class="number">#ffd700</span>;</span><br><span class="line">    <span class="attribute">font-weight</span>: bold;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">16px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-class">.welcome-content</span> <span class="selector-class">.distance</span> &#123;</span><br><span class="line">    <span class="attribute">color</span>: <span class="number">#4dabf7</span>;</span><br><span class="line">    <span class="attribute">font-weight</span>: bold;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-class">.welcome-content</span> <span class="selector-class">.ip-address</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">12px</span>;</span><br><span class="line">    <span class="attribute">opacity</span>: <span class="number">0.7</span>;</span><br><span class="line">    <span class="attribute">margin-top</span>: <span class="number">5px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  </span><br><span class="line">  <span class="selector-class">.card-welcome</span> <span class="selector-class">.welcome-content</span> <span class="selector-class">.greeting</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">14px</span>;</span><br><span class="line">    <span class="attribute">line-height</span>: <span class="number">1.5</span>;</span><br><span class="line">    <span class="attribute">opacity</span>: <span class="number">0.95</span>;</span><br><span class="line">    <span class="attribute">letter-spacing</span>: <span class="number">0.3px</span>;</span><br><span class="line">  &#125;</span><br></pre></td></tr></table></figure><p><font style="color:rgb(76, 73, 72);background-color:rgba(255, 255, 255, 0.9);">_config.anzhiyu.yml 调用自定义 welcome.css和welcome.js</font></p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">inject:</span></span><br><span class="line">  <span class="attr">head:</span></span><br><span class="line">    <span class="comment"># 自定义css</span></span><br><span class="line">    <span class="string">...</span></span><br><span class="line">    <span class="bullet">-</span> <span class="string">&lt;link</span> <span class="string">rel=&quot;stylesheet&quot;</span> <span class="string">href=&quot;/cdn/css/welcome.css&quot;&gt;</span></span><br><span class="line">    <span class="string">...</span></span><br><span class="line"> </span><br><span class="line">  <span class="attr">bottom:</span></span><br><span class="line">    <span class="comment"># 自定义js</span></span><br><span class="line">    <span class="string">...</span></span><br><span class="line">    <span class="bullet">-</span> <span class="string">&lt;script</span> <span class="string">defer</span> <span class="string">src=&quot;/cdn/js/welcome.js&quot;&gt;&lt;/script&gt;</span></span><br><span class="line">    <span class="string">...</span></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E4%BE%A7%E8%BE%B9%E6%A0%8F/">侧边栏</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/04/12/378d6ae1/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL 16.3中复制槽的配置</title>
      <link>https://blog.eucalyptus.cc/2026/04/02/630c30a3/</link>
      <guid>https://blog.eucalyptus.cc/2026/04/02/630c30a3/</guid>
      <pubDate>Thu, 02 Apr 2026 08:52:43 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h3&gt;&lt;p&gt;复制槽（Replication Slot）是数据库（如</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h3><p>复制槽（Replication Slot）是数据库（如 PostgreSQL）中用于保障主从复制数据一致性与安全性的核心机制，它通过在主库上为每个从库建立一个持久的状态记录点，强制主库保留该从库尚未确认接收的 WAL（预写日志），从而防止因日志过早被清理而导致从库断连后无法继续同步；简单来说，它就像一根”安全绳”，确保即使从库长时间离线或网络中断，重新连接后也能无缝续传缺失的数据，避免主从数据出现不可修复的断层。</p><p>流复制的配置不在做过多的缀述，直接基于之前搭建的流式复制配置复制槽。</p><h3 id="配置"><a href="#配置" class="headerlink" title="配置"></a>配置</h3><p>首先在主库上创建物理复制槽</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#创建</span><br><span class="line"></span><br><span class="line"><span class="keyword">select</span> pg_create_physical_replication_slot(<span class="string">&#x27;demo_slot&#x27;</span>, <span class="literal">true</span>);</span><br><span class="line"></span><br><span class="line">#查询</span><br><span class="line"></span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> pg_replication_slots;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-04-02/img1.avif"></p><p>然后再去备库配置连接信息，由于使用的是 PostgreSQL 16.3 的搭建的流式复制，故直接在postgresql.auto.conf中配置</p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#在postgresql.auto.conf中添加</span></span><br><span class="line"></span><br><span class="line"><span class="attr">primary_slot_name</span> = <span class="string">&#x27;demo_slot&#x27;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-04-02/img2.avif"></p><p>最后重启备库后，在主库查看slot的状态，active&#x3D;true的话说明slot已经被激活</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2026-04-02/img3.avif"></p><h3 id="复制槽字段详解"><a href="#复制槽字段详解" class="headerlink" title="复制槽字段详解"></a>复制槽字段详解</h3><table><thead><tr><th>字段名</th><th>含义与解释</th></tr></thead><tbody><tr><td>slot_name</td><td>槽的名称。这是你创建槽时指定的唯一标识符，例如你的 demo_slot 在配置主从连接 (primary_slot_name) 时会用到它。</td></tr><tr><td>plugin</td><td>插件名称。如果是物理复制 (Physical)，此值为 null；如果是逻辑复制 (Logical)，这里会显示使用的输出插件名，如 pgoutput, test_decoding 等。</td></tr><tr><td>slot_type</td><td>槽的类型。physical: 用于流复制备库（Standby）；logical: 用于逻辑解码或逻辑订阅（Logical Subscription）。</td></tr><tr><td>datoid</td><td>数据库 OID。仅对逻辑复制槽有效，表示该槽关联的数据库 ID。物理复制槽与此无关，所以是 null。</td></tr><tr><td>database</td><td>数据库名称。同上，仅对逻辑复制槽有效，显示关联的数据库名。</td></tr><tr><td>temporary</td><td>是否为临时槽。True: 临时槽，当创建它的会话结束时自动删除；False: 持久化槽，重启后依然存在（你的 demo_slot 就是这种）。</td></tr><tr><td>active</td><td>是否活跃。True: 表示有一个备库或客户端正连接并使用这个槽（你的情况）；False: 槽存在但没人用。如果长期为 False，说明备库断连了，需要检查网络或配置。</td></tr><tr><td>active_pid</td><td>活跃进程的 PID。显示主库上哪个后端进程（Walsender）正在服务这个槽。可以用 SELECT * FROM pg_stat_activity WHERE pid &#x3D; 79803; 查看该进程详情。</td></tr><tr><td>xmin</td><td>事务 ID 下限。仅对逻辑复制槽有意义。表示为了防止逻辑解码所需的事务快照被清理，系统必须保留的最早事务 ID。物理复制槽通常为 null。</td></tr><tr><td>catalog_xmin</td><td>目录事务 ID 下限。仅对逻辑复制槽有意义。类似 xmin，但是针对系统目录表的变更。</td></tr><tr><td>restart_lsn</td><td>重启 LSN (Log Sequence Number) 这是物理复制最重要的字段。它表示：”从这个位置开始的 WAL 日志，我都还没确认备库收到了，所以主库绝对不能删除这些日志”。随着备库不断确认接收，这个值会向后推进。</td></tr><tr><td>confirmed_flush_lsn</td><td>已确认刷新的 LSN。仅对逻辑复制有效。表示逻辑订阅者已经成功处理并重放到的位置。物理复制槽此值为 null。</td></tr><tr><td>wal_status</td><td>WAL 日志状态。reserved: 正常状态，表示槽正在保留 WAL 日志；lost: 警告状态！表示槽需要的 WAL 日志已经被主库清理掉了，复制将中断，需要重新做基础备份。</td></tr><tr><td>safe_wal_size</td><td>安全的 WAL 大小。估算值，表示在当前状态下，主库还能安全地生成多少 WAL 日志而不会触发 wal_status &#x3D; ‘lost’。如果这个值变成负数，说明已经很危险了。</td></tr><tr><td>two_phase</td><td>是否支持两阶段提交。仅对逻辑复制槽有效。如果为 True，表示该槽可以复制两阶段提交（PREPARE TRANSACTION）的事务。</td></tr><tr><td>conflicting</td><td>是否存在冲突。仅对逻辑复制槽有效。如果在解码过程中遇到无法解决的冲突（比如表结构不一致），这里会标记为 True。</td></tr></tbody></table>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/04/02/630c30a3/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL基础命令</title>
      <link>https://blog.eucalyptus.cc/2026/04/02/d02aa65a/</link>
      <guid>https://blog.eucalyptus.cc/2026/04/02/d02aa65a/</guid>
      <pubDate>Thu, 02 Apr 2026 08:47:08 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;常用命令说明&quot;&gt;&lt;a href=&quot;#常用命令说明&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="常用命令说明"><a href="#常用命令说明" class="headerlink" title="常用命令说明"></a>常用命令说明</h3><table><thead><tr><th>序号</th><th>功能</th><th>命令</th></tr></thead><tbody><tr><td>1</td><td>列出所有数据库</td><td>\l</td></tr><tr><td>2</td><td>列出数据库中所有的表</td><td>\d</td></tr><tr><td>3</td><td>显示指定表的结构</td><td>\d table_name</td></tr><tr><td>4</td><td>列出所有的帮助命令</td><td>?</td></tr><tr><td>5</td><td>列出数据库中所有的索引</td><td>\di</td></tr><tr><td>6</td><td>列出数据库中所有的view</td><td>\dv</td></tr><tr><td>7</td><td>sql命令帮助</td><td>\h</td></tr><tr><td>8</td><td>退出连接</td><td>\q</td></tr><tr><td>9</td><td>切换到指定的数据库</td><td>\c [database_name]</td></tr><tr><td>10</td><td>显示当前数据库和用户</td><td>\c</td></tr><tr><td>11</td><td>显示客户端的连接信息</td><td>\conninfo</td></tr><tr><td>12</td><td>显示所有用户</td><td>\du</td></tr><tr><td>13</td><td>显示数据库中的schema</td><td>\dn</td></tr><tr><td>14</td><td>显示字符集</td><td>\encoding</td></tr><tr><td>15</td><td>执行sql文件</td><td>\i mydb.sql</td></tr><tr><td>16</td><td>扩展展示信息，相当于MySQL中的\G</td><td>\x</td></tr><tr><td>17</td><td>将下一条sql执行结果导入文件中</td><td>\o &#x2F;opt&#x2F;test.txt</td></tr></tbody></table><h4 id="进阶命令"><a href="#进阶命令" class="headerlink" title="进阶命令"></a>进阶命令</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#查看复制状态，master执行</span><br><span class="line"></span><br><span class="line"><span class="keyword">select</span> client_addr, state, sent_lsn, flush_lsn, sync_state <span class="keyword">from</span> pg_stat_replication;</span><br><span class="line"></span><br><span class="line">#查看延迟，slave执行</span><br><span class="line"></span><br><span class="line"><span class="keyword">select</span> pg_last_wal_receive_lsn(), pg_last_wal_replay_lsn();</span><br></pre></td></tr></table></figure><h3 id="登陆命令"><a href="#登陆命令" class="headerlink" title="登陆命令"></a>登陆命令</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">psql -h 172.16.0.2 -p 5432 -U postgres -d 数据库名 -W</span><br></pre></td></tr></table></figure><ul><li><code>-h</code> 数据库所在的IP地址</li><li><code>-p</code> （默认5432）数据库的监听端口</li><li><code>-U</code> 用户名</li><li><code>-d</code> 数据库名称</li><li><code>-W</code> 指示 psql 命令在连接数据库时强制提示输入密码</li></ul><h3 id="PG状态管理"><a href="#PG状态管理" class="headerlink" title="PG状态管理"></a>PG状态管理</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">pg_ctl start/status/stop</span><br><span class="line"></span><br><span class="line">systemctl start/status/stop postgresql-16</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/04/02/d02aa65a/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker部署兰空图床并开启AVIF支持</title>
      <link>https://blog.eucalyptus.cc/2026/03/09/26e23449/</link>
      <guid>https://blog.eucalyptus.cc/2026/03/09/26e23449/</guid>
      <pubDate>Mon, 09 Mar 2026 07:55:07 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;部署&quot;&gt;&lt;a href=&quot;#部署&quot; class=&quot;headerlink&quot; title=&quot;部署&quot;&gt;&lt;/a&gt;部署&lt;/h3&gt;&lt;p&gt;Lsky</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="部署"><a href="#部署" class="headerlink" title="部署"></a>部署</h3><p>Lsky Pro（兰空图床）是一个基于PHP语言的现代图片管理系统，它依赖于特定的PHP扩展和数据库环境。为了规避手动配置LNMP环境可能出现的兼容性问题，并实现服务的快速上线与迁移，本次实践将采用 <strong>Docker Compose</strong> 进行编排部署。</p><p>下面我们直接使用宝塔部署，也可以自行使用命令行部署</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img1.avif"></p><p>docker-compose文件内容</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">services:</span></span><br><span class="line">  <span class="attr">lsky-pro:</span></span><br><span class="line">    <span class="attr">container_name:</span> <span class="string">lsky-pro</span></span><br><span class="line">    <span class="attr">image:</span> <span class="string">dko0/lsky-pro</span></span><br><span class="line">    <span class="attr">restart:</span> <span class="string">always</span></span><br><span class="line">    <span class="attr">volumes:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">./data/html:/var/www/html</span> <span class="comment">#映射到本地</span></span><br><span class="line">    <span class="attr">ports:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">$&#123;PORT_1&#125;:80</span></span><br><span class="line">    <span class="attr">environment:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_HOST=mysql</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_DATABASE=$&#123;MYSQL_DATABASE&#125;</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_USER=$&#123;MYSQL_USER&#125;</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_PASSWORD=$&#123;MYSQL_PASSWORD&#125;</span></span><br><span class="line">  <span class="attr">mysql:</span></span><br><span class="line">    <span class="attr">image:</span> <span class="string">mysql:5.7</span></span><br><span class="line">    <span class="attr">container_name:</span> <span class="string">lsky-pro-db</span></span><br><span class="line">    <span class="attr">restart:</span> <span class="string">always</span></span><br><span class="line">    <span class="attr">environment:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_DATABASE=$&#123;MYSQL_DATABASE&#125;</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_USER=$&#123;MYSQL_USER&#125;</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_PASSWORD=$&#123;MYSQL_PASSWORD&#125;</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">MYSQL_ROOT_PASSWORD=$&#123;MYSQL_PASSWORD&#125;</span></span><br><span class="line">    <span class="attr">volumes:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">./data/db:/var/lib/mysql</span></span><br><span class="line">    <span class="attr">ports:</span></span><br><span class="line">      <span class="bullet">-</span> <span class="string">$&#123;PORT_2&#125;:3306</span></span><br></pre></td></tr></table></figure><p>.env</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">MYSQL_DATABASE=lsky</span><br><span class="line">MYSQL_USER=lsky</span><br><span class="line">MYSQL_PASSWORD=lsky</span><br><span class="line">MYSQL_ROOT_PASSWORD=lsky</span><br><span class="line">PORT_1=7791</span><br><span class="line">PORT_2=3389</span><br><span class="line">LSKY_PATH=/www/dk_project/dk_app/dk_lsky</span><br></pre></td></tr></table></figure><p>在完成所有配置和部署步骤之后，您可以通过服务器的公网域名加上指定的端口号来访问您的应用程序或服务。例如，如果您的公网ip为 <code>192.168.0.2</code>，并且您设置的服务监听在 7791 端口上，那么您就可以通过在浏览器中输入 <code>http://192.168.0.2:7791</code> 来访问该服务。请确保您的防火墙规则允许外部流量到达所使用的端口。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img2.avif"></p><p>下面的内容和.env中的对应即可</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img4.avif"></p><h3 id="avif格式支持"><a href="#avif格式支持" class="headerlink" title="avif格式支持"></a>avif格式支持</h3><p>Lsky Pro本身功能强大，通过Docker容器化部署也极为便捷，但其默认的图片处理逻辑并未开放AVIF格式的上传权限。接下来，我们会通过代码层面的调整，使其兼容AVIF这一前沿图像格式。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#进入容器，更新仓库，然后安装vim</span></span><br><span class="line">docker <span class="built_in">exec</span> -it lsky-pro bash</span><br><span class="line">apt update</span><br><span class="line">apt install -y vim</span><br></pre></td></tr></table></figure><p>由于 AVIF 格式较新，部分图片处理功能（如水印、压缩、审核等）可能无法正常工作，因此需要在代码中跳过这些处理步骤。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">vim config/convention.php</span><br><span class="line"><span class="comment"># 找到第 109 行，在数组中添加 &#x27;avif&#x27;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img5.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">vim app/Http/Requests/Admin/GroupRequest.php</span><br><span class="line"><span class="comment"># 找到第 41 行，添加 avif</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img6.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">vim app/Services/ImageService.php</span><br><span class="line"><span class="comment">#第 159 行左右，在跳过处理的数组中添加 &#x27;avif&#x27;：</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img7.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">vim app/Services/ImageService.php</span><br><span class="line"><span class="comment">#第 253 行左右，在图片检测跳过的数组中添加 &#x27;avif&#x27;：</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img8.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">vim app/Http/Controllers/Controller.php</span><br><span class="line"><span class="comment">#第 168 行左右，在水印判断中添加 &#x27;avif&#x27;：</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img9.avif"></p><figure class="highlight php"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">vim app/Http/Controllers/Controller.php</span><br><span class="line"><span class="comment">// ico 图片直接输出，不经过 InterventionImage 处理</span></span><br><span class="line"><span class="keyword">if</span> (<span class="title function_ invoke__">in_array</span>(<span class="variable">$image</span>-&gt;extension, [<span class="string">&#x27;ico&#x27;</span>, <span class="string">&#x27;avif&#x27;</span>])) &#123;</span><br><span class="line">    <span class="keyword">goto</span> out;</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img10.avif"></p><p>修改完成后，在后台的角色组设置中勾选 AVIF 格式即可启用</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img11.avif"></p><p>然后便可上传avif格式图片</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2026-03-09/img12.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/03/09/26e23449/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中常见的慢查询与优化</title>
      <link>https://blog.eucalyptus.cc/2026/03/05/7b98aaac/</link>
      <guid>https://blog.eucalyptus.cc/2026/03/05/7b98aaac/</guid>
      <pubDate>Thu, 05 Mar 2026 03:45:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;explain执行计划详解&lt;/p&gt;
&lt;h3 id=&quot;没有将等值条件列用做组合索引前缀&quot;&gt;&lt;a href=&quot;#没有将等值条件列用做组合索引前缀&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>explain执行计划详解</p><h3 id="没有将等值条件列用做组合索引前缀"><a href="#没有将等值条件列用做组合索引前缀" class="headerlink" title="没有将等值条件列用做组合索引前缀"></a>没有将等值条件列用做组合索引前缀</h3><p>如果查询语句的谓词条件是范围条件与等值条件,存在组合索引,那么当范围条件列作为索引前缀的时候,等值条件是无法被range optimizer用来生成引擎扫描range减少扫描行数的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img1.avif"></p><p>查看optimize trace中的 potential_range_indexes 可以看到表中的三个联合索引都被标记是可用的,排除了主键索引</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img2.avif"></p><p>在往下看 analyzing_range_alternatives 中的 range_scan_alternatives 可以看到 index : id_num_name_index 被淘汰,而 index : num_name_index 和 index : name_num_index 被标记可。,但是 index : num_name_index 扫描 rows : 220, cost : 77.26,而 index : name_num_index 扫描 rows : 5, cost : 2.01</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img3.avif"></p><p>再往下看,可以看到 considered_execution_plans 这里选择了 used_index : name_num_index</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img4.avif"></p><h3 id="索引列类型和常量类型不一致"><a href="#索引列类型和常量类型不一致" class="headerlink" title="索引列类型和常量类型不一致"></a>索引列类型和常量类型不一致</h3><p>当索引列类型和常量类型不一致的时候,可能导致索引无法使用。例如下面的例子,列类型是varchar,而常量类型是Int。在MySQL中varchar类型和int类型比较是会将varchar转换为int类型去比较,这就导致下面语句需要扫描每一行数据将id转换为int类型再做比较。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img5.avif"></p><h3 id="关联字段类型不一致"><a href="#关联字段类型不一致" class="headerlink" title="关联字段类型不一致"></a>关联字段类型不一致</h3><p>对于JOIN操作,如果关联字段类型不一样,比如一个是Int,一个是varchar,由于比较类型是Int,那么varchar字段的关联索引就无法用来生成REF访问,减少扫描行数。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img6.avif"></p><h3 id="关联字段字符集不一致"><a href="#关联字段字符集不一致" class="headerlink" title="关联字段字符集不一致"></a>关联字段字符集不一致</h3><p>对于JOIN操作,如果关联字段的字符集不一致,这也会导致索引无法被有效利用,进而导致扫描大量数据,查询执行慢。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img7.avif"></p><h3 id="索引列上有表达式计算"><a href="#索引列上有表达式计算" class="headerlink" title="索引列上有表达式计算"></a>索引列上有表达式计算</h3><p>当谓词条件中,索引列上有表达式计算的时候,优化器会无法分析抽取range</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img10.avif"></p><h3 id="range-optimizer限制"><a href="#range-optimizer限制" class="headerlink" title="range optimizer限制"></a>range optimizer限制</h3><p>索引的扫描范围分析是由range optimizer处理,一些场景会触发range optimizer的限制。例如in list或者or的条件数太多,在分析扫描范围区间的时候,会消耗大量内存,导致超过range_optimizer_max_mem_size的大小,这类语句EXPLAIN后,在warnings信息中会有提示:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">***************************[ 1. row ]***************************</span><br><span class="line">Level | Warning</span><br><span class="line">Code | 3170</span><br><span class="line">Message | Memory capacity of 5 bytes <span class="keyword">for</span> <span class="string">&#x27;range_optimizer_max_mem_size&#x27;</span> exceeded. Range optimization was not <span class="keyword">done</span> <span class="keyword">for</span> this query.</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-05/img11.avif"></p><p>在 MySQL 中,<code>range_optimizer_max_mem_size</code> 是一个系统变量,用于控制查询优化器在执行查询时可以使用的最大内存大小。这个参数影响查询优化器在处理范围查询 如 <code>BETWEEN</code>、<code>IN</code> 等 时的行为,特别是当这些查询涉及多个表和大量数据时。</p><h4 id="参数作用"><a href="#参数作用" class="headerlink" title="参数作用"></a>参数作用</h4><ul><li><strong>内存使用</strong>:<code>range_optimizer_max_mem_size</code> 指定了查询优化器在处理范围查询时可以使用的最大内存量。如果查询的内存需求超过了这个限制,优化器将尝试使用其他方法来处理查询,例如将范围查询转换为全表扫描。</li></ul><h4 id="参数值"><a href="#参数值" class="headerlink" title="参数值"></a>参数值</h4><ul><li><strong>默认值</strong>:默认值通常为 1MB 1024MB ,这意味着查询优化器在处理范围查询时最多可以使用 1MB 的内存。</li><li><strong>调整</strong>:你可以根据服务器的内存大小和查询的复杂性来调整这个值。增加这个值可以让查询优化器在处理更复杂的范围查询时有更多的内存可用,但也可能增加内存消耗。</li></ul><h3 id="Range-optimizer跳过index-dive"><a href="#Range-optimizer跳过index-dive" class="headerlink" title="Range optimizer跳过index dive*"></a>Range optimizer跳过index dive*</h3><p>对于索引范围,range optimizer会通过index dive来估算实际扫描行数。由于这会带来实际的数据访问,有一定的代价开销,优化器会限制index dive的场景。对于in list等值条件特别多的场景,当超过eq_range_index_dive_limit的阈值,优化器就不会做index dive,而是基于NDV统计信息去估算扫描行数。如果in list中有倾斜的数据,那么行数估算就会错误。</p><h4 id="Index-Dive"><a href="#Index-Dive" class="headerlink" title="Index Dive"></a><strong>Index Dive</strong></h4><p><strong>总结</strong>:<strong>拿着每个 IN 值或区间边界去索引根页 → 二分定位 → 读取叶子页中的 记录条数 rec_per_key 。</strong></p><p>例如:</p><p>拿着一个 IN 值 → 找到它在索引里的 边界页假设表 t 有二级索引 idx(c1),且当前 SQL 是</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> t <span class="keyword">WHERE</span> c1 <span class="keyword">IN</span> (<span class="number">17</span>, <span class="number">29</span>, <span class="number">53</span>);</span><br></pre></td></tr></table></figure><p>优化器拿到第一个值 17。</p><p>从 索引根页 root page 开始二分:根页里存的是“子页的最小键值 页号”。<br>例:根页条目 [10→pageA, 20→pageB, 30→pageC]<br>17 落在 10<del>20 之间 → 指向 pageA。<br>继续二分直到 叶子页。pageA 不是叶子,再二分 → 找到 叶子页 L17,叶子页里才是真正按顺序排好序的 (c1, row_id) 记录。在叶子页里 统计 17 这个键值出现了多少条,叶子页内部也是有序的,二分即可找到第一条 17。顺序往后扫,直到键值 ≠ 17,统计行数 → 得到 rec_per_key(17) 5 条。把这个行数累加到本次 range 的总扫描行数。对 29、53 重复 1</del>3 步,就能算出。<br>total_rows rec_per_key(17) rec_per_key(29) rec_per_key(53)。</p><h4 id="基于NDV统计信息去估算扫描行数"><a href="#基于NDV统计信息去估算扫描行数" class="headerlink" title="基于NDV统计信息去估算扫描行数"></a>基于NDV统计信息去估算扫描行数</h4><p><strong>总结:</strong><br>“基于 NDV 统计信息去估算扫描行数” 就是“用总行数 ÷ 列的不同值个数,再乘以查询涉及的不同值个数”</p><ul><li><strong>NDV</strong><br>Number of Distinct Values——某一列里 有多少个不同的取值。<br>例:列 status 只有 ‘OK’,’FAIL’,’RUNNING’ 3 种值 ⇒ NDV 3。</li><li><strong>统计信息</strong><br>MySQL 在执行 ANALYZE TABLE 后,会把</li><li>表总行数 rows</li><li>该列的 NDV存进 mysql.innodb_index_stats 或 mysql.column_stats 里,8.0 直方图更细 。因此 平均每值出现的行数 rows &#x2F; NDV。</li><li><strong>估算扫描行数</strong><br>当优化器放弃 “index dive” 时,就直接用上面的平均值乘以 查询里要用到的不同值个数。例子:</li></ul><p>如果数据倾斜 例如 c1 1 其实有 8 万行,其余值只有 1 行 ,<br>估算 100 行 vs 实际 80 004 行,就会出现 <strong>“基于 NDV 的估算失真”</strong>。</p><ul><li>表 100 万行,列 c1 NDV 5 万 ⇒ 平均 20 行&#x2F;值。</li><li>SQL:WHERE c1 IN (1,2,3,4,5) 5 个值 。</li><li>估算行数 20 × 5 100 行。</li></ul><hr><p>内容整合于 数据库内核月报 2024 &#x2F; 12</p><h3 id="MySQL查询优化分析-常见慢查问题与优化方法"><a href="#MySQL查询优化分析-常见慢查问题与优化方法" class="headerlink" title="MySQL查询优化分析 - 常见慢查问题与优化方法"></a>MySQL查询优化分析 - 常见慢查问题与优化方法</h3>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/03/05/7b98aaac/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>mysql 黑名单</title>
      <link>https://blog.eucalyptus.cc/2026/03/03/f412cd74/</link>
      <guid>https://blog.eucalyptus.cc/2026/03/03/f412cd74/</guid>
      <pubDate>Tue, 03 Mar 2026 08:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;目的:使用iptables禁止121.43.122.130客户端连接140.143.94.243机器上部署的mysql&lt;/strong&gt;&lt;/p&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;角色&lt;/th&gt;
&lt;th&gt;IP地址&lt;/th&gt;
&lt;/tr&gt;
&lt;/t</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>目的:使用iptables禁止121.43.122.130客户端连接140.143.94.243机器上部署的mysql</strong></p><table><thead><tr><th>角色</th><th>IP地址</th></tr></thead><tbody><tr><td>部署MySQL的机器</td><td>140.143.94.243</td></tr><tr><td>客户端</td><td>121.43.122.130</td></tr></tbody></table><blockquote><p>安装 iptables-services 若没装</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`yum install -y iptables-services`</span><br></pre></td></tr></table></figure><p>让 systemd 接管iptables</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`systemctl start iptables`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-03/img1.avif"></p></blockquote><p>在部署MySQL机器上的filter表INPUT链里加一条DROP规则</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">iptables <span class="operator">-</span>I INPUT <span class="operator">-</span>s <span class="number">121.43</span><span class="number">.122</span><span class="number">.130</span> <span class="operator">-</span>p tcp <span class="comment">--dport 3306 -j DROP</span></span><br></pre></td></tr></table></figure><p>查看规则是否已插入</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">iptables -nvL</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-03/img2.avif"></p><p>验证</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-03/img3.avif"></p><p>这种情况下端口不通</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-03/img4.avif"></p><p>删除规则</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">iptables <span class="operator">-</span>D INPUT <span class="operator">-</span>s <span class="number">121.43</span><span class="number">.122</span><span class="number">.130</span> <span class="operator">-</span>p tcp <span class="comment">--dport 3306 -j DROP</span></span><br></pre></td></tr></table></figure><p>针对这类iptables禁用后使用wireshark分析抓包情况,可以看到tcp一直再重传</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-03-03/img5.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/03/03/f412cd74/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Hexo网站地图生成与百度主动推送</title>
      <link>https://blog.eucalyptus.cc/2026/03/01/910e4c01/</link>
      <guid>https://blog.eucalyptus.cc/2026/03/01/910e4c01/</guid>
      <pubDate>Sun, 01 Mar 2026 10:43:45 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;网站地图生成&quot;&gt;&lt;a href=&quot;#网站地图生成&quot; class=&quot;headerlink&quot; title=&quot;网站地图生成&quot;&gt;&lt;/a&gt;网站地图生成&lt;/h2&gt;&lt;h3 id=&quot;安装插件&quot;&gt;&lt;a href=&quot;#安装插件&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="网站地图生成"><a href="#网站地图生成" class="headerlink" title="网站地图生成"></a>网站地图生成</h2><h3 id="安装插件"><a href="#安装插件" class="headerlink" title="安装插件"></a>安装插件</h3><p>在 Hexo 站点根目录执行：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">npm install hexo-generator-sitemap --save</span><br></pre></td></tr></table></figure><h3 id="配置-config-yml"><a href="#配置-config-yml" class="headerlink" title="配置 _config.yml"></a>配置 _config.yml</h3><p>编辑 Hexo 根目录的 <code>_config.yml</code> 文件，添加以下配置：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 站点地图配置</span></span><br><span class="line"><span class="attr">sitemap:</span></span><br><span class="line">  <span class="attr">path:</span> <span class="string">sitemap.xml</span></span><br><span class="line">  <span class="comment"># 可选参数</span></span><br><span class="line">  <span class="attr">priority:</span> <span class="number">0.5</span>        <span class="comment"># 页面优先级，范围 0.0-1.0</span></span><br><span class="line">  <span class="attr">changefreq:</span> <span class="string">daily</span>    <span class="comment"># 更新频率：always/hourly/daily/weekly/monthly/yearly/never</span></span><br><span class="line">  <span class="attr">lastmod:</span> <span class="literal">true</span>        <span class="comment"># 是否包含最后修改时间</span></span><br><span class="line">  <span class="attr">tags:</span> <span class="literal">true</span>           <span class="comment"># 是否包含标签页</span></span><br><span class="line">  <span class="attr">categories:</span> <span class="literal">true</span>     <span class="comment"># 是否包含分类页</span></span><br></pre></td></tr></table></figure><p><strong>注意</strong>：确保 <code>_config.yml</code> 中的 <code>url</code> 配置正确，站点地图会基于这个 URL 生成完整链接 ：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># URL 配置（必须正确设置）</span></span><br><span class="line"><span class="attr">url:</span> <span class="string">https://img.eucalyptus.cc</span></span><br><span class="line"><span class="attr">root:</span> <span class="string">/</span></span><br><span class="line"><span class="attr">permalink:</span> <span class="string">:year/:month/:day/:title/</span></span><br></pre></td></tr></table></figure><h3 id="生成站点地图"><a href="#生成站点地图" class="headerlink" title="生成站点地图"></a>生成站点地图</h3><p>执行生成命令：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">hexo clean &amp;&amp; hexo generate</span><br></pre></td></tr></table></figure><p>生成后会在 <code>public/</code> 目录下创建文件：<code>sitemap.xml</code> </p><h2 id="百度主动推送"><a href="#百度主动推送" class="headerlink" title="百度主动推送"></a>百度主动推送</h2><h3 id="1-安装插件"><a href="#1-安装插件" class="headerlink" title="1. 安装插件"></a>1. 安装插件</h3><p>在 Hexo 站点根目录下执行：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">npm install hexo-baidu-url-submit --save</span><br></pre></td></tr></table></figure><h3 id="2-获取百度-Token"><a href="#2-获取百度-Token" class="headerlink" title="2. 获取百度 Token"></a>2. 获取百度 Token</h3><ol><li>访问 <div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://ziyuan.baidu.com/site">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://ziyuan.baidu.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://ziyuan.baidu.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">百度搜索资源平台</div>            <div class="tag-link-sitename">百度SEO</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></li><li>注册&#x2F;登录并添加你的网站</li><li>进入 <strong>站点管理 → 资源提交 → 链接提交 → 主动推送(实时)</strong></li><li>找到推送接口地址，复制 <code>token=</code> 后面的字符串</li></ol><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-03-01/1.avif"></p><h3 id="3-修改站点配置"><a href="#3-修改站点配置" class="headerlink" title="3. 修改站点配置"></a>3. 修改站点配置</h3><p>编辑 Hexo 根目录的 <code>_config.yml</code>，添加以下配置：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 百度主动推送配置</span></span><br><span class="line"><span class="attr">baidu_url_submit:</span></span><br><span class="line">  <span class="attr">count:</span> <span class="number">10</span>              <span class="comment"># 提交最新的多少个链接（默认200）</span></span><br><span class="line">  <span class="attr">host:</span> <span class="string">img.eucalyptus.cc</span>  <span class="comment"># 在百度站长平台注册的域名（不含 http/https）</span></span><br><span class="line">  <span class="attr">token:</span> <span class="string">your_token_here</span>  <span class="comment"># 你的百度推送密钥（不要泄露！）</span></span><br><span class="line">  <span class="attr">path:</span> <span class="string">baidu_urls.txt</span>    <span class="comment"># 生成的链接文件路径（默认即可）</span></span><br></pre></td></tr></table></figure><p><strong>注意</strong>：<code>host</code> 字段不要带 <code>http://</code> 或 <code>https://</code>，只需要纯域名 。</p><h3 id="4-添加部署配置"><a href="#4-添加部署配置" class="headerlink" title="4. 添加部署配置"></a>4. 添加部署配置</h3><p>在 <code>_config.yml</code> 的 <code>deploy</code> 部分添加推送类型：</p><figure class="highlight yaml"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="attr">deploy:</span></span><br><span class="line">  <span class="bullet">-</span> <span class="attr">type:</span> <span class="string">baidu_url_submitter</span>    <span class="comment"># 添加这一行</span></span><br></pre></td></tr></table></figure><p>如果有多个部署目标，确保每个 <code>type</code> 前都有 <code>- </code> 。</p><h3 id="5-验证配置"><a href="#5-验证配置" class="headerlink" title="5. 验证配置"></a>5. 验证配置</h3><p>执行部署命令：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">hexo clean &amp;&amp; hexo generate &amp;&amp; hexo deploy</span><br></pre></td></tr></table></figure><p>推送成功后会显示下述信息：</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-03-01/2.avif"></p><h2 id="手动提交"><a href="#手动提交" class="headerlink" title="手动提交"></a>手动提交</h2><p>手动提交可以参考之前写的这篇文章</p><div class='anzhiyu-tag-link'><a class="tag-Link"  href="/2023/05/08/faf925bf/">    <div class="tag-link-tips">站内地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://img.eucalyptus.cc/images/logo.png" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://img.eucalyptus.cc/images/logo.png" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">网站提交搜索引擎</div>            <div class="tag-link-sitename">本站文章</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/SEO/">SEO</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/03/01/910e4c01/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL【bug】 spatial key</title>
      <link>https://blog.eucalyptus.cc/2026/02/28/42d7ed85/</link>
      <guid>https://blog.eucalyptus.cc/2026/02/28/42d7ed85/</guid>
      <pubDate>Sat, 28 Feb 2026 06:10:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;【bug1】&quot;&gt;&lt;a href=&quot;#【bug1】&quot; class=&quot;headerlink&quot; title=&quot;【bug1】&quot;&gt;&lt;/a&gt;【bug1】&lt;/h3&gt;&lt;p&gt;MySQL建&lt;strong&gt;Spatial&lt;/strong&gt;索引的前提条件是列定义&lt;strong&gt;NOT</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="【bug1】"><a href="#【bug1】" class="headerlink" title="【bug1】"></a>【bug1】</h3><p>MySQL建<strong>Spatial</strong>索引的前提条件是列定义<strong>NOT NULL</strong>,而当<strong>location</strong>列中有**’GEOMETRYCOLLECTION EMPTY ‘<strong>的值时,这里</strong>‘GEOMETRYCOLLECTION EMPTY’**变相绕过了这个限制,会导致报错。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img1.avif"></p><blockquote><p>插入空集合 <strong>GEOMETRYCOLLECTION EMPTY,<strong>空集合</strong>占一行空间</strong>,语义上“我知道这里该有几何,但当前没有数据”。</p><p>与 NULL 的区别</p><p>场景</p><p>| 存储值</p><p>| ST_IsEmpty</p><p>| ST_AsText</p><p>|<br>NULL</p><p>| 无</p><p>| NULL</p><p>| NULL</p><p>|<br>GEOMETRYCOLLECTION EMPTY</p><p>| 有</p><p>| 1</p><p>| GEOMETRYCOLLECTION EMPTY</p><p>|</p></blockquote><blockquote></blockquote><p>重建表也无法进行修复</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img2.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> spatial_table (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span> AUTO_INCREMENT,</span><br><span class="line">name <span class="type">varchar</span>(<span class="number">255</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">location geometry <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span>,</span><br><span class="line">number <span class="type">varchar</span>(<span class="number">20</span>) <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="string">&#x27;7425346&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id ),</span><br><span class="line"><span class="keyword">UNIQUE</span> KEY number ( number ),</span><br><span class="line">SPATIAL KEY location_index ( location )</span><br><span class="line">);</span><br><span class="line"></span><br><span class="line"><span class="keyword">INSERT INTO</span> spatial_table (id, name, location, number)</span><br><span class="line"><span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">1</span>, <span class="string">&#x27;Place A&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;POINT(1 1)&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425341&#x27;</span>),</span><br><span class="line">(<span class="number">2</span>, <span class="string">&#x27;Place B&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;LINESTRING(1 1,2 2,3 3)&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425342&#x27;</span>),</span><br><span class="line">(<span class="number">3</span>, <span class="string">&#x27;Place C&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;POLYGON((0 0,10 0,10 10,0 10,0 0),(5 5,7 5,7 7,5 7,5 5))&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425343&#x27;</span>),</span><br><span class="line">(<span class="number">4</span>, <span class="string">&#x27;Place D&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;MULTIPOINT((0 0),(20 20),(60 60))&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425344&#x27;</span>),</span><br><span class="line">(<span class="number">5</span>, <span class="string">&#x27;Place E&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;GEOMETRYCOLLECTION(POINT(10 10),POINT(30 30),LINESTRING(15 15,20 20))&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425345&#x27;</span>),</span><br><span class="line">(<span class="number">6</span>, <span class="string">&#x27;Place F&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;GEOMETRYCOLLECTION(POINT(10 10),POINT(30 30),LINESTRING(15 15,20 20))&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425348&#x27;</span>),</span><br><span class="line">(<span class="number">7</span>, <span class="string">&#x27;Beijing&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;POINT(39.9042 116.4074)&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425347&#x27;</span>),</span><br><span class="line">(<span class="number">8</span>, <span class="string">&#x27;&lt;null&gt;&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;GEOMETRYCOLLECTION EMPTY&#x27;</span>, <span class="number">4326</span>), <span class="string">&#x27;7425346&#x27;</span>);</span><br><span class="line"></span><br><span class="line"><span class="keyword">SELECT</span> id,name,st_astext(location),number <span class="keyword">From</span> spatial_table;</span><br></pre></td></tr></table></figure><p><strong>解决方法:删除这些行并重建表</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img3.avif"></p><h3 id="【bug2】"><a href="#【bug2】" class="headerlink" title="【bug2】"></a>【bug2】</h3><p>先对含** SPATIAL KEY** 的表做过 <strong>ALTER TABLE → R-tree <strong>根页指针错乱,后续</strong> UPDATE&#x2F;DELETE</strong>走空间索引时找不到记录 → 报** Record in index … not found**。在<strong>MySQL Server 5.7.49</strong>、<strong>8.0.41</strong>、<strong>8.4.4</strong>和<strong>9.2.0</strong>版本中修复。</p><p>官方文档:[<a href="https://bugs.mysql.com/bug.php?id">https://bugs.mysql.com/bug.php?id</a> 93728](<a href="https://bugs.mysql.com/bug.php?id">https://bugs.mysql.com/bug.php?id</a> 93728)</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img5.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> tab (</span><br><span class="line">c1 <span class="type">INT</span> <span class="keyword">NOT NULL</span> <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">c2 POINT <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span>,</span><br><span class="line">c3 LINESTRING <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span>,</span><br><span class="line">c4 POLYGON <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span>,</span><br><span class="line">c5 GEOMETRY <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span>,</span><br><span class="line">SPATIAL KEY idx2 (c2),</span><br><span class="line">SPATIAL KEY idx3 (c3),</span><br><span class="line">SPATIAL KEY idx4 (c4),</span><br><span class="line">SPATIAL KEY idx5 (c5)</span><br><span class="line">) ENGINE InnoDB;</span><br><span class="line"></span><br><span class="line"><span class="keyword">INSERT INTO</span> tab(c1,c2,c3,c4,c5) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">1</span>,</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POINT(10 10)&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;LINESTRING(5 5,20 20,30 30)&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POLYGON((30 30,40 40,50 50,30 50,30 40,30 30))&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POLYGON((30 30,40 40,50 50,30 50,30 40,30 30))&#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"></span><br><span class="line"><span class="keyword">INSERT INTO</span> tab(c1,c2,c3,c4,c5) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">2</span>,</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POINT(20 20)&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;LINESTRING(20 20,30 30,40 40)&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POLYGON((40 50,40 70,50 100,70 100,80 80,70 50,40 50))&#x27;</span>, <span class="number">4326</span>),</span><br><span class="line">ST_GeomFromText(<span class="string">&#x27;POLYGON((40 50,40 70,50 100,70 100,80 80,70 50,40 50))&#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"></span><br><span class="line"><span class="keyword">ALTER TABLE</span> tab</span><br><span class="line"><span class="keyword">ADD</span> <span class="keyword">COLUMN</span> new_uniq_col <span class="type">INT</span> <span class="keyword">NOT NULL</span> AUTO_INCREMENT <span class="keyword">FIRST</span>,</span><br><span class="line"><span class="keyword">ADD</span> <span class="keyword">UNIQUE</span> INDEX uniq_idx(new_uniq_col),</span><br><span class="line"><span class="keyword">DROP</span> <span class="keyword">PRIMARY KEY</span>;</span><br><span class="line"></span><br><span class="line"><span class="keyword">DELETE</span> <span class="keyword">From</span> tab;</span><br></pre></td></tr></table></figure><p>解决方法:</p><ul><li>升级版本</li><li>重建表再重新导入数据</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-02-28/img6.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/02/28/42d7ed85/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Hexo中字体的引入与压缩</title>
      <link>https://blog.eucalyptus.cc/2026/02/13/e08e5865/</link>
      <guid>https://blog.eucalyptus.cc/2026/02/13/e08e5865/</guid>
      <pubDate>Fri, 13 Feb 2026 07:58:51 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;引入tff字体&quot;&gt;&lt;a href=&quot;#引入tff字体&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="引入tff字体"><a href="#引入tff字体" class="headerlink" title="引入tff字体"></a>引入tff字体</h2><blockquote><p>本文中涉及的文件没有的话再对应的目录下创建即可</p></blockquote><p>首先，找一个你喜欢的字体。你可以在一些网站上免费下载。下载完之后，把那个.ttf格式的文件放到你网站根目录下的&#x2F;source&#x2F;fonts文件夹里。</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.maoken.com/all-fonts">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.maoken.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.maoken.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">猫啃网 - 免费字体下载</div>            <div class="tag-link-sitename">可免费商用中文字体</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p>接下来，你需要把下面的代码加到&#x2F;source&#x2F;css&#x2F;custom.css文件里，这样就可以引入字体了。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">@font-face &#123;</span><br><span class="line">  font-family: <span class="string">&#x27;BailuFeiYun&#x27;</span>;</span><br><span class="line">  src: url(<span class="string">&#x27;/fonts/BailuFeiYu.ttf&#x27;</span>) format(<span class="string">&#x27;truetype&#x27;</span>); </span><br><span class="line">  font-weight: normal;</span><br><span class="line">  font-style: normal;</span><br><span class="line">  font-display: swap;  /* 关键：防止闪烁，先显示后备字体 */</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>记得在_config.anzhiyu.yml文件里加上custom.css，并且设置一下“# Global font settings”那部分。</p><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="tag">&lt;<span class="name">link</span> <span class="attr">rel</span>=<span class="string">&quot;stylesheet&quot;</span> <span class="attr">href</span>=<span class="string">&quot;/css/custom.css&quot;</span>&gt;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-13/1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-13/2.avif"></p><p>最后一步就是清理缓存，然后重新生成就行了。</p><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">hexo clean</span><br><span class="line">hexo generate</span><br></pre></td></tr></table></figure><h2 id="tff转换woff2"><a href="#tff转换woff2" class="headerlink" title="tff转换woff2"></a>tff转换woff2</h2><p>.ttf字体文件有时候会很大，这样会让网站加载变慢。为了解决这个问题，你可以把.ttf文件转换成.woff2格式，这种格式的文件更小，加载更快。你可以在一些免费的在线网站上完成这个转换。</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://cloudconvert.com/ttf-to-woff2">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://cloudconvert.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://cloudconvert.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">TTF to WOFF2 | CloudConvert</div>            <div class="tag-link-sitename">在线转换工具</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p>记得改一下这里的代码。</p><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">@font-face &#123;</span><br><span class="line">  font-family: &#x27;BailuFeiYun&#x27;;</span><br><span class="line">  src: url(&#x27;/fonts/BailuFeiYu.woff2&#x27;) format(&#x27;woff2&#x27;),</span><br><span class="line">       url(&#x27;/fonts/BailuFeiYun.ttf&#x27;) format(&#x27;truetype&#x27;); </span><br><span class="line">  font-weight: normal;</span><br><span class="line">  font-style: normal;</span><br><span class="line">  font-display: swap;  /* 关键：防止闪烁，先显示后备字体 */</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><h2 id="字体压缩"><a href="#字体压缩" class="headerlink" title="字体压缩"></a>字体压缩</h2><p>如果你引用了*.woff2格式的字体文件，但网站加载还是很慢，那可能就得考虑压缩字体了——可以用字蛛（font-spider）这个工具。</p><p>1、安装字蛛</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 全局安装</span></span><br><span class="line">npm install font-spider -g</span><br><span class="line"></span><br><span class="line"><span class="comment"># 验证安装</span></span><br><span class="line">font-spider --version</span><br></pre></td></tr></table></figure><p>2、准备工作目录</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 创建工作目录</span></span><br><span class="line"><span class="built_in">mkdir</span> font-spider-work</span><br><span class="line"><span class="built_in">cd</span> font-spider-work</span><br><span class="line"></span><br><span class="line"><span class="comment"># 创建必要文件</span></span><br><span class="line"><span class="built_in">touch</span> index.html</span><br><span class="line"><span class="built_in">mkdir</span> -p <span class="built_in">source</span>/fonts</span><br><span class="line"></span><br><span class="line"><span class="comment"># 放入原字体</span></span><br><span class="line"><span class="built_in">cp</span> /source/fonts/BailuFeiYun.ttf <span class="built_in">source</span>/fonts/</span><br></pre></td></tr></table></figure><p>3、建一个index.html文件，在里面放上你博客要用的所有字体。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br></pre></td><td class="code"><pre><span class="line">&lt;!DOCTYPE html&gt;</span><br><span class="line">&lt;html&gt;</span><br><span class="line"></span><br><span class="line">&lt;<span class="built_in">head</span>&gt;</span><br><span class="line">    &lt;meta charset=<span class="string">&quot;UTF-8&quot;</span>&gt;</span><br><span class="line">    &lt;title&gt;Font Spider&lt;/title&gt;</span><br><span class="line">    &lt;style&gt;</span><br><span class="line">        @font-face &#123;</span><br><span class="line">            font-family: <span class="string">&#x27;BailuFeiYun&#x27;</span>;</span><br><span class="line">            src: url(<span class="string">&#x27;../source/fonts/BailuFeiYun.ttf&#x27;</span>) format(<span class="string">&#x27;truetype&#x27;</span>);</span><br><span class="line">            font-weight: normal;</span><br><span class="line">            font-style: normal;</span><br><span class="line">        &#125;</span><br><span class="line"></span><br><span class="line">        .font-test &#123;</span><br><span class="line">            font-family: <span class="string">&#x27;BailuFeiYun&#x27;</span>;</span><br><span class="line">            font-size: 16px;</span><br><span class="line">            line-height: 1.8;</span><br><span class="line">        &#125;</span><br><span class="line">    &lt;/style&gt;</span><br><span class="line">&lt;/head&gt;</span><br><span class="line"></span><br><span class="line">&lt;body&gt;</span><br><span class="line">    &lt;div class=<span class="string">&quot;font-test&quot;</span>&gt;</span><br><span class="line">        &lt;!-- 把你博客的所有文字放这里 --&gt;</span><br><span class="line">        首页文章归档分类标签友链关于</span><br><span class="line">        技术分享HexoWordPress建站心路</span><br><span class="line">        上一篇下一篇打赏作者复制链接</span><br><span class="line">        猫笔千锤岁月长啃文万遍见真功</span><br><span class="line">        &lt;!-- 继续添加更多文字... --&gt;</span><br><span class="line"></span><br><span class="line">        &lt;!-- 常用标点符号 --&gt;</span><br><span class="line">        ，。！？、；：<span class="string">&quot; &quot;</span> <span class="string">&#x27; &#x27;</span> （）《》【】… — ～ · ｜</span><br><span class="line"></span><br><span class="line">        &lt;!-- 常用英文和数字 --&gt;</span><br><span class="line">        abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789</span><br><span class="line"></span><br><span class="line">        &lt;!-- 你的博客标题/昵称（如果有特殊字） --&gt;</span><br><span class="line">        安知鱼 白路飞云 手写体 博客 笔记 技术 生活 随笔</span><br><span class="line"></span><br><span class="line">        &lt;!-- 从你的文章提取的高频文字（复制几篇文章的标题和摘要） --&gt;</span><br><span class="line">        &lt;!-- 这里粘贴你几篇文章的标题和内容中的汉字 --&gt;</span><br><span class="line">    &lt;/div&gt;</span><br><span class="line">&lt;/body&gt;</span><br><span class="line"></span><br><span class="line">&lt;/html&gt;</span><br></pre></td></tr></table></figure><p>4、执行压缩</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">font-spider index.html</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-13/3.avif"></p><p>最后，只需要在custom.css文件里加入压缩后的字体就行了。</p><h2 id="压缩脚本"><a href="#压缩脚本" class="headerlink" title="压缩脚本"></a>压缩脚本</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br><span class="line">252</span><br><span class="line">253</span><br><span class="line">254</span><br><span class="line">255</span><br><span class="line">256</span><br><span class="line">257</span><br><span class="line">258</span><br><span class="line">259</span><br><span class="line">260</span><br><span class="line">261</span><br><span class="line">262</span><br><span class="line">263</span><br><span class="line">264</span><br><span class="line">265</span><br><span class="line">266</span><br><span class="line">267</span><br><span class="line">268</span><br><span class="line">269</span><br><span class="line">270</span><br><span class="line">271</span><br><span class="line">272</span><br><span class="line">273</span><br><span class="line">274</span><br><span class="line">275</span><br><span class="line">276</span><br><span class="line">277</span><br><span class="line">278</span><br><span class="line">279</span><br><span class="line">280</span><br><span class="line">281</span><br><span class="line">282</span><br><span class="line">283</span><br><span class="line">284</span><br><span class="line">285</span><br><span class="line">286</span><br><span class="line">287</span><br><span class="line">288</span><br><span class="line">289</span><br><span class="line">290</span><br><span class="line">291</span><br><span class="line">292</span><br><span class="line">293</span><br><span class="line">294</span><br><span class="line">295</span><br><span class="line">296</span><br><span class="line">297</span><br><span class="line">298</span><br><span class="line">299</span><br><span class="line">300</span><br><span class="line">301</span><br><span class="line">302</span><br><span class="line">303</span><br><span class="line">304</span><br><span class="line">305</span><br><span class="line">306</span><br><span class="line">307</span><br><span class="line">308</span><br><span class="line">309</span><br><span class="line">310</span><br><span class="line">311</span><br><span class="line">312</span><br><span class="line">313</span><br><span class="line">314</span><br><span class="line">315</span><br><span class="line">316</span><br><span class="line">317</span><br><span class="line">318</span><br><span class="line">319</span><br><span class="line">320</span><br><span class="line">321</span><br><span class="line">322</span><br><span class="line">323</span><br><span class="line">324</span><br><span class="line">325</span><br><span class="line">326</span><br><span class="line">327</span><br><span class="line">328</span><br><span class="line">329</span><br><span class="line">330</span><br><span class="line">331</span><br><span class="line">332</span><br><span class="line">333</span><br><span class="line">334</span><br><span class="line">335</span><br><span class="line">336</span><br><span class="line">337</span><br><span class="line">338</span><br><span class="line">339</span><br><span class="line">340</span><br><span class="line">341</span><br><span class="line">342</span><br><span class="line">343</span><br><span class="line">344</span><br><span class="line">345</span><br><span class="line">346</span><br><span class="line">347</span><br><span class="line">348</span><br><span class="line">349</span><br><span class="line">350</span><br><span class="line">351</span><br><span class="line">352</span><br><span class="line">353</span><br><span class="line">354</span><br><span class="line">355</span><br><span class="line">356</span><br><span class="line">357</span><br><span class="line">358</span><br><span class="line">359</span><br><span class="line">360</span><br><span class="line">361</span><br><span class="line">362</span><br><span class="line">363</span><br><span class="line">364</span><br><span class="line">365</span><br><span class="line">366</span><br><span class="line">367</span><br><span class="line">368</span><br><span class="line">369</span><br><span class="line">370</span><br><span class="line">371</span><br><span class="line">372</span><br><span class="line">373</span><br><span class="line">374</span><br><span class="line">375</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">#!/usr/bin/env python3</span></span><br><span class="line"><span class="comment"># -*- coding: utf-8 -*-</span></span><br><span class="line"><span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">Hexo 博客字体压缩脚本 - 动态完整版</span></span><br><span class="line"><span class="string">扫描汉字、英文、数字、标点</span></span><br><span class="line"><span class="string">&quot;</span><span class="string">&quot;&quot;</span></span><br><span class="line"></span><br><span class="line">import os</span><br><span class="line">import re</span><br><span class="line">import sys</span><br><span class="line">import yaml</span><br><span class="line">import json</span><br><span class="line"></span><br><span class="line"></span><br><span class="line">def extract_chars_from_file(filepath, skip_comments=False):</span><br><span class="line">    <span class="string">&quot;&quot;</span><span class="string">&quot;从文件提取所有字符（汉字、英文、数字、标点）&quot;</span><span class="string">&quot;&quot;</span></span><br><span class="line">    try:</span><br><span class="line">        with open(filepath, <span class="string">&#x27;r&#x27;</span>, encoding=<span class="string">&#x27;utf-8&#x27;</span>, errors=<span class="string">&#x27;ignore&#x27;</span>) as f:</span><br><span class="line">            content = f.read()</span><br><span class="line">            </span><br><span class="line">            <span class="comment"># 如果需要过滤注释（YAML 文件）</span></span><br><span class="line">            <span class="keyword">if</span> skip_comments:</span><br><span class="line">                lines = content.split(<span class="string">&#x27;\n&#x27;</span>)</span><br><span class="line">                content = <span class="string">&#x27;\n&#x27;</span>.<span class="built_in">join</span>([line <span class="keyword">for</span> line <span class="keyword">in</span> lines <span class="keyword">if</span> not line.strip().startswith(<span class="string">&#x27;#&#x27;</span>)])</span><br><span class="line">            </span><br><span class="line">            chars = <span class="built_in">set</span>()</span><br><span class="line">            </span><br><span class="line">            <span class="comment"># 1. 汉字</span></span><br><span class="line">            chars.update(re.findall(r<span class="string">&#x27;[\u4e00-\u9fa5]&#x27;</span>, content))</span><br><span class="line">            </span><br><span class="line">            <span class="comment"># 2. 英文字母（大小写）</span></span><br><span class="line">            chars.update(re.findall(r<span class="string">&#x27;[a-zA-Z]&#x27;</span>, content))</span><br><span class="line">            </span><br><span class="line">            <span class="comment"># 3. 数字</span></span><br><span class="line">            chars.update(re.findall(r<span class="string">&#x27;[0-9]&#x27;</span>, content))</span><br><span class="line">            </span><br><span class="line">            <span class="comment"># 4. 常用标点符号</span></span><br><span class="line">            <span class="comment"># 中文标点</span></span><br><span class="line">            chars.update(re.findall(r<span class="string">&#x27;[，。！？、；：&quot;&quot;&#x27;</span><span class="string">&#x27;（）《》【】…—～·｜「」『』【】]&#x27;</span>, content))</span><br><span class="line">            <span class="comment"># 英文标点</span></span><br><span class="line">            chars.update(re.findall(r<span class="string">&#x27;[.,!?;:\&#x27;</span>\&quot;()\[\]&#123;&#125;@#$%^&amp;*+=_\-\\/&lt;&gt;~`]<span class="string">&#x27;, content))</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            return chars</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">    except Exception as e:</span></span><br><span class="line"><span class="string">        print(f&quot;读取文件失败 &#123;filepath&#125;: &#123;e&#125;&quot;)</span></span><br><span class="line"><span class="string">        return set()</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def extract_chars_from_json_yaml(filepath):</span></span><br><span class="line"><span class="string">    &quot;&quot;&quot;从 JSON/YAML 文件递归提取所有字符串中的字符&quot;&quot;&quot;</span></span><br><span class="line"><span class="string">    chars = set()</span></span><br><span class="line"><span class="string">    try:</span></span><br><span class="line"><span class="string">        with open(filepath, &#x27;</span>r<span class="string">&#x27;, encoding=&#x27;</span>utf-8<span class="string">&#x27;, errors=&#x27;</span>ignore<span class="string">&#x27;) as f:</span></span><br><span class="line"><span class="string">            content = f.read()</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            # 尝试解析为 JSON 或 YAML</span></span><br><span class="line"><span class="string">            data = None</span></span><br><span class="line"><span class="string">            try:</span></span><br><span class="line"><span class="string">                data = json.loads(content)</span></span><br><span class="line"><span class="string">            except:</span></span><br><span class="line"><span class="string">                try:</span></span><br><span class="line"><span class="string">                    data = yaml.safe_load(content)</span></span><br><span class="line"><span class="string">                except:</span></span><br><span class="line"><span class="string">                    pass</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            def extract_strings(obj):</span></span><br><span class="line"><span class="string">                if isinstance(obj, str):</span></span><br><span class="line"><span class="string">                    result = set()</span></span><br><span class="line"><span class="string">                    # 汉字</span></span><br><span class="line"><span class="string">                    result.update(re.findall(r&#x27;</span>[\u4e00-\u9fa5]<span class="string">&#x27;, obj))</span></span><br><span class="line"><span class="string">                    # 英文</span></span><br><span class="line"><span class="string">                    result.update(re.findall(r&#x27;</span>[a-zA-Z]<span class="string">&#x27;, obj))</span></span><br><span class="line"><span class="string">                    # 数字</span></span><br><span class="line"><span class="string">                    result.update(re.findall(r&#x27;</span>[0-9]<span class="string">&#x27;, obj))</span></span><br><span class="line"><span class="string">                    # 标点</span></span><br><span class="line"><span class="string">                    result.update(re.findall(r&#x27;</span>[，。！？、；：<span class="string">&quot;&quot;</span><span class="string">&#x27;&#x27;</span>（）《》【】…—～·｜「」『』【】.,!?;:\&#x27;\&quot;()\[\]&#123;&#125;@#$%^&amp;*+=_\-\\/&lt;&gt;~`]<span class="string">&#x27;, obj))</span></span><br><span class="line"><span class="string">                    return result</span></span><br><span class="line"><span class="string">                elif isinstance(obj, list):</span></span><br><span class="line"><span class="string">                    result = set()</span></span><br><span class="line"><span class="string">                    for item in obj:</span></span><br><span class="line"><span class="string">                        result.update(extract_strings(item))</span></span><br><span class="line"><span class="string">                    return result</span></span><br><span class="line"><span class="string">                elif isinstance(obj, dict):</span></span><br><span class="line"><span class="string">                    result = set()</span></span><br><span class="line"><span class="string">                    for key, value in obj.items():</span></span><br><span class="line"><span class="string">                        result.update(extract_strings(key))</span></span><br><span class="line"><span class="string">                        result.update(extract_strings(value))</span></span><br><span class="line"><span class="string">                    return result</span></span><br><span class="line"><span class="string">                return set()</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            if data:</span></span><br><span class="line"><span class="string">                chars.update(extract_strings(data))</span></span><br><span class="line"><span class="string">            else:</span></span><br><span class="line"><span class="string">                # 解析失败，直接正则提取</span></span><br><span class="line"><span class="string">                chars.update(extract_chars_from_file(filepath))</span></span><br><span class="line"><span class="string">                </span></span><br><span class="line"><span class="string">    except Exception as e:</span></span><br><span class="line"><span class="string">        print(f&quot;读取失败 &#123;filepath&#125;: &#123;e&#125;&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    return chars</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def extract_title_from_md(filepath):</span></span><br><span class="line"><span class="string">    &quot;&quot;&quot;只提取 Markdown 文件的 Front-matter title&quot;&quot;&quot;</span></span><br><span class="line"><span class="string">    try:</span></span><br><span class="line"><span class="string">        with open(filepath, &#x27;</span>r<span class="string">&#x27;, encoding=&#x27;</span>utf-8<span class="string">&#x27;, errors=&#x27;</span>ignore<span class="string">&#x27;) as f:</span></span><br><span class="line"><span class="string">            content = f.read()</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            # 匹配 Front-matter</span></span><br><span class="line"><span class="string">            fm_match = re.match(r&#x27;</span>^---\s*\n(.*?)\n---<span class="string">&#x27;, content, re.DOTALL)</span></span><br><span class="line"><span class="string">            title = &#x27;</span><span class="string">&#x27;</span></span><br><span class="line"><span class="string">            if fm_match:</span></span><br><span class="line"><span class="string">                try:</span></span><br><span class="line"><span class="string">                    fm = yaml.safe_load(fm_match.group(1))</span></span><br><span class="line"><span class="string">                    title = str(fm.get(&#x27;</span>title<span class="string">&#x27;, &#x27;</span><span class="string">&#x27;))</span></span><br><span class="line"><span class="string">                except:</span></span><br><span class="line"><span class="string">                    pass</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            # 备用：正则提取 title: xxx</span></span><br><span class="line"><span class="string">            if not title:</span></span><br><span class="line"><span class="string">                title_match = re.search(r&#x27;</span>^title:\s*(.+)$<span class="string">&#x27;, content, re.MULTILINE)</span></span><br><span class="line"><span class="string">                if title_match:</span></span><br><span class="line"><span class="string">                    title = title_match.group(1).strip().strip(&#x27;</span><span class="string">&quot;\&#x27;&#x27;)</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            # 提取所有字符</span></span><br><span class="line"><span class="string">            chars = set()</span></span><br><span class="line"><span class="string">            chars.update(re.findall(r&#x27;[\u4e00-\u9fa5]&#x27;, title))</span></span><br><span class="line"><span class="string">            chars.update(re.findall(r&#x27;[a-zA-Z]&#x27;, title))</span></span><br><span class="line"><span class="string">            chars.update(re.findall(r&#x27;[0-9]&#x27;, title))</span></span><br><span class="line"><span class="string">            chars.update(re.findall(r&#x27;[，。！？、；：&quot;</span><span class="string">&quot;&#x27;&#x27;（）《》【】…—～·｜「」『』【】.,!?;:\&#x27;\&quot;()\[\]&#123;&#125;@#$%^&amp;*+=_\-\\/&lt;&gt;~`]&#x27;, title))</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            return chars</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">    except Exception as e:</span></span><br><span class="line"><span class="string">        print(f&quot;</span>读取失败 &#123;filepath&#125;: &#123;e&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        return set()</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def get_dynamic_fixed_chars(hexo_root):</span></span><br><span class="line"><span class="string">    &quot;</span><span class="string">&quot;&quot;</span>从配置文件动态读取固定字符<span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">    chars = set()</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 1. 从站点配置 _config.yml 读取</span></span><br><span class="line"><span class="string">    site_config = os.path.join(hexo_root, &#x27;_config.yml&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(site_config):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>  读取站点配置: _config.yml<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        config_chars = extract_chars_from_file(site_config, skip_comments=True)</span></span><br><span class="line"><span class="string">        chars.update(config_chars)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>    -&gt; &#123;len(config_chars)&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 2. 从主题配置 _config.anzhiyu.yml 读取（过滤注释）</span></span><br><span class="line"><span class="string">    theme_config = os.path.join(hexo_root, &#x27;_config.anzhiyu.yml&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(theme_config):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>  读取主题配置: _config.anzhiyu.yml<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        config_chars = extract_chars_from_file(theme_config, skip_comments=True)</span></span><br><span class="line"><span class="string">        chars.update(config_chars)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>    -&gt; &#123;len(config_chars)&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 3. 从主题语言文件读取</span></span><br><span class="line"><span class="string">    theme_lang_dir = os.path.join(hexo_root, &#x27;themes&#x27;, &#x27;anzhiyu&#x27;, &#x27;languages&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(theme_lang_dir):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>  读取主题语言文件:<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        for lang_file in os.listdir(theme_lang_dir):</span></span><br><span class="line"><span class="string">            if lang_file.endswith((&#x27;.yml&#x27;, &#x27;.yaml&#x27;)):</span></span><br><span class="line"><span class="string">                filepath = os.path.join(theme_lang_dir, lang_file)</span></span><br><span class="line"><span class="string">                lang_chars = extract_chars_from_file(filepath, skip_comments=True)</span></span><br><span class="line"><span class="string">                if lang_chars:</span></span><br><span class="line"><span class="string">                    chars.update(lang_chars)</span></span><br><span class="line"><span class="string">                    print(f&quot;</span>    &#123;lang_file&#125; -&gt; &#123;len(lang_chars)&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    return chars</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def scan_directory_full(directory, chars_set, skip_dirs=None, depth=0):</span></span><br><span class="line"><span class="string">    &quot;</span><span class="string">&quot;&quot;</span>递归扫描目录下所有文件<span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">    if skip_dirs is None:</span></span><br><span class="line"><span class="string">        skip_dirs = [&#x27;node_modules&#x27;, &#x27;.git&#x27;, &#x27;images&#x27;, &#x27;img&#x27;, &#x27;fonts&#x27;, &#x27;css&#x27;, &#x27;js&#x27;]</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    if not os.path.exists(directory):</span></span><br><span class="line"><span class="string">        return 0, 0</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    file_count = 0</span></span><br><span class="line"><span class="string">    total_chars = 0</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    prefix = &quot;</span>  <span class="string">&quot; * depth</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    for root, dirs, files in os.walk(directory):</span></span><br><span class="line"><span class="string">        dirs[:] = [d for d in dirs if d not in skip_dirs and not d.startswith(&#x27;.&#x27;)]</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">        for file in files:</span></span><br><span class="line"><span class="string">            filepath = os.path.join(root, file)</span></span><br><span class="line"><span class="string">            rel_path = os.path.relpath(filepath, directory)</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            file_chars = set()</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            if file.endswith(&#x27;.md&#x27;):</span></span><br><span class="line"><span class="string">                file_chars = extract_chars_from_file(filepath)</span></span><br><span class="line"><span class="string">            elif file.endswith((&#x27;.json&#x27;, &#x27;.yml&#x27;, &#x27;.yaml&#x27;)):</span></span><br><span class="line"><span class="string">                file_chars = extract_chars_from_json_yaml(filepath)</span></span><br><span class="line"><span class="string">            elif file.endswith((&#x27;.html&#x27;, &#x27;.htm&#x27;, &#x27;.txt&#x27;)):</span></span><br><span class="line"><span class="string">                file_chars = extract_chars_from_file(filepath)</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            if file_chars:</span></span><br><span class="line"><span class="string">                chars_set.update(file_chars)</span></span><br><span class="line"><span class="string">                file_count += 1</span></span><br><span class="line"><span class="string">                total_chars += len(file_chars)</span></span><br><span class="line"><span class="string">                print(f&quot;</span>&#123;prefix&#125;  &#123;rel_path&#125; -&gt; &#123;len(file_chars)&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    return file_count, total_chars</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def generate_char_file(output_path, hexo_root):</span></span><br><span class="line"><span class="string">    &quot;</span><span class="string">&quot;&quot;</span>生成字符文件<span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">    print(&quot;</span>=<span class="string">&quot; * 60)</span></span><br><span class="line"><span class="string">    print(&quot;</span>Hexo 博客字体压缩工具 - 动态完整版<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(&quot;</span>=<span class="string">&quot; * 60)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    chars = set()</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 1. 文章目录：只扫描标题</span></span><br><span class="line"><span class="string">    posts_dir = os.path.join(hexo_root, &#x27;source&#x27;, &#x27;_posts&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(posts_dir):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n📁 扫描文章标题(仅title): &#123;posts_dir&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        count = 0</span></span><br><span class="line"><span class="string">        for root, dirs, files in os.walk(posts_dir):</span></span><br><span class="line"><span class="string">            dirs[:] = [d for d in dirs if d not in [&#x27;node_modules&#x27;, &#x27;.git&#x27;]]</span></span><br><span class="line"><span class="string">            for file in files:</span></span><br><span class="line"><span class="string">                if file.endswith(&#x27;.md&#x27;):</span></span><br><span class="line"><span class="string">                    filepath = os.path.join(root, file)</span></span><br><span class="line"><span class="string">                    title_chars = extract_title_from_md(filepath)</span></span><br><span class="line"><span class="string">                    chars.update(title_chars)</span></span><br><span class="line"><span class="string">                    count += 1</span></span><br><span class="line"><span class="string">        print(f&quot;</span>  扫描了 &#123;count&#125; 篇文章，提取 &#123;len(chars)&#125; 个独特字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 2. 其他页面目录：全内容扫描</span></span><br><span class="line"><span class="string">    source_dir = os.path.join(hexo_root, &#x27;source&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(source_dir):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n📁 扫描页面目录(全内容递归):<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">        for item in os.listdir(source_dir):</span></span><br><span class="line"><span class="string">            if item in [&#x27;_posts&#x27;, &#x27;images&#x27;, &#x27;img&#x27;, &#x27;fonts&#x27;, &#x27;css&#x27;, &#x27;js&#x27;]:</span></span><br><span class="line"><span class="string">                continue</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            item_path = os.path.join(source_dir, item)</span></span><br><span class="line"><span class="string">            </span></span><br><span class="line"><span class="string">            if os.path.isdir(item_path):</span></span><br><span class="line"><span class="string">                print(f&quot;</span>\n  📂 &#123;item&#125;/<span class="string">&quot;)</span></span><br><span class="line"><span class="string">                file_count, total_chars = scan_directory_full(item_path, chars, depth=1)</span></span><br><span class="line"><span class="string">                print(f&quot;</span>    合计: &#123;file_count&#125; 个文件，&#123;total_chars&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 3. 扫描 _data 目录</span></span><br><span class="line"><span class="string">    data_dir = os.path.join(hexo_root, &#x27;source&#x27;, &#x27;_data&#x27;)</span></span><br><span class="line"><span class="string">    if os.path.exists(data_dir):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n📁 扫描数据目录(_data):<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        file_count, total_chars = scan_directory_full(data_dir, chars, depth=1)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>    合计: &#123;file_count&#125; 个文件，&#123;total_chars&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 4. 动态读取配置文件</span></span><br><span class="line"><span class="string">    print(f&quot;</span>\n📁 动态读取配置文件:<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    fixed_chars = get_dynamic_fixed_chars(hexo_root)</span></span><br><span class="line"><span class="string">    chars.update(fixed_chars)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>  配置文件共提取: &#123;len(fixed_chars)&#125; 字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    # 5. 排序并保存</span></span><br><span class="line"><span class="string">    # 按字符类型排序：汉字 -&gt; 英文 -&gt; 数字 -&gt; 标点</span></span><br><span class="line"><span class="string">    hanzi = sorted([c for c in chars if &#x27;\u4e00&#x27; &lt;= c &lt;= &#x27;\u9fa5&#x27;])</span></span><br><span class="line"><span class="string">    english = sorted([c for c in chars if c.isalpha()])</span></span><br><span class="line"><span class="string">    digits = sorted([c for c in chars if c.isdigit()])</span></span><br><span class="line"><span class="string">    others = sorted([c for c in chars if not (&#x27;\u4e00&#x27; &lt;= c &lt;= &#x27;\u9fa5&#x27; or c.isalnum())])</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    sorted_chars = &#x27;&#x27;.join(hanzi + english + digits + others)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    with open(output_path, &#x27;w&#x27;, encoding=&#x27;utf-8&#x27;) as f:</span></span><br><span class="line"><span class="string">        f.write(sorted_chars)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    print(f&quot;</span>\n<span class="string">&quot; + &quot;</span>=<span class="string">&quot; * 60)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>✅ 共收集 &#123;len(chars)&#125; 个独特字符<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   - 汉字: &#123;len(hanzi)&#125; 个<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   - 英文: &#123;len(english)&#125; 个<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   - 数字: &#123;len(digits)&#125; 个<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   - 标点/其他: &#123;len(others)&#125; 个<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>💾 已保存到: &#123;output_path&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    preview = sorted_chars[:100]</span></span><br><span class="line"><span class="string">    print(f&quot;</span>\n📋 字符预览: &#123;preview&#125;...<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    return sorted_chars</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def subset_font(input_font, output_font, chars_file):</span></span><br><span class="line"><span class="string">    &quot;</span><span class="string">&quot;&quot;</span>使用 fonttools 子集化字体<span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">    try:</span></span><br><span class="line"><span class="string">        from fontTools.subset import main as subset_main</span></span><br><span class="line"><span class="string">    except ImportError:</span></span><br><span class="line"><span class="string">        print(&quot;</span>\n❌ 缺少 fonttools，正在安装...<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        os.system(f&quot;</span>&#123;sys.executable&#125; -m pip install fonttools brotli zopfli<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        from fontTools.subset import main as subset_main</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    print(f&quot;</span>\n🔧 开始压缩字体...<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   输入: &#123;input_font&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    print(f&quot;</span>   输出: &#123;output_font&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    args = [</span></span><br><span class="line"><span class="string">        input_font,</span></span><br><span class="line"><span class="string">        f&quot;</span>--text-file=&#123;chars_file&#125;<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        f&quot;</span>--output-file=&#123;output_font&#125;<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--flavor=woff2<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--desubroutinize<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--recalc-bounds<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--canonical-order<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--layout-features=*<span class="string">&quot;,</span></span><br><span class="line"><span class="string">    ]</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    ttf_output = output_font.replace(&#x27;.woff2&#x27;, &#x27;.ttf&#x27;)</span></span><br><span class="line"><span class="string">    args_ttf = [</span></span><br><span class="line"><span class="string">        input_font,</span></span><br><span class="line"><span class="string">        f&quot;</span>--text-file=&#123;chars_file&#125;<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        f&quot;</span>--output-file=&#123;ttf_output&#125;<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--desubroutinize<span class="string">&quot;,</span></span><br><span class="line"><span class="string">        &quot;</span>--recalc-bounds<span class="string">&quot;,</span></span><br><span class="line"><span class="string">    ]</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    try:</span></span><br><span class="line"><span class="string">        subset_main(args)</span></span><br><span class="line"><span class="string">        subset_main(args_ttf)</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">        original_size = os.path.getsize(input_font)</span></span><br><span class="line"><span class="string">        woff2_size = os.path.getsize(output_font)</span></span><br><span class="line"><span class="string">        ttf_size = os.path.getsize(ttf_output)</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n✅ 压缩完成!<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>   原始大小: &#123;original_size/1024:.2f&#125; KB<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>   WOFF2 大小: &#123;woff2_size/1024:.2f&#125; KB (压缩率: &#123;woff2_size/original_size*100:.1f&#125;%)<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>   TTF 大小: &#123;ttf_size/1024:.2f&#125; KB (压缩率: &#123;ttf_size/original_size*100:.1f&#125;%)<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">        return True</span></span><br><span class="line"><span class="string">        </span></span><br><span class="line"><span class="string">    except Exception as e:</span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n❌ 压缩失败: &#123;e&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        return False</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">def main():</span></span><br><span class="line"><span class="string">    &quot;</span><span class="string">&quot;&quot;</span>主函数<span class="string">&quot;&quot;</span><span class="string">&quot;</span></span><br><span class="line"><span class="string">    HEXO_ROOT = &quot;</span>/www/wwwroot/myblog<span class="string">&quot;</span></span><br><span class="line"><span class="string">    WORK_DIR = &quot;</span>/www/wwwroot/myblog/font-spider-work<span class="string">&quot;</span></span><br><span class="line"><span class="string">    INPUT_FONT = os.path.join(WORK_DIR, &quot;</span>fonts<span class="string">&quot;, &quot;</span>BailuFeiYun.ttf<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    CHARS_FILE = os.path.join(WORK_DIR, &quot;</span>chars-full.txt<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    OUTPUT_WOFF2 = os.path.join(HEXO_ROOT, &quot;</span><span class="built_in">source</span><span class="string">&quot;, &quot;</span>fonts<span class="string">&quot;, &quot;</span>BailuFeiYun.woff2<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    if not os.path.exists(INPUT_FONT):</span></span><br><span class="line"><span class="string">        print(f&quot;</span>❌ 未找到原始字体: &#123;INPUT_FONT&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        sys.exit(1)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    os.makedirs(os.path.dirname(OUTPUT_WOFF2), exist_ok=True)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    chars = generate_char_file(CHARS_FILE, HEXO_ROOT)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    if len(chars) &lt; 50:</span></span><br><span class="line"><span class="string">        print(&quot;</span>⚠️  提取字符过少，请检查路径<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        sys.exit(1)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    success = subset_font(INPUT_FONT, OUTPUT_WOFF2, CHARS_FILE)</span></span><br><span class="line"><span class="string">    </span></span><br><span class="line"><span class="string">    if success:</span></span><br><span class="line"><span class="string">        print(f&quot;</span>\n🎉 全部完成!<span class="string">&quot;)</span></span><br><span class="line"><span class="string">        print(f&quot;</span>   压缩后的字体已输出到: &#123;os.path.dirname(OUTPUT_WOFF2)&#125;<span class="string">&quot;)</span></span><br><span class="line"><span class="string">    else:</span></span><br><span class="line"><span class="string">        sys.exit(1)</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">if __name__ == &quot;</span>__main__<span class="string">&quot;:</span></span><br><span class="line"><span class="string">    main()</span></span><br></pre></td></tr></table></figure><h3 id="工作流程"><a href="#工作流程" class="headerlink" title="工作流程"></a>工作流程</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">1. 扫描文章标题 ──┐</span><br><span class="line">2. 扫描页面内容 ──┤</span><br><span class="line">3. 扫描 _data 目录 ─┼──&gt; 收集所有字符 ──&gt; 去重排序 ──&gt; 生成字符文件</span><br><span class="line">4. 扫描配置文件 ──┤</span><br><span class="line">5. 扫描语言文件 ──┘</span><br><span class="line"></span><br><span class="line">6. 使用 fonttools 压缩字体</span><br><span class="line">   ├── 输入：原始 TTF 字体</span><br><span class="line">   ├── 根据字符文件裁剪</span><br><span class="line">   └── 输出：WOFF2 + TTF（子集化后）</span><br></pre></td></tr></table></figure><h3 id="输出示例"><a href="#输出示例" class="headerlink" title="输出示例"></a>输出示例</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br></pre></td><td class="code"><pre><span class="line">============================================================</span><br><span class="line">Hexo 博客字体压缩工具 - 动态完整版</span><br><span class="line">============================================================</span><br><span class="line"></span><br><span class="line">📁 扫描文章标题(仅title): /www/wwwroot/myblog/source/_posts</span><br><span class="line">  扫描了 17 篇文章，提取 143 个独特字符</span><br><span class="line"></span><br><span class="line">📁 扫描页面目录(全内容递归):</span><br><span class="line"></span><br><span class="line">  📂 charts/</span><br><span class="line">    index.md -&gt; 67 字符</span><br><span class="line">    合计: 1 个文件，67 字符</span><br><span class="line"></span><br><span class="line">  📂 agreement/</span><br><span class="line">    index.md -&gt; 433 字符</span><br><span class="line">    合计: 1 个文件，433 字符</span><br><span class="line"></span><br><span class="line">  📂 link/</span><br><span class="line">    index.md -&gt; 126 字符</span><br><span class="line">    合计: 1 个文件，126 字符</span><br><span class="line"></span><br><span class="line">  📂 essay/</span><br><span class="line">    index.md -&gt; 29 字符</span><br><span class="line">    合计: 1 个文件，29 字符</span><br><span class="line"></span><br><span class="line">  📂 categories/</span><br><span class="line">    index.md -&gt; 28 字符</span><br><span class="line">    合计: 1 个文件，28 字符</span><br><span class="line"></span><br><span class="line">  📂 _data/</span><br><span class="line">    link.yml -&gt; 201 字符</span><br><span class="line">    bangumis.json -&gt; 231 字符</span><br><span class="line">    creativity.yml -&gt; 75 字符</span><br><span class="line">    essay.yml -&gt; 73 字符</span><br><span class="line">    about.yml -&gt; 232 字符</span><br><span class="line">    合计: 5 个文件，812 字符</span><br><span class="line"></span><br><span class="line">  📂 cdn/</span><br><span class="line">    合计: 0 个文件，0 字符</span><br><span class="line"></span><br><span class="line">  📂 about/</span><br><span class="line">    index.md -&gt; 34 字符</span><br><span class="line">    合计: 1 个文件，34 字符</span><br><span class="line"></span><br><span class="line">  📂 sitemap/</span><br><span class="line">    合计: 0 个文件，0 字符</span><br><span class="line"></span><br><span class="line">  📂 tags/</span><br><span class="line">    index.md -&gt; 28 字符</span><br><span class="line">    合计: 1 个文件，28 字符</span><br><span class="line"></span><br><span class="line">  📂 privacy/</span><br><span class="line">    index.md -&gt; 379 字符</span><br><span class="line">    合计: 1 个文件，379 字符</span><br><span class="line"></span><br><span class="line">📁 扫描数据目录(_data):</span><br><span class="line">    link.yml -&gt; 201 字符</span><br><span class="line">    bangumis.json -&gt; 231 字符</span><br><span class="line">    creativity.yml -&gt; 75 字符</span><br><span class="line">    essay.yml -&gt; 73 字符</span><br><span class="line">    about.yml -&gt; 232 字符</span><br><span class="line">    合计: 5 个文件，812 字符</span><br><span class="line"></span><br><span class="line">📁 动态读取配置文件:</span><br><span class="line">  读取站点配置: _config.yml</span><br><span class="line">    -&gt; 360 字符</span><br><span class="line">  读取主题配置: _config.anzhiyu.yml</span><br><span class="line">    -&gt; 526 字符</span><br><span class="line">  读取主题语言文件:</span><br><span class="line">    zh-TW.yml -&gt; 341 字符</span><br><span class="line">    en.yml -&gt; 67 字符</span><br><span class="line">    zh-CN.yml -&gt; 346 字符</span><br><span class="line">    default.yml -&gt; 251 字符</span><br><span class="line">  配置文件共提取: 843 字符</span><br><span class="line"></span><br><span class="line">============================================================</span><br><span class="line">✅ 共收集 1180 个独特字符</span><br><span class="line">   - 汉字: 1073 个</span><br><span class="line">   - 英文: 1125 个</span><br><span class="line">   - 数字: 10 个</span><br><span class="line">   - 标点/其他: 45 个</span><br><span class="line">💾 已保存到: /www/wwwroot/myblog/font-spider-work/chars-full.txt</span><br><span class="line"></span><br><span class="line">📋 字符预览: 一七万三上下不与专且世业东丢个中丰为主举久么义之乌乎乐也习书乾了予二于云互些交亦产享亮人亿什仅仇今介仍从他付仙代以们件价任份优伙会传伦伴伸但位低住体何作你使來例供依侧侵便保信修個們倒值假偏做停健偿備储...</span><br><span class="line"></span><br><span class="line">🔧 开始压缩字体...</span><br><span class="line">   输入: /www/wwwroot/myblog/font-spider-work/fonts/BailuFeiYun.ttf</span><br><span class="line">   输出: /www/wwwroot/myblog/source/fonts/BailuFeiYun.woff2</span><br><span class="line"></span><br><span class="line">✅ 压缩完成!</span><br></pre></td></tr></table></figure><h3 id="文件位置"><a href="#文件位置" class="headerlink" title="文件位置"></a>文件位置</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">/www/wwwroot/myblog/</span><br><span class="line">├── source/fonts/           # 输出压缩后的字体</span><br><span class="line">│   ├── BailuFeiYun.woff2</span><br><span class="line">│   └── BailuFeiYun.ttf</span><br><span class="line">├── font-spider-work/       # 工作目录</span><br><span class="line">│   ├── fonts/</span><br><span class="line">│   │   └── BailuFeiYun.ttf  # 原始字体</span><br><span class="line">│   └── chars-full.txt       # 提取的字符列表</span><br><span class="line">└── compress_font.py         # 本脚本</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AD%97%E4%BD%93/">字体</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/02/13/e08e5865/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Twikoo私有化部署</title>
      <link>https://blog.eucalyptus.cc/2026/02/08/af1cafe0/</link>
      <guid>https://blog.eucalyptus.cc/2026/02/08/af1cafe0/</guid>
      <pubDate>Sun, 08 Feb 2026 10:25:41 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h2&gt;&lt;p&gt;对于使用 Hexo 搭建的静态博客而言，一个稳定、轻量的评论系统是连接读者的重要桥梁。Twikoo</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>对于使用 Hexo 搭建的静态博客而言，一个稳定、轻量的评论系统是连接读者的重要桥梁。Twikoo 作为目前最受欢迎的开源评论方案之一，除了官方提供的云开发版本外，私有化部署能让你获得完全的数据自主权——不再受限于免费额度，无需担心云厂商政策变动，还能通过自定义二级域名和 SSL 证书实现更专业、更稳定的访问体验。<br>本文将提供一份从零开始的实操指南，手把手教你通过 Docker 完成 Twikoo 的私有化部署。无论你是习惯命令行的开发者，还是偏好图形界面的宝塔用户，都能找到适合自己的部署方式。内容涵盖域名解析、容器配置、反向代理到证书申请的全流程，特别针对 AnZhiYu 等热门 Hexo 主题给出了详细的对接配置。跟随本文操作，你将拥有一个完全属于自己、独立运行的评论服务。</p><h2 id="准备：解析二级域名"><a href="#准备：解析二级域名" class="headerlink" title="准备：解析二级域名"></a>准备：解析二级域名</h2><p>建议为 Twikoo 单独分配一个二级域名（如 <code>twikoo.yourdomain.com</code>），便于后期维护和管理。</p><ul><li><strong>记录类型</strong>：A 记录</li><li><strong>主机记录</strong>：<code>twikoo</code>（或其他你喜欢的二级域名前缀）</li><li><strong>记录值</strong>：你的服务器 IP 地址</li></ul><blockquote><p><strong>提示</strong>：解析生效需要几分钟到几小时不等，可通过 <code>ping twikoo.yourdomain.com</code> 验证是否生效。</p></blockquote><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image.avif"></p><h2 id="拉起Twikoo的容器"><a href="#拉起Twikoo的容器" class="headerlink" title="拉起Twikoo的容器"></a>拉起Twikoo的容器</h2><h3 id="方案一：Docker-命令行部署（推荐）"><a href="#方案一：Docker-命令行部署（推荐）" class="headerlink" title="方案一：Docker 命令行部署（推荐）"></a>方案一：Docker 命令行部署（推荐）</h3><p>适合熟悉 Linux 命令的开发者，轻量且可控。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run --name twikoo -e TWIKOO_THROTTLE=1000 -p 8181:8080 -v <span class="variable">$&#123;PWD&#125;</span>/data:/app/data -d imaegoo/twikoo</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image1.avif"></p><h3 id="方案二：宝塔面板部署（可视化）"><a href="#方案二：宝塔面板部署（可视化）" class="headerlink" title="方案二：宝塔面板部署（可视化）"></a>方案二：宝塔面板部署（可视化）</h3><p>适合不熟悉命令行或已安装宝塔面板的用户。</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image2.avif"></p><h2 id="配置反向代理"><a href="#配置反向代理" class="headerlink" title="配置反向代理"></a>配置反向代理</h2><p>直接使用 IP:端口 访问既不优雅也不安全。通过 Nginx 反向代理，可以实现：</p><ul><li>使用域名访问（如 <code>twikoo.yourdomain.com</code>）</li><li>后续支持 HTTPS（SSL 证书）</li><li>隐藏真实端口，提高安全性</li></ul><p>Nginx 配置示例,在宝塔 “网站” → “反向代理” 中添加：</p><ul><li>目标 URL：<code>http://127.0.0.1:8181</code>（即你刚才映射的本地端口）</li><li>发送域名：$host</li></ul><blockquote><p>原理：所有访问 <code>twikoo.yourdomain.com</code> 的请求，都会被 Nginx 转发到本地的 8181 端口，由 Twikoo 容器处理。</p></blockquote><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image3.avif"></p><h2 id="部署ssl证书"><a href="#部署ssl证书" class="headerlink" title="部署ssl证书"></a>部署ssl证书</h2><p>为保证数据传输安全，强烈建议配置 HTTPS。宝塔中操作如下：</p><ul><li>在刚才的反向代理站点中，点击 “SSL” 选项卡</li><li>选择 “Let’s Encrypt” 免费证书，或上传自己的证书</li><li>开启 “强制 HTTPS”</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/imag4.avif"></p><p>最后再浏览器访问你的Twikoo的域名，以下输出代表Twikoo部署已经完成</p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image5.avif"></p><h2 id="开启评论功能"><a href="#开启评论功能" class="headerlink" title="开启评论功能"></a>开启评论功能</h2><p>下面可以参考安知鱼主题官方文档开启评论功能</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://docs.anheyu.com/advanced/#%E8%AF%84%E8%AE%BA">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://docs.anheyu.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://docs.anheyu.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">安知鱼主题 - 评论</div>            <div class="tag-link-sitename">安知鱼主题官方文档</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/Hexo/2026-02-08/image7.avif"></p><p>到这里Twikoo就部署完成了,最后记得清除缓存和重新生成静态网站</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">hexo clean</span><br><span class="line">hexo generate</span><br></pre></td></tr></table></figure><h2 id="常见问题"><a href="#常见问题" class="headerlink" title="常见问题"></a>常见问题</h2><p>Q：为什么选择私有化部署而非云开发？<br>A：云开发有免费额度限制（如腾讯云每日读取次数限制），私有化部署只要服务器不宕机就永久可用，数据完全自主可控。<br>Q：容器重启后数据会丢失吗？<br>A：不会。-v ${PWD}&#x2F;data:&#x2F;app&#x2F;data 已将数据持久化到宿主机，只要 data 文件夹在，重新运行容器数据依然保留。<br>Q：评论通知如何配置？<br>A：访问 Twikoo 管理后台（在评论区点击登录，输入管理员密码），在”设置”中配置 SMTP 邮箱或 webhook 推送。</p><p>至此，你拥有了一个完全独立的私有化评论系统！</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Hexo/">Hexo</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Twikoo/">Twikoo</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/02/08/af1cafe0/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL性能分析工具（perf+Flame Graphs）</title>
      <link>https://blog.eucalyptus.cc/2026/01/25/6abeceaf/</link>
      <guid>https://blog.eucalyptus.cc/2026/01/25/6abeceaf/</guid>
      <pubDate>Sun, 25 Jan 2026 07:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;本文将介绍如何使用perf和Flame Graphs工具对MySQL进行性能分析,这两个工具能够以图形化的形式展现MySQL中的哪些函数被调用以及调用次数,对于MySQL性能分析和优化有较大的作用。&lt;/p&gt;
&lt;p&gt;perf 用来采集性能数据,Flame Graphs</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>本文将介绍如何使用perf和Flame Graphs工具对MySQL进行性能分析,这两个工具能够以图形化的形式展现MySQL中的哪些函数被调用以及调用次数,对于MySQL性能分析和优化有较大的作用。</p><p>perf 用来采集性能数据,Flame Graphs 使用perf采集的数据进行图形化展示</p><p>安装perf</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">yum install -y perf</span><br></pre></td></tr></table></figure><p>使用Linux perf工具进行系统级性能数据采集</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 针对特定进程进行性能分析</span></span><br><span class="line">perf record -F 99 -p &lt;PID&gt; -g -- <span class="built_in">sleep</span> 60</span><br><span class="line"><span class="comment">#任务时钟</span></span><br><span class="line">perf record -a -g -e task-clock -p 3601 -- <span class="built_in">sleep</span> 60</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img2.avif"></p><p>数据采集完成后,通常会生成一个二进制数据文件perf.data,通过下面的命令将采集的二进制数据进行加工,转换成易于阅读的文本文件,</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">perf script &gt; perf.script</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img3.avif"></p><p>安装FlameGraph</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">git clone https://github.com/brendangregg/FlameGraph</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img4.avif"></p><p>将perf.script文件作为输入,通过Flame Graphs工具,生成svg格式的性能图形</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">../FlameGraph/stackcollapse-perf.pl perf.script | ../FlameGraph/flamegraph.pl &gt; flamegraph.svg</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img5.avif"></p><p>现在,可以在网络浏览器中打开 flamegraph.svg</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2026-01-25/img6.avif"></p><p>使用perf Flame Graphs方式,能够从更深层的函数调用上,以图形化的方式看到MySQL是如何执行的,以及具体某个函数执行了多少次,能够更好地看到隐藏在进程之后的具体操作,相对于文本,图形化的展示,更容易被人阅读,也更容易发现性能瓶颈以及相应的优化方向。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2026/01/25/6abeceaf/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0.30 版本中redo log的变化</title>
      <link>https://blog.eucalyptus.cc/2025/12/20/d27e216a/</link>
      <guid>https://blog.eucalyptus.cc/2025/12/20/d27e216a/</guid>
      <pubDate>Sat, 20 Dec 2025 02:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;MySQL8-0-30-redo-log-动态调整&quot;&gt;&lt;a href=&quot;#MySQL8-0-30-redo-log-动态调整&quot; class=&quot;headerlink&quot; title=&quot;MySQL8.0.30 redo log</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="MySQL8-0-30-redo-log-动态调整"><a href="#MySQL8-0-30-redo-log-动态调整" class="headerlink" title="MySQL8.0.30 redo log 动态调整"></a>MySQL8.0.30 redo log 动态调整</h3><p>MySQL redo log记录数据记录变更,以及未数据一致性恢复提供保障。在运维MySQL 过程中,会遇到调整redo log 和redo buffer size 大小的需求,然而修改redo log 文件大小需要重启,不过 MySQL 8.0.30 版本中提供动态调整redo log 文件大小的功能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img1.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html">https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html</a></p><p>从 MySQL 8.0.30 开始, innodb_redo_log_capacity系统变量控制 redo log 总的大小。</p><p>因为在该版本以及之后的版本参数innodb_log_file_size 和 innodb_log_files_in_group 已经被废弃。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img2.avif"></p><p>如下图所示,8.0.30 版本对原来的循环覆盖写的结构进行了改造,不再以 redo 文件个数和单个 redo 文件的大小来进行限制,而是通过 innodb_redo_log_capacity来指定整个 redo 空间的大小。整个redo空间会被切成32个文件 固定个数 ,文件按照 ib_redo$SEQ 的方式进行编号,$SEQ 是一个递增的序列号。在文件管理上,所有的文件会被分成两类:</p><ul><li>normal redo 文件,命名为 ib_redo$SEQ,正常的 redo 文件,和以前一样,任意时刻只会有一个 redo 文件进行写入;</li><li>unused redo 文件,命名为 ib_redo$SEQ_tmp,未被使用的 redo 文件在被使用时,会被重命名为正常文件;</li></ul><p>后台的 log_files_governor 线程会负责处理已经写完成的文件,在满足回收条件时,会重新变成 unused redo 文件</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img4.avif"></p><p>当 innodb_redo_log_capacity 发生变化时,已经使用过的和正在使用过的 redo 文件并不会发生改变,仅需要调整 unused redo 文件。当用户修改 innodb_redo_log_capacity 时,会唤醒后台的 log_files_governor 线程,后台线程首先会重新计算当前的 redo_log_capacity,然后根据变化的类型:</p><ul><li>如果是空间放大,直接根据放大后的大小,重新生成新的 unused redo 文件;</li><li>如果是空间缩小,需要计算当前已使用的空间数能否满足目标值,如果满足,那么缩小过程和放大过程一样,直接重新生成新的 ununsed redo 文件即可;如果不能,还需要在更新 redo_log_capacity 之后,通过调整暴露给 log_writer 和 page_cleaner 线程的 lsn 信息,来加速空间回收;</li></ul><p>unused redo 文件的引入,类似于引入了缓存区的机制,因为 unused redo 文件不是正在使用的 redo 文件,所以可以直接进行重建,从而满足 innodb_redo_log_capacity 的设置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img6.avif"></p><p>在运行时设置时,配置更改会立即发生,但可能需要一些时间才能完全实现新的限制。如果重做日志文件占用的空间小于指定值,则脏页将从缓冲池中较不积极地刷新到表空间数据文件中,最终增加重做日志文件所占用的磁盘空间。如果重做日志文件占用的空间超过指定值,则会更积极地刷新脏页,最终减少重做日志文件所占用的磁盘空间。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img7.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html">https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html</a></p><h3 id="MySQL-8-0-17-redo-log归档"><a href="#MySQL-8-0-17-redo-log归档" class="headerlink" title="MySQL 8.0.17 redo log归档"></a>MySQL 8.0.17 redo log归档</h3><p>在需要备份重做日志以满足审计合规要求、进行数据库维护升级或迁移、以及在高负载系统中减少磁盘 I&#x2F;O 操作对性能影响的情况下特别有用。归档操作应在系统负载较低时进行,并且需要确保归档目录的安全性和正确配置。</p><p>在启用 redo log 归档之前,需要创建一个或多个目录来存储归档的 redo log,确保运行 mysqld的系统用户拥有该目录的访问权限。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> -p /var/lib/mysql-redo-archive/backup1</span><br><span class="line"><span class="built_in">chown</span> -R mysql.mysql /var/lib/mysql-redo-archive</span><br><span class="line"><span class="built_in">chmod</span> -R 700 /var/lib/mysql-redo-archive/</span><br></pre></td></tr></table></figure><p>使用 innodb_redo_log_archive_dirs 全局变量定义标记的归档路径,或者在配置文件种配置,格式为 label:directory-path,可以使用分号分隔多个条目。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">set</span> <span class="keyword">global</span> innodb_redo_log_archive_dirs <span class="string">&#x27;backup1:/var/lib/mysql-redo-archive/&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img8.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> variables <span class="keyword">like</span> <span class="string">&#x27;innodb_redo_log_archive_dirs&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img9.avif"></p><p>启动和停止归档,具有 innodb_redo_log_archive 权限的用户可以调用 innodb_redo_log_archive_start() 或 innodb_redo_log_archive_stop() 函数来启动或停止归档。</p><p>启动</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">do innodb_redo_log_archive_start(<span class="string">&#x27;backup1&#x27;</span>, <span class="string">&#x27;backup1&#x27;</span>);</span><br><span class="line"><span class="keyword">or</span></span><br><span class="line"><span class="keyword">select</span> innodb_redo_log_archive_start(<span class="string">&#x27;backup1&#x27;</span>, <span class="string">&#x27;backup1&#x27;</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img10.avif"></p><p>停止</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">do innodb_redo_log_archive_stop();</span><br><span class="line"><span class="keyword">or</span></span><br><span class="line"><span class="keyword">select</span> innodb_redo_log_archive_stop();</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img11.avif"></p><h3 id="MySQL-8-0-16-redo-log加密"><a href="#MySQL-8-0-16-redo-log加密" class="headerlink" title="MySQL 8.0.16 redo log加密"></a>MySQL 8.0.16 redo log加密</h3><p>MySQL 8.0.16版本以后可以使用innodb_redo_log_encrypt配置选项启用了Redo日志数据加密。默认情况下,Redo日志加密是禁用的。与表空间数据一样,Redo日志数据加密是在将数据写入磁盘时进行的,而解密是在从磁盘读取重做日志数据时进行的。一旦数据读入内存,它就处于未加密形式。使用表空间加密密钥对重做日志数据进行加密和解密。</p><p>启用innodb_redo_log_encrypt时,磁盘上存在的未加密Redo日志页面将保持未加密状态,新的Redo日志页面将以加密形式写入磁盘。同样,禁用innodb_redo_log_encrypt时,磁盘上存在的已加密Redo日志页面将保持加密状态,新的Redo日志页面将以未加密形式写入磁盘。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img12.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html">https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html</a></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> default_table_encryption <span class="keyword">ON</span>;</span><br></pre></td></tr></table></figure><h3 id="MySQL-8-0-21-redo-log禁用"><a href="#MySQL-8-0-21-redo-log禁用" class="headerlink" title="MySQL 8.0.21 redo log禁用"></a>MySQL 8.0.21 redo log禁用</h3><p>MySQL 8.0.21版本之后可以启禁用Redo log功能。可以通过避免写入Redo和doublewrite缓冲来加快数据加载。一般初期大量灌入数据是采用。平时就不建议使用此功能,意外发生 或 服务停止可能会导致数据丢失和实例损坏。</p><p>启禁用需要有INNODB_REDO_LOG_ENABLE权限</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">#启用</span><br><span class="line"><span class="keyword">ALTER</span> INSTANCE ENABLE INNODB REDO_LOG;</span><br><span class="line"><span class="keyword">SHOW</span> <span class="keyword">GLOBAL</span> STATUS <span class="keyword">LIKE</span> <span class="string">&#x27;Innodb_redo_log_enabled&#x27;</span>;</span><br><span class="line">#禁用</span><br><span class="line"><span class="keyword">ALTER</span> INSTANCE DISABLE INNODB REDO_LOG;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-20/img13.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/12/20/d27e216a/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>从Miniflux 到 NextFlux：一步升级，拥抱现代化阅读体验</title>
      <link>https://blog.eucalyptus.cc/2025/12/11/e848d122/</link>
      <guid>https://blog.eucalyptus.cc/2025/12/11/e848d122/</guid>
      <pubDate>Thu, 11 Dec 2025 03:51:56 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;前段时间我部署了Miniflux，这是一款功能强大的极简主义RSS订阅器，它支持多平台同步、文章过滤和离线阅读等实用功能，完全满足了我的信息聚合需求；不过它的界面设计确实过于朴素，采用了最基础的列表布局和单调的配色方案，在这个视觉至上的时代里，这种毫不修饰的极简风格可能会让</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>前段时间我部署了Miniflux，这是一款功能强大的极简主义RSS订阅器，它支持多平台同步、文章过滤和离线阅读等实用功能，完全满足了我的信息聚合需求；不过它的界面设计确实过于朴素，采用了最基础的列表布局和单调的配色方案，在这个视觉至上的时代里，这种毫不修饰的极简风格可能会让许多用户在初次接触时就失去耐心，随手划走转而选择那些界面更炫目、交互更花哨的阅读应用。</p><p>因此，为了弥补 Miniflux 在视觉和交互体验上的不足，我这次专门挑选了一款高颜值的第三方客户端 Nextflux。它不仅继承了 Miniflux 强大的 RSS 订阅和内容聚合功能，更通过现代化的界面设计、流畅的动画效果和直观的操作逻辑，大幅提升了用户的使用愉悦感。例如，Nextflux 支持暗黑模式与自定义主题，卡片式布局让信息浏览更加清晰高效，同时保留了 Miniflux 原有的离线阅读与全文抓取等核心能力，真正实现了功能与美感的平衡。</p><p>Nextflux 是一个基于现代化技术栈精心打造的 RSS 阅读器客户端，它专门为开源的Miniflux后端服务设计，完美融合了便捷性和功能性。该客户端采用前沿的React框架进行用户界面开发，并结合Vite这一高效构建工具，不仅确保了极速的热重载和流畅的开发体验，还优化了生产环境的打包性能，为用户提供轻量、响应迅速且高度可定制的阅读界面。无论是订阅源的智能管理、文章的分类筛选，还是跨设备的同步阅读，Nextflux都致力于提升信息获取的效率和舒适度，让用户能够专注于内容本身，而无需为技术细节分心。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/1.avif"></p><p>Nextflux与Miniflux类似，同样采用轻量级的容器化部署方式，能够通过Docker或Podman等工具快速搭建和运行，极大简化了安装与维护流程；这种部署模式不仅确保了环境的一致性，还支持灵活扩展与版本管理，特别适合个人或小团队在云服务器、本地主机乃至树莓派等设备上高效部署，同时保持了低资源占用和高稳定性的特点。</p><p>由于之前部署了Miniflux下面就直接部署Nextflux了，当然再结尾也会附上Miniflux+Nextflux+DB的完整yml文件</p><p>使用下述命令直接拉起nextflux的容器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd  --restart unless-stopped  --name nextflux  -p 8121:3000    electh/nextflux:latest</span><br></pre></td></tr></table></figure><p>这里需要注意下Nextflux容器的端口</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/2.avif"></p><p>拉起容器后，直接通过宿主机的IP地址加上映射的8121端口（如<code>http://192.168.1.100:8121</code>）在浏览器中访问即可；若页面加载失败，通常是由于端口映射错误导致的，此时需要检查容器日志确认实际监听的端口号，既可以通过命令行方式查看（如执行<code>docker logs 容器ID</code>命令获取详细日志），也可以在宝塔面板的”容器管理”界面中直观地查看运行日志，此外还需确认服务器防火墙是否放行了该端口，这些都是导致访问失败的常见原因。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/3.avif"></p><p>到这里基本上就可以看到Nextflux的登录界面了，我们可以看到这里除了用户名和密码外，还有个服务地址，这个服务地址就是Miniflux的访问地址，但是有几点需要注意</p><ul><li>如果你浏览器访问Nextflux的地址使用的是ip，那么服务地址这里就需要使用 <code>http://ip:port</code>，</li><li>如果你浏览器访问Nextflux的地址使用的域名，那么服务地址这里必须使用 <code>https://域名</code></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/4.avif"></p><p>下面，我们来详细分析使用IP地址访问时出现”Failed to fetch”错误的问题：当按照本文的部署方式部署Nextflux和Miniflux后，即使使用同一IP地址访问也会遇到跨域问题，这是因为浏览器严格执行同源策略，会对比前端页面来源和API请求地址的协议、域名和端口是否完全一致。具体来说，假设你通过<code>http://140.143.94.243:8121</code>访问Nextflux前端界面，而该前端尝试向<code>http://140.143.94.243:80</code>的Miniflux后端发起API请求时，虽然IP地址相同，但由于端口号不同（8121 vs 80），浏览器会判定为跨域请求，此时浏览器会先发送一个OPTIONS预检请求来检查服务器是否允许跨域访问；如果Miniflux后端没有正确配置CORS头部信息，特别是缺少关键的Access-Control-Allow-Origin响应头，或者该头部的值不包含前端来源地址，浏览器就会直接拦截后续的实际请求，导致前端控制台报出”Failed to fetch”错误。要解决这个问题，最直接的方法是在启动Miniflux容器时添加两个必要的环境变量，这些配置会让Miniflux正确处理跨域请求并返回适当的CORS头部，修改后需要重启Miniflux容器使配置生效。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">environment:</span><br><span class="line">  - CORS_ORIGINS=http://140.143.94.243:8121</span><br><span class="line">  - CORS_ALLOW_HEADERS=*</span><br></pre></td></tr></table></figure><p>这里我建议直接使用宝塔面板的可视化操作界面进行操作，这样不仅能显著提高操作容错率，还能避免因手动输入命令导致的潜在错误；关于yml配置文件，我们可以直接复用之前部署Miniflux时使用的模板文件，只需在数据库配置部分额外添加这两个关键环境变量即可，完成这些修改后，直接保存配置文件即可生效，此时我们再次通过IP地址访问服务并进行登录操作，整个过程就会变得非常顺畅，不会再出现之前遇到的连接或认证问题，这种方案既保留了原有配置的稳定性，又通过最小改动实现了新功能的支持。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-12-11/6.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br></pre></td><td class="code"><pre><span class="line">services:</span><br><span class="line">  miniflux:</span><br><span class="line">    image: miniflux/miniflux:latest</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;8383:8080&quot;</span></span><br><span class="line">    depends_on:</span><br><span class="line">      db:</span><br><span class="line">        condition: service_healthy</span><br><span class="line">    environment:</span><br><span class="line">      - DATABASE_URL=postgres://miniflux:admin@123@db/miniflux?sslmode=<span class="built_in">disable</span></span><br><span class="line">      - RUN_MIGRATIONS=1</span><br><span class="line">      - CREATE_ADMIN=1</span><br><span class="line">      - ADMIN_USERNAME=admin</span><br><span class="line">      - ADMIN_PASSWORD=admin@123</span><br><span class="line">  - CORS_ORIGINS=http://140.143.94.243:8121   <span class="comment">#填写你的实际ip和port</span></span><br><span class="line">      - CORS_ALLOW_HEADERS=*</span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;/usr/bin/miniflux&quot;</span>, <span class="string">&quot;-healthcheck&quot;</span>, <span class="string">&quot;auto&quot;</span>]</span><br><span class="line"></span><br><span class="line">  db:</span><br><span class="line">    image: postgres:17-alpine</span><br><span class="line">    environment:</span><br><span class="line">      - POSTGRES_USER=miniflux</span><br><span class="line">      - POSTGRES_PASSWORD=admin@123</span><br><span class="line">      - POSTGRES_DB=miniflux</span><br><span class="line">    volumes:</span><br><span class="line">      - miniflux-db:/var/lib/postgresql/data</span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;pg_isready&quot;</span>, <span class="string">&quot;-U&quot;</span>, <span class="string">&quot;miniflux&quot;</span>]</span><br><span class="line">      interval: 10s</span><br><span class="line">      start_period: 30s</span><br><span class="line"></span><br><span class="line">volumes:</span><br><span class="line">  miniflux-db:</span><br></pre></td></tr></table></figure><p>最后，我们重点讲解使用域名访问和登录时需要注意的技术细节，特别是关于HTTPS协议和URL格式规范的问题。当使用HTTPS协议访问Miniflux服务时，必须确保后端服务地址同样采用HTTPS协议，否则浏览器会因混合内容安全策略而阻止请求。这里特别要强调的是URL尾斜杠的处理问题：如果你在服务地址栏输入的是类似”<code>https://miniflux.eucalyptus.cc/</code>这样带有尾斜杠的地址，而前端JavaScript代码在拼接API路径时又没有正确处理这个斜杠，就会产生<code>https://miniflux.eucalyptus.cc**//**api/me</code>这样的双斜杠路径。这种URL格式错误虽然看起来很小，但会导致严重的后果：大多数现代Web服务器（如Nginx、Apache）会将其视为无效路径，返回404 Not Found错误；而浏览器端的fetch API则会抛出”Failed to fetch”的通用错误，给调试带来困难。这个问题在单页应用(SPA)开发中尤为常见，正确的做法应该是在配置文件中统一规范基础URL格式，或者在JavaScript代码中加入路径标准化处理逻辑，确保API请求的URL始终保持正确的单斜杠格式。</p><p>如果你之前没有部署过Miniflux这个轻量级RSS阅读器的话，使用docker-compose进行一体化安装是最便捷的方式，首先你需要创建一个名为docker-compose.yml的配置文件，将以下内容完整复制进去，其中包括了Miniflux服务及其必需的PostgreSQL数据库配置，确保网络设置和端口映射（通常Miniflux默认使用8080端口）正确无误后，在当前目录下执行docker-compose up -d命令即可启动容器编排，系统会自动拉取最新镜像并完成所有依赖服务的部署，整个过程无需手动干预，非常适合快速搭建个人阅读服务。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br></pre></td><td class="code"><pre><span class="line">version: <span class="string">&#x27;3&#x27;</span></span><br><span class="line"></span><br><span class="line">services:</span><br><span class="line">  miniflux:</span><br><span class="line">    image: miniflux/miniflux:latest</span><br><span class="line">    container_name: miniflux-server</span><br><span class="line">    restart: unless-stopped</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;8120:8080&quot;</span></span><br><span class="line">    depends_on:</span><br><span class="line">      db:</span><br><span class="line">        condition: service_healthy</span><br><span class="line">    environment:</span><br><span class="line">      - DATABASE_URL=postgres://miniflux:secret@db/miniflux?sslmode=<span class="built_in">disable</span></span><br><span class="line">      - RUN_MIGRATIONS=1</span><br><span class="line">      - CREATE_ADMIN=1</span><br><span class="line">      - ADMIN_USERNAME=admin</span><br><span class="line">      - ADMIN_PASSWORD=test123</span><br><span class="line">  </span><br><span class="line">  db:</span><br><span class="line">    image: postgres:17-alpine</span><br><span class="line">    container_name: miniflux-db</span><br><span class="line">    restart: unless-stopped</span><br><span class="line">    environment:</span><br><span class="line">      - POSTGRES_USER=miniflux</span><br><span class="line">      - POSTGRES_PASSWORD=secret</span><br><span class="line">      - POSTGRES_DB=miniflux</span><br><span class="line">    volumes:</span><br><span class="line">      - ./data:/var/lib/postgresql/data</span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;pg_isready&quot;</span>, <span class="string">&quot;-U&quot;</span>, <span class="string">&quot;miniflux&quot;</span>]</span><br><span class="line">      interval: 10s</span><br><span class="line">      start_period: 30s</span><br><span class="line"></span><br><span class="line">  nextflux:</span><br><span class="line">    image: electh/nextflux:latest</span><br><span class="line">    container_name: miniflux-nextflux</span><br><span class="line">    restart: unless-stopped</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;8121:80&quot;</span></span><br></pre></td></tr></table></figure><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker-compose up -d</span><br></pre></td></tr></table></figure><p>这种联合部署的方式Eucalyptus之前确实没有尝试过，主要参考了AWS和Azure的混合云架构设计思路，并结合了《云计算架构设计模式》一书中提到的服务网格集成方案，如果有任何配置问题或性能优化建议，欢迎各位技术同行在评论区留言讨论。另外Eucalyptus部署的Nextflux测试环境已经稳定运行两周，访问地址是<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://nextflux.eucalyptus.cc">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://nextflux.eucalyptus.cc/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://nextflux.eucalyptus.cc/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Nextflux 测试环境</div>            <div class="tag-link-sitename">RSS聚合平台</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>，该平台集成了实时数据流处理和可视化分析功能，各位朋友如果需要测试体验的话可以留言说明具体，Eucalyptus会根据使用场景为大家提供免费的测试账号。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/RSS/">RSS</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Miniflux/">Miniflux</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/12/11/e848d122/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>gh-ost菜鸟教程</title>
      <link>https://blog.eucalyptus.cc/2025/12/10/86c3fbe0/</link>
      <guid>https://blog.eucalyptus.cc/2025/12/10/86c3fbe0/</guid>
      <pubDate>Wed, 10 Dec 2025 05:40:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h3&gt;&lt;p&gt;&lt;code&gt;gh-ost&lt;/code&gt; 是 GitHub 开发的一款用于 MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h3><p><code>gh-ost</code> 是 GitHub 开发的一款用于 MySQL 数据库的在线模式迁移解决方案,它支持无触发器的在线模式迁移。这个工具是可测试的,并提供暂停、动态控制&#x2F;重新配置、审计以及许多操作特权。<code>gh-ost</code> 旨在改变表迁移的范式,它在迁移过程中对主服务器产生的工作量很小,并且与已迁移表上的现有工作负载分离,从而减少对数据库性能的影响。</p><h4 id="原理"><a href="#原理" class="headerlink" title="原理"></a>原理</h4><p>主要实现原理,首先建两张表,一张_gho的影子表,gh-ost会将原表数据以及增量数据都应用到这个表,最后会将这个表和原表做次表名切换,另一张是_ghc表,这个表是存放changelog的数据,包括信号标记,心跳等。其次 ,gh-ost会开两个goroutine,一个用于拷贝原表数据,一个用于apply增量的binlog到_gho表,并且两个goroutine的并行在跑的,也就是不用关心数据是先拷贝过去还是先apply binlog过去。因为这里会对insert语句做调整,首先我们拷贝的insert into会改写成insert ignore into,而binlog内insert into会改写成replace into,这样可以很好的支持两个goroutine的并行。但这样的调整能适用所有的DDL吗?答案是否定的。最后,当原表数据全部拷贝完成后,gh-ost会进入到表交换阶段,采用更加安全的原子交换。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img1.avif"></p><h4 id="过程"><a href="#过程" class="headerlink" title="过程"></a>过程</h4><ul><li>检查有没有外键和触发器。</li><li>检查表的主键信息。</li><li>检查是否主库或从库,是否开启log_slave_updates,以及binlog信息</li><li>检查gho和del结尾的临时表是否存在</li><li>创建ghc结尾的表,存数据迁移的信息,以及binlog信息等<br><em><strong>—以上校验阶段</strong></em></li><li>初始化stream的连接,添加binlog的监听<br><em><strong>—以下迁移阶段</strong></em></li><li>创建gho结尾的临时表,执行DDL在gho结尾的临时表上</li><li>开启事务,按照主键id把源表数据写入到gho结尾的表上,再提交,以及binlog apply。<br><em><strong>—以下cut-over阶段</strong></em></li><li>lock源表,rename 表:rename 源表 to 源_del表,gho表 to 源表。</li><li>清理ghc表</li></ul><h3 id="安装"><a href="#安装" class="headerlink" title="安装"></a>安装</h3><p>由于gh-ost是基于go1.5编译的,故安装gh-ost之前需要安装go,安装go 我的yum仓库中有go包,故直接使用yum安装,没有的话需要进行下载tar包源码安装</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img2.avif"></p><p>验证go是否安装成功</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">go env</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img3.avif"></p><p>接下来安装gh-ost,由于gh-ost的tar包再github中,下载的时候可能由于网络的原因导致下载失败,故我们使用gitee中的项目</p><p><a href="https://gitee.com/mirrors/gh-ost">https://gitee.com/mirrors/gh-ost</a></p><p>我这里直接下载的zip包,然后上传到服务器</p><p>下载到服务器上后进行解压</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">unzip gh-ost-master.zip</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img4.avif"></p><p>解压之后进入gh-ost-master目录,</p><p>然后再当前的目录下初始化一个git仓库</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">git init</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img5.avif"></p><p>然后需要在build.sh中指定gh-ost版本</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img6.avif"></p><p>打开build.sh脚本设置你需要的gh-ost版本,然后保存,</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">RELEASE_VERSION v1.1.7</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img7.avif"></p><p>然后运行build.sh脚本</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img8.avif"></p><p>接下来解压适用于你操作系统的tar包,</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">tar xvzf gh-ost-binary-linux-amd64-20251022142618.tar.gz</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img9.avif"></p><p>最后将gh-ost二进制文件移动到&#x2F;usr&#x2F;local&#x2F;bin下,然后使用gh-ost –version验证gh-ost是否安装成功</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mv</span> gh-ost /usr/local/bin/</span><br><span class="line">gh-ost --version</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img10.avif"></p><h3 id="实战-单节点"><a href="#实战-单节点" class="headerlink" title="实战 单节点"></a>实战 单节点</h3><p>我们创建了一个example_table表,然后使用gh-ost删除这个表中的全文索引ftx_first_name</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> example_table(</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT,</span><br><span class="line">first_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">last_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">100</span>),</span><br><span class="line">created_at <span class="type">TIMESTAMP</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">status ENUM(<span class="string">&#x27;active&#x27;</span>, <span class="string">&#x27;inactive&#x27;</span>) <span class="keyword">DEFAULT</span> <span class="string">&#x27;active&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> (id),</span><br><span class="line">INDEX idx_last_name (last_name),</span><br><span class="line">FULLTEXT INDEX ftx_first_name (first_name),</span><br><span class="line">INDEX idx_status (status),</span><br><span class="line">INDEX idx_created_at (created_at),</span><br><span class="line">INDEX idx_first_name_last_name (first_name, last_name)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img11.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">gh<span class="operator">-</span>ost \</span><br><span class="line"><span class="comment">--host 127.0.0.1 \</span></span><br><span class="line"><span class="comment">--user root \</span></span><br><span class="line"><span class="comment">--password 123456 \</span></span><br><span class="line"><span class="comment">--database demo1 \</span></span><br><span class="line"><span class="comment">--table example_table \</span></span><br><span class="line"><span class="comment">--alter DROP INDEX ftx_first_name \</span></span><br><span class="line"><span class="comment">--execute \</span></span><br><span class="line"><span class="comment">--allow-on-master</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img12.avif"></p><p>可以看到example_table中的全文索引ftx_first_name已经删除</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img13.avif"></p><p>通过解析binlog我们可以看到首先gh-ost创建了存放changelog的 demo1 . _example_table_ghc 表,然后创建了影子表 demo1 . _example_table_gho</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img14.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="comment">/* gh-ost */</span> <span class="keyword">table</span> demo1 . _example_table_ghc (</span><br><span class="line">id <span class="type">bigint</span> unsigned auto_increment,</span><br><span class="line">last_update <span class="type">timestamp</span> <span class="keyword">not null</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span> <span class="keyword">ON</span> <span class="keyword">UPDATE</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">hint <span class="type">varchar</span>(<span class="number">64</span>) charset ascii <span class="keyword">not null</span>,</span><br><span class="line"><span class="keyword">value</span> <span class="type">varchar</span>(<span class="number">4096</span>) charset ascii <span class="keyword">not null</span>,</span><br><span class="line"><span class="keyword">primary key</span>(id),</span><br><span class="line"><span class="keyword">unique</span> key hint_uidx(hint)</span><br><span class="line">) auto_increment <span class="number">256</span> comment <span class="string">&#x27;gh-ost changelog&#x27;</span></span><br><span class="line"><span class="comment">/*!*/</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>随后在影子表 demo1 . _example_table_gho 执行了ddl,并设置了AUTO_INCREMENT</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img15.avif"></p><p>binlog中继续往下看,在end_log_pos 18708,又创建了 demo1 . _example_table_del</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img16.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="comment">/* gh-ost */</span> <span class="keyword">table</span> demo1 . _example_table_del (</span><br><span class="line">id <span class="type">int</span> auto_increment <span class="keyword">primary key</span></span><br><span class="line">) engine InnoDB comment <span class="string">&#x27;ghost-cut-over-sentry&#x27;</span></span><br><span class="line"><span class="comment">/*!*/</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>在end_log_pos 24355,删除了 _example_table_del</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img17.avif"></p><p>在end_log_pos 25086,使用rename了</p><p>将 demo1 . example_table 重命名为 demo1 . _example_table_del</p><p>将 demo1 . _example_table_gho 重命名为 demo1 . example_table</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img18.avif"></p><p>最后删除了 _example_table_ghc 和 _example_table_ghk</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-12-10/img19.avif"></p><p>开发板推荐：天空星STM32F407VET6开发板</p><p>超高性价比 STM32主控 | 超高主频 | 一板兼容百芯 | 比赛神器 | 沉金彩色丝印</p><p>点击查看</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/12/10/86c3fbe0/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的数据类型占用空间和范围</title>
      <link>https://blog.eucalyptus.cc/2025/11/28/190cf8ac/</link>
      <guid>https://blog.eucalyptus.cc/2025/11/28/190cf8ac/</guid>
      <pubDate>Fri, 28 Nov 2025 03:15:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;数据类型&lt;/th&gt;
&lt;th&gt;描述&lt;/th&gt;
&lt;th&gt;占用空间&lt;/th&gt;
&lt;th&gt;最大值~最小值 (SIGNED)&lt;/th&gt;
&lt;th&gt;最大值~最小值</description>
          
        
      
      
      
      <content:encoded><![CDATA[<table><thead><tr><th>数据类型</th><th>描述</th><th>占用空间</th><th>最大值~最小值 (SIGNED)</th><th>最大值~最小值 (UNSIGNED)</th></tr></thead><tbody><tr><td>TINYINT</td><td>微整数</td><td>1 byte</td><td>-128 ~ 127</td><td>0 ~ 255</td></tr><tr><td>SMALLINT</td><td>小整数</td><td>2 bytes</td><td>-32768 ~ 32767</td><td>0 ~ 65535</td></tr><tr><td>MEDIUMINT</td><td>中等整数</td><td>3 bytes</td><td>-8388608 ~ 8388607</td><td>0 ~ 16777215</td></tr><tr><td><strong>INT</strong> 或 INTEGER</td><td>整数</td><td>4 bytes</td><td>-2147483648 ~ 2147483647</td><td>0 ~ 4294967295</td></tr><tr><td><strong>BIGINT</strong></td><td>大整数</td><td>8 bytes</td><td>-9223372036854775808 ~ 9223372036854775807</td><td>0 ~ 18446744073709551615</td></tr><tr><td>FLOAT</td><td>单精度浮点数</td><td>4 bytes</td><td>-3.40282347E 38 ~ 3.40282347E 38</td><td>0 ~ 3.40282347E 38</td></tr><tr><td>DOUBLE</td><td>双精度浮点数</td><td>8 bytes</td><td>-1.7976931348623157E 308 ~ 1.7976931348623157E 308</td><td>0 ~ 1.7976931348623157E 308</td></tr><tr><td>DECIMAL(M,D)</td><td>精确小数,M为总位数,D为小数位</td><td>M 2字节</td><td>取决于M和D</td><td>取决于M和D</td></tr><tr><td>DATE</td><td>日期</td><td>3 bytes</td><td>0000-01-01 ~ 9999-12-31</td><td>0000-01-01 ~ 9999-12-31</td></tr><tr><td>TIME</td><td>时间</td><td>3 bytes</td><td>-838:59:59 ~ 838:59:59</td><td>00:00:00 ~ 838:59:59</td></tr><tr><td>DATETIME</td><td>日期时间</td><td>5 bytes</td><td>0000-01-01 00:00:00 ~ 9999-12-31 23:59:59</td><td>0000-01-01 00:00:00 ~ 9999-12-31 23:59:59</td></tr><tr><td>TIMESTAMP</td><td>时间戳</td><td>4 bytes</td><td>1970-01-01 00:00:01 UTC ~ 2038-01-19 03:14:07 UTC</td><td>1970-01-01 00:00:01 UTC ~ 2038-01-19 03:14:07 UTC</td></tr><tr><td>YEAR</td><td>年份</td><td>1 byte</td><td>1901 ~ 2155</td><td>1901 ~ 2155</td></tr><tr><td><strong>CHAR(M)</strong></td><td>固定长度字符串</td><td>M bytes</td><td>空字符串 ~ M字符字符串</td><td>空字符串 ~ M字符字符串</td></tr><tr><td><strong>VARCHAR(M)</strong></td><td>可变长度字符串</td><td>长度 1 byte</td><td>空字符串 ~ M字符字符串</td><td>空字符串 ~ M字符字符串</td></tr><tr><td>TINYTEXT</td><td>小文本</td><td>长度 1 byte</td><td>空字符串 ~ 255字符字符串</td><td>空字符串 ~ 255字符字符串</td></tr><tr><td>TEXT</td><td>文本</td><td>长度 2 bytes</td><td>空字符串 ~ 65,535字符字符串</td><td>空字符串 ~ 65,535字符字符串</td></tr><tr><td>MEDIUMTEXT</td><td>中等文本</td><td>长度 3 bytes</td><td>空字符串 ~ 16,777,215字符字符串</td><td>空字符串 ~ 16,777,215字符字符串</td></tr><tr><td>LONGTEXT</td><td>大文本</td><td>长度 4 bytes</td><td>空字符串 ~ 4,294,967,295字符字符串</td><td>空字符串 ~ 4,294,967,295字符字符串</td></tr><tr><td>BINARY(M)</td><td>固定长度二进制字符串</td><td>M bytes</td><td>空字符串 ~ M字节字符串</td><td>空字符串 ~ M字节字符串</td></tr><tr><td>VARBINARY(M)</td><td>可变长度二进制字符串</td><td>长度 1 byte</td><td>空字符串 ~ M字节字符串</td><td>空字符串 ~ M字节字符串</td></tr><tr><td>TINYBLOB</td><td>小BLOB</td><td>长度 1 byte</td><td>空二进制字符串 ~ 255字节</td><td>空二进制字符串 ~ 255字节</td></tr><tr><td>BLOB</td><td>BLOB</td><td>长度 2 bytes</td><td>空二进制字符串 ~ 65,535字节</td><td>空二进制字符串 ~ 65,535字节</td></tr><tr><td>MEDIUMBLOB</td><td>中等BLOB</td><td>长度 3 bytes</td><td>空二进制字符串 ~ 16,777,215字节</td><td>空二进制字符串 ~ 16,777,215字节</td></tr><tr><td>LONGBLOB</td><td>大BLOB</td><td>长度 4 bytes</td><td>空二进制字符串 ~ 4,294,967,295字节</td><td>空二进制字符串 ~ 4,294,967,295字节</td></tr><tr><td>ENUM(‘value1’,…)</td><td>枚举,预定义字符串列表中选择</td><td>1~2 bytes</td><td>取决于枚举值</td><td>取决于枚举值</td></tr><tr><td>SET(‘value1’,…)</td><td>集合,预定义字符串列表中选择</td><td>1~8 bytes</td><td>取决于集合值</td><td>取决于集合值</td></tr><tr><td>BIT(M)</td><td>位字段</td><td>M bits</td><td>0 ~ 2^M - 1</td><td>0 ~ 2^M - 1</td></tr><tr><td>GEOMETRY</td><td>空间几何数据类型</td><td>可变</td><td>取决于数据大小</td><td>取决于数据大小</td></tr><tr><td>POINT</td><td>点类型</td><td>可变</td><td>取决于数据大小</td><td>取决于数据大小</td></tr><tr><td>LINESTRING</td><td>线字符串类型</td><td>可变</td><td>取决于数据大小</td><td>取决于数据大小</td></tr><tr><td>POLYGON</td><td>多边形类型</td><td>可变</td><td>取决于数据大小</td><td>取决于数据大小</td></tr><tr><td>JSON</td><td>JSON数据类型</td><td>可变</td><td>取决于JSON数据大小</td><td>取决于JSON数据大小</td></tr></tbody></table>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/11/28/190cf8ac/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MiniFlux安全升级</title>
      <link>https://blog.eucalyptus.cc/2025/11/08/d24ee1a7/</link>
      <guid>https://blog.eucalyptus.cc/2025/11/08/d24ee1a7/</guid>
      <pubDate>Sat, 08 Nov 2025 08:39:45 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在信息过载的时代，RSS 依旧是高效获取优质内容的“净土”。Miniflux 以轻量、简洁、开源的姿态，成为许多技术人自托管 RSS 的首选。然而，只在内网 IP 下阅读未免辜负了它的优雅；给 Miniflux 配一个专属的二级域名，再披上 HTTPS</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在信息过载的时代，RSS 依旧是高效获取优质内容的“净土”。Miniflux 以轻量、简洁、开源的姿态，成为许多技术人自托管 RSS 的首选。然而，只在内网 IP 下阅读未免辜负了它的优雅；给 Miniflux 配一个专属的二级域名，再披上 HTTPS 的“安全外衣”，不仅能让阅读随时随地、安全无虞，更是对自己数字领地的一次仪式感升级。接下来的篇幅，我们一起把<code>localhost:8383</code>变成<code>https://miniflux.eucalyptus.cc/</code>，让每一次订阅与更新都拥有值得收藏的新地址。</p><p>首先本篇文章中使用的是二级域名，大伙都知道域名是需要进行备案的，“而二级域名需不需要备案”取决于它的一级域名是否已经取得备案号，以及二者是否使用同一家云接入商，大致分为以下几种情况。</p><ul><li>一级域名已备案，且二级域名与一级域名在同一接入商 → 二级域名无需单独备案。</li><li>一级域名已备案，但二级域名要换到另一家国内接入商 → 先做一次“新增接入备案”，等通过后才能解析到新 IP。</li><li>一级域名没有任何备案号 → 必须先把一级域名提交首次备案，二级域名才能在中国大陆正常访问。</li><li>政府&#x2F;事业单位的<code>.gov.cn</code>等后缀二级域名 → 无论一级域名是否已备案，都要单独备案。</li></ul><p>只要网站服务器放在中国大陆，访问者能直接通过二级域名打开网页，就适用上述规则；如果服务器在境外，理论上不受中国备案系统约束，但国内 DNS&#x2F;CDN 厂商通常仍会提示“一级域名需已备案”才能开启加速或防护功能。</p><p>备案就不过多赘述了，如果不清楚的，可以参考下这篇文章：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://blog.csdn.net/weixin_72610956/article/details/135545236">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://blog.csdn.net/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://blog.csdn.net/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">网站ICP备案和公安备案教程</div>            <div class="tag-link-sitename">CSDN文章</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>，下面直接进行二级域名解析教程</p><p>这里以阿里云为例，在一级域名中添加一条解析记录时，首先需要登录阿里云控制台并进入域名解析管理页面，在DNS解析设置中选择”添加记录”选项，这里的记录类型可以根据实际需求选择A类型（用于将域名指向IPv4地址），主机记录则填写你的二级域名前缀（如”www”或”blog”等），记录值需要填写对应服务器的公网IP地址（对于A记录），TTL（生存时间）通常保持默认值即可，但也可以根据业务需求进行调整，设置完成后点击确认即可完成解析记录的添加，一般情况下解析会在10分钟内生效，但受各地DNS缓存影响，全球完全生效可能需要24-48小时。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-11-08/1.avif"></p><p>接下来进行Nginx反向代理的配置，全程使用宝塔面板的可视化界面操作，首先登录宝塔面板后，在左侧导航栏找到”网站”模块并点击进入，在菜单中选择”反向代理”选项，这时会显示当前站点的反向代理配置页面，然后点击左上角的”添加反向代理”按钮</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-11-08/2.avif"></p><p>在域名配置栏中，需要填写之前在域名控制台已解析完成的二级域名（如”test.example.com”），目标URL地址则应填写本地服务器地址<code>http://127.0.0.1</code>并加上对应的服务端口号（例如<code>:8383</code>表示该服务运行在8383端口），发送域名host保持默认设置即可（通常为自动填充的当前域名），备注栏可根据实际需求填写该条记录的相关说明（如”测试环境API服务”或”开发调试用”等描述性内容），确认所有信息无误后点击保存按钮完成配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-11-08/3.avif"></p><p>最后为刚才配置的反向代理服务开启HTTPS加密连接，首先在控制面板中找到并点击刚才添加的反向代理条目右侧的设置按钮，在弹出的菜单中选择”SSL”选项，然后选择<code>Let’sL Encrypt</code>免费证书服务，系统会自动验证域名所有权并生成证书请求，验证通过后点击”申请证书”按钮，等待证书签发完成后，务必记得点击”部署”按钮将证书应用到当前反向代理配置中，这样就能为网站流量提供端到端的加密保护，有效防止数据在传输过程中被窃听或篡改，同时还能提升网站在搜索引擎中的排名。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-11-08/4.avif"></p><p>到这里Miniflux 安全升级的全部部署工作已经圆满完成，我们不仅为Eucalyptus的个人RSS阅读器Miniflux绑定了专属域名miniflux.eucalyptus.cc，还成功配置了HTTPS加密协议，确保数据传输的安全性，现在您可以通过<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://miniflux.eucalyptus.cc/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://miniflux.eucalyptus.cc/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://miniflux.eucalyptus.cc/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Miniflux 安全访问地址</div>            <div class="tag-link-sitename">RSS阅读器</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>这个安全链接访问这个清爽简洁的RSS聚合平台，该平台采用Go语言开发，具有极低的资源占用和快速的响应速度，特别适合追求高效阅读体验的用户，如果您对这款轻量级RSS阅读器感兴趣，想要亲自体验它的强大功能，比如文章分类管理、快捷键操作、多设备同步等特性，欢迎在评论区留言，Eucalyptus会热情地为每位感兴趣的朋友创建专属测试账号，让您零门槛感受Miniflux的独特魅力。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/RSS/">RSS</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Miniflux/">Miniflux</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/11/08/d24ee1a7/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>py_innodb_page_info.py表空间分析</title>
      <link>https://blog.eucalyptus.cc/2025/10/30/83670dc6/</link>
      <guid>https://blog.eucalyptus.cc/2025/10/30/83670dc6/</guid>
      <pubDate>Thu, 30 Oct 2025 08:25:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;介绍&quot;&gt;&lt;a href=&quot;#介绍&quot; class=&quot;headerlink&quot; title=&quot;介绍&quot;&gt;&lt;/a&gt;介绍&lt;/h3&gt;&lt;p&gt;由《MySQL技术内幕 InnoDB存储引擎》一书的作者姜承尧开发的 py_innodb_page_info.py</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="介绍"><a href="#介绍" class="headerlink" title="介绍"></a>介绍</h3><p>由《MySQL技术内幕 InnoDB存储引擎》一书的作者姜承尧开发的 py_innodb_page_info.py 是一款功能强大的工具,旨在深入分析MySQL表空间中的页面类型及其详细信息。该工具采用Python编写,由三个文件组成: py_innodb_page_info.py 、 mylib.py 和 include.py 。为了确保工具的正常运行,这三个文件需要放置在同一个目录下。</p><p>值得注意的是,该工具需要在Python 2的环境中运行。如果在Python 3环境下使用,可能会遇到兼容性问题,导致运行出错。此外, py_innodb_page_info.py 工具专门设计用于解析MySQL 5.7版本的 .ibd 文件。对于MySQL 8.0及更高版本的 .ibd 文件,该工具可能无法正确解析。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img1.avif"></p><h3 id="include-py"><a href="#include-py" class="headerlink" title="include.py"></a>include.py</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br></pre></td><td class="code"><pre><span class="line">#include.py</span><br><span class="line">#encoding utf<span class="number">-8</span></span><br><span class="line">INNODB_PAGE_SIZE <span class="number">1024</span> <span class="operator">*</span> <span class="number">16</span> # InnoDB Page <span class="number">16</span>K</span><br><span class="line"></span><br><span class="line"># <span class="keyword">Start</span> <span class="keyword">of</span> the data <span class="keyword">on</span> the page</span><br><span class="line">FIL_PAGE_DATA <span class="number">38</span></span><br><span class="line"></span><br><span class="line">FIL_PAGE_OFFSET <span class="number">4</span> # page <span class="keyword">offset</span> inside space</span><br><span class="line">FIL_PAGE_TYPE <span class="number">24</span> # File page type</span><br><span class="line"></span><br><span class="line"># Types <span class="keyword">of</span> an undo log segment <span class="operator">*</span><span class="operator">/</span></span><br><span class="line">TRX_UNDO_INSERT <span class="number">1</span></span><br><span class="line">TRX_UNDO_UPDATE <span class="number">2</span></span><br><span class="line"></span><br><span class="line"># <span class="keyword">On</span> a page <span class="keyword">of</span> <span class="keyword">any</span> file segment, data may be put starting <span class="keyword">from</span> this <span class="keyword">offset</span></span><br><span class="line">FSEG_PAGE_DATA FIL_PAGE_DATA</span><br><span class="line"></span><br><span class="line"># The <span class="keyword">offset</span> <span class="keyword">of</span> the undo log page header <span class="keyword">on</span> pages <span class="keyword">of</span> the undo log</span><br><span class="line">TRX_UNDO_PAGE_HDR FSEG_PAGE_DATA</span><br><span class="line"></span><br><span class="line">PAGE_LEVEL <span class="number">26</span> #level <span class="keyword">of</span> the node <span class="keyword">in</span> an index tree; the leaf level <span class="keyword">is</span> the level <span class="number">0</span> <span class="operator">*</span><span class="operator">/</span></span><br><span class="line"></span><br><span class="line">innodb_page_type &#123;</span><br><span class="line"><span class="string">&#x27;0000&#x27;</span>:u<span class="string">&#x27;Freshly Allocated Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0002&#x27;</span>:u<span class="string">&#x27;Undo Log Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0003&#x27;</span>:u<span class="string">&#x27;File Segment inode&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0004&#x27;</span>:u<span class="string">&#x27;Insert Buffer Free List&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0005&#x27;</span>:u<span class="string">&#x27;Insert Buffer Bitmap&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0006&#x27;</span>:u<span class="string">&#x27;System Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0007&#x27;</span>:u<span class="string">&#x27;Transaction system Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0008&#x27;</span>:u<span class="string">&#x27;File Space Header&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0009&#x27;</span>:u<span class="string">&#x27;Extend Description Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;000a&#x27;</span>:u<span class="string">&#x27;Uncompressed BLOB Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;000b&#x27;</span>:u<span class="string">&#x27;1st compressed BLOB Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;000c&#x27;</span>:u<span class="string">&#x27;Subsequent compressed BLOB Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;45bf&#x27;</span>:u<span class="string">&#x27;B-tree Node&#x27;</span></span><br><span class="line">&#125;</span><br><span class="line">innodb_page_direction &#123;</span><br><span class="line"><span class="string">&#x27;0000&#x27;</span>: <span class="string">&#x27;Unknown(0x0000)&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0001&#x27;</span>: <span class="string">&#x27;Page Left&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0002&#x27;</span>: <span class="string">&#x27;Page Right&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0003&#x27;</span>: <span class="string">&#x27;Page Same Rec&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0004&#x27;</span>: <span class="string">&#x27;Page Same Page&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;0005&#x27;</span>: <span class="string">&#x27;Page No Direction&#x27;</span>,</span><br><span class="line"><span class="string">&#x27;ffff&#x27;</span>: <span class="string">&#x27;Unkown2(0xffff)&#x27;</span></span><br><span class="line">&#125;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="mylib-py"><a href="#mylib-py" class="headerlink" title="mylib.py"></a>mylib.py</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#encoding utf-8</span></span><br><span class="line">import os</span><br><span class="line">import include</span><br><span class="line">from include import *</span><br><span class="line"></span><br><span class="line">VARIABLE_FIELD_COUNT 1</span><br><span class="line">NULL_FIELD_COUNT 0</span><br><span class="line"></span><br><span class="line">class myargv(object):</span><br><span class="line">def __init__(self, argv):</span><br><span class="line">self.argv argv</span><br><span class="line">self.parms &#123;&#125;</span><br><span class="line">self.tablespace <span class="string">&#x27;&#x27;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 解析输入参数</span></span><br><span class="line">def parse_cmdline(self):</span><br><span class="line">argv self.argv</span><br><span class="line"><span class="keyword">if</span> len(argv) 1:</span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;Usage: python py_innodb_page_info.py [OPTIONS] tablespace_file&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;For more options, use python py_innodb_page_info.py -h&#x27;</span></span><br><span class="line"><span class="built_in">return</span> 0</span><br><span class="line"><span class="keyword">while</span> argv:</span><br><span class="line"><span class="keyword">if</span> argv[0][0] <span class="string">&#x27;-&#x27;</span>:</span><br><span class="line"><span class="keyword">if</span> argv[0][1] <span class="string">&#x27;h&#x27;</span>:</span><br><span class="line">self.parms[argv[0]] <span class="string">&#x27;&#x27;</span></span><br><span class="line">argv argv[1:]</span><br><span class="line"><span class="built_in">break</span></span><br><span class="line"><span class="keyword">if</span> argv[0][1] <span class="string">&#x27;v&#x27;</span>:</span><br><span class="line">self.parms[argv[0]] <span class="string">&#x27;&#x27;</span></span><br><span class="line">argv argv[1:]</span><br><span class="line"><span class="keyword">else</span>:</span><br><span class="line">self.parms[argv[0]] argv[1]</span><br><span class="line">argv argv[2:]</span><br><span class="line"><span class="keyword">else</span>:</span><br><span class="line">self.tablespace argv[0]</span><br><span class="line">argv argv[1:]</span><br><span class="line"><span class="keyword">if</span> self.parms.has_key(<span class="string">&#x27;-h&#x27;</span>):</span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;Get InnoDB Page Info&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;Usage: python py_innodb_page_info.py [OPTIONS] tablespace_file\n&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;The following options may be given as the first argument:&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;-h help &#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;-o output put the result to file&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;-t number thread to anayle the tablespace file&#x27;</span></span><br><span class="line"><span class="built_in">print</span> <span class="string">&#x27;-v verbose mode&#x27;</span></span><br><span class="line"><span class="built_in">return</span> 0</span><br><span class="line"><span class="built_in">return</span> 1</span><br><span class="line"></span><br><span class="line">def mach_read_from_n(page,start_offset,length):</span><br><span class="line">ret page[start_offset:start_offset length]</span><br><span class="line"><span class="built_in">return</span> ret.encode(<span class="string">&#x27;hex&#x27;</span>)</span><br><span class="line"></span><br><span class="line"><span class="comment"># main方法</span></span><br><span class="line">def get_innodb_page_type(myargv):</span><br><span class="line"><span class="comment"># 读取 .ibd 文件,存入 f</span></span><br><span class="line">f file(myargv.tablespace,<span class="string">&#x27;rb&#x27;</span>)</span><br><span class="line"><span class="comment"># INNODB_PAGE_SIZE 16KB,f 一定是16KB的整数倍,一页大小是16KB</span></span><br><span class="line"><span class="comment"># 使用 f 的字节总数除以 16KB,得到的 fsize 表示页数</span></span><br><span class="line">fsize os.path.getsize(f.name)/INNODB_PAGE_SIZE</span><br><span class="line">ret &#123;&#125;</span><br><span class="line"><span class="comment"># 枚举每一页</span></span><br><span class="line"><span class="keyword">for</span> i <span class="keyword">in</span> range(fsize):</span><br><span class="line"><span class="comment"># 读取16KB数据,存入page,是第i的数据</span></span><br><span class="line"><span class="comment"># page 是二进制文件</span></span><br><span class="line">page f.read(INNODB_PAGE_SIZE)</span><br><span class="line"><span class="comment"># page_offset 是 page[4, 8) 字符所表示的数据</span></span><br><span class="line">page_offset mach_read_from_n(page,FIL_PAGE_OFFSET,4)</span><br><span class="line"><span class="comment"># page_type 是 page[24, 26) 字符所表示的数据</span></span><br><span class="line">page_type mach_read_from_n(page,FIL_PAGE_TYPE,2)</span><br><span class="line"><span class="comment"># 如果加了参数 -v,表示输出详细数据</span></span><br><span class="line"><span class="keyword">if</span> myargv.parms.has_key(<span class="string">&#x27;-v&#x27;</span>):</span><br><span class="line"><span class="comment"># page_type 为 45bf,表示 B-tree Node,输出它的信息</span></span><br><span class="line"><span class="keyword">if</span> page_type <span class="string">&#x27;45bf&#x27;</span>:</span><br><span class="line"><span class="comment"># page_level 是 page[64, 66) 字符所表示的数据</span></span><br><span class="line">page_level mach_read_from_n(page,FIL_PAGE_DATA PAGE_LEVEL,2)</span><br><span class="line"><span class="built_in">print</span> page offset %s, page <span class="built_in">type</span> &lt;%s&gt;, page level &lt;%s&gt; %(page_offset,innodb_page_type[page_type],page_level)</span><br><span class="line"><span class="comment"># page_type 对应 include.py 中的 innodb_page_type,输出它的信息</span></span><br><span class="line"><span class="keyword">else</span>:</span><br><span class="line"><span class="built_in">print</span> page offset %s, page <span class="built_in">type</span> &lt;%s&gt; %(page_offset,innodb_page_type[page_type])</span><br><span class="line"><span class="comment"># 统计数据</span></span><br><span class="line"><span class="keyword">if</span> not ret.has_key(page_type):</span><br><span class="line">ret[page_type] 1</span><br><span class="line"><span class="keyword">else</span>:</span><br><span class="line">ret[page_type] ret[page_type] 1</span><br><span class="line"><span class="comment"># 输出fsize,表示有多少页</span></span><br><span class="line"><span class="built_in">print</span> Total number of page: %d: %fsize</span><br><span class="line"><span class="comment"># 输出统计数据</span></span><br><span class="line"><span class="keyword">for</span> <span class="built_in">type</span> <span class="keyword">in</span> ret:</span><br><span class="line"><span class="built_in">print</span> %s: %s %(innodb_page_type[<span class="built_in">type</span>],ret[<span class="built_in">type</span>])</span><br><span class="line"></span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="py-innodb-page-info-py"><a href="#py-innodb-page-info-py" class="headerlink" title="py_innodb_page_info.py"></a>py_innodb_page_info.py</h3><figure class="highlight python"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#! /usr/bin/env python</span></span><br><span class="line"><span class="comment">#encoding utf-8</span></span><br><span class="line"><span class="keyword">import</span> mylib</span><br><span class="line"><span class="keyword">from</span> sys <span class="keyword">import</span> argv</span><br><span class="line"><span class="keyword">from</span> mylib <span class="keyword">import</span> myargv</span><br><span class="line"></span><br><span class="line"><span class="comment"># main函数</span></span><br><span class="line"><span class="keyword">if</span> __name__ <span class="string">&#x27;__main__&#x27;</span>:</span><br><span class="line">myargv myargv(argv)</span><br><span class="line"><span class="keyword">if</span> myargv.parse_cmdline() <span class="number">0</span>:</span><br><span class="line"><span class="keyword">pass</span></span><br><span class="line"><span class="keyword">else</span>:</span><br><span class="line"><span class="comment"># 执行main方法</span></span><br><span class="line">mylib.get_innodb_page_type(myargv)</span><br><span class="line"></span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h3><p>先创建个example_table空表,看下example_table.ibd,可以看到总共分配了11page Total number of page: 11 ,但是为啥空闲的只有6page B-tree Node: 6 ,这里就不得不提到之前说到的预留空间了</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img2.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> example_table(</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT,</span><br><span class="line">first_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">last_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">100</span>),</span><br><span class="line">created_at <span class="type">TIMESTAMP</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">status ENUM(<span class="string">&#x27;active&#x27;</span>, <span class="string">&#x27;inactive&#x27;</span>) <span class="keyword">DEFAULT</span> <span class="string">&#x27;active&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> (id),</span><br><span class="line">INDEX idx_last_name (last_name),</span><br><span class="line">FULLTEXT INDEX ftx_first_name (first_name),</span><br><span class="line">INDEX idx_status (status),</span><br><span class="line">INDEX idx_created_at (created_at),</span><br><span class="line">INDEX idx_first_name_last_name (first_name, last_name)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">python2 py_innodb_page_info.py -v demo1/example_table.ibd</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img3.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br></pre></td><td class="code"><pre><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>File Space Header<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000001</span>, page type <span class="operator">&lt;</span><span class="keyword">Insert</span> Buffer Bitmap<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000002</span>, page type <span class="operator">&lt;</span>File Segment inode<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000003</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span> <span class="operator">/</span><span class="operator">/</span>数据页,<span class="number">0001</span>表示根层,<span class="number">0000</span>表示叶子层</span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000004</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000005</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000006</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000007</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000008</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">Total number <span class="keyword">of</span> page: <span class="number">11</span>:<span class="operator">/</span><span class="operator">/</span>总共分配的页数</span><br><span class="line">Freshly Allocated Page: <span class="number">2</span><span class="operator">/</span><span class="operator">/</span>可用的数据页</span><br><span class="line"><span class="keyword">Insert</span> Buffer Bitmap: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>插入缓冲页</span><br><span class="line">File Space Header: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>文件空间头</span><br><span class="line">B<span class="operator">-</span>tree Node: <span class="number">6</span><span class="operator">/</span><span class="operator">/</span>数据页</span><br><span class="line">File Segment inode: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>文件端inonde</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>然后再使用存储过程插入1W行数据,再分析example_table.ibd</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br></pre></td><td class="code"><pre><span class="line">DELIMITER $$</span><br><span class="line"></span><br><span class="line"><span class="keyword">CREATE</span> <span class="keyword">PROCEDURE</span> InsertExampleData()</span><br><span class="line"><span class="keyword">BEGIN</span></span><br><span class="line"><span class="keyword">DECLARE</span> i <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="number">1</span>;</span><br><span class="line"><span class="keyword">DECLARE</span> maxEmail <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="number">1000</span>;</span><br><span class="line"><span class="keyword">DECLARE</span> firstName <span class="type">VARCHAR</span>(<span class="number">50</span>);</span><br><span class="line"><span class="keyword">DECLARE</span> lastName <span class="type">VARCHAR</span>(<span class="number">50</span>);</span><br><span class="line"><span class="keyword">DECLARE</span> email <span class="type">VARCHAR</span>(<span class="number">100</span>);</span><br><span class="line"><span class="keyword">DECLARE</span> status ENUM(<span class="string">&#x27;active&#x27;</span>, <span class="string">&#x27;inactive&#x27;</span>);</span><br><span class="line"><span class="keyword">DECLARE</span> <span class="type">timestamp</span> DATETIME;</span><br><span class="line"></span><br><span class="line">WHILE i <span class="operator">&lt;</span> <span class="number">10000</span> DO</span><br><span class="line"><span class="keyword">SET</span> firstName CONCAT(<span class="string">&#x27;Name&#x27;</span>, LPAD(i, <span class="number">5</span>, <span class="string">&#x27;0&#x27;</span>));</span><br><span class="line"><span class="keyword">SET</span> lastName CONCAT(<span class="string">&#x27;Surname&#x27;</span>, LPAD(i, <span class="number">5</span>, <span class="string">&#x27;0&#x27;</span>));</span><br><span class="line"><span class="keyword">SET</span> email CONCAT(firstName, <span class="string">&#x27;_&#x27;</span>, lastName, <span class="string">&#x27;_&#x27;</span>, i, <span class="string">&#x27; example.com&#x27;</span>);</span><br><span class="line"><span class="keyword">SET</span> status IF(i <span class="operator">%</span> <span class="number">2</span> <span class="number">0</span>, <span class="string">&#x27;active&#x27;</span>, <span class="string">&#x27;inactive&#x27;</span>);</span><br><span class="line"><span class="keyword">SET</span> <span class="type">timestamp</span> DATE_ADD(NOW(), <span class="type">INTERVAL</span> <span class="built_in">FLOOR</span>(RAND() <span class="operator">*</span> <span class="number">365</span>) <span class="keyword">DAY</span>);</span><br><span class="line"></span><br><span class="line"><span class="keyword">INSERT INTO</span> example_table (first_name, last_name, email, created_at, status)</span><br><span class="line"><span class="keyword">VALUES</span> (firstName, lastName, email, <span class="type">timestamp</span>, status);</span><br><span class="line"></span><br><span class="line"><span class="keyword">SET</span> i i <span class="number">1</span>;</span><br><span class="line"><span class="keyword">END</span> WHILE;</span><br><span class="line"><span class="keyword">END</span>$$</span><br><span class="line"></span><br><span class="line">DELIMITER ;</span><br></pre></td></tr></table></figure><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">CALL InsertExampleData();</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img4.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br></pre></td><td class="code"><pre><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>File Space Header<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000001</span>, page type <span class="operator">&lt;</span><span class="keyword">Insert</span> Buffer Bitmap<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000002</span>, page type <span class="operator">&lt;</span>File Segment inode<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000003</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000004</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000005</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000006</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000007</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000008</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0001</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000009</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>a, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>b, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>c, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>d, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>e, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">0000000</span>f, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000010</span>, page type <span class="operator">&lt;</span>B<span class="operator">-</span>tree Node<span class="operator">&gt;</span>, page level <span class="operator">&lt;</span><span class="number">0000</span><span class="operator">&gt;</span></span><br><span class="line"></span><br><span class="line">....</span><br><span class="line"></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">page <span class="keyword">offset</span> <span class="number">00000000</span>, page type <span class="operator">&lt;</span>Freshly Allocated Page<span class="operator">&gt;</span></span><br><span class="line">Total number <span class="keyword">of</span> page: <span class="number">640</span>:<span class="operator">/</span><span class="operator">/</span>总共分配的页数</span><br><span class="line">Freshly Allocated Page: <span class="number">493</span><span class="operator">/</span><span class="operator">/</span>可用的数据页</span><br><span class="line"><span class="keyword">Insert</span> Buffer Bitmap: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>插入缓冲页</span><br><span class="line">File Space Header: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>文件空间头</span><br><span class="line">B<span class="operator">-</span>tree Node: <span class="number">144</span><span class="operator">/</span><span class="operator">/</span>数据页</span><br><span class="line">File Segment inode: <span class="number">1</span><span class="operator">/</span><span class="operator">/</span>文件端inonde</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img5.avif"></p><p>这时可以看到总共分配640页 Total number of page 即10240kb,使用了144页 B-tree Node 即2304kb,可用的数据页493页 Freshly Allocated Page 即7888kb</p><p>同时去看information_schema.tables中example_table的信息,可以看到DATA_LENGTH INDEX_LENGTH 1589248byte 1261568byte 2850816byte 2784kb,DATA_FREE 4194304byte 4096kb,</p><p>DATA_LENGTH INDEX_LENGTH DATA_FREE 6880kb 10240-6880 3360kb</p><p>Insert Buffer Bitmap File Space Header File Segment inode 48kb</p><p>那这里为什么6880kb DATA_LENGTH INDEX_LENGTH DATA_FREE 要远远小于10240kb Total number of page ,这是除了之前提到的预留空间还有碎片率吗?</p><p>ok,我们带着这个问题去分析。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> information_schema.tables <span class="keyword">where</span> table_schema <span class="string">&#x27;demo1&#x27;</span> <span class="keyword">and</span> table_name <span class="string">&#x27;example_table&#x27;</span>\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img6.avif"></p><p>这里我们计算下空间碎片率Space Debris Rate (70451204194304)×100≈59.53%</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">table_name,</span><br><span class="line">table_rows,</span><br><span class="line">ROUND(data_length <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> data_length_gb,</span><br><span class="line">ROUND(index_length <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> index_length_gb,</span><br><span class="line">data_free,</span><br><span class="line"><span class="keyword">CASE</span></span><br><span class="line"><span class="keyword">WHEN</span> (data_length index_length data_free) <span class="operator">&gt;</span> <span class="number">0</span> <span class="keyword">THEN</span></span><br><span class="line">ROUND(data_free <span class="operator">/</span> (data_length index_length data_free) <span class="operator">*</span> <span class="number">100</span>, <span class="number">2</span>)</span><br><span class="line"><span class="keyword">ELSE</span></span><br><span class="line"><span class="number">0</span></span><br><span class="line"><span class="keyword">END</span> <span class="keyword">AS</span> space_debris_rate</span><br><span class="line"><span class="keyword">FROM</span> information_schema.tables</span><br><span class="line"><span class="keyword">WHERE</span> table_schema <span class="string">&#x27;demo1&#x27;</span> <span class="keyword">AND</span> table_name <span class="string">&#x27;example_table&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img7.avif"></p><p>这里我们将example_table的数据全部删除然后analyze table example_table; ,再查看information_schema.tables的统计信息,然后执行optimize table demo1.example_table; ,再去分析。最后可以看到DATA_LENGTH INDEX_LENGTH DATA_FREE 16384 81920 0 96kb 6page B-tree Node</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img11.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/10/30/83670dc6/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL5.7.44编译安装</title>
      <link>https://blog.eucalyptus.cc/2025/10/30/c2b5c4a7/</link>
      <guid>https://blog.eucalyptus.cc/2025/10/30/c2b5c4a7/</guid>
      <pubDate>Thu, 30 Oct 2025 06:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h5 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h5&gt;&lt;p&gt;本次编译安装的是MySQL5.7.44的版本,是在centos stream</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h5 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h5><p>本次编译安装的是MySQL5.7.44的版本,是在centos stream 9中安装,且服务器上已经运行了一个使用rpm包安装的MySQL8.0.37,故在配置的过程中要注意路径和环境变量的冲突。默认MySQL8.0.37的数据目录在&#x2F;val&#x2F;lib&#x2F;mysql,安装目录在&#x2F;usr&#x2F;bin,配置文件在&#x2F;etc&#x2F;my.cnf下。因此我们把MySQL5.7.44的安装目录放在&#x2F;usr&#x2F;local&#x2F;mysql5.7.44,数据目录放在&#x2F;home&#x2F;mysql5.7.44&#x2F;data,配置文件在&#x2F;home&#x2F;mysql5.7.44&#x2F;my.cnf。ok,下面我们开始配置</p><h5 id="1、为了安全在安装之前-我们创建一个单独的用户用来运行MySQL"><a href="#1、为了安全在安装之前-我们创建一个单独的用户用来运行MySQL" class="headerlink" title="1、为了安全在安装之前,我们创建一个单独的用户用来运行MySQL,"></a>1、为了安全在安装之前,我们创建一个单独的用户用来运行MySQL,</h5><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">groupadd mysql5</span><br><span class="line">useradd -g mysql5 -d /home/mysql5.7.44 mysql5</span><br></pre></td></tr></table></figure><h5 id="2、接下来在官网下载源码包-Product-Version选择需要的版本-Operating-System选择Source-Code-OS-Version选择All"><a href="#2、接下来在官网下载源码包-Product-Version选择需要的版本-Operating-System选择Source-Code-OS-Version选择All" class="headerlink" title="2、接下来在官网下载源码包,Product Version选择需要的版本,Operating System选择Source Code,OS Version选择All,"></a>2、接下来在官网下载源码包,Product Version选择需要的版本,Operating System选择Source Code,OS Version选择All,</h5><p><a href="https://downloads.mysql.com/archives/community/">https://downloads.mysql.com/archives/community/</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img1.avif"></p><h6 id="然后选择mysql-5-7-44-tar-gz下载-可以直接使用wget下载到服务器上-或者下载到本地然后上传到服务器"><a href="#然后选择mysql-5-7-44-tar-gz下载-可以直接使用wget下载到服务器上-或者下载到本地然后上传到服务器" class="headerlink" title="然后选择mysql-5.7.44.tar.gz下载,可以直接使用wget下载到服务器上,或者下载到本地然后上传到服务器"></a>然后选择mysql-5.7.44.tar.gz下载,可以直接使用wget下载到服务器上,或者下载到本地然后上传到服务器</h6><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">wget https://downloads.mysql.com/archives/get/p/23/file/mysql-5.7.44.tar.gz</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img2.avif"></p><h6 id="下一步操作解压"><a href="#下一步操作解压" class="headerlink" title="下一步操作解压"></a>下一步操作解压</h6><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img3.avif"></p><h5 id="3、下一步进行编译-但是为了保持源码目录的清洁-我们在这里创建一个单独的目录用来编译"><a href="#3、下一步进行编译-但是为了保持源码目录的清洁-我们在这里创建一个单独的目录用来编译" class="headerlink" title="3、下一步进行编译,但是为了保持源码目录的清洁,我们在这里创建一个单独的目录用来编译"></a>3、下一步进行编译,但是为了保持源码目录的清洁,我们在这里创建一个单独的目录用来编译</h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cd</span> mysql-5.7.44</span><br><span class="line"><span class="built_in">mkdir</span> build</span><br><span class="line"><span class="built_in">cd</span> build</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img4.avif"></p><h6 id="配置编译选项"><a href="#配置编译选项" class="headerlink" title="配置编译选项"></a>配置编译选项</h6><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">cmake .. \</span><br><span class="line">-DCMAKE_INSTALL_PREFIX /usr/local/mysql5.7.44 \</span><br><span class="line">-DMYSQL_DATADIR /home/mysql5.7.44/data \</span><br><span class="line">-DSYSCONFDIR /home/mysql5.7.44/my.cnf \</span><br><span class="line">-DWITH_INNOBASE_STORAGE_ENGINE 1 \</span><br><span class="line">-DENABLED_LOCAL_INFILE 1</span><br></pre></td></tr></table></figure><p><code>-DCMAKE_INSTALL_PREFIX /usr/local/mysql5.7.44</code></p><ul><li>作用:指定 MySQL 的安装路径。</li><li>是否必要:必要。如果不指定,默认安装路径通常是 <code>/usr/local/mysql</code>,但指定路径可以避免冲突。</li></ul><p><code>-DMYSQL_DATADIR /home/mysql5.7.44/data</code></p><ul><li>作用:指定 MySQL 数据目录的路径。</li><li>是否必要:必要。如果不指定,默认路径通常是 <code>/usr/local/mysql/data</code>,但指定路径可以避免冲突。</li></ul><p><code>-DSYSCONFDIR /home/mysql5.7.44/my.cnf</code></p><ul><li>作用:指定 MySQL 配置文件的路径。</li><li>是否必要:可能不必要。默认配置文件路径通常是 <code>/etc/mysql/my.cnf</code> 或 <code>/etc/my.cnf</code>。如果你希望将配置文件放在非标准路径,这个选项是必要的。</li></ul><p><code>-DWITH_INNOBASE_STORAGE_ENGINE 1</code></p><ul><li>作用:启用 InnoDB 存储引擎。</li><li>是否必要:通常必要。InnoDB 是 MySQL 的默认存储引擎,大多数生产环境中都需要它。</li></ul><p><code>-DENABLED_LOCAL_INFILE 1</code></p><ul><li>作用:启用本地文件加载功能 <code>LOAD DATA LOCAL INFILE</code> 。</li><li>是否必要:根据需求决定。如果你需要从本地文件加载数据,这个选项是必要的。否则,可以省略以提高安全性。</li></ul><h6 id="这里cmake的时候出现了报错-提示需要boost-1-59-0-正常来说-MySQL-的源码包-mysql-5-7-44-tar-gz-不应该依赖于-Boost-库-为什么这里会报错呢-嗯…-先解决问题吧-既然缺少了boost-1-59-0那就安装一个吧"><a href="#这里cmake的时候出现了报错-提示需要boost-1-59-0-正常来说-MySQL-的源码包-mysql-5-7-44-tar-gz-不应该依赖于-Boost-库-为什么这里会报错呢-嗯…-先解决问题吧-既然缺少了boost-1-59-0那就安装一个吧" class="headerlink" title="这里cmake的时候出现了报错,提示需要boost_1_59_0,正常来说,MySQL 的源码包 mysql-5.7.44.tar.gz 不应该依赖于 Boost 库,为什么这里会报错呢,嗯… 先解决问题吧,既然缺少了boost_1_59_0那就安装一个吧"></a>这里cmake的时候出现了报错,提示需要boost_1_59_0,正常来说,MySQL 的源码包 <code>mysql-5.7.44.tar.gz</code> 不应该依赖于 Boost 库,为什么这里会报错呢,嗯… 先解决问题吧,既然缺少了boost_1_59_0那就安装一个吧</h6><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img5.avif"></p><h6 id="还是老规矩-直接使用wget下载-然后解压安装-b2-install执行时间会比较久-请耐心等待"><a href="#还是老规矩-直接使用wget下载-然后解压安装-b2-install执行时间会比较久-请耐心等待" class="headerlink" title="还是老规矩,直接使用wget下载,然后解压安装, .&#x2F;b2 install执行时间会比较久,请耐心等待"></a>还是老规矩,直接使用wget下载,然后解压安装, .&#x2F;b2 install执行时间会比较久,请耐心等待</h6><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">wget https://nchc.dl.sourceforge.net/project/boost/boost/1.59.0/boost_1_59_0.tar.gz</span><br><span class="line">tar -xzvf boost_1_59_0.tar.gz</span><br><span class="line"><span class="built_in">cd</span> boost_1_59_0</span><br><span class="line">./bootstrap.sh</span><br><span class="line">./b2 install</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img7.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img8.avif"></p><h6 id="boost-1-59-0安装完成-并清理build下的缓存-然后再次尝试cmake-这里又发现有缺少了rpc-h头文件"><a href="#boost-1-59-0安装完成-并清理build下的缓存-然后再次尝试cmake-这里又发现有缺少了rpc-h头文件" class="headerlink" title="boost_1_59_0安装完成,并清理build下的缓存,然后再次尝试cmake,这里又发现有缺少了rpc.h头文件"></a>boost_1_59_0安装完成,并清理build下的缓存,然后再次尝试cmake,这里又发现有缺少了rpc.h头文件</h6><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img9.avif"></p><h6 id="这个rpc-h头文件需要安装libtirpc-devel来解决-由于我使用的操作系统是CentOS-Stream-9-而libtirpc-devel不在默认的仓库中这里yum安装之前需要先启动CRB仓库"><a href="#这个rpc-h头文件需要安装libtirpc-devel来解决-由于我使用的操作系统是CentOS-Stream-9-而libtirpc-devel不在默认的仓库中这里yum安装之前需要先启动CRB仓库" class="headerlink" title="这个rpc.h头文件需要安装libtirpc-devel来解决,由于我使用的操作系统是CentOS Stream 9,而libtirpc-devel不在默认的仓库中这里yum安装之前需要先启动CRB仓库,"></a>这个rpc.h头文件需要安装libtirpc-devel来解决,由于我使用的操作系统是CentOS Stream 9,而libtirpc-devel不在默认的仓库中这里yum安装之前需要先启动CRB仓库,</h6><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">dnf config<span class="operator">-</span>manager <span class="comment">--set-enabled crb</span></span><br><span class="line">yum install <span class="operator">-</span>y libtirpc<span class="operator">-</span>devel</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img10.avif"></p><h6 id="清理build的缓存-然后继续重试cmake。呃…又遇到报错了-缺少了rpcgen"><a href="#清理build的缓存-然后继续重试cmake。呃…又遇到报错了-缺少了rpcgen" class="headerlink" title="清理build的缓存,然后继续重试cmake。呃…又遇到报错了,缺少了rpcgen,"></a>清理build的缓存,然后继续重试cmake。呃…又遇到报错了,缺少了rpcgen,</h6><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img11.avif"></p><h6 id="这里我直接使用了yum安装-如果这里yum安装失败可以考虑下载rpcgen的源码包然后编译安装-或者配置yum仓库后再yum安装-ok没问题后-清理build的缓存后重新cmake"><a href="#这里我直接使用了yum安装-如果这里yum安装失败可以考虑下载rpcgen的源码包然后编译安装-或者配置yum仓库后再yum安装-ok没问题后-清理build的缓存后重新cmake" class="headerlink" title="这里我直接使用了yum安装,如果这里yum安装失败可以考虑下载rpcgen的源码包然后编译安装,或者配置yum仓库后再yum安装,ok没问题后,清理build的缓存后重新cmake"></a>这里我直接使用了yum安装,如果这里yum安装失败可以考虑下载rpcgen的源码包然后编译安装,或者配置yum仓库后再yum安装,ok没问题后,清理build的缓存后重新cmake</h6><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img12.avif"></p><p>嗯,到这里就没有问题了,使用cmake 已经可以成功了,不会再遇到致命错误…</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img13.avif"></p><h5 id="4、下一步进行编译-使用make-j-nproc-或者make都可以"><a href="#4、下一步进行编译-使用make-j-nproc-或者make都可以" class="headerlink" title="4、下一步进行编译,使用make -j$(nproc) 或者make都可以"></a>4、下一步进行编译,使用make -j$(nproc) 或者make都可以</h5><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">make -j$(nproc) / make</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img14.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img15.avif"></p><h5 id="5、最后进行安装"><a href="#5、最后进行安装" class="headerlink" title="5、最后进行安装"></a>5、最后进行安装</h5><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">make install</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img16.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img17.avif"></p><h5 id="6、在-root-bashrc中配置环境变量"><a href="#6、在-root-bashrc中配置环境变量" class="headerlink" title="6、在&#x2F;root&#x2F;.bashrc中配置环境变量,"></a>6、在&#x2F;root&#x2F;.bashrc中配置环境变量,</h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">export</span> PATH <span class="variable">$PATH</span>:/usr/local/mysql5.7.44/bin</span><br><span class="line"><span class="built_in">source</span> /root/.bashrc</span><br></pre></td></tr></table></figure><h5 id="7、配置-home-mysql5-7-44-my-cnf-MySQL5-7-44的配置文件"><a href="#7、配置-home-mysql5-7-44-my-cnf-MySQL5-7-44的配置文件" class="headerlink" title="7、配置&#x2F;home&#x2F;mysql5.7.44&#x2F;my.cnf MySQL5.7.44的配置文件"></a>7、配置&#x2F;home&#x2F;mysql5.7.44&#x2F;my.cnf MySQL5.7.44的配置文件</h5><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[mysqld]</span></span><br><span class="line">user mysql5</span><br><span class="line">port 3303</span><br><span class="line">basedir /usr/local/mysql5.7.44</span><br><span class="line">datadir /home/mysql5.7.44/data</span><br><span class="line">socket /home/mysql5.7.44/data/mysql.sock</span><br><span class="line">character-set-server UTF8</span><br><span class="line">lower_case_table_names 1</span><br><span class="line">log-error /home/mysql5.7.44/error.log</span><br><span class="line"></span><br><span class="line"><span class="section">[client]</span></span><br><span class="line">socket /home/mysql5.7.44/data/mysql.sock</span><br><span class="line"></span><br></pre></td></tr></table></figure><h5 id="8、初始化MySQL数据目录-初始化生成的密码可以在指定的error-log-中查看"><a href="#8、初始化MySQL数据目录-初始化生成的密码可以在指定的error-log-中查看" class="headerlink" title="8、初始化MySQL数据目录,初始化生成的密码可以在指定的error.log 中查看"></a>8、初始化MySQL数据目录,初始化生成的密码可以在指定的error.log 中查看</h5><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/mysql5.7.44/bin/mysqld --defaults-file /home/mysql5.7.44/my.cnf --initialize</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img18.avif"></p><h5 id="9、启动MySQL-可以看到-usr-local-mysql5-7-44-bin-mysqld-已经启动-3303端口已运行"><a href="#9、启动MySQL-可以看到-usr-local-mysql5-7-44-bin-mysqld-已经启动-3303端口已运行" class="headerlink" title="9、启动MySQL,可以看到&#x2F;usr&#x2F;local&#x2F;mysql5.7.44&#x2F;bin&#x2F;mysqld 已经启动,3303端口已运行"></a>9、启动MySQL,可以看到&#x2F;usr&#x2F;local&#x2F;mysql5.7.44&#x2F;bin&#x2F;mysqld 已经启动,3303端口已运行</h5><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/mysql5.7.44/bin/mysqld --defaults-file /home/mysql5.7.44/my.cnf &amp;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img19.avif"></p><h5 id="10、更新密码并测试连接"><a href="#10、更新密码并测试连接" class="headerlink" title="10、更新密码并测试连接"></a>10、更新密码并测试连接</h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/mysql5.7.44/bin/mysqladmin -u root -p<span class="string">&#x27;R1uJLjcP4w#)&#x27;</span> --socket /home/mysql5.7.44/data/mysql.sock password <span class="string">&#x27;123456&#x27;</span></span><br><span class="line">/usr/local/mysql5.7.44/bin/mysql -u root -p<span class="string">&#x27;R1uJLjcP4w#)&#x27;</span> --socket /home/mysql5.7.44/data/mysql.sock</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img20.avif"></p><h5 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h5><p>在配置的过程中,遇到的最大的问题就是在cmake的时候,由于缺少依赖导致cmake中断,本次配置中缺少的依赖主要就是下面3个比较难搞一点,其他的直接使用yum安装就可以了,解决方法已经在文章中,大家可以借鉴</p><ul><li>boost_1_59_0</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img5.avif"></p><ul><li>rpc.h头文件</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img9.avif"></p><ul><li>rpcgen</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-30/img11.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/10/30/c2b5c4a7/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的空间碎片率计算分析</title>
      <link>https://blog.eucalyptus.cc/2025/10/24/aa20384c/</link>
      <guid>https://blog.eucalyptus.cc/2025/10/24/aa20384c/</guid>
      <pubDate>Fri, 24 Oct 2025 07:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;空间碎片的类型&quot;&gt;&lt;a href=&quot;#空间碎片的类型&quot; class=&quot;headerlink&quot; title=&quot;空间碎片的类型&quot;&gt;&lt;/a&gt;&lt;strong&gt;空间碎片的类型&lt;/strong&gt;&lt;/h3&gt;&lt;p&gt;MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="空间碎片的类型"><a href="#空间碎片的类型" class="headerlink" title="空间碎片的类型"></a><strong>空间碎片的类型</strong></h3><p>MySQL 中的空间碎片主要分为两种类型:<strong>数据碎片</strong>和<strong>索引碎片</strong>。</p><h3 id="数据碎片"><a href="#数据碎片" class="headerlink" title="数据碎片"></a>数据碎片</h3><p>数据碎片是指表中的数据页 或数据块 中未被充分利用的空间。数据页是 MySQL 存储数据的基本单位,通常大小为 16 KB 对于 InnoDB 存储引擎 。</p><ul><li><code>INSERT</code>** 操作**:插入数据时,如果插入的数据量较小,可能会导致数据页没有被完全填满,从而产生未使用的空间。</li><li><code>DELETE</code>** 操作**:删除数据时,被删除的数据行所占用的空间会变成未使用的空间。如果这些空间没有被后续的 <code>INSERT</code> 操作重新利用,就会形成碎片。</li><li><code>UPDATE</code>** 操作**:如果更新操作导致数据行的大小发生变化 例如,从较短的字符串更新为较长的字符串 ,可能会导致数据行被移动到新的数据页,从而产生碎片。</li></ul><h3 id="索引碎片"><a href="#索引碎片" class="headerlink" title="索引碎片"></a>索引碎片</h3><p>索引碎片是指索引中的索引页 或索引块 中未被充分利用的空间。索引页是 MySQL 存储索引信息的基本单位,通常大小为 16 KB 对于 InnoDB 存储引擎 。</p><ul><li><code>INSERT</code>** 操作**:插入数据时,如果插入的数据行导致索引页分裂,可能会产生未使用的空间。</li><li><code>DELETE</code>** 操作**:删除数据时,被删除的数据行所占用的索引空间会变成未使用的空间。如果这些空间没有被后续的 <code>INSERT</code> 操作重新利用,就会形成碎片。</li><li><code>UPDATE</code>** 操作**:如果更新操作导致索引键值的变化,可能会导致索引页的重新组织,从而产生碎片。</li></ul><h3 id="碎片的危害"><a href="#碎片的危害" class="headerlink" title="碎片的危害"></a>碎片的危害</h3><ul><li><strong>增加磁盘 I&#x2F;O 操作</strong>:当存在存储碎片时,数据在磁盘上的存储位置变得分散。例如,一个查询原本只需要读取一个连续的数据块就能获取所需信息,但由于碎片的存在,数据可能分布在多个不连续的磁盘位置。这就导致数据库在执行查询操作时,需要多次进行磁盘 I&#x2F;O 操作来读取分散的数据。对于频繁查询的数据库系统,大量的额外磁盘 I&#x2F;O 会显著降低系统的整体性能。</li><li><strong>降低存储效率</strong>:在 MySQL 中,缓冲池 如 InnoDB 缓冲池 用于缓存数据页和索引页,以减少磁盘 I&#x2F;O。但是,碎片会使数据页和索引页在缓冲池中难以高效地缓存。由于碎片导致数据页不完整或部分空闲,缓冲池可能无法充分利用其空间来缓存完整的、经常使用的数据页。</li><li><strong>造成磁盘空间浪费</strong>:存储碎片使得磁盘空间无法得到有效利用。这些碎片空间单个可能较小,但随着时间的推移和操作的积累,它们会占用大量的磁盘空间。例如,在一个数据库表空间中,由于数据的删除和更新操作产生了许多小碎片,这些碎片空间加起来可能占据了相当大的磁盘容量,但却无法被有效地用于存储新的数据。</li></ul><h3 id="空间碎片率计算公式"><a href="#空间碎片率计算公式" class="headerlink" title="空间碎片率计算公式"></a>空间碎片率计算公式</h3><h4 id="8-0"><a href="#8-0" class="headerlink" title="8.0"></a>8.0</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">TABLE_NAME,</span><br><span class="line">TABLE_ROWS,</span><br><span class="line">ROUND(DATA_LENGTH <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> DATA_LENGTH_GB,</span><br><span class="line">ROUND(INDEX_LENGTH <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> INDEX_LENGTH_GB,</span><br><span class="line">DATA_FREE,</span><br><span class="line"><span class="keyword">CASE</span></span><br><span class="line"><span class="keyword">WHEN</span> (DATA_LENGTH INDEX_LENGTH DATA_FREE) <span class="operator">&gt;</span> <span class="number">0</span> <span class="keyword">THEN</span></span><br><span class="line">ROUND(DATA_FREE <span class="operator">/</span> (DATA_LENGTH INDEX_LENGTH DATA_FREE) <span class="operator">*</span> <span class="number">100</span>, <span class="number">2</span>)</span><br><span class="line"><span class="keyword">ELSE</span></span><br><span class="line"><span class="number">0</span></span><br><span class="line"><span class="keyword">END</span> <span class="keyword">AS</span> Space_debris_rate,</span><br><span class="line">(<span class="keyword">SELECT</span> ROUND(FILE_SIZE <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>)</span><br><span class="line"><span class="keyword">FROM</span> information_schema.innodb_tablespaces</span><br><span class="line"><span class="keyword">WHERE</span> name <span class="string">&#x27;demo1/example_table&#x27;</span>) <span class="keyword">AS</span> FILE_SIZE_GB</span><br><span class="line"><span class="keyword">FROM</span> information_schema.tables</span><br><span class="line"><span class="keyword">WHERE</span> table_schema <span class="string">&#x27;demo1&#x27;</span> <span class="keyword">AND</span> table_name <span class="string">&#x27;example_table&#x27;</span>;</span><br></pre></td></tr></table></figure><h4 id="5-7"><a href="#5-7" class="headerlink" title="5.7"></a>5.7</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">table_name,</span><br><span class="line">table_rows,</span><br><span class="line">ROUND(data_length <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> data_length_gb,</span><br><span class="line">ROUND(index_length <span class="operator">/</span> (<span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span> <span class="operator">*</span> <span class="number">1024</span>), <span class="number">2</span>) <span class="keyword">AS</span> index_length_gb,</span><br><span class="line">data_free,</span><br><span class="line"><span class="keyword">CASE</span></span><br><span class="line"><span class="keyword">WHEN</span> (data_length index_length data_free) <span class="operator">&gt;</span> <span class="number">0</span> <span class="keyword">THEN</span></span><br><span class="line">ROUND(data_free <span class="operator">/</span> (data_length index_length data_free) <span class="operator">*</span> <span class="number">100</span>, <span class="number">2</span>)</span><br><span class="line"><span class="keyword">ELSE</span></span><br><span class="line"><span class="number">0</span></span><br><span class="line"><span class="keyword">END</span> <span class="keyword">AS</span> space_debris_rate</span><br><span class="line"><span class="keyword">FROM</span> information_schema.tables</span><br><span class="line"><span class="keyword">WHERE</span> table_schema <span class="string">&#x27;demo1&#x27;</span> <span class="keyword">AND</span> table_name <span class="string">&#x27;example_table&#x27;</span>;</span><br></pre></td></tr></table></figure><h3 id="单个节点空间碎片率分析"><a href="#单个节点空间碎片率分析" class="headerlink" title="单个节点空间碎片率分析"></a>单个节点空间碎片率分析</h3><p>创建example_table,然后使用存储过程插入2千万行数据</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img1.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> example_table(</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT,</span><br><span class="line">first_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">last_name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">100</span>),</span><br><span class="line">created_at <span class="type">TIMESTAMP</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">status ENUM(<span class="string">&#x27;active&#x27;</span>, <span class="string">&#x27;inactive&#x27;</span>) <span class="keyword">DEFAULT</span> <span class="string">&#x27;active&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> (id),</span><br><span class="line">INDEX idx_last_name (last_name),</span><br><span class="line">FULLTEXT INDEX ftx_first_name (first_name),</span><br><span class="line">INDEX idx_status (status),</span><br><span class="line">INDEX idx_created_at (created_at),</span><br><span class="line">INDEX idx_first_name_last_name (first_name, last_name)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img2.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br></pre></td><td class="code"><pre><span class="line">DELIMITER <span class="operator">/</span><span class="operator">/</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">CREATE</span> <span class="keyword">PROCEDURE</span> InsertTwentyMillionRows()</span><br><span class="line"><span class="keyword">BEGIN</span></span><br><span class="line"><span class="keyword">DECLARE</span> v_max <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="number">20000000</span>; <span class="comment">-- 总行数</span></span><br><span class="line"><span class="keyword">DECLARE</span> v_batch_size <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="number">1000</span>; <span class="comment">-- 每次插入的行数:1000</span></span><br><span class="line"><span class="keyword">DECLARE</span> v_count <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="number">0</span>; <span class="comment">-- 当前插入的行数</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">START</span> TRANSACTION;</span><br><span class="line"></span><br><span class="line"><span class="comment">-- 循环直到达到目标行数</span></span><br><span class="line">WHILE v_count <span class="operator">&lt;</span> v_max DO</span><br><span class="line"><span class="comment">-- 插入1000行数据</span></span><br><span class="line"><span class="keyword">INSERT INTO</span> example_table (first_name, last_name, email, status)</span><br><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">CONCAT(<span class="string">&#x27;FirstName&#x27;</span>, LPAD((v_count <span class="operator">*</span> v_batch_size) num, <span class="number">7</span>, <span class="string">&#x27;0&#x27;</span>)) <span class="keyword">AS</span> first_name,</span><br><span class="line">CONCAT(<span class="string">&#x27;LastName&#x27;</span>, LPAD((v_count <span class="operator">*</span> v_batch_size) num, <span class="number">7</span>, <span class="string">&#x27;0&#x27;</span>)) <span class="keyword">AS</span> last_name,</span><br><span class="line">CONCAT(<span class="string">&#x27;user&#x27;</span>, LPAD((v_count <span class="operator">*</span> v_batch_size) num, <span class="number">7</span>, <span class="string">&#x27;0&#x27;</span>), <span class="string">&#x27; example.com&#x27;</span>) <span class="keyword">AS</span> email,</span><br><span class="line"><span class="keyword">CASE</span> <span class="keyword">WHEN</span> ((v_count <span class="operator">*</span> v_batch_size) num) <span class="operator">%</span> <span class="number">2</span> <span class="number">0</span> <span class="keyword">THEN</span> <span class="string">&#x27;active&#x27;</span> <span class="keyword">ELSE</span> <span class="string">&#x27;inactive&#x27;</span> <span class="keyword">END</span> <span class="keyword">AS</span> status</span><br><span class="line"><span class="keyword">FROM</span> (</span><br><span class="line"><span class="keyword">SELECT</span> a.num (b.num <span class="operator">*</span> <span class="number">10</span>) <span class="keyword">AS</span> num</span><br><span class="line"><span class="keyword">FROM</span> (</span><br><span class="line"><span class="keyword">SELECT</span> <span class="number">0</span> <span class="keyword">AS</span> num <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">1</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">2</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">3</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">4</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">5</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">6</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">7</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">8</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">9</span></span><br><span class="line">) a</span><br><span class="line"><span class="keyword">CROSS</span> <span class="keyword">JOIN</span> (</span><br><span class="line"><span class="keyword">SELECT</span> <span class="number">0</span> <span class="keyword">AS</span> num <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">1</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">2</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">3</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">4</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">5</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">6</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">7</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">8</span> <span class="keyword">UNION</span> <span class="keyword">ALL</span> <span class="keyword">SELECT</span> <span class="number">9</span></span><br><span class="line">) b</span><br><span class="line">) <span class="keyword">AS</span> subquery;</span><br><span class="line"></span><br><span class="line"><span class="comment">-- 更新当前插入的行数</span></span><br><span class="line"><span class="keyword">SET</span> v_count v_count v_batch_size;</span><br><span class="line"></span><br><span class="line"><span class="comment">-- 每插入100000行数据,提交一次事务,避免事务过大导致性能问题</span></span><br><span class="line">IF v_count <span class="operator">%</span> <span class="number">100000</span> <span class="number">0</span> <span class="keyword">THEN</span></span><br><span class="line"><span class="keyword">COMMIT</span>;</span><br><span class="line"><span class="keyword">START</span> TRANSACTION;</span><br><span class="line"><span class="keyword">END</span> IF;</span><br><span class="line"><span class="keyword">END</span> WHILE;</span><br><span class="line"></span><br><span class="line"><span class="keyword">COMMIT</span>;</span><br><span class="line"><span class="keyword">END</span> <span class="operator">/</span><span class="operator">/</span></span><br><span class="line"></span><br><span class="line">DELIMITER ;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img3.avif"></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">CALL InsertTwentyMillionRows();</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img4.avif"></p><p>查看information_schema.tables表中的信息</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img5.avif"></p><p>delete删除表中的所有数据,并使用上述sql查看碎片率</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img7.avif"></p><p>再次查看information_schema.tables表中的统计信息,没有变化,使用analyze更新统计信息</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img9.avif"></p><p>再次查看information_schema.tables表中的统计信息,发现已更新,这时在次使用上述sql查看碎片率,发现碎片率变到99.98%</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img11.avif"></p><p>最后使用optimize重建表后发现碎片率归0</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img12.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img13.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img14.avif"></p><p>这里有时执行optimize后data_free并不会完全归零,这是因为InnoDB 存储引擎在表空间中预留了一部分空间,用于未来的插入操作。这是为了提高插入性能,避免频繁的页分裂。即使表空间被重新组织,InnoDB 也会保留这部分预留空间,因此 data_free 不会完全归零。当然除了预留空间外,还可能包括未使用的页、表空间的最小单位、并发操作以及存储引擎的限制。</p><p>表空间和页的概念</p><ul><li>**表空间 Tablespace **:InnoDB 使用表空间来存储数据和索引。表空间是由一个或多个文件组成的,这些文件可以是单个文件 如 <code>ibdata1</code> 或多文件表空间 如 <code>.ibd</code> 文件 。表空间是 InnoDB 存储数据和索引的基本单位。</li><li>**页 Page **:页是表空间中存储数据和索引的基本单位,通常大小为 16 KB。每个页可以存储多行数据或索引条目。InnoDB 通过页来管理数据和索引的存储。</li></ul><p>预留空间的目的</p><p>InnoDB 在表空间中预留一部分空间的主要目的是为了优化插入操作和减少碎片化。以下是具体原因:</p><p>提高插入性能</p><ul><li><strong>预留空间</strong>:当表中插入新数据时,InnoDB 会尝试将新数据插入到预留空间中。预留空间的存在减少了频繁分配新页的需要,从而提高了插入操作的效率。</li><li><strong>减少页分裂</strong>:如果没有预留空间,插入操作可能会导致页分裂。页分裂是指一个页满了之后,InnoDB 会将页中的数据分成两部分,分别存储在两个新的页中。页分裂会增加碎片化,降低读写性能。预留空间可以减少页分裂的发生。</li></ul><p>减少碎片化</p><ul><li><strong>减少未使用空间</strong>:预留空间可以减少表空间中的未使用空间 <code>DATA_FREE</code> 。通过预留一部分空间,InnoDB 可以更有效地利用表空间,减少碎片化的产生。</li><li><strong>优化存储管理</strong>:预留空间有助于优化表空间的存储管理,减少表空间的碎片化,提高存储效率。</li></ul><h3 id="主从节点空间碎片率分析"><a href="#主从节点空间碎片率分析" class="headerlink" title="主从节点空间碎片率分析"></a>主从节点空间碎片率分析</h3><p>使用上述相同的方式插入2千万行数据,可以发现主节点和只读节点的空间碎片率和物理文件存在差异</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img15.avif"></p><p>在主节点执行analyze更新统计信息</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img16.avif"></p><p>这时碎片率有所上升,但是主和只读还是不完全相等</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img17.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-10-24/img18.avif"></p><h4 id="主库和只读实例的碎片率出现较大差异的原因分析"><a href="#主库和只读实例的碎片率出现较大差异的原因分析" class="headerlink" title="主库和只读实例的碎片率出现较大差异的原因分析"></a>主库和只读实例的碎片率出现较大差异的原因分析</h4><h5 id="复制原理与多线程复制"><a href="#复制原理与多线程复制" class="headerlink" title="复制原理与多线程复制"></a>复制原理与多线程复制</h5><ul><li>逻辑复制原理:MySQL 的逻辑复制是基于二进制日志 binlog 的。主库将数据变更操作记录到 binlog 中,从库通过 I&#x2F;O 线程读取主库的 binlog,并将其存储到本地的中继日志 relay log 中。然后,从库的 SQL 线程会读取 relay log 并应用这些变更。</li><li>多线程复制:为了提高复制效率,MySQL 支持多线程复制。在多线程复制中,从库可以使用多个 SQL 线程并行地应用 relay log 中的事件。这可以显著提高复制的性能,但也会引入一些复杂性。</li></ul><h5 id="多线程复制中的顺序问题"><a href="#多线程复制中的顺序问题" class="headerlink" title="多线程复制中的顺序问题"></a>多线程复制中的顺序问题</h5><ul><li>事务依赖性:在单线程复制中,SQL 线程会严格按照 binlog 中的顺序应用事件,确保数据的一致性。但在多线程复制中,多个 SQL 线程可能会并行地应用 relay log 中的事件。如果这些事件之间存在依赖关系 例如,一个 <code>INSERT</code> 操作依赖于之前的某个 <code>DELETE</code> 操作 ,并行应用可能会导致顺序发生变化。</li><li>分组提交:MySQL 的多线程复制支持分组提交 Group Commit ,即将多个事件分组后并行提交。虽然 MySQL 会尽量保证分组内的事件顺序,但不同分组之间的事件顺序可能会发生变化。</li></ul><p>碎片率差异的原因</p><ul><li><code>INSERT</code> 和 <code>DELETE</code> 操作顺序变化:如果只读实例的 <code>INSERT</code> 和 <code>DELETE</code> 操作顺序与主库不同,可能会导致数据分布和索引结构的变化。例如,主库中先执行了一个 <code>DELETE</code> 操作,然后执行了一个 <code>INSERT</code> 操作,而只读实例中这两个操作的顺序相反,这可能会导致只读实例中的数据碎片率增加。</li><li>索引维护差异:<code>INSERT</code> 和 <code>DELETE</code> 操作会影响索引的维护。如果操作顺序不同,索引的分裂和合并操作也会不同,从而导致索引碎片率的差异。</li><li>并发写入和删除:在多线程复制中,多个线程可能会同时对同一个表进行写入和删除操作。如果这些操作的顺序不一致,可能会导致数据页的碎片化。例如,一个线程在某个数据页中插入了大量数据,而另一个线程在同一个数据页中删除了部分数据,这可能会导致数据页的碎片化。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/10/24/aa20384c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Miniflux – RSS 订阅</title>
      <link>https://blog.eucalyptus.cc/2025/10/07/bf96e2d2/</link>
      <guid>https://blog.eucalyptus.cc/2025/10/07/bf96e2d2/</guid>
      <pubDate>Tue, 07 Oct 2025 12:12:24 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是Miniflux&quot;&gt;&lt;a href=&quot;#什么是Miniflux&quot; class=&quot;headerlink&quot; title=&quot;什么是Miniflux&quot;&gt;&lt;/a&gt;什么是Miniflux&lt;/h2&gt;&lt;p&gt;Miniflux 是一个用 Go 写的极简开源 RSS</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是Miniflux"><a href="#什么是Miniflux" class="headerlink" title="什么是Miniflux"></a>什么是Miniflux</h2><p>Miniflux 是一个用 Go 写的极简开源 RSS 阅读器，单二进制 +内建 Web UI，五分钟就能容器化跑起来；它默认 Fever API、内存占用极低，界面干净无广告，适合只想安静看文章、不想折腾样式插件的极简党。</p><h3 id="核心功能与特点"><a href="#核心功能与特点" class="headerlink" title="核心功能与特点"></a>核心功能与特点</h3><ul><li>极简设计 ：功能精简，专注于核心阅读体验。</li><li>高性能 ：基于 Go 语言开发，单二进制文件，无依赖。</li><li>轻量且快速 ：资源占用低，响应迅速。</li><li>现代技术栈 ：使用现代 JavaScript（ES6 和 Fetch API），无复杂框架。</li><li>单一数据库支持 ：仅支持 PostgreSQL，确保数据一致性和性能。</li><li>易于安装 ：提供 Docker 镜像，一键部署。</li></ul><h3 id="适用场景"><a href="#适用场景" class="headerlink" title="适用场景"></a>适用场景</h3><ul><li>极简主义爱好者：追求简洁、高效的新闻阅读体验。</li><li>开发者：通过 API 集成到其他应用中。</li><li>低资源环境：在树莓派等低性能设备上运行。</li></ul><h3 id="官方地址"><a href="#官方地址" class="headerlink" title="官方地址"></a>官方地址</h3><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://miniflux.app">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://miniflux.app/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://miniflux.app/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Miniflux 官方网站</div>            <div class="tag-link-sitename">官方网站</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><ul><li>GitHub 仓库：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://github.com/miniflux/v2">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://github.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://github.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Miniflux GitHub</div>            <div class="tag-link-sitename">GitHub仓库</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></li></ul><h2 id="前提条件"><a href="#前提条件" class="headerlink" title="前提条件"></a>前提条件</h2><p>在开始部署之前，请确保你的系统已经安装了 Docker 和 Docker Compose。如果尚未安装，请参考Eucalyptus写的<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://blog.csdn.net/weixin_72610956/article/details/131507884">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://blog.csdn.net/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://blog.csdn.net/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Centos7下安装Docker</div>            <div class="tag-link-sitename">CSDN博客</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div> ，</p><h2 id="创建-Docker-Compose-配置文件"><a href="#创建-Docker-Compose-配置文件" class="headerlink" title="创建 Docker Compose 配置文件"></a>创建 Docker Compose 配置文件</h2><h3 id="命令行部署"><a href="#命令行部署" class="headerlink" title="命令行部署"></a>命令行部署</h3><p>首先登录你部署Miniflux的服务器，然后创建个docker-compose.yml文件</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br></pre></td><td class="code"><pre><span class="line">services:</span><br><span class="line">  miniflux:</span><br><span class="line">    image: miniflux/miniflux:latest</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;80:8080&quot;</span></span><br><span class="line">    depends_on:</span><br><span class="line">      db:</span><br><span class="line">        condition: service_healthy</span><br><span class="line">    environment:</span><br><span class="line">      - DATABASE_URL=postgres://miniflux:admin@123@db/miniflux?sslmode=<span class="built_in">disable</span></span><br><span class="line">      - RUN_MIGRATIONS=1</span><br><span class="line">      - CREATE_ADMIN=1</span><br><span class="line">      - ADMIN_USERNAME=admin</span><br><span class="line">      - ADMIN_PASSWORD=admin@123</span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;/usr/bin/miniflux&quot;</span>, <span class="string">&quot;-healthcheck&quot;</span>, <span class="string">&quot;auto&quot;</span>]</span><br><span class="line"></span><br><span class="line">  db:</span><br><span class="line">    image: postgres:17-alpine</span><br><span class="line">    environment:</span><br><span class="line">      - POSTGRES_USER=miniflux          <span class="comment"># 与 DATABASE_URL 用户一致</span></span><br><span class="line">      - POSTGRES_PASSWORD=admin@123</span><br><span class="line">      - POSTGRES_DB=miniflux</span><br><span class="line">    volumes:</span><br><span class="line">      - miniflux-db:/var/lib/postgresql/data   <span class="comment"># 官方默认路径</span></span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;pg_isready&quot;</span>, <span class="string">&quot;-U&quot;</span>, <span class="string">&quot;miniflux&quot;</span>]  <span class="comment"># 用户一致</span></span><br><span class="line">      interval: 10s</span><br><span class="line">      start_period: 30s</span><br><span class="line"></span><br><span class="line">volumes:</span><br><span class="line">  miniflux-db:</span><br></pre></td></tr></table></figure><p>接下来再当前目录下直接执行下述命令即可</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker compose up -d</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/1.avif"></p><h3 id="宝塔可视化部署"><a href="#宝塔可视化部署" class="headerlink" title="宝塔可视化部署"></a>宝塔可视化部署</h3><p>当然也可完全使用宝塔可视化部署，在宝塔中的docker容器编排这里部署</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/3.avif"></p><p>compose内容</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br></pre></td><td class="code"><pre><span class="line">version: <span class="string">&quot;3.9&quot;</span></span><br><span class="line"></span><br><span class="line">services:</span><br><span class="line">  miniflux:</span><br><span class="line">    image: miniflux/miniflux:latest</span><br><span class="line">    ports:</span><br><span class="line">      - <span class="string">&quot;<span class="variable">$&#123;MINIFLUX_PORT&#125;</span>:8080&quot;</span>          <span class="comment"># ← 变量</span></span><br><span class="line">    depends_on:</span><br><span class="line">      db:</span><br><span class="line">        condition: service_healthy</span><br><span class="line">    environment:</span><br><span class="line">      - DATABASE_URL=postgres://<span class="variable">$&#123;DB_USER&#125;</span>:<span class="variable">$&#123;DB_PASS&#125;</span>@db/<span class="variable">$&#123;DB_NAME&#125;</span>?sslmode=<span class="built_in">disable</span></span><br><span class="line">      - RUN_MIGRATIONS=1</span><br><span class="line">      - CREATE_ADMIN=1</span><br><span class="line">      - ADMIN_USERNAME=<span class="variable">$&#123;ADMIN_USER&#125;</span></span><br><span class="line">      - ADMIN_PASSWORD=<span class="variable">$&#123;ADMIN_PASS&#125;</span></span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;/usr/bin/miniflux&quot;</span>, <span class="string">&quot;-healthcheck&quot;</span>, <span class="string">&quot;auto&quot;</span>]</span><br><span class="line"></span><br><span class="line">  db:</span><br><span class="line">    image: postgres:17-alpine</span><br><span class="line">    environment:</span><br><span class="line">      - POSTGRES_USER=<span class="variable">$&#123;DB_USER&#125;</span></span><br><span class="line">      - POSTGRES_PASSWORD=<span class="variable">$&#123;DB_PASS&#125;</span></span><br><span class="line">      - POSTGRES_DB=<span class="variable">$&#123;DB_NAME&#125;</span></span><br><span class="line">    volumes:</span><br><span class="line">      - miniflux-db:/var/lib/postgresql/data</span><br><span class="line">    healthcheck:</span><br><span class="line">      <span class="built_in">test</span>: [<span class="string">&quot;CMD&quot;</span>, <span class="string">&quot;pg_isready&quot;</span>, <span class="string">&quot;-U&quot;</span>, <span class="string">&quot;<span class="variable">$&#123;DB_USER&#125;</span>&quot;</span>]</span><br><span class="line">      interval: 10s</span><br><span class="line">      start_period: 30s</span><br><span class="line"></span><br><span class="line">volumes:</span><br><span class="line">  miniflux-db:</span><br></pre></td></tr></table></figure><p>.env内容</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># Miniflux 外部端口</span></span><br><span class="line">MINIFLUX_PORT=80</span><br><span class="line"></span><br><span class="line"><span class="comment"># 数据库三要素</span></span><br><span class="line">DB_USER=miniflux</span><br><span class="line">DB_PASS=admin@123</span><br><span class="line">DB_NAME=miniflux</span><br><span class="line"></span><br><span class="line"><span class="comment"># 管理员账号</span></span><br><span class="line">ADMIN_USER=admin</span><br><span class="line">ADMIN_PASS=admin@123</span><br></pre></td></tr></table></figure><h3 id="Miniflux订阅RSS"><a href="#Miniflux订阅RSS" class="headerlink" title="Miniflux订阅RSS"></a>Miniflux订阅RSS</h3><p>到这里Miniflux已经部署完成了，接下来在浏览器访问<code>http://&lt;IP&gt;:80</code>即可，ip使用你部署Miniflux服务器的公网ip，Miniflux的用户是admin，密码是admin@123，pg的用户名是miniflux，密码是admin@123</p><p>输入Miniflux密码进行登录</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/4.avif"></p><p>刚进去的是英文界面，可以在set设置简体中文</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/5.avif"></p><p>然后添加订阅源，输入你要订阅BLOG的RSS地址例如：<code>https://eucalyptus.cc/feed/</code></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/6.avif"></p><p>然后就可以看到BLOG的文章内容了</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-10-07/7.avif"></p><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><p>到这里Miniflux就完成了部署并且订阅了Blog的RSS，整个过程仅需几分钟就能搭建起一个轻量高效的RSS阅读平台，你可以通过网页端随时随地获取最新内容更新，无需担心广告干扰或算法推荐；如果你不方便自行部署的话，可以_<strong>留言申请Eucalyptus</strong>_部署的Miniflux服务的用户名进行体验，我们提供免费的测试账号供你试用一周，期间你可以完整体验Miniflux的所有功能，包括多设备同步、快捷键操作、文章收藏等特色功能，感受这款开源RSS阅读器的简洁与高效。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/RSS/">RSS</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Miniflux/">Miniflux</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/10/07/bf96e2d2/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL抛出的Public Key Retrieval is not allowed</title>
      <link>https://blog.eucalyptus.cc/2025/09/20/723a6a1c/</link>
      <guid>https://blog.eucalyptus.cc/2025/09/20/723a6a1c/</guid>
      <pubDate>Sat, 20 Sep 2025 02:40:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;有时候在连接实例的时候会遇到这样的报错&lt;strong&gt;Public Key Retrieval is not allowed&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>有时候在连接实例的时候会遇到这样的报错<strong>Public Key Retrieval is not allowed</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img2.avif"></p><h3 id="问题分析"><a href="#问题分析" class="headerlink" title="问题分析"></a>问题分析</h3><p>这是因为账号使用了caching_sha2_password 密码插件</p><p>而caching_sha2_password 插件为了加快认证过程,在服务端维护了一个<strong>密码哈希缓存</strong>。当客户端发起连接时:</p><ul><li><em><strong>如果用户的密码哈希已经被缓存,服务端可以直接验证,无需客户端发送明文密码进行验证。</strong></em></li><li><em><strong>如果缓存中没有该用户的密码哈希,则客户端需要发送明文密码进行认证。</strong></em></li></ul><p>在发送明文密码时,出于安全考虑,MySQL 要求:</p><ul><li>要么客户端和服务端之间建立 SSL 加密连接。</li><li>要么客户端允许通过服务端公钥加密明文密码。</li></ul><p>如果两者都不满足,就会抛出 Public Key Retrieval is not allowed 错误。</p><p>以下三种情况会导致缓存中没有用户的密码哈希</p><ul><li>发生重启</li><li>发生HA</li><li>有操作flush privileges</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img3.avif"></p><h3 id="解决方法"><a href="#解决方法" class="headerlink" title="解决方法"></a>解决方法</h3><p>1、客户端的话可以设置驱动中的allowPublicKeyRetrieval true</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img4.avif"></p><p>2、JDBC的话可以在连接字符串中添加allowPublicKeyRetrieval true参数,以允许公钥检索。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">jdbc:mysql://localhost:3306/?allowPublicKeyRetrieval true</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img5.avif"></p><p>3、将账号的密码插件改为mysql_native_password</p><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><p>设置allowPublicKeyRetrieval true的方法会自动从 MySQL 服务端获取 RSA 公钥,但这种方法有一定的安全风险,可能会受到中间人攻击。攻击者可以伪造 RSA 公钥,窃取用户密码。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/09/20/723a6a1c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL JDBC 驱动未找到</title>
      <link>https://blog.eucalyptus.cc/2025/09/20/03f3318d/</link>
      <guid>https://blog.eucalyptus.cc/2025/09/20/03f3318d/</guid>
      <pubDate>Sat, 20 Sep 2025 01:15:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;新手在idea中使用jdbc连接mysql的时候可能会遇到这样的报错 MySQL JDBC 驱动未找到,下面给大家提供解决方法&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>新手在idea中使用jdbc连接mysql的时候可能会遇到这样的报错 MySQL JDBC 驱动未找到,下面给大家提供解决方法</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img1.avif"></p><h3 id="驱动下载"><a href="#驱动下载" class="headerlink" title="驱动下载"></a>驱动下载</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img6.avif"></p><h3 id="驱动配置"><a href="#驱动配置" class="headerlink" title="驱动配置"></a>驱动配置</h3><p>下载解压后,找到这jar文件然后复制</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img7.avif"></p><p>打开idea,在当前的目录下新建一个lib目录,将刚才的jar文件复制到lib目录下</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img8.avif"></p><p>鼠标右击刚才copy过来的jar文件选择添加为库</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img9.avif"></p><p>最后点击确定即可</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img10.avif"></p><p>最后在运行代码可以看到已经连接成功</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-20/img11.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/09/20/03f3318d/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的Got an error reading communication packet</title>
      <link>https://blog.eucalyptus.cc/2025/09/16/5ff60ddc/</link>
      <guid>https://blog.eucalyptus.cc/2025/09/16/5ff60ddc/</guid>
      <pubDate>Tue, 16 Sep 2025 09:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;我们经常在MySQL的error log中可以看到这样的[Note],从官网的介绍来说,导致下述这种情况出现的原因,有下述几种&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>我们经常在MySQL的error log中可以看到这样的[Note],从官网的介绍来说,导致下述这种情况出现的原因,有下述几种</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img2.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html">https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html</a></p><p>另外我们要清楚,Got an error reading communication packets:是客户端异常关闭之后DB才会被动打印的日志,不是DB主动关闭的。所以首要排查方向应该是应用侧,非db侧。如果是客户端超过wait_timeout不活动被DB主动关闭的话,应该打印的日志是:Got timeout reading communication packets</p><h3 id="场景分析"><a href="#场景分析" class="headerlink" title="场景分析"></a>场景分析</h3><p>客户端使用mycli和mysql分别去连接</p><p>mycli</p><p>可以看到使用mycli连接后Aborted_clients 增加,并且错误日志中出现</p><p>[Note] [MY-010914] [Server] Aborted connection 9 to db: ‘unconnected’ user: ‘root’ host: ‘localhost’ (Got an error reading communication packets)</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img4.avif"></p><p>mysql</p><p>而使用mysql连接后则没有这个问题</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img5.avif"></p><p>针对mycli连接时出现的这个情况进行了抓包分析,可以看到38行有个[FIN,ACK]的Flags,查看传输层的信息发现是客户端主动关闭了连接,This frame initiates the connection closing。查看39行,可以看到应用层返回了</p><p>Error message: Got an error reading communication packets,并且在40行可以看到RST的Flags,这里可能和mycli的客户端行为有关</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img7.avif"></p><p>而使用mysql连接时查看返回的抓包情况并没有RST的Flags</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-09-16/img8.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/09/16/5ff60ddc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Wordpress登录页面DIY</title>
      <link>https://blog.eucalyptus.cc/2025/09/01/c9af3afa/</link>
      <guid>https://blog.eucalyptus.cc/2025/09/01/c9af3afa/</guid>
      <pubDate>Mon, 01 Sep 2025 12:37:45 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;由于部分WordPress主题在默认配置下没有对后台登录界面进行定制化开发，用户只能使用系统自带的原生登录页面，这种页面往往设计简陋、缺乏品牌特色，与网站整体风格格格不入，影响了用户体验和品牌形象；为此，我通过深入研究WordPress的login_head和login_f</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>由于部分WordPress主题在默认配置下没有对后台登录界面进行定制化开发，用户只能使用系统自带的原生登录页面，这种页面往往设计简陋、缺乏品牌特色，与网站整体风格格格不入，影响了用户体验和品牌形象；为此，我通过深入研究WordPress的login_head和login_footer钩子，对原生登录页面进行了全面的二次开发，不仅替换了默认的WordPress logo为网站品牌标识，还重新设计了登录表单的布局和配色方案，增加了背景图片和CSS3动画效果，同时优化了移动端的响应式布局，使登录页面与网站主题风格完美统一，大大提升了后台管理的专业性和视觉体验。</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://gitcode.com/weixin_72610956/Blog/tree/login">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://gitcode.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://gitcode.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">登录页面DIY 源码下载</div>            <div class="tag-link-sitename">GitCode</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-09-01/1.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#下述了两个代码文件均放置到主题目录下的自建self-innovate文件中</span></span><br><span class="line">login-style.php</span><br><span class="line">login-style.css</span><br></pre></td></tr></table></figure><p>核心代码</p><figure class="highlight php"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;?php</span></span><br><span class="line"><span class="comment">/**</span></span><br><span class="line"><span class="comment"> * 登录页美化（Logo 完全禁用点击）</span></span><br><span class="line"><span class="comment"> */</span></span><br><span class="line"><span class="title function_ invoke__">add_action</span>( <span class="string">&#x27;login_enqueue_scripts&#x27;</span>, function () &#123;</span><br><span class="line">    <span class="title function_ invoke__">wp_enqueue_style</span>( <span class="string">&#x27;my-login&#x27;</span>, <span class="title function_ invoke__">get_theme_file_uri</span>( <span class="string">&#x27;/self-innovate/login-style.css&#x27;</span> ), [], <span class="string">&#x27;1.0.0&#x27;</span> );</span><br><span class="line">&#125; );</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 完全移除 &lt;a&gt; 的 href，避免刷新 */</span></span><br><span class="line"><span class="title function_ invoke__">add_filter</span>( <span class="string">&#x27;login_headerurl&#x27;</span>, function () &#123;</span><br><span class="line">    <span class="keyword">return</span> <span class="string">&#x27;javascript:void(0);&#x27;</span>;   <span class="comment">// 真正无动作</span></span><br><span class="line">&#125; );</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 悬停文字留空，防止提示 */</span></span><br><span class="line"><span class="title function_ invoke__">add_filter</span>( <span class="string">&#x27;login_headertext&#x27;</span>, <span class="string">&#x27;__return_empty_string&#x27;</span> );</span><br></pre></td></tr></table></figure><p>下述是css代码，需替换css中body.login和login::before的background:url(”)路径</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br></pre></td><td class="code"><pre><span class="line">/* 1. 背景与斜遮罩 */</span><br><span class="line">body.login&#123;</span><br><span class="line">  height:100vh;</span><br><span class="line">  margin:0;</span><br><span class="line">  display:flex;</span><br><span class="line">  align-items:center;</span><br><span class="line">  justify-content:center;</span><br><span class="line">  background:url(<span class="string">&#x27;https://blog.eucalyptus.cc/wp-content/uploads/2025/05/16-scaled.jpg&#x27;</span>) center/cover no-repeat;</span><br><span class="line">  position:relative;</span><br><span class="line">&#125;</span><br><span class="line">body.login::before&#123;</span><br><span class="line">  content:<span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  position:absolute;</span><br><span class="line">  inset:0;</span><br><span class="line">  background:linear-gradient(-75deg, transparent 0% 50%, rgba(255,255,255,.6) 50% 100%);</span><br><span class="line">  z-index:1;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 2. 登录框整体定位与 Logo */</span><br><span class="line"><span class="comment">#login&#123;</span></span><br><span class="line">  position:relative;</span><br><span class="line">  z-index:2;</span><br><span class="line">  width:340px;</span><br><span class="line">  padding:40px 40px 40px; /* 40px+140px空间已含在顶部padding */</span><br><span class="line">  padding-top:140px;      /* 给Logo留空间 */</span><br><span class="line">  margin-left:150px;</span><br><span class="line">&#125;</span><br><span class="line"><span class="comment">#login::before&#123;           /* Logo伪元素 */</span></span><br><span class="line">  content:<span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  position:absolute;</span><br><span class="line">  top:20px;</span><br><span class="line">  left:50%;</span><br><span class="line">  transform:translateX(-50%);</span><br><span class="line">  width:160px;</span><br><span class="line">  aspect-ratio:1;</span><br><span class="line">  background:url(<span class="string">&#x27;https://img.eucalyptus.cc/logo/logo1.avif?imageslim&#x27;</span>) center/contain no-repeat;</span><br><span class="line">  pointer-events:none;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 3. 表单 */</span><br><span class="line">body.login form#loginform&#123;</span><br><span class="line">  margin:24px 0 !important;</span><br><span class="line">  padding:26px 24px !important;</span><br><span class="line">  box-shadow:0 1px 3px rgba(0,0,0,.04) !important;</span><br><span class="line">  background:transparent !important;</span><br><span class="line">  border:none !important;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 4. 文字Logo */</span><br><span class="line">.login h1 a&#123;</span><br><span class="line">  background:none !important;</span><br><span class="line">  text-indent:0;</span><br><span class="line">  width:auto;</span><br><span class="line">  height:auto;</span><br><span class="line">  font:700 24px/1.2 sans-serif;</span><br><span class="line">  color:#333;</span><br><span class="line">  margin-bottom:24px;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 5. 输入框 */</span><br><span class="line">.login form .input&#123;</span><br><span class="line">  border:1px solid <span class="comment">#e1e5e9;</span></span><br><span class="line">  border-radius:8px;</span><br><span class="line">  padding:12px 16px;</span><br><span class="line">  font-size:15px;</span><br><span class="line">  transition:border-color .3s, box-shadow .3s;</span><br><span class="line">&#125;</span><br><span class="line">.login form .input:focus&#123;</span><br><span class="line">  border-color:#667eea;</span><br><span class="line">  box-shadow:0 0 0 2px rgba(102,126,234,.25);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 6. 按钮 */</span><br><span class="line">.wp-core-ui .button-primary&#123;</span><br><span class="line">  width:100%;</span><br><span class="line">  border:none;</span><br><span class="line">  border-radius:30px;</span><br><span class="line">  padding:12px 0;</span><br><span class="line">  font:600 16px/1 sans-serif;</span><br><span class="line">  background:linear-gradient(135deg,#667eea 0%,#764ba2 100%);</span><br><span class="line">  transition:transform .3s;</span><br><span class="line">&#125;</span><br><span class="line">.wp-core-ui .button-primary:hover&#123;</span><br><span class="line">  transform:translateY(-2px);</span><br><span class="line">  box-shadow:0 6px 20px rgba(102,126,234,.45);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">/* 7. 隐藏语言切换 */</span><br><span class="line"><span class="comment">#language-switcher&#123;display:none !important;&#125;</span></span><br></pre></td></tr></table></figure><p>最后需再functions.php中调用该模块</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">require_once get_theme_file_path( <span class="string">&#x27;/self-innovate/login-style.php&#x27;</span> );</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%8F%92%E4%BB%B6/">插件</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/09/01/c9af3afa/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Meteor主题友链页面自研</title>
      <link>https://blog.eucalyptus.cc/2025/08/31/d915d040/</link>
      <guid>https://blog.eucalyptus.cc/2025/08/31/d915d040/</guid>
      <pubDate>Sun, 31 Aug 2025 13:47:25 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;Meteor主题虽然设计简约现代，但由于缺乏原生的友情链接管理功能，许多博主只能将友情链接勉强添加在网站底部，这不仅影响页面美观，也不便于访客查找和互动；为了解决这一痛点，本博主对主题进行了深度二次开发，专门打造了一个独立的友情链接页面，该页面不仅实现了友链分类展示、图文混</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>Meteor主题虽然设计简约现代，但由于缺乏原生的友情链接管理功能，许多博主只能将友情链接勉强添加在网站底部，这不仅影响页面美观，也不便于访客查找和互动；为了解决这一痛点，本博主对主题进行了深度二次开发，专门打造了一个独立的友情链接页面，该页面不仅实现了友链分类展示、图文混排等基本功能，更创新性地开发了前端提交表单，允许其他站长直接在线提交申请，同时配套开发了完善的后台审核系统，管理员可以便捷地查看申请信息、审核状态，并一键通过或拒绝，整个流程实现了自动化闭环管理，大大提升了友链交换的效率和用户体验。</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://gitcode.com/weixin_72610956/Blog/tree/link">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://gitcode.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://gitcode.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Meteor主题友链页面 源码下载</div>            <div class="tag-link-sitename">GitCode</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">default-avatar.jpg</span><br><span class="line">page-links.css</span><br><span class="line">page-links.js</span><br><span class="line">pending-links.php</span><br></pre></td></tr></table></figure><p>以下是核心代码部分，这段代码实现了系统的关键功能，</p><p>并且这里对友链头像有三个判断的逻辑</p><ul><li>有头像 → 正常显示；</li><li>无头像 → 立即显示默认头像；</li><li>有头像但 3 秒仍未加载完成 → 自动替换成默认头像。</li></ul><figure class="highlight php"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;?php</span></span><br><span class="line"><span class="comment">/*</span></span><br><span class="line"><span class="comment"> * Template Name: 友情链接</span></span><br><span class="line"><span class="comment"> * Description:  极简友链模板（样式/脚本已分离，含评论）</span></span><br><span class="line"><span class="comment"> */</span></span><br><span class="line"></span><br><span class="line"><span class="title function_ invoke__">get_header</span>(); </span><br><span class="line"><span class="meta">?&gt;</span></span><br><span class="line"></span><br><span class="line">&lt;div <span class="class"><span class="keyword">class</span>=&quot;<span class="title">hero</span>-<span class="title">title</span>&quot;&gt;</span></span><br><span class="line"><span class="class">  &lt;?<span class="title">php</span> <span class="title">the_title</span>( &#x27;&lt;<span class="title">h1</span>&gt;&#x27;, &#x27;&lt;/<span class="title">h1</span>&gt;&#x27; ); ?&gt;</span></span><br><span class="line"><span class="class">  &lt;<span class="title">p</span> <span class="title">class</span>=&quot;<span class="title">hero</span>-<span class="title">sub</span>&quot;&gt;欢迎交换友链 · 携手点亮彼此的星空&lt;/<span class="title">p</span>&gt;</span></span><br><span class="line"><span class="class">&lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">&lt;!-- 载入独立样式 --&gt;</span></span><br><span class="line"><span class="class">&lt;<span class="title">link</span> <span class="title">rel</span>=&quot;<span class="title">stylesheet</span>&quot; <span class="title">href</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">get_template_directory_uri</span>(); ?&gt;/<span class="title">self</span>-<span class="title">innovate</span>/<span class="title">page</span>-<span class="title">links</span>.<span class="title">css</span>&quot;&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">&lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">page</span>-<span class="title">links</span>&quot;&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">  &lt;!-- 搜索框 --&gt;</span></span><br><span class="line"><span class="class">  &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">search</span>&quot;&gt;</span></span><br><span class="line"><span class="class">    &lt;<span class="title">input</span> <span class="title">type</span>=&quot;<span class="title">text</span>&quot; <span class="title">id</span>=&quot;<span class="title">link</span>-<span class="title">search</span>&quot; <span class="title">placeholder</span>=&quot;搜索站点名称或描述…&quot;&gt;</span></span><br><span class="line"><span class="class">  &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">  &lt;!-- 友链列表 --&gt;</span></span><br><span class="line"><span class="class">  &lt;?<span class="title">php</span></span></span><br><span class="line"><span class="class">  $<span class="title">cats</span> = <span class="title">get_terms</span>( &#x27;<span class="title">link_category</span>&#x27;, <span class="title">array</span>( &#x27;<span class="title">hide_empty</span>&#x27; =&gt; 0 ) );</span></span><br><span class="line"><span class="class">  <span class="title">foreach</span> ( $<span class="title">cats</span> <span class="title">as</span> $<span class="title">cat</span> ) :</span></span><br><span class="line"><span class="class">    $<span class="title">bookmarks</span> = <span class="title">get_bookmarks</span>( <span class="title">array</span>(</span></span><br><span class="line"><span class="class">      &#x27;<span class="title">category</span>&#x27; =&gt; $<span class="title">cat</span>-&gt;<span class="title">term_id</span>,</span></span><br><span class="line"><span class="class">      &#x27;<span class="title">orderby</span>&#x27;  =&gt; &#x27;<span class="title">rating</span>&#x27;,</span></span><br><span class="line"><span class="class">      &#x27;<span class="title">order</span>&#x27;    =&gt; &#x27;<span class="title">DESC</span>&#x27;</span></span><br><span class="line"><span class="class">    ) );</span></span><br><span class="line"><span class="class">    <span class="title">if</span> ( <span class="title">empty</span>( $<span class="title">bookmarks</span> ) ) <span class="title">continue</span>;</span></span><br><span class="line"><span class="class">  ?&gt;</span></span><br><span class="line"><span class="class">    &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">cat</span>&quot;&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">h2</span>&gt;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_html</span>( $<span class="title">cat</span>-&gt;<span class="title">name</span> ); ?&gt;&lt;/<span class="title">h2</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;?<span class="title">php</span> <span class="title">if</span> ( ! <span class="title">empty</span>( $<span class="title">cat</span>-&gt;<span class="title">description</span> ) ) : ?&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">p</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">cat</span>-<span class="title">desc</span>&quot;&gt;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_html</span>( $<span class="title">cat</span>-&gt;<span class="title">description</span> ); ?&gt;&lt;/<span class="title">p</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;?<span class="title">php</span> <span class="title">endif</span>; ?&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">links</span>&quot;&gt;</span></span><br><span class="line"><span class="class">      &lt;?<span class="title">php</span> <span class="title">foreach</span> ( $<span class="title">bookmarks</span> <span class="title">as</span> $<span class="title">link</span> ) : ?&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">a</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">card</span>&quot; <span class="title">href</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_url</span>( $<span class="title">link</span>-&gt;<span class="title">link_url</span> ); ?&gt;&quot; <span class="title">target</span>=&quot;<span class="title">_blank</span>&quot; <span class="title">rel</span>=&quot;<span class="title">noopener</span>&quot;&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">img</span></span></span><br><span class="line"><span class="class">          <span class="title">src</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_url</span>( $<span class="title">link</span>-&gt;<span class="title">link_image</span> ?: &#x27;&#x27; ); ?&gt;&quot;</span></span><br><span class="line"><span class="class">          <span class="title">data</span>-<span class="title">default</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_url</span>( <span class="title">get_template_directory_uri</span>() . &#x27;/<span class="title">self</span>-<span class="title">innovate</span>/<span class="title">default</span>-<span class="title">avatar</span>.<span class="title">jpg</span>&#x27; ); ?&gt;&quot;</span></span><br><span class="line"><span class="class">          <span class="title">alt</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_attr</span>( $<span class="title">link</span>-&gt;<span class="title">link_name</span> ); ?&gt;&quot;</span></span><br><span class="line"><span class="class">          <span class="title">onerror</span>=&quot;<span class="title">this</span>.<span class="title">src</span>=<span class="title">this</span>.<span class="title">dataset</span>.<span class="title">default</span>&quot;</span></span><br><span class="line"><span class="class">          <span class="title">onload</span>=&quot;<span class="title">clearTimeout</span>(<span class="title">this</span>.<span class="title">t</span>)&quot;</span></span><br><span class="line"><span class="class">          <span class="title">ontimeout</span>=&quot;<span class="title">this</span>.<span class="title">src</span>=<span class="title">this</span>.<span class="title">dataset</span>.<span class="title">default</span>&quot;</span></span><br><span class="line"><span class="class">      /&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">script</span>&gt;</span></span><br><span class="line"><span class="class">          (<span class="title">function</span>(<span class="title">img</span>)</span>&#123;</span><br><span class="line">            img.t = <span class="title function_ invoke__">setTimeout</span>(function()&#123; img.src = img.dataset.<span class="keyword">default</span>; &#125;, <span class="number">3000</span>);</span><br><span class="line">          &#125;)(document.currentScript.previousElementSibling);</span><br><span class="line">        &lt;/script&gt;</span><br><span class="line">          &lt;div <span class="class"><span class="keyword">class</span>=&quot;<span class="title">info</span>&quot;&gt;</span></span><br><span class="line"><span class="class">            &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">name</span>&quot;&gt;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_html</span>( $<span class="title">link</span>-&gt;<span class="title">link_name</span> ); ?&gt;&lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">            &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">desc</span>&quot;&gt;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">esc_html</span>( $<span class="title">link</span>-&gt;<span class="title">link_description</span> ); ?&gt;&lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">          &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;/<span class="title">a</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;?<span class="title">php</span> <span class="title">endforeach</span>; ?&gt;</span></span><br><span class="line"><span class="class">      &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">    &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">  &lt;?<span class="title">php</span> <span class="title">endforeach</span>; ?&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">    &lt;!-- 后台内容显示 --&gt;</span></span><br><span class="line"><span class="class">  &lt;?<span class="title">php</span> <span class="title">if</span> ( <span class="title">get_the_content</span>() ) : ?&gt;</span></span><br><span class="line"><span class="class">    &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">intro</span>&quot; <span class="title">style</span>=&quot;<span class="title">margin</span>-<span class="title">bottom</span>:30<span class="title">px</span>;&quot;&gt;&lt;?<span class="title">php</span> <span class="title">the_content</span>(); ?&gt;&lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">  &lt;?<span class="title">php</span> <span class="title">endif</span>; ?&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">  </span></span><br><span class="line"><span class="class">  &lt;!-- 友链申请弹窗 --&gt;</span></span><br><span class="line"><span class="class">  &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">btn</span>-<span class="title">center</span>&quot;&gt;</span></span><br><span class="line"><span class="class">    &lt;<span class="title">button</span> <span class="title">id</span>=&quot;<span class="title">open</span>-<span class="title">link</span>-<span class="title">modal</span>&quot; <span class="title">class</span>=&quot;<span class="title">btn</span>-<span class="title">hero</span>&quot;&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">span</span>&gt;申请交换友链&lt;/<span class="title">span</span>&gt;</span></span><br><span class="line"><span class="class">    &lt;/<span class="title">button</span>&gt;</span></span><br><span class="line"><span class="class">  &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">  &lt;!-- ===== 评论区 ===== --&gt;</span></span><br><span class="line"><span class="class">    &lt;?<span class="title">php</span></span></span><br><span class="line"><span class="class">    // <span class="title">while</span> ( <span class="title">have_posts</span>() ) : <span class="title">the_post</span>();</span></span><br><span class="line"><span class="class">        <span class="title">if</span> ( <span class="title">comments_open</span>() || <span class="title">get_comments_number</span>() ) : ?&gt;</span></span><br><span class="line"><span class="class">            &lt;<span class="title">section</span> <span class="title">class</span>=&quot;<span class="title">link</span>-<span class="title">comments</span>&quot;&gt;</span></span><br><span class="line"><span class="class">                &lt;<span class="title">h2</span> <span class="title">class</span>=&quot;<span class="title">comments</span>-<span class="title">title</span>&quot;&gt;&lt;/<span class="title">h2</span>&gt;</span></span><br><span class="line"><span class="class">                &lt;?<span class="title">php</span> <span class="title">comments_template</span>(); ?&gt;</span></span><br><span class="line"><span class="class">            &lt;/<span class="title">section</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;?<span class="title">php</span></span></span><br><span class="line"><span class="class">        <span class="title">endif</span>;</span></span><br><span class="line"><span class="class">    // <span class="title">endwhile</span>;</span></span><br><span class="line"><span class="class">    ?&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">  &lt;!-- 弹窗 --&gt;</span></span><br><span class="line"><span class="class">  &lt;<span class="title">div</span> <span class="title">id</span>=&quot;<span class="title">link</span>-<span class="title">modal</span>-<span class="title">overlay</span>&quot; <span class="title">class</span>=&quot;<span class="title">modal</span>-<span class="title">fade</span>&quot;&gt;</span></span><br><span class="line"><span class="class">    &lt;<span class="title">div</span> <span class="title">class</span>=&quot;<span class="title">modal</span>-<span class="title">dialog</span>&quot;&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">button</span> <span class="title">class</span>=&quot;<span class="title">modal</span>-<span class="title">close</span>&quot; <span class="title">aria</span>-<span class="title">label</span>=&quot;关闭&quot;&gt;×&lt;/<span class="title">button</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">h3</span> <span class="title">class</span>=&quot;<span class="title">modal</span>-<span class="title">title</span>&quot;&gt;申请交换友链&lt;/<span class="title">h3</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;<span class="title">form</span> <span class="title">id</span>=&quot;<span class="title">link</span>-<span class="title">form</span>&quot; <span class="title">class</span>=&quot;<span class="title">modal</span>-<span class="title">form</span>&quot;&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">input</span> <span class="title">type</span>=&quot;<span class="title">text</span>&quot;   <span class="title">name</span>=&quot;<span class="title">link_name</span>&quot;        <span class="title">placeholder</span>=&quot;网站名称 *&quot; <span class="title">required</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">input</span> <span class="title">type</span>=&quot;<span class="title">url</span>&quot;    <span class="title">name</span>=&quot;<span class="title">link_url</span>&quot;         <span class="title">placeholder</span>=&quot;网站地址 *&quot; <span class="title">required</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">input</span> <span class="title">type</span>=&quot;<span class="title">email</span>&quot;  <span class="title">name</span>=&quot;<span class="title">link_owner_email</span>&quot; <span class="title">placeholder</span>=&quot;站长邮箱 *&quot; <span class="title">required</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">input</span> <span class="title">type</span>=&quot;<span class="title">url</span>&quot;    <span class="title">name</span>=&quot;<span class="title">link_image</span>&quot;       <span class="title">placeholder</span>=&quot;头像 / <span class="title">Logo</span> *&quot; <span class="title">required</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">textarea</span> <span class="title">name</span>=&quot;<span class="title">link_description</span>&quot; <span class="title">rows</span>=&quot;3&quot; <span class="title">placeholder</span>=&quot;一句话描述 *&quot; <span class="title">required</span>&gt;&lt;/<span class="title">textarea</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">button</span> <span class="title">type</span>=&quot;<span class="title">submit</span>&quot; <span class="title">class</span>=&quot;<span class="title">btn</span>-<span class="title">submit</span>&quot;&gt;提交申请&lt;/<span class="title">button</span>&gt;</span></span><br><span class="line"><span class="class">        &lt;<span class="title">p</span> <span class="title">id</span>=&quot;<span class="title">form</span>-<span class="title">msg</span>&quot; <span class="title">class</span>=&quot;<span class="title">form</span>-<span class="title">msg</span>&quot;&gt;&lt;/<span class="title">p</span>&gt;</span></span><br><span class="line"><span class="class">      &lt;/<span class="title">form</span>&gt;</span></span><br><span class="line"><span class="class">    &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">  &lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class">&lt;/<span class="title">div</span>&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">&lt;!-- 载入独立脚本 --&gt;</span></span><br><span class="line"><span class="class">&lt;<span class="title">script</span>&gt;</span></span><br><span class="line"><span class="class">  <span class="title">var</span> <span class="title">ajax_comment_obj</span> = &lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">wp_json_encode</span>(<span class="title">array</span>(&#x27;<span class="title">ajax_url</span>&#x27; =&gt; <span class="title">admin_url</span>(&#x27;<span class="title">admin</span>-<span class="title">ajax</span>.<span class="title">php</span>&#x27;))); ?&gt;;</span></span><br><span class="line"><span class="class">&lt;/<span class="title">script</span>&gt;</span></span><br><span class="line"><span class="class">&lt;<span class="title">script</span> <span class="title">src</span>=&quot;&lt;?<span class="title">php</span> <span class="title">echo</span> <span class="title">get_template_directory_uri</span>(); ?&gt;/<span class="title">self</span>-<span class="title">innovate</span>/<span class="title">page</span>-<span class="title">links</span>.<span class="title">js</span>&quot; <span class="title">defer</span>&gt;&lt;/<span class="title">script</span>&gt;</span></span><br><span class="line"><span class="class"></span></span><br><span class="line"><span class="class">&lt;?<span class="title">php</span> <span class="title">get_footer</span>(); ?&gt;</span></span><br></pre></td></tr></table></figure><p>下面是核心代码的css样式</p><figure class="highlight css"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br><span class="line">252</span><br><span class="line">253</span><br><span class="line">254</span><br><span class="line">255</span><br><span class="line">256</span><br><span class="line">257</span><br><span class="line">258</span><br><span class="line">259</span><br><span class="line">260</span><br><span class="line">261</span><br><span class="line">262</span><br><span class="line">263</span><br><span class="line">264</span><br><span class="line">265</span><br><span class="line">266</span><br><span class="line">267</span><br><span class="line">268</span><br><span class="line">269</span><br><span class="line">270</span><br><span class="line">271</span><br><span class="line">272</span><br><span class="line">273</span><br><span class="line">274</span><br><span class="line">275</span><br><span class="line">276</span><br><span class="line">277</span><br><span class="line">278</span><br><span class="line">279</span><br><span class="line">280</span><br><span class="line">281</span><br><span class="line">282</span><br><span class="line">283</span><br><span class="line">284</span><br><span class="line">285</span><br><span class="line">286</span><br><span class="line">287</span><br><span class="line">288</span><br><span class="line">289</span><br><span class="line">290</span><br><span class="line">291</span><br><span class="line">292</span><br><span class="line">293</span><br><span class="line">294</span><br><span class="line">295</span><br><span class="line">296</span><br><span class="line">297</span><br><span class="line">298</span><br><span class="line">299</span><br><span class="line">300</span><br><span class="line">301</span><br><span class="line">302</span><br><span class="line">303</span><br><span class="line">304</span><br><span class="line">305</span><br><span class="line">306</span><br><span class="line">307</span><br><span class="line">308</span><br><span class="line">309</span><br><span class="line">310</span><br><span class="line">311</span><br><span class="line">312</span><br><span class="line">313</span><br><span class="line">314</span><br><span class="line">315</span><br><span class="line">316</span><br><span class="line">317</span><br><span class="line">318</span><br><span class="line">319</span><br><span class="line">320</span><br><span class="line">321</span><br><span class="line">322</span><br><span class="line">323</span><br><span class="line">324</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/**</span></span><br><span class="line"><span class="comment"> *  * page-links.css</span></span><br><span class="line"><span class="comment"> *   * 版本：1.0.0</span></span><br><span class="line"><span class="comment"> *    * 描述：友情链接页面专用样式</span></span><br><span class="line"><span class="comment"> *     * 作者：Eucalyptus</span></span><br><span class="line"><span class="comment"> *      * 创建日期：2025-08-30</span></span><br><span class="line"><span class="comment"> *       * 修改记录：</span></span><br><span class="line"><span class="comment"> *        *   - 2025-08-30：首版，含友链卡片、搜索、弹窗</span></span><br><span class="line"><span class="comment"> *         */</span></span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= 1. 页面通用 ========= */</span></span><br><span class="line"><span class="selector-class">.page-links</span>&#123;</span><br><span class="line">  <span class="attribute">max-width</span>:<span class="number">960px</span>;</span><br><span class="line">  <span class="attribute">margin</span>:<span class="number">0</span> auto;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">40px</span> <span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">font-family</span>:-apple-system,BlinkMacSystemFont,<span class="string">&quot;Segoe UI&quot;</span>,Roboto,<span class="string">&quot;Helvetica Neue&quot;</span>,Arial,<span class="string">&quot;Noto Sans&quot;</span>,sans-serif;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ============ 顶部标题（跟随深浅 + 移动端适配） ============ */</span></span><br><span class="line"><span class="comment">/* 友情链接横幅 */</span></span><br><span class="line"><span class="selector-class">.hero-title</span>&#123;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">3.5rem</span> <span class="number">1.5rem</span> <span class="number">2.5rem</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">0</span> <span class="number">0</span> <span class="number">1.5rem</span> <span class="number">1.5rem</span>;</span><br><span class="line">  <span class="attribute">text-align</span>:center;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.hero-title</span> <span class="selector-tag">h1</span>&#123;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">2.2rem</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>:<span class="number">700</span>;</span><br><span class="line">  <span class="attribute">letter-spacing</span>:.<span class="number">5px</span>;</span><br><span class="line">  <span class="attribute">position</span>:relative;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.hero-title</span> <span class="selector-tag">h1</span><span class="selector-pseudo">::after</span>&#123;</span><br><span class="line">  <span class="attribute">content</span>:<span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  <span class="attribute">display</span>:block;</span><br><span class="line">  <span class="attribute">width</span>:<span class="number">60px</span>;</span><br><span class="line">  <span class="attribute">height</span>:<span class="number">3px</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="number">#667eea</span>;</span><br><span class="line">  <span class="attribute">margin</span>:<span class="number">8px</span> auto <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">2px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.hero-sub</span>&#123;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">1rem</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#666</span>;</span><br><span class="line">  <span class="attribute">margin-top</span>:.<span class="number">75rem</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= 玻璃态卡片 3.0 ========= */</span></span><br><span class="line"><span class="selector-class">.links</span>&#123;</span><br><span class="line">  <span class="attribute">display</span>:grid;</span><br><span class="line">  <span class="attribute">grid-template-columns</span>:<span class="built_in">repeat</span>(<span class="number">3</span>, <span class="number">1</span>fr); <span class="comment">/* 固定 3 列 */</span></span><br><span class="line">  <span class="attribute">gap</span>:<span class="number">24px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.link-card</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>:relative;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">background</span>:transparent;                <span class="comment">/* 跟随深浅 */</span></span><br><span class="line">  <span class="attribute">border</span>:<span class="number">1px</span> solid <span class="built_in">rgba</span>(<span class="built_in">var</span>(--color-border,<span class="number">0</span> <span class="number">0</span> <span class="number">0</span>),.<span class="number">1</span>);</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">8px</span> <span class="number">32px</span> <span class="built_in">rgba</span>(<span class="number">0</span>,<span class="number">0</span>,<span class="number">0</span>,.<span class="number">08</span>);  <span class="comment">/* 深浅通用阴影 */</span></span><br><span class="line">  <span class="attribute">transition</span>:.<span class="number">4s</span> <span class="built_in">cubic-bezier</span>(.<span class="number">175</span>,.<span class="number">885</span>,.<span class="number">32</span>,<span class="number">1.275</span>);</span><br><span class="line">  <span class="attribute">overflow</span>:hidden;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-pseudo">:root</span>&#123;</span><br><span class="line">  <span class="attr">--color-border</span>: <span class="number">0</span> <span class="number">0</span> <span class="number">0</span>;       <span class="comment">/* 深色模式 */</span></span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-attr">[data-theme=<span class="string">&quot;light&quot;</span>]</span>&#123;</span><br><span class="line">  <span class="attr">--color-border</span>: <span class="number">255</span> <span class="number">255</span> <span class="number">255</span>; <span class="comment">/* 浅色模式 */</span></span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.link-card</span><span class="selector-pseudo">::before</span>&#123;                               <span class="comment">/* 光泽渐变 */</span></span><br><span class="line">  <span class="attribute">content</span>:<span class="string">&#x27;&#x27;</span>;</span><br><span class="line">  <span class="attribute">position</span>:absolute;</span><br><span class="line">  <span class="attribute">inset</span>:<span class="number">0</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="built_in">linear-gradient</span>(<span class="number">135deg</span>,transparent <span class="number">40%</span>,<span class="built_in">rgba</span>(<span class="number">255</span>,<span class="number">255</span>,<span class="number">255</span>,.<span class="number">3</span>));</span><br><span class="line">  <span class="attribute">pointer-events</span>:none;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.link-card</span><span class="selector-pseudo">:hover</span>&#123;</span><br><span class="line">  <span class="attribute">transform</span>:<span class="built_in">translateY</span>(-<span class="number">6px</span>) <span class="built_in">scale</span>(<span class="number">1.02</span>);</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">12px</span> <span class="number">48px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">25</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 头像 */</span></span><br><span class="line"><span class="selector-class">.link-card</span> <span class="selector-tag">img</span>&#123;</span><br><span class="line">  <span class="attribute">width</span>:<span class="number">64px</span>;</span><br><span class="line">  <span class="attribute">height</span>:<span class="number">64px</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">50%</span>;</span><br><span class="line">  <span class="attribute">border</span>:<span class="number">2px</span> solid <span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">4px</span> <span class="number">12px</span> <span class="built_in">rgba</span>(<span class="number">0</span>,<span class="number">0</span>,<span class="number">0</span>,.<span class="number">08</span>);</span><br><span class="line">  <span class="attribute">object-fit</span>:cover;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 文字区 */</span></span><br><span class="line"><span class="selector-class">.link-card</span> <span class="selector-class">.info</span>&#123;</span><br><span class="line">  <span class="attribute">margin-left</span>:<span class="number">16px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.link-card</span> <span class="selector-class">.name</span>&#123;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">18px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>:<span class="number">700</span>;</span><br><span class="line">  <span class="attribute">letter-spacing</span>:.<span class="number">5px</span>;</span><br><span class="line">  <span class="attribute">margin-bottom</span>:<span class="number">6px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.link-card</span> <span class="selector-class">.desc</span>&#123;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">14px</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#555</span>;</span><br><span class="line">  <span class="attribute">line-height</span>:<span class="number">1.5</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 右上角角标（纯 CSS） */</span></span><br><span class="line"><span class="selector-class">.link-card</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>: relative;           <span class="comment">/* 为伪元素定位 */</span></span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.link-card</span><span class="selector-pseudo">::after</span>&#123;</span><br><span class="line">  <span class="attribute">content</span>: <span class="string">&quot;友链&quot;</span>;              <span class="comment">/* 角标文字 */</span></span><br><span class="line">  <span class="attribute">position</span>: absolute;</span><br><span class="line">  <span class="attribute">top</span>: <span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">right</span>: <span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">padding</span>: <span class="number">2px</span> <span class="number">6px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">11px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>: <span class="number">600</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">background</span>: <span class="built_in">linear-gradient</span>(<span class="number">135deg</span>,<span class="number">#ea66d4</span>,<span class="number">#ac5196</span>);</span><br><span class="line">  <span class="attribute">border-radius</span>: <span class="number">4px</span>;</span><br><span class="line">  <span class="attribute">opacity</span>: <span class="number">0</span>;</span><br><span class="line">  <span class="attribute">transition</span>: opacity .<span class="number">3s</span>;</span><br><span class="line">  <span class="attribute">pointer-events</span>: none;         <span class="comment">/* 不影响点击 */</span></span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.link-card</span><span class="selector-pseudo">:hover</span><span class="selector-pseudo">::after</span>&#123;</span><br><span class="line">  <span class="attribute">opacity</span>: <span class="number">1</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ===== 分类标题 3.0 ===== */</span></span><br><span class="line"><span class="selector-class">.link-cat</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>:relative;</span><br><span class="line">  <span class="attribute">margin-bottom</span>:<span class="number">40px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.link-cat</span> <span class="selector-tag">h2</span>&#123;</span><br><span class="line">  <span class="attribute">display</span>:inline-flex;</span><br><span class="line">  <span class="attribute">align-items</span>:center;</span><br><span class="line">  <span class="attribute">gap</span>:<span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">8px</span> <span class="number">18px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">margin-bottom</span>: <span class="number">15px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>:<span class="number">700</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="built_in">linear-gradient</span>(<span class="number">135deg</span>,<span class="number">#667eea</span>,<span class="number">#764ba2</span>);</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">20px</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">4px</span> <span class="number">12px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">25</span>);</span><br><span class="line">  <span class="attribute">letter-spacing</span>:.<span class="number">5px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 分类描述 */</span></span><br><span class="line"><span class="selector-class">.link-cat-desc</span>&#123;</span><br><span class="line">  <span class="attribute">margin</span>: -<span class="number">8px</span> <span class="number">0</span> <span class="number">24px</span> <span class="number">18px</span>;   <span class="comment">/* 负值贴紧标题，左侧与标题文字对齐 */</span></span><br><span class="line">  <span class="attribute">font-size</span>: <span class="number">0.9rem</span>;</span><br><span class="line">  <span class="attribute">color</span>: <span class="number">#555</span>;</span><br><span class="line">  <span class="attribute">letter-spacing</span>: .<span class="number">4px</span>;</span><br><span class="line">  <span class="attribute">line-height</span>: <span class="number">1.5</span>;</span><br><span class="line">  <span class="attribute">max-width</span>: <span class="number">540px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= 移动端适配 ========= */</span></span><br><span class="line"><span class="keyword">@media</span> (<span class="attribute">max-width</span>: <span class="number">768px</span>) &#123;</span><br><span class="line">  <span class="selector-class">.links</span> &#123;</span><br><span class="line">    <span class="attribute">grid-template-columns</span>: <span class="number">1</span>fr; <span class="comment">/* 1 列 */</span></span><br><span class="line">    <span class="attribute">gap</span>: <span class="number">20px</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.link-card</span> &#123;</span><br><span class="line">    <span class="attribute">padding</span>: <span class="number">16px</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.link-card</span> <span class="selector-tag">img</span> &#123;</span><br><span class="line">    <span class="attribute">width</span>: <span class="number">48px</span>;</span><br><span class="line">    <span class="attribute">height</span>: <span class="number">48px</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.link-card</span> <span class="selector-class">.name</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">16px</span>;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="selector-class">.link-card</span> <span class="selector-class">.desc</span> &#123;</span><br><span class="line">    <span class="attribute">font-size</span>: <span class="number">13px</span>;</span><br><span class="line">  &#125;</span><br><span class="line">&#125;</span><br><span class="line"><span class="comment">/* ========= 4. 搜索框 ========= */</span></span><br><span class="line"><span class="selector-class">.link-search</span>&#123;</span><br><span class="line">  <span class="attribute">display</span>:flex;</span><br><span class="line">  <span class="attribute">margin-bottom</span>:<span class="number">40px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="selector-class">.link-search</span> <span class="selector-tag">input</span>&#123;</span><br><span class="line">  <span class="attribute">width</span>:<span class="number">100%</span>;</span><br><span class="line">  <span class="attribute">max-width</span>:<span class="number">320px</span>;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">12px</span> <span class="number">40px</span> <span class="number">12px</span> <span class="number">16px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">15px</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#333</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">border</span>:<span class="number">2px</span> solid transparent;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">30px</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">4px</span> <span class="number">12px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">15</span>);</span><br><span class="line">  <span class="attribute">transition</span>:border-color .<span class="number">3s</span>, box-shadow .<span class="number">3s</span>;</span><br><span class="line">  <span class="attribute">outline</span>:none;</span><br><span class="line">  <span class="attribute">background-image</span>:<span class="built_in">url</span>(<span class="string">&#x27;data:image/svg+xml;utf8,&lt;svg xmlns=&quot;http://www.w3.org/2000/svg&quot; width=&quot;20&quot; height=&quot;20&quot; viewBox=&quot;0 0 24 24&quot; fill=&quot;none&quot; stroke=&quot;%23667eea&quot; stroke-width=&quot;2&quot; stroke-linecap=&quot;round&quot; stroke-linejoin=&quot;round&quot;&gt;&lt;circle cx=&quot;11&quot; cy=&quot;11&quot; r=&quot;8&quot;&gt;&lt;/circle&gt;&lt;line x1=&quot;21&quot; y1=&quot;21&quot; x2=&quot;16.65&quot; y2=&quot;16.65&quot;&gt;&lt;/line&gt;&lt;/svg&gt;&#x27;</span>);</span><br><span class="line">  <span class="attribute">background-repeat</span>:no-repeat;</span><br><span class="line">  <span class="attribute">background-position</span><span class="selector-pseudo">:right</span> <span class="number">14px</span> center;</span><br><span class="line">  <span class="attribute">background-size</span>:<span class="number">20px</span> <span class="number">20px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 悬浮/聚焦高亮 */</span></span><br><span class="line"><span class="selector-class">.link-search</span> <span class="selector-tag">input</span><span class="selector-pseudo">:focus</span>&#123;</span><br><span class="line">  <span class="attribute">border-color</span>:<span class="number">#667eea</span>;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">0</span> <span class="number">0</span> <span class="number">4px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">25</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* placeholder 样式 */</span></span><br><span class="line"><span class="selector-class">.link-search</span> <span class="selector-tag">input</span><span class="selector-pseudo">::placeholder</span>&#123;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#7f8c8d</span>;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">14px</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= 5. 按钮 &amp; 弹窗 ========= */</span></span><br><span class="line"><span class="comment">/* 5.1 触发按钮居中容器 */</span></span><br><span class="line"><span class="selector-class">.btn-center</span>&#123;</span><br><span class="line">  <span class="attribute">display</span>:flex;</span><br><span class="line">  <span class="attribute">justify-content</span>:center;</span><br><span class="line">  <span class="attribute">margin</span>:<span class="number">30px</span> <span class="number">0</span>;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 5.2 主按钮样式 */</span></span><br><span class="line"><span class="selector-class">.btn-hero</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>:relative;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">12px</span> <span class="number">32px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">16px</span>;</span><br><span class="line">  <span class="attribute">font-weight</span>:<span class="number">600</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="built_in">linear-gradient</span>(<span class="number">135deg</span>,<span class="number">#667eea</span> <span class="number">0%</span>, <span class="number">#764ba2</span> <span class="number">100%</span>);</span><br><span class="line">  <span class="attribute">border</span>:none;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">30px</span>;</span><br><span class="line">  <span class="attribute">cursor</span>:pointer;</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">6px</span> <span class="number">20px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">4</span>);</span><br><span class="line">  <span class="attribute">transition</span>:all .<span class="number">3s</span>;</span><br><span class="line">  <span class="attribute">overflow</span>:hidden;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.btn-hero</span><span class="selector-pseudo">:hover</span>&#123;</span><br><span class="line">  <span class="attribute">transform</span>:<span class="built_in">translateY</span>(-<span class="number">3px</span>) <span class="built_in">scale</span>(<span class="number">1.03</span>);</span><br><span class="line">  <span class="attribute">box-shadow</span>:<span class="number">0</span> <span class="number">10px</span> <span class="number">30px</span> <span class="built_in">rgba</span>(<span class="number">102</span>,<span class="number">126</span>,<span class="number">234</span>,.<span class="number">55</span>);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 5.3 弹窗遮罩 */</span></span><br><span class="line"><span class="selector-class">.modal-fade</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>:fixed;</span><br><span class="line">  <span class="attribute">inset</span>:<span class="number">0</span>;</span><br><span class="line">  <span class="attribute">display</span>:flex;</span><br><span class="line">  <span class="attribute">align-items</span>:center;</span><br><span class="line">  <span class="attribute">justify-content</span>:center;</span><br><span class="line">  <span class="attribute">background</span>:<span class="built_in">rgba</span>(<span class="number">0</span>,<span class="number">0</span>,<span class="number">0</span>,.<span class="number">55</span>);</span><br><span class="line">  <span class="attribute">backdrop-filter</span>:<span class="built_in">blur</span>(<span class="number">4px</span>);</span><br><span class="line">  <span class="attribute">opacity</span>:<span class="number">0</span>;</span><br><span class="line">  <span class="attribute">visibility</span>:hidden;</span><br><span class="line">  <span class="attribute">transition</span>:.<span class="number">35s</span>;</span><br><span class="line">  <span class="attribute">z-index</span>:<span class="number">9999</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.modal-fade</span><span class="selector-class">.show</span>&#123;</span><br><span class="line">  <span class="attribute">opacity</span>:<span class="number">1</span>;</span><br><span class="line">  <span class="attribute">visibility</span>:visible;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 5.4 弹窗主体 */</span></span><br><span class="line"><span class="selector-class">.modal-dialog</span>&#123;</span><br><span class="line">  <span class="attribute">width</span>:<span class="number">92%</span>;</span><br><span class="line">  <span class="attribute">max-width</span>:<span class="number">420px</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">16px</span>;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">32px</span> <span class="number">36px</span> <span class="number">36px</span>;</span><br><span class="line">  <span class="attribute">position</span>:relative;</span><br><span class="line">  <span class="attribute">transform</span>:<span class="built_in">translateY</span>(-<span class="number">30px</span>) <span class="built_in">scale</span>(.<span class="number">95</span>);</span><br><span class="line">  <span class="attribute">transition</span>:transform .<span class="number">35s</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.modal-fade</span><span class="selector-class">.show</span> <span class="selector-class">.modal-dialog</span>&#123;</span><br><span class="line">  <span class="attribute">transform</span>:none;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 5.5 关闭按钮 */</span></span><br><span class="line"><span class="selector-class">.modal-close</span>&#123;</span><br><span class="line">  <span class="attribute">position</span>:absolute;</span><br><span class="line">  <span class="attribute">top</span>:<span class="number">14px</span>;</span><br><span class="line">  <span class="attribute">right</span>:<span class="number">18px</span>;</span><br><span class="line">  <span class="attribute">font-size</span>:<span class="number">26px</span>;</span><br><span class="line">  <span class="attribute">background</span>:none;</span><br><span class="line">  <span class="attribute">border</span>:none;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#999</span>;</span><br><span class="line">  <span class="attribute">cursor</span>:pointer;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 5.6 表单元素 */</span></span><br><span class="line"><span class="selector-class">.modal-form</span>&#123;</span><br><span class="line">  <span class="attribute">display</span>:flex;</span><br><span class="line">  <span class="attribute">flex-direction</span>:column;</span><br><span class="line">  <span class="attribute">gap</span>:<span class="number">14px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.modal-form</span> <span class="selector-tag">input</span>,</span><br><span class="line"><span class="selector-class">.modal-form</span> <span class="selector-tag">textarea</span>&#123;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">12px</span> <span class="number">14px</span>;</span><br><span class="line">  <span class="attribute">border</span>:<span class="number">1px</span> solid <span class="number">#e1e5e9</span>;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">8px</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="selector-class">.btn-submit</span>&#123;</span><br><span class="line">  <span class="attribute">margin-top</span>:<span class="number">8px</span>;</span><br><span class="line">  <span class="attribute">padding</span>:<span class="number">12px</span>;</span><br><span class="line">  <span class="attribute">color</span>:<span class="number">#fff</span>;</span><br><span class="line">  <span class="attribute">border</span>:none;</span><br><span class="line">  <span class="attribute">border-radius</span>:<span class="number">30px</span>;</span><br><span class="line">  <span class="attribute">background</span>:<span class="built_in">linear-gradient</span>(<span class="number">135deg</span>,<span class="number">#667eea</span> <span class="number">0%</span>,<span class="number">#764ba2</span> <span class="number">100%</span>);</span><br><span class="line">  <span class="attribute">cursor</span>:pointer;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 移动端补丁，溢出锁死 */</span></span><br><span class="line"><span class="selector-class">.page-links</span>&#123;</span><br><span class="line">  <span class="attribute">overflow-x</span>: hidden;   <span class="comment">/* 关键：禁止横向滚动 */</span></span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>以下是JavaScript代码，主要用来实现前端友链页面的实时搜索功能、友链提交弹窗（使用模态框组件展示表单，包含必填字段验证和样式反馈）以及后端提交申请内容到后端的功能</p><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/* ========= 实时搜索 ========= */</span></span><br><span class="line"><span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;link-search&#x27;</span>).<span class="title function_">addEventListener</span>(<span class="string">&#x27;input&#x27;</span>, <span class="keyword">function</span> (<span class="params"></span>) &#123;</span><br><span class="line">  <span class="keyword">const</span> kw = <span class="variable language_">this</span>.<span class="property">value</span>.<span class="title function_">toLowerCase</span>();</span><br><span class="line">  <span class="variable language_">document</span>.<span class="title function_">querySelectorAll</span>(<span class="string">&#x27;.link-card&#x27;</span>).<span class="title function_">forEach</span>(<span class="function"><span class="params">card</span> =&gt;</span> &#123;</span><br><span class="line">    card.<span class="property">style</span>.<span class="property">display</span> = card.<span class="property">textContent</span>.<span class="title function_">toLowerCase</span>().<span class="title function_">includes</span>(kw) ? <span class="string">&#x27;flex&#x27;</span> : <span class="string">&#x27;none&#x27;</span>;</span><br><span class="line">  &#125;);</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= 弹窗控制 ========= */</span></span><br><span class="line"><span class="keyword">const</span> overlay = <span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;link-modal-overlay&#x27;</span>);</span><br><span class="line"><span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;open-link-modal&#x27;</span>).<span class="title function_">addEventListener</span>(<span class="string">&#x27;click&#x27;</span>, <span class="function">() =&gt;</span> overlay.<span class="property">classList</span>.<span class="title function_">add</span>(<span class="string">&#x27;show&#x27;</span>));</span><br><span class="line">overlay.<span class="title function_">addEventListener</span>(<span class="string">&#x27;click&#x27;</span>, <span class="function"><span class="params">e</span> =&gt;</span> &#123;</span><br><span class="line">  <span class="keyword">if</span> (e.<span class="property">target</span> === overlay || e.<span class="property">target</span>.<span class="property">classList</span>.<span class="title function_">contains</span>(<span class="string">&#x27;modal-close&#x27;</span>)) overlay.<span class="property">classList</span>.<span class="title function_">remove</span>(<span class="string">&#x27;show&#x27;</span>);</span><br><span class="line">&#125;);</span><br><span class="line"></span><br><span class="line"><span class="comment">/* ========= Ajax 提交友链 ========= */</span></span><br><span class="line"><span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;link-form&#x27;</span>).<span class="title function_">addEventListener</span>(<span class="string">&#x27;submit&#x27;</span>, <span class="keyword">function</span> (<span class="params">e</span>) &#123;</span><br><span class="line">  e.<span class="title function_">preventDefault</span>();</span><br><span class="line">  <span class="keyword">const</span> data = <span class="keyword">new</span> <span class="title class_">FormData</span>(<span class="variable language_">this</span>);</span><br><span class="line">  data.<span class="title function_">append</span>(<span class="string">&#x27;action&#x27;</span>, <span class="string">&#x27;submit_link_apply&#x27;</span>);</span><br><span class="line">  <span class="title function_">fetch</span>(ajax_comment_obj.<span class="property">ajax_url</span>, &#123; <span class="attr">method</span>: <span class="string">&#x27;POST&#x27;</span>, <span class="attr">body</span>: data &#125;)</span><br><span class="line">    .<span class="title function_">then</span>(<span class="function"><span class="params">r</span> =&gt;</span> r.<span class="title function_">json</span>())</span><br><span class="line">    .<span class="title function_">then</span>(<span class="function"><span class="params">res</span> =&gt;</span> &#123;</span><br><span class="line">      <span class="variable language_">document</span>.<span class="title function_">getElementById</span>(<span class="string">&#x27;form-msg&#x27;</span>).<span class="property">textContent</span> = res.<span class="property">data</span>;</span><br><span class="line">      <span class="keyword">if</span> (res.<span class="property">success</span>) &#123;</span><br><span class="line">        <span class="variable language_">this</span>.<span class="title function_">reset</span>();</span><br><span class="line">        <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> overlay.<span class="property">classList</span>.<span class="title function_">remove</span>(<span class="string">&#x27;show&#x27;</span>), <span class="number">1500</span>);</span><br><span class="line">      &#125;</span><br><span class="line">    &#125;);</span><br><span class="line">&#125;);</span><br></pre></td></tr></table></figure><p>最后是后端处理前端请求并为link_manager新增待审核列的代码，审核逻辑基于链接是否在前端隐藏， 关闭私密功能即可前端展示</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-08-31/1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-08-31/2.avif"></p><figure class="highlight php"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;?php</span></span><br><span class="line"><span class="comment">/**</span></span><br><span class="line"><span class="comment"> * 待审核友链提示</span></span><br><span class="line"><span class="comment"> * 包含：后台列表新增“待审核”列 + 红色气泡菜单提示 + Ajax 接收</span></span><br><span class="line"><span class="comment"> */</span></span><br><span class="line"></span><br><span class="line"><span class="comment">/* --------------------------------------------------</span></span><br><span class="line"><span class="comment"> * 1. 后台列表新增“待审核”列，纯文本，系统默认样式</span></span><br><span class="line"><span class="comment"> * -------------------------------------------------- */</span></span><br><span class="line"><span class="comment">/* 新增“待审核”列（键名 review） */</span></span><br><span class="line"><span class="title function_ invoke__">add_filter</span>( <span class="string">&#x27;manage_link-manager_columns&#x27;</span>, function ( <span class="variable">$cols</span> ) &#123;</span><br><span class="line">    <span class="variable">$cols</span>[<span class="string">&#x27;review&#x27;</span>] = <span class="string">&#x27;待审核&#x27;</span>;</span><br><span class="line">    <span class="keyword">return</span> <span class="variable">$cols</span>;</span><br><span class="line">&#125; );</span><br><span class="line"></span><br><span class="line"><span class="comment">/* 单元格输出红色气泡 */</span></span><br><span class="line"><span class="title function_ invoke__">add_action</span>( <span class="string">&#x27;manage_link_custom_column&#x27;</span>, function ( <span class="variable">$col</span>, <span class="variable">$link_id</span> ) &#123;</span><br><span class="line">    <span class="keyword">if</span> ( <span class="variable">$col</span> === <span class="string">&#x27;review&#x27;</span> ) &#123;</span><br><span class="line">        <span class="keyword">echo</span> <span class="title function_ invoke__">get_bookmark_field</span>( <span class="string">&#x27;link_visible&#x27;</span>, <span class="variable">$link_id</span> ) === <span class="string">&#x27;N&#x27;</span></span><br><span class="line">            ? <span class="string">&#x27;&lt;span style=&quot;display:inline-block;background:#e60026;color:#fff;font-size:11px;padding:2px 6px;border-radius:10px;margin-left:4px;&quot;&gt;待审&lt;/span&gt;&#x27;</span></span><br><span class="line">            : <span class="string">&#x27;&#x27;</span>;</span><br><span class="line">    &#125;</span><br><span class="line">&#125;, <span class="number">10</span>, <span class="number">2</span> );</span><br><span class="line"></span><br><span class="line"></span><br><span class="line"><span class="comment">/* --------------------------------------------------</span></span><br><span class="line"><span class="comment"> * 2. 后台“链接”菜单右上角红色数字气泡</span></span><br><span class="line"><span class="comment"> * -------------------------------------------------- */</span></span><br><span class="line"><span class="title function_ invoke__">add_action</span>( <span class="string">&#x27;admin_menu&#x27;</span>, function () &#123;</span><br><span class="line">    <span class="variable">$count</span> = <span class="number">0</span>;</span><br><span class="line">    <span class="keyword">foreach</span> ( <span class="title function_ invoke__">get_bookmarks</span>( [ <span class="string">&#x27;hide_invisible&#x27;</span> =&gt; <span class="number">0</span> ] ) <span class="keyword">as</span> <span class="variable">$link</span> ) &#123;</span><br><span class="line">        <span class="keyword">if</span> ( <span class="variable">$link</span>-&gt;link_visible === <span class="string">&#x27;N&#x27;</span> ) <span class="variable">$count</span>++;</span><br><span class="line">    &#125;</span><br><span class="line">    <span class="keyword">if</span> ( <span class="variable">$count</span> ) &#123;</span><br><span class="line">        <span class="keyword">global</span> <span class="variable">$menu</span>;</span><br><span class="line">        <span class="keyword">foreach</span> ( <span class="variable">$menu</span> <span class="keyword">as</span> &amp;<span class="variable">$item</span> ) &#123;</span><br><span class="line">            <span class="keyword">if</span> ( <span class="variable">$item</span>[<span class="number">2</span>] === <span class="string">&#x27;link-manager.php&#x27;</span> ) &#123;</span><br><span class="line">                <span class="variable">$item</span>[<span class="number">0</span>] .= <span class="string">&#x27; &lt;span class=&quot;awaiting-mod&quot;&gt;&lt;span class=&quot;pending-count&quot;&gt;&#x27;</span> . <span class="variable">$count</span> . <span class="string">&#x27;&lt;/span&gt;&lt;/span&gt;&#x27;</span>;</span><br><span class="line">                <span class="keyword">break</span>;</span><br><span class="line">            &#125;</span><br><span class="line">        &#125;</span><br><span class="line">    &#125;</span><br><span class="line">&#125; );</span><br><span class="line"></span><br><span class="line"><span class="comment">/* --------------------------------------------------</span></span><br><span class="line"><span class="comment"> * 3. Ajax 接收端（无邮件）</span></span><br><span class="line"><span class="comment"> * -------------------------------------------------- */</span></span><br><span class="line"><span class="title function_ invoke__">add_action</span>( <span class="string">&#x27;wp_ajax_nopriv_submit_link_apply&#x27;</span>, <span class="string">&#x27;handle_link_apply&#x27;</span> );</span><br><span class="line"><span class="title function_ invoke__">add_action</span>( <span class="string">&#x27;wp_ajax_submit_link_apply&#x27;</span>,        <span class="string">&#x27;handle_link_apply&#x27;</span> );</span><br><span class="line"><span class="function"><span class="keyword">function</span> <span class="title">handle_link_apply</span>(<span class="params"></span>) </span>&#123;</span><br><span class="line">    <span class="variable">$name</span>  = <span class="title function_ invoke__">sanitize_text_field</span>( <span class="variable">$_POST</span>[<span class="string">&#x27;link_name&#x27;</span>] ?? <span class="string">&#x27;&#x27;</span> );</span><br><span class="line">    <span class="variable">$url</span>   = <span class="title function_ invoke__">esc_url_raw</span>        ( <span class="variable">$_POST</span>[<span class="string">&#x27;link_url&#x27;</span>]  ?? <span class="string">&#x27;&#x27;</span> );</span><br><span class="line">    <span class="variable">$email</span> = <span class="title function_ invoke__">sanitize_email</span>      ( <span class="variable">$_POST</span>[<span class="string">&#x27;link_owner_email&#x27;</span>] ?? <span class="string">&#x27;&#x27;</span> );</span><br><span class="line">    <span class="variable">$desc</span>  = <span class="title function_ invoke__">sanitize_text_field</span>( <span class="variable">$_POST</span>[<span class="string">&#x27;link_description&#x27;</span>] ?? <span class="string">&#x27;&#x27;</span> );</span><br><span class="line">    <span class="variable">$img</span>   = <span class="title function_ invoke__">esc_url_raw</span>        ( <span class="variable">$_POST</span>[<span class="string">&#x27;link_image&#x27;</span>]       ?? <span class="string">&#x27;&#x27;</span> );</span><br><span class="line"></span><br><span class="line">    <span class="keyword">if</span> ( <span class="keyword">empty</span>( <span class="variable">$name</span> ) || <span class="keyword">empty</span>( <span class="variable">$url</span> ) || ! <span class="title function_ invoke__">is_email</span>( <span class="variable">$email</span> ) ) &#123;</span><br><span class="line">        <span class="title function_ invoke__">wp_send_json_error</span>( <span class="string">&#x27;请完整填写必填项&#x27;</span> );</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    <span class="title function_ invoke__">wp_insert_link</span>( [</span><br><span class="line">        <span class="string">&#x27;link_name&#x27;</span>        =&gt; <span class="variable">$name</span>,</span><br><span class="line">        <span class="string">&#x27;link_url&#x27;</span>         =&gt; <span class="variable">$url</span>,</span><br><span class="line">        <span class="string">&#x27;link_description&#x27;</span> =&gt; <span class="variable">$desc</span>,</span><br><span class="line">        <span class="string">&#x27;link_image&#x27;</span>       =&gt; <span class="variable">$img</span>,</span><br><span class="line">        <span class="string">&#x27;link_owner_email&#x27;</span> =&gt; <span class="variable">$email</span>,</span><br><span class="line">        <span class="string">&#x27;link_visible&#x27;</span>     =&gt; <span class="string">&#x27;N&#x27;</span>,</span><br><span class="line">    ] );</span><br><span class="line"></span><br><span class="line">    <span class="title function_ invoke__">wp_send_json_success</span>( <span class="string">&#x27;已收到申请，审核后显示，感谢！&#x27;</span> );</span><br><span class="line">&#125;</span><br></pre></td></tr></table></figure><p>上传代码至Meteor主题目录完成部署，最后在functions.php中启用link_manager并调用pending-links.php处理后台任务。</p><p>WordPress的functions.php文件中添加指定代码可实现特定功能，需注意代码正确性和备份以防出错。</p><figure class="highlight php"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">/* 开启后台链接 */</span></span><br><span class="line"><span class="title function_ invoke__">add_filter</span>( <span class="string">&#x27;pre_option_link_manager_enabled&#x27;</span>, <span class="string">&#x27;__return_true&#x27;</span> );</span><br><span class="line"></span><br><span class="line"> <span class="comment">/* 后台新增友链提示功能 */</span></span><br><span class="line"><span class="keyword">require_once</span> <span class="title function_ invoke__">get_theme_file_path</span>( <span class="string">&#x27;/self-innovate/pending-links.php&#x27;</span> );</span><br></pre></td></tr></table></figure><blockquote><p>展示地址：<a href="https://img.eucalyptus.cc/%e5%8f%8b%e9%93%be/">https://img.eucalyptus.cc/%e5%8f%8b%e9%93%be/</a></p></blockquote>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/Meteor/">Meteor</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/08/31/d915d040/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0.14 双密码机制</title>
      <link>https://blog.eucalyptus.cc/2025/08/15/0bf3650b/</link>
      <guid>https://blog.eucalyptus.cc/2025/08/15/0bf3650b/</guid>
      <pubDate>Fri, 15 Aug 2025 06:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;MySQL 8.0</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>MySQL 8.0 引入了双密码策略,这是一种增强安全性的机制。双密码策略允许为每个用户设置两个密码:主密码和次级密码。主密码用于日常操作数据库,而次级密码则用于紧急情况下的访问,有效防止了密码泄露和未授权访问。</p><p>双密码机制使得大规模数据库密码轮换变得更平滑,而无需任何的停机时间。在 MySQL 8.0.14 版本之前,更换密码通常会遇到服务不可用时间的问题。而从*** MySQL 8.0.14*** 起,开始支持了双密码策略。在密码更换时,可以保留旧密码依旧可用。</p><p>在更改密码时,首先通过 RETAIN CURRENT PASSWORD 子句设置新的主密码,并保留当前密码作为辅助密码。此时,客户端可以继续使用旧密码 辅助密码 连接数据库,同时新密码 主密码 也已经生效。当新密码已经在所有服务器上同步,且所有应用程序也更新为使用新密码时,可以使用 DISCARD OLD PASSWORD 子句来丢弃辅助密码 原密码 ,使得数据库仅接受主密码 新密码 。</p><p>这种机制特别适用于复杂的系统,尤其是涉及大量 MySQL 实例、复制、多个应用程序连接以及频繁的密码更新时,能够保持服务不中断,从而实现更流畅的密码更改流程。</p><h3 id="语法"><a href="#语法" class="headerlink" title="语法"></a>语法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">#创建<span class="string">&#x27;demo7&#x27;</span> <span class="string">&#x27;%&#x27;</span>用户设置密码<span class="number">123456</span></span><br><span class="line"><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;demo7&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;123456&#x27;</span>;</span><br><span class="line">#更新<span class="string">&#x27;demo7&#x27;</span> <span class="string">&#x27;%&#x27;</span>的密码为<span class="number">1234567</span>并保留旧密码<span class="number">123456</span></span><br><span class="line"><span class="keyword">ALTER</span> <span class="keyword">USER</span> <span class="string">&#x27;demo7&#x27;</span> <span class="string">&#x27;%&#x27;</span> IDENTIFIED <span class="keyword">BY</span> <span class="string">&#x27;1234567&#x27;</span> RETAIN <span class="keyword">CURRENT</span> PASSWORD;</span><br><span class="line">#丢弃旧密码</span><br><span class="line"><span class="keyword">alter</span> <span class="keyword">user</span> <span class="string">&#x27;demo7&#x27;</span> <span class="string">&#x27;%&#x27;</span> DISCARD <span class="keyword">OLD</span> PASSWORD;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img4.avif"></p><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><p><em><strong>MySQL 8.0.14</strong></em> 起,开始支持了双密码策略,之前并不支持</p><p>8.0.13</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img5.avif"></p><p>8.0.14</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-15/img6.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/08/15/0bf3650b/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL内置数据库】performance_schema</title>
      <link>https://blog.eucalyptus.cc/2025/08/05/767eb1d9/</link>
      <guid>https://blog.eucalyptus.cc/2025/08/05/767eb1d9/</guid>
      <pubDate>Tue, 05 Aug 2025 08:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;MySQL8.0.37 performance_schema下共有111张表&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img1.avif&quot;&gt;&lt;/p&gt;
&lt;p&gt;官方文档:&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>MySQL8.0.37 performance_schema下共有111张表</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img1.avif"></p><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.0/en/performance-schema.html">https://dev.mysql.com/doc/refman/8.0/en/performance-schema.html</a></p><h3 id="统计"><a href="#统计" class="headerlink" title="统计"></a>统计</h3><table><thead><tr><th>序号</th><th>表名</th></tr></thead><tbody><tr><td>1</td><td>accounts</td></tr><tr><td>2</td><td>binary_log_transaction_compression_stats</td></tr><tr><td>3</td><td>cond_instances</td></tr><tr><td>4</td><td>data_lock_waits</td></tr><tr><td>5</td><td>data_locks</td></tr><tr><td>6</td><td>error_log</td></tr><tr><td>7</td><td>events_errors_summary_by_account_by_error</td></tr><tr><td>8</td><td>events_errors_summary_by_host_by_error</td></tr><tr><td>9</td><td>events_errors_summary_by_thread_by_error</td></tr><tr><td>10</td><td>events_errors_summary_by_user_by_error</td></tr><tr><td>11</td><td>events_errors_summary_global_by_error</td></tr><tr><td>12</td><td>events_stages_current</td></tr><tr><td>13</td><td>events_stages_history</td></tr><tr><td>14</td><td>events_stages_history_long</td></tr><tr><td>15</td><td>events_stages_summary_by_account_by_event_name</td></tr><tr><td>16</td><td>events_stages_summary_by_host_by_event_name</td></tr><tr><td>17</td><td>events_stages_summary_by_thread_by_event_name</td></tr><tr><td>18</td><td>events_stages_summary_by_user_by_event_name</td></tr><tr><td>19</td><td>events_stages_summary_global_by_event_name</td></tr><tr><td>20</td><td>events_statements_current</td></tr><tr><td>21</td><td>events_statements_histogram_by_digest</td></tr><tr><td>22</td><td>events_statements_histogram_global</td></tr><tr><td>23</td><td>events_statements_history</td></tr><tr><td>24</td><td>events_statements_history_long</td></tr><tr><td>25</td><td>events_statements_summary_by_account_by_event_name</td></tr><tr><td>26</td><td>events_statements_summary_by_digest</td></tr><tr><td>27</td><td>events_statements_summary_by_host_by_event_name</td></tr><tr><td>28</td><td>events_statements_summary_by_program</td></tr><tr><td>29</td><td>events_statements_summary_by_thread_by_event_name</td></tr><tr><td>30</td><td>events_statements_summary_by_user_by_event_name</td></tr><tr><td>31</td><td>events_statements_summary_global_by_event_name</td></tr><tr><td>32</td><td>events_transactions_current</td></tr><tr><td>33</td><td>events_transactions_history</td></tr><tr><td>34</td><td>events_transactions_history_long</td></tr><tr><td>35</td><td>events_transactions_summary_by_account_by_event_name</td></tr><tr><td>36</td><td>events_transactions_summary_by_host_by_event_name</td></tr><tr><td>37</td><td>events_transactions_summary_by_thread_by_event_name</td></tr><tr><td>38</td><td>events_transactions_summary_by_user_by_event_name</td></tr><tr><td>39</td><td>events_transactions_summary_global_by_event_name</td></tr><tr><td>40</td><td>events_waits_current</td></tr><tr><td>41</td><td>events_waits_history</td></tr><tr><td>42</td><td>events_waits_history_long</td></tr><tr><td>43</td><td>events_waits_summary_by_account_by_event_name</td></tr><tr><td>44</td><td>events_waits_summary_by_host_by_event_name</td></tr><tr><td>45</td><td>events_waits_summary_by_instance</td></tr><tr><td>46</td><td>events_waits_summary_by_thread_by_event_name</td></tr><tr><td>47</td><td>events_waits_summary_by_user_by_event_name</td></tr><tr><td>48</td><td>events_waits_summary_global_by_event_name</td></tr><tr><td>49</td><td>file_instances</td></tr><tr><td>50</td><td>file_summary_by_event_name</td></tr><tr><td>51</td><td>file_summary_by_instance</td></tr><tr><td>52</td><td>global_status</td></tr><tr><td>53</td><td>global_variables</td></tr><tr><td>54</td><td>host_cache</td></tr><tr><td>55</td><td>hosts</td></tr><tr><td>56</td><td>innodb_redo_log_files</td></tr><tr><td>57</td><td>keyring_component_status</td></tr><tr><td>58</td><td>keyring_keys</td></tr><tr><td>59</td><td>log_status</td></tr><tr><td>60</td><td>memory_summary_by_account_by_event_name</td></tr><tr><td>61</td><td>memory_summary_by_host_by_event_name</td></tr><tr><td>62</td><td>memory_summary_by_thread_by_event_name</td></tr><tr><td>63</td><td>memory_summary_by_user_by_event_name</td></tr><tr><td>64</td><td>memory_summary_global_by_event_name</td></tr><tr><td>65</td><td>metadata_locks</td></tr><tr><td>66</td><td>mutex_instances</td></tr><tr><td>67</td><td>objects_summary_global_by_type</td></tr><tr><td>68</td><td>performance_timers</td></tr><tr><td>69</td><td>persisted_variables</td></tr><tr><td>70</td><td>prepared_statements_instances</td></tr><tr><td>71</td><td>processlist</td></tr><tr><td>72</td><td>replication_applier_configuration</td></tr><tr><td>73</td><td>replication_applier_filters</td></tr><tr><td>74</td><td>replication_applier_global_filters</td></tr><tr><td>75</td><td>replication_applier_status</td></tr><tr><td>76</td><td>replication_applier_status_by_coordinator</td></tr><tr><td>77</td><td>replication_applier_status_by_worker</td></tr><tr><td>78</td><td>replication_asynchronous_connection_failover</td></tr><tr><td>79</td><td>replication_asynchronous_connection_failover_managed</td></tr><tr><td>80</td><td>replication_connection_configuration</td></tr><tr><td>81</td><td>replication_connection_status</td></tr><tr><td>82</td><td>replication_group_member_stats</td></tr><tr><td>83</td><td>replication_group_members</td></tr><tr><td>84</td><td>rwlock_instances</td></tr><tr><td>85</td><td>session_account_connect_attrs</td></tr><tr><td>86</td><td>session_connect_attrs</td></tr><tr><td>87</td><td>session_status</td></tr><tr><td>88</td><td>session_variables</td></tr><tr><td>89</td><td>setup_actors</td></tr><tr><td>90</td><td>setup_consumers</td></tr><tr><td>91</td><td>setup_instruments</td></tr><tr><td>92</td><td>setup_objects</td></tr><tr><td>93</td><td>setup_threads</td></tr><tr><td>94</td><td>socket_instances</td></tr><tr><td>95</td><td>socket_summary_by_event_name</td></tr><tr><td>96</td><td>socket_summary_by_instance</td></tr><tr><td>97</td><td>status_by_account</td></tr><tr><td>98</td><td>status_by_host</td></tr><tr><td>99</td><td>status_by_thread</td></tr><tr><td>100</td><td>status_by_user</td></tr><tr><td>101</td><td>table_handles</td></tr><tr><td>102</td><td>table_io_waits_summary_by_index_usage</td></tr><tr><td>103</td><td>table_io_waits_summary_by_table</td></tr><tr><td>104</td><td>table_lock_waits_summary_by_table</td></tr><tr><td>105</td><td>threads</td></tr><tr><td>106</td><td>tls_channel_status</td></tr><tr><td>107</td><td>user_defined_functions</td></tr><tr><td>108</td><td>user_variables_by_thread</td></tr><tr><td>109</td><td>users</td></tr><tr><td>110</td><td>variables_by_thread</td></tr><tr><td>111</td><td>variables_info</td></tr></tbody></table><h3 id="accounts"><a href="#accounts" class="headerlink" title="accounts"></a>accounts</h3><p>这个表是MySQL性能模式中的<code>accounts</code>表,用于存储数据库用户账户的信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 数据库用户名。</li><li><strong>HOST</strong>: 用户连接到数据库的主机名或IP地址。</li><li><strong>CURRENT_CONNECTIONS</strong>: 当前用户会话的数量。</li><li><strong>TOTAL_CONNECTIONS</strong>: 自从服务器启动以来该用户建立的连接总数。</li><li><strong>MAX_SESSION_CONTROLLED_MEMORY</strong>: 为用户会话设置的最大受控内存。</li><li><strong>MAX_SESSION_TOTAL_MEMORY</strong>: 为用户会话设置的最大总内存。</li></ul><p>这些列提供了关于数据库用户账户的连接和内存使用情况的详细信息,有助于监控和管理系统资源。表中还有一个唯一键<code>UNIQUE KEY ACCOUNT (&#39;USER&#39;, &#39;HOST&#39;)</code>,用于确保每个用户和主机的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img2.avif"></p><h3 id="binary-log-transaction-compression-stats"><a href="#binary-log-transaction-compression-stats" class="headerlink" title="binary_log_transaction_compression_stats"></a>binary_log_transaction_compression_stats</h3><p>这个表是MySQL性能模式中的<code>binary_log_transaction_compression_stats</code>表,用于记录二进制日志事务压缩的统计信息。以下是表中每一列的含义:</p><ul><li><strong>LOG_TYPE</strong>: 日志类型,指示事务被写入的日志类型。</li><li><strong>COMPRESSION_TYPE</strong>: 事务压缩使用的算法。</li><li><strong>TRANSACTION_COUNTER</strong>: 写入的事务总数。</li><li><strong>COMPRESSED_BYTES_COUNTER</strong>: 压缩后的总字节数。</li><li><strong>UNCOMPRESSED_BYTES_COUNTER</strong>: 压缩前的总字节数。</li><li><strong>COMPRESSION_PERCENTAGE</strong>: 压缩率,以百分比表示。</li><li><strong>FIRST_TRANSACTION_ID</strong>: 写入的第一个事务的ID。</li><li><strong>FIRST_TRANSACTION_UNCOMPRESSED_BYTES</strong>: 第一个事务压缩前的字节数。</li><li><strong>FIRST_TRANSACTION_TIMESTAMP</strong>: 第一个事务写入的时间戳。</li><li><strong>LAST_TRANSACTION_ID</strong>: 最后一个事务的ID。</li><li><strong>LAST_TRANSACTION_COMPRESSED_BYTES</strong>: 最后一个事务压缩后的字节数。</li><li><strong>LAST_TRANSACTION_UNCOMPRESSED_BYTES</strong>: 最后一个事务压缩前的字节数。</li><li><strong>LAST_TRANSACTION_TIMESTAMP</strong>: 最后一个事务写入的时间戳。</li></ul><p>这些列提供了关于二进制日志事务压缩的详细统计信息,有助于分析压缩效率和性能。表中的数据可以帮助数据库管理员了解压缩对存储和网络带宽的影响。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img3.avif"></p><h3 id="cond-instances"><a href="#cond-instances" class="headerlink" title="cond_instances"></a>cond_instances</h3><p><code>cond_instances</code> 是 MySQL 和 MariaDB 中 <code>performance_schema</code> 数据库的一个表,用于记录服务器执行期间性能模式所看到的所有条件 Condition 。</p><p>表的作用</p><p>条件 Condition 是一种同步机制,用于在代码中信号特定事件的发生,以便等待该条件的线程可以恢复工作。例如,当一个线程等待某个事件发生时,<code>cond_instances</code> 表中的 <code>NAME</code> 列会显示该线程正在等待的条件名称,但无法直接显示是哪个线程触发了该条件。</p><p><code>cond_instances</code> 表包含以下列:</p><ul><li><code>NAME</code>:与条件相关联的仪器 instrument 名称。</li><li><code>OBJECT_INSTANCE_BEGIN</code>:检测条件在内存中的地址。</li></ul><p>该表主要用于性能监控和调试,帮助开发者和 DBA 理解线程等待的条件及其触发机制。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img4.avif"></p><h3 id="data-lock-waits"><a href="#data-lock-waits" class="headerlink" title="data_lock_waits"></a>data_lock_waits</h3><p><code>data_lock_waits</code> 表是 MySQL Performance Schema 中的一个表,用于记录和分析 InnoDB 存储引擎中发生的行锁等待事件。这个表可以帮助你理解哪些事务在等待获取锁,哪些事务持有锁,以及它们之间的等待关系。以下是表中每一列的详细解释:</p><ul><li><strong>REQUESTING_ENGINE_LOCK_ID</strong>: 请求锁的引擎锁ID。标识请求锁的事务的引擎锁ID。</li><li><strong>REQUESTING_ENGINE_TRANSACTION_ID</strong>: 请求锁的事务ID。标识请求锁的事务ID。</li><li><strong>REQUESTING_THREAD_ID</strong>: 请求锁的线程ID。标识请求锁的线程ID。</li><li><strong>REQUESTING_EVENT_ID</strong>: 请求锁的事件ID。标识请求锁的事务中的事件ID。</li><li><strong>BLOCKING_ENGINE_LOCK_ID</strong>: 阻塞请求事务的引擎锁ID。标识阻塞请求事务的引擎锁ID。</li><li><strong>BLOCKING_TRANSACTION_ID</strong>: 阻塞事务的事务ID。标识持有锁的事务ID。</li><li><strong>BLOCKING_THREAD_ID</strong>: 阻塞线程的线程ID。标识持有锁的线程ID。</li><li><strong>BLOCKING_EVENT_ID</strong>: 阻塞事务的事件ID。标识持有锁的事务中的事件ID。</li></ul><p>这些列共同描述了事务之间因锁等待而产生的依赖关系,可以帮助你识别和解决数据库中的锁争用问题。</p><p>例如,如果你发现系统中存在长时间运行的事务,或者某些事务似乎在等待其他事务释放锁,你可以查询 <code>data_lock_waits</code> 表来获取详细信息,了解哪些事务在等待哪些锁,以及哪些事务持有这些锁。这有助于你优化事务处理死锁争用、性能瓶颈等问题。</p><p>在实际使用中,你可以通过以下查询来获取锁等待的详细信息:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line"><span class="number">1</span> <span class="keyword">AS</span> Waiting_thread,</span><br><span class="line"><span class="number">2</span> <span class="keyword">AS</span> Blocking_thread,</span><br><span class="line"><span class="number">3</span> <span class="keyword">AS</span> Waiting_event,</span><br><span class="line"><span class="number">4</span> <span class="keyword">AS</span> Waiting_time</span><br><span class="line"><span class="keyword">FROM</span> data_lock_waits;</span><br></pre></td></tr></table></figure><p>这将返回等待的线程ID、阻塞它的线程ID以及等待时间 秒 。通过这些信息,你可以进一步分析和优化数据库性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img5.avif"></p><h3 id="data-locks"><a href="#data-locks" class="headerlink" title="data_locks"></a>data_locks</h3><p><code>data_locks</code> 表是 MySQL Performance Schema 中的一个表,用于记录 InnoDB 存储引擎中发生的行锁等待事件。以下是表中每一列的含义:</p><ul><li><p><strong>ENGINE</strong>:请求锁的引擎名称 例如 InnoDB 。</p></li><li><p><strong>ENGINE_LOCK_ID</strong>:请求锁的事务的引擎锁ID。</p></li><li><p><strong>ENGINE_TRANSACTION_ID</strong>:请求锁的事务ID。</p></li><li><p><strong>THREAD_ID</strong>:请求锁的线程ID。</p></li><li><p><strong>EVENT_ID</strong>:请求锁的事件ID。</p></li><li><p><strong>OBJECT_SCHEMA</strong>:被锁定对象所在的数据库名称。</p></li><li><p><strong>OBJECT_NAME</strong>:被锁定的对象名称 例如表名 。</p></li><li><p><strong>PARTITION_NAME</strong>:被锁定的对象的分区名称 如果有 。</p></li><li><p><strong>SUBPARTITION_NAME</strong>:被锁定的对象的子分区名称 如果有 。</p></li><li><p><strong>INDEX_NAME</strong>:被锁定的索引名称。</p></li><li><p><strong>OBJECT_INSTANCE_BEGIN</strong>:对象实例开始时间。</p></li><li><p><strong>LOCK_TYPE</strong>:锁类型 例如行锁、表锁等 。</p></li><li><p><strong>LOCK_MODE</strong>:锁模式 例如共享锁、排他锁等 。</p></li><li><p><strong>LOCK_STATUS</strong>:锁状态 例如等待、阻塞等 。</p></li><li><p><strong>LOCK_DATA</strong>:锁相关的数据,以 JSON 格式存储,包含请求事务ID、引擎等信息。</p></li><li><p>查看当前所有锁等待事件:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> data_locks;</span><br></pre></td></tr></table></figure><ul><li>查看特定表的锁等待事件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> data_locks <span class="keyword">WHERE</span> OBJECT_SCHEMA <span class="string">&#x27;your_db&#x27;</span> <span class="keyword">AND</span> OBJECT_NAME <span class="string">&#x27;your_table&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>看特定事务的锁等待事件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> data_locks <span class="keyword">WHERE</span> ENGINE_TRANSACTION_ID your_transaction_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些事务在等待获取锁,哪些事务持有锁,以及它们之间的等待关系。这有助于诊断和解决数据库中的锁争用问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img6.avif"></p><h3 id="error-log"><a href="#error-log" class="headerlink" title="error_log"></a>error_log</h3><p><code>error_log</code> 表是 MySQL Performance Schema 中的一个表,用于记录 MySQL 服务器的错误日志信息。以下是表中每一列的含义:</p><ul><li><p><strong>LOGGED</strong>:记录创建时间戳,表示错误发生的时间。</p></li><li><p><strong>THREAD_ID</strong>:产生错误的线程ID。</p></li><li><p><strong>PRIO</strong>:错误优先级,可以是 <code>System</code>、<code>Error</code>、<code>Warning</code> 或 <code>Note</code>。</p></li><li><p><strong>ERROR_CODE</strong>:错误代码,表示错误的具体代码。</p></li><li><p><strong>SUBSYSTEM</strong>:子系统名称,表示错误的来源系统 如 MySQL 服务器、存储引擎等 。</p></li><li><p><strong>DATA</strong>:错误信息文本,包含错误的详细描述。</p></li><li><p>查看所有错误日志:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> error_log;</span><br></pre></td></tr></table></figure><ul><li>查看特定类型的错误日志 例如,错误 :</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> error_log <span class="keyword">WHERE</span> PRIO <span class="string">&#x27;Error&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的错误日志:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> error_log <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解 MySQL 服务器上发生的错误信息,包括错误发生时间、错误级别、错误代码、错误来源和详细描述。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img7.avif"></p><h3 id="events-errors-summary-by-account-by-error"><a href="#events-errors-summary-by-account-by-error" class="headerlink" title="events_errors_summary_by_account_by_error"></a>events_errors_summary_by_account_by_error</h3><p><code>events_errors_summary_by_account_by_error</code> 表是 MySQL Performance Schema 中的一个表,用于按账户统计错误事件的摘要信息。以下是表中每一列的含义:</p><ul><li><p><strong>USER</strong>:发生错误的用户名称。</p></li><li><p><strong>HOST</strong>:发生错误的主机名。</p></li><li><p><strong>ERROR_NUMBER</strong>:错误代码。</p></li><li><p><strong>ERROR_NAME</strong>:错误名称。</p></li><li><p><strong>SQL_STATE</strong>:SQL 状态。</p></li><li><p><strong>SUM_ERROR_RAISED</strong>:统计错误发生的次数。</p></li><li><p><strong>SUM_ERROR_HANDLED</strong>:统计已处理错误的次数。</p></li><li><p><strong>FIRST_SEEN</strong>:首次看到错误的时间戳。</p></li><li><p><strong>LAST_SEEN</strong>:最后看到错误的时间戳。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_account_by_error;</span><br></pre></td></tr></table></figure><ul><li>查特定用户的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_account_by_error <span class="keyword">WHERE</span> <span class="keyword">USER</span> <span class="string">&#x27;your_user&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>按错误代码过滤:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_account_by_error <span class="keyword">WHERE</span> ERROR_NUMBER your_error_number;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些用户在什么主机上发生了哪些错误,错误的名称、SQL 状态、发生次数以及首次和最后发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img8.avif"></p><h3 id="events-errors-summary-by-host-by-error"><a href="#events-errors-summary-by-host-by-error" class="headerlink" title="events_errors_summary_by_host_by_error"></a>events_errors_summary_by_host_by_error</h3><p><code>events_errors_summary_by_host_by_error</code> 表是 MySQL Performance Schema 中的一个表,用于按主机和错误类型统计错误信息。以下是表中每一列的含义:</p><ul><li><p><strong>HOST</strong>:发生错误的主机名。</p></li><li><p><strong>ERROR_NUMBER</strong>:错误代码。</p></li><li><p><strong>ERROR_NAME</strong>:错误名称。</p></li><li><p><strong>SQL_STATE</strong>:SQL 状态。</p></li><li><p><strong>SUM_ERROR_RAISED</strong>:统计错误发生的次数。</p></li><li><p><strong>SUM_ERROR_HANDLED</strong>:统计已处理错误的次数。</p></li><li><p><strong>FIRST_SEEN</strong>:首次看到错误的时间戳。</p></li><li><p><strong>LAST_SEEN</strong>:最后看到错误的时间戳。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_host_by_error;</span><br></pre></td></tr></table></figure><ul><li>查特定主机的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_host_by_error <span class="keyword">WHERE</span> HOST <span class="string">&#x27;your_host&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>按错误代码过滤:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_host_by_error <span class="keyword">WHERE</span> ERROR_NUMBER your_error_number;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些主机上发生了哪些错误,错误的名称、SQL 状态、发生次数以及首次和最后发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img9.avif"></p><h3 id="events-errors-summary-by-thread-by-error"><a href="#events-errors-summary-by-thread-by-error" class="headerlink" title="events_errors_summary_by_thread_by_error"></a>events_errors_summary_by_thread_by_error</h3><p><code>events_errors_summary_by_thread_by_error</code> 表是 MySQL Performance Schema 中的一个表,用于按线程和错误类型统计错误信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:发生错误的线程ID。</p></li><li><p><strong>ERROR_NUMBER</strong>:错误代码。</p></li><li><p><strong>ERROR_NAME</strong>:错误名称。</p></li><li><p><strong>SQL_STATE</strong>:SQL 状态。</p></li><li><p><strong>SUM_ERROR_RAISED</strong>:统计错误发生的次数。</p></li><li><p><strong>SUM_ERROR_HANDLED</strong>:统计已处理错误的次数。</p></li><li><p><strong>FIRST_SEEN</strong>:首次看到错误的时间戳。</p></li><li><p><strong>LAST_SEEN</strong>:最后看到的时间戳。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_thread_by_error;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_thread_by_error <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><ul><li>按错误代码过滤:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_thread_by_thread_by_error <span class="keyword">WHERE</span> ERROR_NUMBER your_error_number;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程上发生了哪些错误,错误的名称、SQL 状态、发生次数以及首次和最后发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img10.avif"></p><h3 id="events-errors-summary-by-user-by-error"><a href="#events-errors-summary-by-user-by-error" class="headerlink" title="events_errors_summary_by_user_by_error"></a>events_errors_summary_by_user_by_error</h3><p><code>events_errors_summary_by_user_by_error</code> 表是 MySQL Performance Schema 中的一个表,用于按用户和错误类型统计错误信息。以下是表中每一列的含义:</p><ul><li><p><strong>USER</strong>:发生错误的用户名称。</p></li><li><p><strong>ERROR_NUMBER</strong>:错误代码。</p></li><li><p><strong>ERROR_NAME</strong>:错误名称。</p></li><li><p><strong>SQL_STATE</strong>:SQL 状态。</p></li><li><p><strong>SUM_ERROR_RAISED</strong>:统计错误发生的次数。</p></li><li><p><strong>SUM_ERROR_HANDLED</strong>:统计已处理错误的次数。</p></li><li><p><strong>FIRST_SEEN</strong>:首次看到的时间戳。</p></li><li><p><strong>LAST_SEEN</strong>:最后看到的时间戳。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_user_by_error;</span><br></pre></td></tr></table></figure><ul><li>查特定用户的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_by_user_by_error <span class="keyword">WHERE</span> <span class="keyword">USER</span> <span class="string">&#x27;your_user&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>按错误代码过滤:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_user_by_error <span class="keyword">WHERE</span> ERROR_NUMBER your_error_number;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些用户发生了哪些错误,错误的名称、SQL 状态、发生次数以及首次和最后发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img11.avif"></p><h3 id="events-errors-summary-global-by-error"><a href="#events-errors-summary-global-by-error" class="headerlink" title="events_errors_summary_global_by_error"></a>events_errors_summary_global_by_error</h3><p><code>events_errors_summary_global_by_error</code> 表是 MySQL Performance Schema 中的一个表,用于按错误类型统计全局错误信息。以下是表中每一列的含义:</p><ul><li><p><strong>ERROR_NUMBER</strong>:错误代码。</p></li><li><p><strong>ERROR_NAME</strong>:错误名称。</p></li><li><p><strong>SQL_STATE</strong>:SQL 状态。</p></li><li><p><strong>SUM_ERROR_RAISED</strong>:统计错误发生的次数。</p></li><li><p><strong>SUM_ERROR_HANDLED</strong>:统计已处理错误的次数。</p></li><li><p><strong>FIRST_SEEN</strong>:首次看到的时间戳。</p></li><li><p><strong>LAST_SEEN</strong>:最后看到的时间戳。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_global_by_error;</span><br></pre></td></tr></table></figure><ul><li>查特定错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_errors_summary_global_by_error <span class="keyword">WHERE</span> ERROR_NUMBER your_error_number;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些错误发生了多少次,错误的名称、SQL 状态、发生次数以及首次和最后发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img12.avif"></p><h3 id="events-stages-current"><a href="#events-stages-current" class="headerlink" title="events_stages_current"></a>events_stages_current</h3><p><code>events_stages_current</code> 表是 MySQL Performance Schema 中的一个表,用于记录当前会话中正在执行的事件的各个阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:线程ID,标识正在执行事件的线程。</p></li><li><p><strong>EVENT_ID</strong>:事件ID。</p></li><li><p><strong>END_EVENT_ID</strong>:结束事件ID。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>SOURCE</strong>:事件来源 例如,可能是 <code>SERVER</code>、<code>WAIT</code>、<code>USER</code>等 。</p></li><li><p><strong>TIMER_START</strong>:事件开始时间戳。</p></li><li><p><strong>TIMER_END</strong>:事件结束时间戳。</p></li><li><p><strong>TIMER_WAIT</strong>:等待时间 如果事件处于等待状态 。</p></li><li><p><strong>WORK_COMPLETED</strong>:已完成的工作量。</p></li><li><p><strong>WORK_ESTIMATED</strong>:估计剩余工作量。</p></li><li><p><strong>NESTING_EVENT_ID</strong>:嵌套事件ID 如果有 。</p></li><li><p><strong>NESTING_EVENT_TYPE</strong>:嵌套事件类型 <code>TRANSACTION</code>、<code>、</code>STAGE<code>或</code>WAIT 。</p></li><li><p>查看当前所有事件:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_current;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的事件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_current <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程正在执行哪些事件,事件名称、来源、开始和结束时间、等待时间、完成情况等信息。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img13.avif"></p><h3 id="events-stages-history"><a href="#events-stages-history" class="headerlink" title="events_stages_history"></a>events_stages_history</h3><p><code>events_stages_history</code> 表是 MySQL Performance Schema 中的一个表,用于记录历史事件的各个阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:线程ID,标识执行事件的线程。</p></li><li><p><strong>EVENT_ID</strong>:事件ID。</p></li><li><p><strong>END_EVENT_ID</strong>:结束事件ID。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>SOURCE</strong>:事件来源 例如,<code>SERVER</code>、<code>USER</code>等 。</p></li><li><p><strong>TIMER_START</strong>:事件开始时间戳。</p></li><li><p><strong>TIMER_END</strong>:事件结束时间戳。</p></li><li><p><strong>TIMER_WAIT</strong>:等待时间 如果事件处于等待状态 。</p></li><li><p><strong>WORK_COMPLETED</strong>:已完成的工作量。</p></li><li><p><strong>WORK_ESTIMATED</strong>:估计剩余工作量。</p></li><li><p><strong>NESTING_EVENT_ID</strong>:嵌套事件ID 如果有 。</p></li><li><p><strong>NESTING_EVENT_TYPE</strong>:嵌套事件类型 <code>TRANSACTION</code>、<code>STAGE</code>或<code>WAIT</code> 。</p></li><li><p>查看所有事件:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_history;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的事件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_history <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程上发生了哪些事件,事件名称、来源、开始和结束时间、等待时间、完成情况等信息。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img14.avif"></p><h3 id="events-stages-history-long"><a href="#events-stages-history-long" class="headerlink" title="events_stages_history_long"></a>events_stages_history_long</h3><p><code>events_stages_history_long</code> 表是 MySQL Performance Schema 中的一个表,用于记录长时间运行的事件的各个阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:线程ID,标识执行事件的线程。</p></li><li><p><strong>EVENT_ID</strong>:事件ID。</p></li><li><p><strong>END_EVENT_ID</strong>:结束事件ID。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>SOURCE</strong>:事件来源 例如,<code>SERVER</code>USER<code>、</code>WAIT 等 。</p></li><li><p><strong>TIMER_START</strong>:事件开始时间戳。</p></li><li><p><strong>TIMER_END</strong>:事件结束时间戳。</p></li><li><p><strong>TIMER_WAIT</strong>:等待时间 如果事件处于等待状态 。</p></li><li><p><strong>WORK_COMPLETED</strong>:已完成的工作量。</p></li><li><p><strong>WORK_ESTIMATED</strong>:估计剩余工作量。</p></li><li><p><strong>NESTING_EVENT_ID</strong>:嵌套事件ID 如果有 。</p></li><li><p><strong>NESTING_EVENT_TYPE</strong>:嵌套事件类型 <code>TRANSACTION</code>、<code>STAGE</code>或<code>WAIT</code> 。</p></li><li><p>查看所有事件:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_history;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的事件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_history <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程上发生了哪些事件,事件名称、来源、开始和结束时间、等待时间、完成情况等信息。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img15.avif"></p><h3 id="events-stages-summary-by-account-by-event-name"><a href="#events-stages-summary-by-account-by-event-name" class="headerlink" title="events_stages_summary_by_account_by_event_name"></a>events_stages_summary_by_account_by_event_name</h3><p><code>events_stages_summary_by_account_by_event_name</code> 表是 MySQL Performance Schema 中的一个表,用于按账户和事件名称统计事件名称统计阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>USER</strong>:发生事件的用户。</p></li><li><p><strong>HOST</strong>:发生事件的主机名。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>COUNT_STAR</strong>:事件开始的次数。</p></li><li><p><strong>SUM_TIMER_WAIT</strong>:总等待时间 毫秒 。</p></li><li><p><strong>MIN_TIMER_WAIT</strong>:最小等待时间 毫秒 。</p></li><li><p><strong>AVG_TIMER_WAIT</strong>:平均等待时间 毫秒 。</p></li><li><p><strong>MAX_TIMER_WAIT</strong>:最大等待时间 毫秒 。</p></li><li><p>查看所有事件摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_by_event_name;</span><br></pre></td></tr></table></figure><ul><li>查特定事件的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_by_event_name <span class="keyword">WHERE</span> EVENT_NAME <span class="string">&#x27;your_event_name&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>查特定用户的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_by_event_name <span class="keyword">WHERE</span> <span class="keyword">USER</span> <span class="string">&#x27;your_user&#x27;</span>;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些用户发生了哪些事件,事件名称、等待时间、发生次数以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img16.avif"></p><h3 id="events-stages-summary-by-host-by-event-name"><a href="#events-stages-summary-by-host-by-event-name" class="headerlink" title="events_stages_summary_by_host_by_event_name"></a>events_stages_summary_by_host_by_event_name</h3><p><code>events_stages_summary_by_host_by_event_name</code> 表是 MySQL Performance Schema 中的一个表,用于按主机和事件名称统计事件名称统计事件阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>HOST</strong>:发生事件的主机名。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>COUNT_STAR</strong>:事件开始的次数。</p></li><li><p><strong>SUM_TIMER_WAIT</strong>:总等待时间 毫秒 。</p></li><li><p><strong>MIN_TIMER_WAIT</strong>:最小等待时间 毫秒 。</p></li><li><p><strong>AVG_WAIT</strong>:平均等待时间 毫秒 。</p></li><li><p><strong>MMAX_TIMER_WAIT</strong>:最大等待时间 毫秒 。</p></li><li><p>查看所有事件摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_by_event_name;</span><br></pre></td></tr></table></figure><ul><li>查特定事件的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_by_event_name <span class="keyword">WHERE</span> EVENT_NAME <span class="string">&#x27;your_event_name&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>查特定主机的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_by_event_name <span class="keyword">WHERE</span> HOST <span class="string">&#x27;your_host&#x27;</span>;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些主机上发生了哪些事件,事件名称、等待时间、发生次数以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img17.avif"></p><h3 id="events-stages-summary-by-thread-by-event-name"><a href="#events-stages-summary-by-thread-by-event-name" class="headerlink" title="events_stages_summary_by_thread_by_event_name"></a>events_stages_summary_by_thread_by_event_name</h3><p><code>events_stages_summary_by_thread_by_thread_by_event_name</code> 表是 MySQL Performance Schema 中的一个表,用于按线程和事件名称统计事件阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:线程ID,标识执行事件的线程。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>COUNT_STAR</strong>:事件开始的次数。</p></li><li><p><strong>SUM_TIMER_WAIT</strong>:总等待时间 毫秒 。</p></li><li><p><strong>MIN_TIMER_WAIT</strong>:最小等待时间 毫秒 。</p></li><li><p><strong>AVG_WAIT</strong>:平均等待时间 毫秒 。</p></li><li><p><strong>MAX_TIMER_WAIT</strong>:最大等待时间 毫秒 。</p></li><li><p>查看所有事件摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_by_thread_by_event_name;</span><br></pre></td></tr></table></figure><ul><li>查特定事件的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_thread_by_event_name <span class="keyword">WHERE</span> EVENT_NAME <span class="string">&#x27;your_event_name&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>查特定线程的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_thread_by_event_name <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程上发生了哪些事件,事件名称、等待时间、发生次数以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img18.avif"></p><h3 id="events-stages-summary-by-user-by-event-name"><a href="#events-stages-summary-by-user-by-event-name" class="headerlink" title="events_stages_summary_by_user_by_event_name"></a>events_stages_summary_by_user_by_event_name</h3><p><code>events_stages_summary_by_user_by_user_by_event_name</code> 表是 MySQL Performance Schema 中的一个表,用于按用户和事件名称统计事件阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>USER</strong>:发生错误的用户名。</p></li><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>COUNT_STAR</strong>:事件开始的次数。</p></li><li><p><strong>SUM_TIMER_WAIT</strong>:总等待时间 毫秒 。</p></li><li><p><strong>MIN_TIMER_WAIT</strong>:最小等待时间 毫秒 。</p></li><li><p><strong>AVG_WAIT</strong>:平均等待时间 毫秒 。</p></li><li><p><strong>MAX_WAIT</strong>:最大等待时间 毫秒 。</p></li><li><p>查看所有错误摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_user_by_event_name;</span><br></pre></td></tr></table></figure><ul><li>查特定事件的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_user_by_event_name <span class="keyword">WHERE</span> EVENT_NAME <span class="string">&#x27;your_event_name&#x27;</span>;</span><br></pre></td></tr></table></figure><ul><li>查特定用户的错误摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_by_user_by_event_name <span class="keyword">WHERE</span> <span class="keyword">USER</span> <span class="string">&#x27;your_user&#x27;</span>;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些用户发生了哪些用户发生了哪些事件,事件名称、等待时间、发生次数以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img19.avif"></p><h3 id="events-stages-summary-global-by-event-name"><a href="#events-stages-summary-global-by-event-name" class="headerlink" title="events_stages_summary_global_by_event_name"></a>events_stages_summary_global_by_event_name</h3><p><code>events_stages_summary_global_by_event_name</code> 表是 MySQL Performance Schema 中的一个表,用于按事件名称统计全局事件阶段信息。以下是表中每一列的含义:</p><ul><li><p><strong>EVENT_NAME</strong>:事件名称。</p></li><li><p><strong>COUNT_STAR</strong>:事件开始的次数。</p></li><li><p><strong>SUM_TIMER_WAIT</strong>:总等待时间 毫秒 。</p></li><li><p><strong>MIN_TIMER_WAIT</strong>:最小等待时间 毫秒 。</p></li><li><p><strong>AVG_WAIT</strong>:平均等待时间 毫秒 。</p></li><li><p><strong>MAX_WAIT</strong>:最大等待时间 毫秒 。</p></li><li><p>查所有事件摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_stages_summary_global_by_event_name;</span><br></pre></td></tr></table></figure><ul><li>查特定事件的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_summary_global_by_event_name <span class="keyword">WHERE</span> EVENT_NAME <span class="string">&#x27;your_event_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些事件发生了,事件名称、等待时间、发生次数以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img20.avif"></p><h3 id="events-statements-current"><a href="#events-statements-current" class="headerlink" title="events_statements_current"></a>events_statements_current</h3><p><code>events_statements_current</code> 表是 MySQL Performance Schema 中的一个表,用于记录当前正在执行的语句信息。以下是表中每一列的含义:</p><ul><li><p><strong>THREAD_ID</strong>:执行语句的线程ID。</p></li><li><p><strong>EVENT_ID</strong>:事件ID。</p></li><li><p><strong>END_EVENT_ID</strong>:结束事件ID。</p></li><li><p><strong>EVENT_NAME</strong>:语句名称 例如,<code>Query</code> 。</p></li><li><p><strong>SOURCE</strong>:语句来源 例如,<code>SERVER</code>、<code>USER</code>等 。</p></li><li><p><strong>TIMER_START</strong>:语句开始时间戳。</p></li><li><p><strong>TIMER_END</strong>:语句结束时间戳。</p></li><li><p><strong>TIMER_WAIT</strong>:等待时间 如果语句处于等待状态 。</p></li><li><p><strong>WORK_COMPLETED</strong>:已完成的工作量。</p></li><li><p><strong>WORK_ESTIMATED</strong>:估计剩余工作量。</p></li><li><p><strong>_NESTING_EVENT_ID</strong>:嵌套事件ID 如果有 。</p></li><li><p><strong>_NESTING_EVENT_TYPE</strong>:嵌套事件类型 <code>TRANSACTION</code>、<code>、</code>STATEMENT<code>、</code>、<code>WAIT</code> 。</p></li><li><p><strong>_ERRORS</strong>:错误代码。</p></li><li><p><strong>_WARNINGS</strong>:警告数量。</p></li><li><p><strong>ROWS_AFFECTED</strong>:受影响的行数。</p></li><li><p><strong>ROWS_SENT</strong>:发送的行数。</p></li><li><p><strong>ROWS_EXAMINED</strong>:已检查的行数。</p></li><li><p><strong>CREATED_TMP_DISK_TABLES</strong>:创建的临时磁盘表数。</p></li><li><p><strong>CREATED_TMP_TABLES</strong>:创建的临时表数。</p></li><li><p><strong>SELECT_FULL_RANGE</strong>:范围检查。</p></li><li><p><strong>SELECT_RANGE</strong>:范围检查。</p></li><li><p><strong>SORT_MERGE_PAGES</strong>:排序页数。</p></li><li><p><strong>SORT_RANGE</strong>:排序页数。</p></li><li><p><strong>SORT_ROWS</strong>:排序行数。</p></li><li><p><strong>SCAN</strong>:扫描行数。</p></li><li><p><strong>NO_INDEX_USED</strong>:未使用索引数。</p></li><li><p><strong>NO_GOOD_INDEX_USED</strong>:未使用的索引数。</p></li><li><p><strong>NESTING_EVENT_ID</strong>:嵌套事件ID。</p></li><li><p><strong>NESTING_EVENT_TYPE</strong>:嵌套事件类型 <code>TRANSACTION</code>、<code>、</code>MENT<code>、</code>、<code>WAIT</code> 。</p></li><li><p>查看所有语句:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_statements_current;</span><br></pre></td></tr></table></figure><ul><li>查特定语句:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_statements_current <span class="keyword">WHERE</span> THREAD_ID your_thread_id;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些线程上发生了哪些语句,语句名称、来源、开始和结束时间、等待时间、完成情况等信息。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img21.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img22.avif"></p><h3 id="events-statements-histogram-by-digest"><a href="#events-statements-histogram-by-digest" class="headerlink" title="events_statements_histogram_by_digest"></a>events_statements_histogram_by_digest</h3><p><code>events_statements_history_by_digest</code> 表是 MySQL Performance Schema 中的一个表,用于记录语句的摘要信息。以下是表中每一列的含义:</p><ul><li><p><strong>SCHEMA_NAME</strong>:数据库名称。</p></li><li><p><strong>DIGEST_NUMBER</strong>:摘要编号。</p></li><li><p><strong>BUCKET_NUMBER</strong>:桶编号。</p></li><li><p><strong>BUCKET_TIMER_LOW</strong>:桶的开始时间戳。</p></li><li><p><strong>BUCKET_TIMER_HIGH</strong>:桶结束时间戳。</p></li><li><p><strong>COUNT_BUCKET</strong>:桶中语句数量。</p></li><li><p><strong>COUNT_BUCKET_AND_LOWER</strong>:桶中语句数量的下限。</p></li><li><p><strong>BUCKET_QUANTITY</strong>:桶数量。</p></li><li><p><strong>SCHEMA_NAME</strong>:数据库名称。</p></li><li><p><strong>DIGEST</strong>:摘要。</p></li><li><p>查所有摘要:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_statements_history_by_digest;</span><br></pre></td></tr></table></figure><ul><li>查特定数据库的摘要:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_statements_history_by_digest <span class="keyword">WHERE</span> SCHEMA_NAME <span class="string">&#x27;your_schema&#x27;</span>;</span><br></pre></td></tr></table></figure><p>通过这些查询,你可以了解哪些数据库发生了哪些数据库,摘要、摘要编号、时间、数量以及首次发生时间。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img23.avif"></p><h3 id="events-statements-histogram-global"><a href="#events-statements-histogram-global" class="headerlink" title="events_statements_histogram_global"></a>events_statements_histogram_global</h3><p><code>events_statements_histogram_global</code> 表是 MySQL Performance Schema 中的一个表,用于记录全局语句的摘要信息。以下是表中每一列的含义:</p><ul><li><p><strong>BUCKET_NUMBER</strong>:桶编号。</p></li><li><p><strong>BUCKET_TIMER_LOW</strong>:桶开始时间戳。</p></li><li><p><strong>BUCKET_TIMER_HIGH</strong>:桶结束时间戳。</p></li><li><p><strong>COUNT_BUCKET</strong>:桶中语句数量。</p></li><li><p><strong>COUNT_BUCKET</strong>:桶中语句数量。</p></li><li><p><strong>COUNT_BUCKET_AND_LOWER</strong>:桶中语句数量的下限。</p></li><li><p><strong>BUCKET_QUANTITY</strong>:桶数量。</p></li><li><p>查所有语句:</p></li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> events_statements_histogram_global;</span><br></pre></td></tr></table></figure><p>这些查询,你可以了解哪些语句,开始时间、结束时间、数量等信息。这有助于诊断和解决数据库中的问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img24.avif"></p><h3 id="events-statements-history"><a href="#events-statements-history" class="headerlink" title="events_statements_history"></a>events_statements_history</h3><p>这个表是MySQL性能模式中的<code>events_statements_history</code>表,用于记录语句事件的执行历史。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行语句的线程ID。</li><li><strong>EVENT_ID</strong>: 语句事件的唯一标识符。</li><li><strong>END_EVENT_ID</strong>: 语句事件结束的唯一标识符。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>SOURCE</strong>: 语句的来源,例如用户或程序。</li><li><strong>TIMER_START</strong>: 语句开始执行的时间戳。</li><li><strong>TIMER_END</strong>: 语句结束执行的时间戳。</li><li><strong>TIMER_WAIT</strong>: 语句等待的时间。</li><li><strong>LOCK_TIME</strong>: 语句等待锁的时间。</li><li><strong>SQL_TEXT</strong>: 执行的SQL语句文本。</li><li><strong>DIGEST</strong>: SQL语句的摘要信息,用于聚合相似的查询。</li><li><strong>DIGEST_TEXT</strong>: 摘要文本,提供摘要的详细信息。</li><li><strong>CURRENT_SCHEMA</strong>: 当前使用的数据库模式。</li><li><strong>OBJECT_TYPE</strong>: 对象类型,例如表或存储过程。</li><li><strong>OBJECT_SCHEMA</strong>: 对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 对象的名称。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始时间戳。</li><li><strong>MYSQL_ERRNO</strong>: 语句执行时返回的错误代码。</li><li><strong>RETURNED_SQLSTATE</strong>: 返回的SQL状态码。</li><li><strong>MESSAGE_TEXT</strong>: 错误或消息的文本描述。</li><li><strong>ERRORS</strong>: 语句执行过程中发生的错误数量。</li><li><strong>WARNINGS</strong>: 语句执行过程中产生的警告数量。</li><li><strong>ROWS_AFFECTED</strong>: 语句影响的行数。</li><li><strong>ROWS_SENT</strong>: 发送到客户端的行数。</li><li><strong>ROWS_EXAMINED</strong>: 语句检查的行数。</li><li><strong>CREATED_TMP_DISK_TABLES</strong>: 语句执行过程中创建的临时磁盘表数量。</li><li><strong>CREATED_TMP_TABLES</strong>: 语句执行过程中创建的临时表数量。</li><li><strong>SELECT_FULL_JOIN</strong>: 是否执行了全表连接。</li><li><strong>SELECT_FULL_RANGE_JOIN</strong>: 是否执行了全范围连接。</li><li><strong>SELECT_RANGE</strong>: 是否执行了范围扫描。</li><li><strong>SELECT_RANGE_CHECK</strong>: 是否执行了范围检查。</li><li><strong>SELECT_SCAN</strong>: 是否执行了全表扫描。</li><li><strong>SORT_MERGE_PASSES</strong>: 排序合并的遍历次数。</li><li><strong>SORT_RANGE</strong>: 是否执行了范围排序。</li><li><strong>SORT_ROWS</strong>: 排序的行数。</li><li><strong>SORT_SCAN</strong>: 是否执行了扫描排序。</li><li><strong>NO_INDEX_USED</strong>: 是否没有使用索引。</li><li><strong>NO_GOOD_INDEX_USED</strong>: 是否没有使用合适的索引。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的ID。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,例如“TRANSACTION”或“STATEMENT”。</li><li><strong>NESTING_EVENT_LEVEL</strong>: 嵌套事件的层级。</li><li><strong>STATEMENT_ID</strong>: 语句ID。</li><li><strong>CPU_TIME</strong>: 语句执行消耗的CPU时间。</li><li><strong>MAX_CONTROLLED_MEMORY</strong>: 语句执行过程中使用的最大受控内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 语句执行过程中使用的最大总内存。</li><li><strong>EXECUTION_ENGINE</strong>: 语句执行使用的引擎,例如“PRIMARY”或“SECONDARY”。</li></ul><p>这些列提供了详细的语句执行信息,有助于分析和优化数据库性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img25.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img26.avif"></p><h3 id="events-statements-history-long"><a href="#events-statements-history-long" class="headerlink" title="events_statements_history_long"></a>events_statements_history_long</h3><p>这个表是MySQL性能模式中的<code>events_statements_history_long</code>表,用于记录长时间运行的语句事件的执行历史。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行语句的线程ID。</li><li><strong>EVENT_ID</strong>: 语句事件的唯一标识符。</li><li><strong>END_EVENT_ID</strong>: 语句事件结束的唯一标识符。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>SOURCE</strong>: 语句的来源,例如用户或程序。</li><li><strong>TIMER_START</strong>: 语句开始执行的时间戳。</li><li><strong>TIMER_END</strong>: 语句结束执行的时间戳。</li><li><strong>TIMER_WAIT</strong>: 语句等待的时间。</li><li><strong>LOCK_TIME</strong>: 语句等待锁的时间。</li><li><strong>SQL_TEXT</strong>: 执行的SQL语句文本。</li><li><strong>DIGEST</strong>: SQL语句的摘要信息,用于聚合相似的查询。</li><li><strong>DIGEST_TEXT</strong>: 摘要文本,提供摘要的详细信息。</li><li><strong>CURRENT_SCHEMA</strong>: 当前使用的数据库模式。</li><li><strong>OBJECT_TYPE</strong>: 对象类型,例如表或存储过程。</li><li><strong>OBJECT_SCHEMA</strong>: 对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 对象的名称。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始时间戳。</li><li><strong>MYSQL_ERRNO</strong>: 语句执行时返回的错误代码。</li><li><strong>RETURNED_SQLSTATE</strong>: 返回的SQL状态码。</li><li><strong>MESSAGE_TEXT</strong>: 错误或消息的文本描述。</li><li><strong>ERRORS</strong>: 语句执行过程中发生的错误数量。</li><li><strong>WARNINGS</strong>: 语句执行过程中产生的警告数量。</li><li><strong>ROWS_AFFECTED</strong>: 语句影响的行数。</li><li><strong>ROWS_SENT</strong>: 发送到客户端的行数。</li><li><strong>ROWS_EXAMINED</strong>: 语句检查的行数。</li><li><strong>CREATED_TMP_DISK_TABLES</strong>: 语句执行过程中创建的临时磁盘表数量。</li><li><strong>CREATED_TMP_TABLES</strong>: 语句执行过程中创建的临时表数量。</li><li><strong>SELECT_FULL_JOIN</strong>: 是否执行了全表连接。</li><li><strong>SELECT_FULL_RANGE_JOIN</strong>: 是否执行了全范围连接。</li><li><strong>SELECT_RANGE</strong>: 是否执行了范围扫描。</li><li><strong>SELECT_RANGE_CHECK</strong>: 是否执行了范围检查。</li><li><strong>SELECT_SCAN</strong>: 是否执行了全表扫描。</li><li><strong>SORT_MERGE_PASSES</strong>: 排序合并的遍历次数。</li><li><strong>SORT_RANGE</strong>: 是否执行了范围排序。</li><li><strong>SORT_ROWS</strong>: 排序的行数。</li><li><strong>SORT_SCAN</strong>: 是否执行了扫描排序。</li><li><strong>NO_INDEX_USED</strong>: 是否没有使用索引。</li><li><strong>NO_GOOD_INDEX_USED</strong>: 是否没有使用合适的索引。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的ID。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,例如“TRANSACTION”或“STATEMENT”。</li><li><strong>NESTING_EVENT_LEVEL</strong>: 嵌套事件的层级。</li><li><strong>STATEMENT_ID</strong>: 语句ID。</li><li><strong>CPU_TIME</strong>: 语句执行消耗的CPU时间。</li><li><strong>MAX_CONTROLLED_MEMORY</strong>: 语句执行过程中使用的最大受控内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 语句执行过程中使用的最大总内存。</li><li><strong>EXECUTION_ENGINE</strong>: 语句执行使用的引擎,例如“PRIMARY”或“SECONDARY”。</li></ul><p>这些列提供了详细的语句执行信息,有助于分析和优化数据库性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img27.avif"></p><h3 id="events-statements-summary-by-account-by-event-name"><a href="#events-statements-summary-by-account-by-event-name" class="headerlink" title="events_statements_summary_by_account_by_event_name"></a>events_statements_summary_by_account_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_account_by_event_name</code>表,用于按账户和事件名称汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 执行语句的数据库用户。</li><li><strong>HOST</strong>: 执行语句的主机。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>COUNT_STAR</strong>: 该账户下该事件名称的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该账户下该事件名称的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该账户下该事件名称的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该账户下该事件名称的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该账户下该事件名称的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该账户下该事件名称的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该账户下该事件名称的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该账户下该事件名称的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该账户下该事件名称的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该账户下该事件名称的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该账户下该事件名称的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该账户下该事件名称的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该账户下该事件名称的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该账户下该事件名称的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该账户下该事件名称的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该账户下该事件名称的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该账户下该事件名称的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该账户下该事件名称的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该账户下该事件名称的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该账户下该事件名称的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该账户下该事件名称的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该账户下该事件名称的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该账户下该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该账户下该事件名称的语句没有使用合适索引的总次数。</li><li><strong>SUM_NO_INDEX</strong>: 该账户下该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX</strong>: 该账户下该事件名称的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 该账户下该事件名称的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该账户下该事件名称的语句使用的最大总内存。</li><li><strong>MAX_CONTROLLED_MEMORY</strong>: 该账户下该事件名称的语句使用的最大受控内存。</li><li><strong>COUNT_SECONDARY</strong>: 该账户下该事件名称的语句执行的次要事件总次数。</li></ul><p>这些列提供了按账户和事件名称汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY ACCOUNT (&#39;USER&#39;, &#39;HOST&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个账户和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img28.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img29.avif"></p><h3 id="events-statements-summary-by-digest"><a href="#events-statements-summary-by-digest" class="headerlink" title="events_statements_summary_by_digest"></a>events_statements_summary_by_digest</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_digest</code>表,用于按SQL摘要汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>SCHEMA_NAME</strong>: 语句执行时使用的数据库模式的名称。</li><li><strong>DIGEST</strong>: SQL语句的摘要信息,用于聚合相似的查询。</li><li><strong>DIGEST_TEXT</strong>: 摘要文本,提供摘要的详细信息。</li><li><strong>COUNT_STAR</strong>: 该摘要对应的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该摘要对应的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该摘要对应的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该摘要对应的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该摘要对应的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该摘要对应的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该摘要对应的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该摘要对应的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该摘要对应的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该摘要对应的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该摘要对应的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该摘要对应的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该摘要对应的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该摘要对应的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该摘要对应的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该摘要对应的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该摘要对应的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该摘要对应的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该摘要对应的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该摘要对应的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该摘要对应的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该摘要对应的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该摘要对应的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该摘要对应的语句没有使用合适索引的总次数。</li><li><strong>SUM_CPU_TIME</strong>: 该摘要对应的语句执行消耗的总CPU时间。</li><li><strong>MAX_CONTROLLED_MEMORY</strong>: 该摘要对应的语句执行过程中使用的最大受控内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该摘要对应的语句执行过程中使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 该摘要对应的语句执行的次要事件总次数。</li><li><strong>FIRST_SEEN</strong>: 该摘要对应的语句首次出现的UTC时间戳。</li><li><strong>LAST_SEEN</strong>: 该摘要对应的语句最后出现的UTC时间戳。</li><li><strong>QUARTERS</strong>: 该摘要对应的语句出现的季度数。</li><li><strong>QUERY_SAMPLE_TEXT</strong>: 该摘要对应的语句样本文本。</li><li><strong>QUERY_SAMPLE_SEEN</strong>: 该摘要对应的语句样本首次出现的UTC时间戳。</li><li><strong>QUERY_SAMPLE_TIMER_WAIT</strong>: 该摘要对应的语句样本的等待时间。</li></ul><p>这些列提供了按SQL摘要汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY SCHEMA_NAME (&#39;SCHEMA_NAME&#39;, &#39;DIGEST&#39;)</code>,用于确保每个模式和摘要的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img30.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img31.avif"></p><h3 id="events-statements-summary-by-host-by-event-name"><a href="#events-statements-summary-by-host-by-event-name" class="headerlink" title="events_statements_summary_by_host_by_event_name"></a>events_statements_summary_by_host_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_host_by_event_name</code>表,用于按主机和事件名称汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>HOST</strong>: 执行语句的主机名。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>COUNT_STAR</strong>: 该主机下该事件名称的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该主机下该事件名称的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该主机下该事件名称的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该主机下该事件名称的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该主机下该事件名称的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该主机下该事件名称的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该主机下该事件名称的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该主机下该事件名称的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该主机下该事件名称的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该主机下该事件名称的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该主机下该事件名称的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该主机下该事件名称的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该主机下该事件名称的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该主机下该事件名称的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该主机下该事件名称的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该主机下该事件名称的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该主机下该事件名称的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该主机下该事件名称的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该主机下该事件名称的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该主机下该事件名称的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该主机下该事件名称的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该主机下该事件名称的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该主机下该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该主机下该事件名称的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 该主机下该事件名称的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该主机下该事件名称的语句使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 该主机下该事件名称的语句执行的次要事件总次数。</li></ul><p>这些列提供了按主机和事件名称汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY HOST (&#39;HOST&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个主机和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img32.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img33.avif"></p><h3 id="events-statements-summary-by-program"><a href="#events-statements-summary-by-program" class="headerlink" title="events_statements_summary_by_program"></a>events_statements_summary_by_program</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_program</code>表,用于按程序 如存储过程、函数、触发器等 汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>OBJECT_TYPE</strong>: 对象类型,可以是EVENT、FUNCTION、PROCEDURE、TABLE或TRIGGER。</li><li><strong>OBJECT_SCHEMA</strong>: 对象所在的数据库模式的名称。</li><li><strong>OBJECT_NAME</strong>: 对象的名称。</li><li><strong>COUNT_STAR</strong>: 该程序对应的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该程序对应的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该程序对应的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该程序对应的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该程序对应的语句最大等待时间。</li><li><strong>COUNT_STATEMENTS</strong>: 该程序中语句的执行总次数。</li><li><strong>SUM_STATEMENTS_WAIT</strong>: 该程序中语句的总等待时间。</li><li><strong>MIN_STATEMENTS_WAIT</strong>: 该程序中语句的最小等待时间。</li><li><strong>AVG_STATEMENTS_WAIT</strong>: 该程序中语句的平均等待时间。</li><li><strong>MAX_STATEMENTS_WAIT</strong>: 该程序中语句的最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该程序对应的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该程序对应的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该程序对应的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该程序对应的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该程序对应的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该程序对应的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该程序对应的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该程序对应的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该程序对应的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该程序对应的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该程序对应的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该程序对应的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该程序对应的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该程序对应的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该程序对应的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该程序对应的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该程序对应的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该程序对应的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该程序对应的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 该程序对应的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该程序对应的语句使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 该程序对应的语句执行的次要事件总次数。</li></ul><p>这些列提供了按程序汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个主键<code>PRIMARY KEY (&#39;OBJECT_TYPE&#39;, &#39;OBJECT_SCHEMA&#39;, &#39;OBJECT_NAME&#39;)</code>,用于确保每个程序在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img34.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img35.avif"></p><h3 id="events-statements-summary-by-thread-by-event-name"><a href="#events-statements-summary-by-thread-by-event-name" class="headerlink" title="events_statements_summary_by_thread_by_event_name"></a>events_statements_summary_by_thread_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_thread_by_event_name</code>表,用于按线程和事件名称汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行语句的线程ID。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>COUNT_STAR</strong>: 该线程下该事件名称的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该线程下该事件名称的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该线程下该事件名称的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该线程下该事件名称的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该线程下该事件名称的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该线程下该事件名称的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该线程下该事件名称的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该线程下该事件名称的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该线程下该事件名称的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该线程下该事件名称的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该线程下该事件名称的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该线程下该事件名称的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该线程下该事件名称的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该线程下该事件名称的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该线程下该事件名称的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该线程下该事件名称的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该线程下该事件名称的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该线程下该事件名称的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该线程下该事件名称的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该线程下该事件名称的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该线程下该事件名称的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该线程下该事件名称的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该线程下该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该线程下该事件名称的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 该线程下该事件名称的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该线程下该事件名称的语句使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 该线程下该事件名称的语句执行的次要事件总次数。</li></ul><p>这些列提供了按线程和事件名称汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个主键<code>PRIMARY KEY (&#39;THREAD_ID&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个线程和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img36.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img37.avif"></p><h3 id="events-statements-summary-by-user-by-event-name"><a href="#events-statements-summary-by-user-by-event-name" class="headerlink" title="events_statements_summary_by_user_by_event_name"></a>events_statements_summary_by_user_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_by_user_by_event_name</code>表,用于按用户和事件名称汇总语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 执行语句的数据库用户名。</li><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>COUNT_STAR</strong>: 该用户下该事件名称的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该用户下该事件名称的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该用户下该事件名称的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该用户下该事件名称的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该用户下该事件名称的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 该用户下该事件名称的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 该用户下该事件名称的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 该用户下该事件名称的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 该用户下该事件名称的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 该用户下该事件名称的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 该用户下该事件名称的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 该用户下该事件名称的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 该用户下该事件名称的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 该用户下该事件名称的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 该用户下该事件名称的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 该用户下该事件名称的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 该用户下该事件名称的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 该用户下该事件名称的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 该用户下该事件名称的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 该用户下该事件名称的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 该用户下该事件名称的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 该用户下该事件名称的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 该用户下该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 该用户下该事件名称的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 该用户下该事件名称的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 该用户下该事件名称的语句使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 该用户下该事件名称的语句执行的次要事件总次数。</li></ul><p>这些列提供了按用户和事件名称汇总的语句执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY USER (&#39;USER&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个用户和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img38.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img39.avif"></p><h3 id="events-statements-summary-global-by-event-name"><a href="#events-statements-summary-global-by-event-name" class="headerlink" title="events_statements_summary_global_by_event_name"></a>events_statements_summary_global_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_statements_summary_global_by_event_name</code>表,用于按事件名称汇总全局语句事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>EVENT_NAME</strong>: 语句事件的名称,例如“statement”或“stage”。</li><li><strong>COUNT_STAR</strong>: 全局该事件名称的语句执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 全局该事件名称的语句总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 全局该事件名称的语句最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 全局该事件名称的语句平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 全局该事件名称的语句最大等待时间。</li><li><strong>SUM_LOCK_TIME</strong>: 全局该事件名称的语句总锁等待时间。</li><li><strong>SUM_ERRORS</strong>: 全局该事件名称的语句执行过程中发生的总错误数。</li><li><strong>SUM_WARNINGS</strong>: 全局该事件名称的语句执行过程中产生的总警告数。</li><li><strong>SUM_ROWS_AFFECTED</strong>: 全局该事件名称的语句影响的总行数。</li><li><strong>SUM_ROWS_SENT</strong>: 全局该事件名称的语句发送到客户端的总行数。</li><li><strong>SUM_ROWS_EXAMINED</strong>: 全局该事件名称的语句检查的总行数。</li><li><strong>SUM_CREATED_TMP_DISK_TABLES</strong>: 全局该事件名称的语句创建的临时磁盘表总数量。</li><li><strong>SUM_CREATED_TMP_TABLES</strong>: 全局该事件名称的语句创建的临时表总数量。</li><li><strong>SUM_SELECT_FULL_JOIN</strong>: 全局该事件名称的语句执行的全表连接总次数。</li><li><strong>SUM_SELECT_FULL_RANGE_JOIN</strong>: 全局该事件名称的语句执行的全范围连接总次数。</li><li><strong>SUM_SELECT_RANGE</strong>: 全局该事件名称的语句执行的范围扫描总次数。</li><li><strong>SUM_SELECT_RANGE_CHECK</strong>: 全局该事件名称的语句执行的范围检查总次数。</li><li><strong>SUM_SELECT_SCAN</strong>: 全局该事件名称的语句执行的全表扫描总次数。</li><li><strong>SUM_SORT_MERGE_PASSES</strong>: 全局该事件名称的语句执行的排序合并遍历总次数。</li><li><strong>SUM_SORT_RANGE</strong>: 全局该事件名称的语句执行的范围排序总次数。</li><li><strong>SUM_SORT_ROWS</strong>: 全局该事件名称的语句排序的总行数。</li><li><strong>SUM_SORT_SCAN</strong>: 全局该事件名称的语句执行的扫描排序总次数。</li><li><strong>SUM_NO_INDEX_USED</strong>: 全局该事件名称的语句没有使用索引的总次数。</li><li><strong>SUM_NO_GOOD_INDEX_USED</strong>: 全局该事件名称的语句没有使用合适索引的总次数。</li><li><strong>MAX_MEMORY_USED</strong>: 全局该事件名称的语句使用的最大内存。</li><li><strong>MAX_TOTAL_MEMORY</strong>: 全局该事件名称的语句使用的最大总内存。</li><li><strong>COUNT_SECONDARY</strong>: 全局该事件名称的语句执行的次要事件总次数。</li></ul><p>这些列提供了按事件名称汇总的全局语句执行统计信息,有助于分析和优化数据库性能。表中还有一个主键<code>PRIMARY KEY (&#39;EVENT_NAME&#39;)</code>,用于确保每个事件名称在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img40.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img41.avif"></p><h3 id="events-transactions-current"><a href="#events-transactions-current" class="headerlink" title="events_transactions_current"></a>events_transactions_current</h3><p>这个表是MySQL性能模式中的<code>events_transactions_current</code>表,用于记录当前活跃的事务信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 事务所属线程的ID。</li><li><strong>EVENT_ID</strong>: 事务事件的唯一标识符。</li><li><strong>END_EVENT_ID</strong>: 事务结束事件的唯一标识符。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>STATE</strong>: 事务的状态,可以是<code>ACTIVE</code> 活跃 、<code>COMMITTED</code> 已提交 或<code>ROLLED BACK</code> 已回滚 。</li><li><strong>TRX_ID</strong>: 事务的ID。</li><li><strong>GTID</strong>: 全局事务标识符 如果启用了GTID 。</li><li><strong>XID_FORMAT_ID</strong>: XID格式的ID 如果事务使用了XID 。</li><li><strong>XID</strong>: XID事务标识符 如果事务使用了XID 。</li><li><strong>XID_STATE</strong>: XID的状态。</li><li><strong>SOURCE</strong>: 事务的来源信息。</li><li><strong>TIMER_START</strong>: 事务开始的时间戳。</li><li><strong>TIMER_END</strong>: 事务结束的时间戳。</li><li><strong>TIMER_WAIT</strong>: 事务等待的时间。</li><li><strong>ACCESS_MODE</strong>: 事务的访问模式,可以是<code>READ ONLY</code> 只读 或<code>READ WRITE</code> 读写 。</li><li><strong>ISOLATION_LEVEL</strong>: 事务的隔离级别。</li><li><strong>AUTOCOMMIT</strong>: 指示事务是否为自动提交,可以是<code>YES</code>或<code>NO</code>。</li><li><strong>NUMBER OF SAVEPOINTS</strong>: 事务中设置的保存点数量。</li><li><strong>NUMBER OF ROLLBACK TO SAVEPOINT</strong>: 事务中回滚到保存点的次数。</li><li><strong>NUMBER OF RELEASE SAVEPOINT</strong>: 事务中释放保存点的次数。</li><li><strong>OBJECT_SCHEMA</strong>: 事务操作的对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 事务操作的对象名称。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的ID 如果有 。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,可以是<code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code>或<code>WAIT</code>。</li></ul><p>这些列提供了关于当前活跃事务的详细信息,有助于监控和分析数据库事务的性能和行为。表中还有一个主键<code>PRIMARY KEY (&#39;THREAD_ID&#39;, &#39;EVENT_ID&#39;)</code>,用于确保每个线程和事件ID的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img42.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img43.avif"></p><h3 id="events-transactions-history"><a href="#events-transactions-history" class="headerlink" title="events_transactions_history"></a>events_transactions_history</h3><p>这个表是MySQL性能模式中的<code>events_transactions_history</code>表,用于记录事务事件的历史信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行事务的线程ID。</li><li><strong>EVENT_ID</strong>: 事务事件的唯一标识符。</li><li><strong>END_EVENT_ID</strong>: 事务结束事件的唯一标识符。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>STATE</strong>: 事务的状态,可以是<code>ACTIVE</code> 活跃 、<code>COMMITTED</code> 已提交 或<code>ROLLED BACK</code> 已回滚 。</li><li><strong>TRX_ID</strong>: 事务的ID。</li><li><strong>GTID</strong>: 全局事务标识符 如果启用了GTID 。</li><li><strong>XID_FORMAT_ID</strong>: XID格式的ID 如果事务使用了XID 。</li><li><strong>XID</strong>: XID事务标识符 如果事务使用了XID 。</li><li><strong>XID_STATE</strong>: XID的状态。</li><li><strong>SOURCE</strong>: 事务的来源信息。</li><li><strong>TIMER_START</strong>: 事务开始的时间戳。</li><li><strong>TIMER_END</strong>: 事务结束的时间戳。</li><li><strong>TIMER_WAIT</strong>: 事务等待的时间。</li><li><strong>ACCESS_MODE</strong>: 事务的访问模式,可以是<code>READ ONLY</code> 只读 或<code>READ WRITE</code> 读写 。</li><li><strong>ISOLATION_LEVEL</strong>: 事务的隔离级别。</li><li><strong>AUTOCOMMIT</strong>: 指示事务是否为自动提交,可以是<code>YES</code>或<code>NO</code>。</li><li><strong>NUMBER OF SAVEPOINTS</strong>: 事务中设置的保存点数量。</li><li><strong>NUMBER OF ROLLBACK TO SAVEPOINT</strong>: 事务中回滚到保存点的次数。</li><li><strong>NUMBER OF RELEASE SAVEPOINT</strong>: 事务中释放保存点的次数。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 事务开始时对象实例的ID。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的ID 如果有 。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,可以是<code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code>或<code>WAIT</code>。</li></ul><p>这些列提供了关于历史事务的详细信息,有助于分析和优化数据库事务的性能和行为。表中还有一个主键<code>PRIMARY KEY (&#39;THREAD_ID&#39;, &#39;EVENT_ID&#39;)</code>,用于确保每个线程和事件ID的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img44.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img45.avif"></p><h3 id="events-transactions-history-long"><a href="#events-transactions-history-long" class="headerlink" title="events_transactions_history_long"></a>events_transactions_history_long</h3><p>这个表是MySQL性能模式中的<code>events_transactions_history_long</code>表,用于记录长时间运行的事务事件的历史信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行事务的线程ID。</li><li><strong>EVENT_ID</strong>: 事务事件的唯一标识符。</li><li><strong>END_EVENT_ID</strong>: 事务结束事件的唯一标识符。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>STATE</strong>: 事务的状态,可以是<code>ACTIVE</code> 活跃 、<code>COMMITTED</code> 已提交 或<code>ROLLED BACK</code> 已回滚 。</li><li><strong>TRX_ID</strong>: 事务的ID。</li><li><strong>GTID</strong>: 全局事务标识符 如果启用了GTID 。</li><li><strong>XID_FORMAT_ID</strong>: XID格式的ID 如果事务使用了XID 。</li><li><strong>XID</strong>: XID事务标识符 如果事务使用了XID 。</li><li><strong>XID_STATE</strong>: XID的状态。</li><li><strong>SOURCE</strong>: 事务的来源信息。</li><li><strong>TIMER_START</strong>: 事务开始的时间戳。</li><li><strong>TIMER_END</strong>: 事务结束的时间戳。</li><li><strong>TIMER_WAIT</strong>: 事务等待的时间。</li><li><strong>ACCESS_MODE</strong>: 事务的访问模式,可以是<code>READ ONLY</code> 只读 或<code>READ WRITE</code> 读写 。</li><li><strong>ISOLATION_LEVEL</strong>: 事务的隔离级别。</li><li><strong>AUTOCOMMIT</strong>: 指示事务是否为自动提交,可以是<code>YES</code>或<code>NO</code>。</li><li><strong>NUMBER OF SAVEPOINTS</strong>: 事务中设置的保存点数量。</li><li><strong>NUMBER OF ROLLBACK TO SAVEPOINT</strong>: 事务中回滚到保存点的次数。</li><li><strong>NUMBER OF RELEASE SAVEPOINT</strong>: 事务中释放保存点的次数。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 事务开始时对象实例的ID。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的ID 如果有 。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,可以是<code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code>或<code>WAIT</code>。</li></ul><p>这些列提供了关于历史事务的详细信息,有助于分析和优化数据库事务的性能和行为。表中还有一个主键<code>PRIMARY KEY (&#39;THREAD_ID&#39;, &#39;EVENT_ID&#39;)</code>,用于确保每个线程和事件ID的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img46.avif"></p><h3 id="events-transactions-summary-by-account-by-event-name"><a href="#events-transactions-summary-by-account-by-event-name" class="headerlink" title="events_transactions_summary_by_account_by_event_name"></a>events_transactions_summary_by_account_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_transactions_summary_by_account_by_event_name</code>表,用于按账户和事件名称汇总事务事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 执行事务的数据库用户名。</li><li><strong>HOST</strong>: 执行事务的主机名或IP地址。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>COUNT_STAR</strong>: 该账户下该事件名称的事务执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该账户下该事件名称的事务总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该账户下该事件名称的事务最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该账户下该事件名称的事务平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该账户下该事件名称的事务最大等待时间。</li><li><strong>COUNT_READ_WRITE</strong>: 该账户下该事件名称的读写事务执行次数。</li><li><strong>SUM_TIMER_READ_WRITE</strong>: 该账户下该事件名称的读写事务总等待时间。</li><li><strong>MIN_TIMER_READ_WRITE</strong>: 该账户下该事件名称的读写事务最小等待时间。</li><li><strong>AVG_TIMER_READ_WRITE</strong>: 该账户下该事件名称的读写事务平均等待时间。</li><li><strong>MAX_TIMER_READ_WRITE</strong>: 该账户下该事件名称的读写事务最大等待时间。</li><li><strong>COUNT_READ_ONLY</strong>: 该账户下该事件名称的只读事务执行次数。</li><li><strong>SUM_TIMER_READ_ONLY</strong>: 该账户下该事件名称的只读事务总等待时间。</li><li><strong>MIN_TIMER_READ_ONLY</strong>: 该账户下该事件名称的只读事务最小等待时间。</li><li><strong>AVG_TIMER_READ_ONLY</strong>: 该账户下该事件名称的只读事务平均等待时间。</li><li><strong>MAX_TIMER_READ_ONLY</strong>: 该账户下该事件名称的只读事务最大等待时间。</li></ul><p>这些列提供了按账户和事件名称汇总的事务执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY ACCOUNT (&#39;USER&#39;, &#39;HOST&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个账户、主机和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img47.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img48.avif"></p><h3 id="events-transactions-summary-by-host-by-event-name"><a href="#events-transactions-summary-by-host-by-event-name" class="headerlink" title="events_transactions_summary_by_host_by_event_name"></a>events_transactions_summary_by_host_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_transactions_summary_by_host_by_event_name</code>表,用于按主机和事件名称汇总事务事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>HOST</strong>: 执行事务的主机名或IP地址。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>COUNT_STAR</strong>: 该主机下该事件名称的事务执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该主机下该事件名称的事务总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该主机下该事件名称的事务最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该主机下该事件名称的事务平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该主机下该事件名称的事务最大等待时间。</li><li><strong>COUNT_READ_WRITE</strong>: 该主机下该事件名称的读写事务执行次数。</li><li><strong>SUM_TIMER_READ_WRITE</strong>: 该主机下该事件名称的读写事务总等待时间。</li><li><strong>MIN_TIMER_READ_WRITE</strong>: 该主机下该事件名称的读写事务最小等待时间。</li><li><strong>AVG_TIMER_READ_WRITE</strong>: 该主机下该事件名称的读写事务平均等待时间。</li><li><strong>MAX_TIMER_READ_WRITE</strong>: 该主机下该事件名称的读写事务最大等待时间。</li><li><strong>COUNT_READ_ONLY</strong>: 该主机下该事件名称的只读事务执行次数。</li><li><strong>SUM_TIMER_READ_ONLY</strong>: 该主机下该事件名称的只读事务总等待时间。</li><li><strong>MIN_TIMER_READ_ONLY</strong>: 该主机下该事件名称的只读事务最小等待时间。</li><li><strong>AVG_TIMER_READ_ONLY</strong>: 该主机下该事件名称的只读事务平均等待时间。</li><li><strong>MAX_TIMER_READ_ONLY</strong>: 该主机下该事件名称的只读事务最大等待时间。</li></ul><p>这些列提供了按主机和事件名称汇总的事务执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY (&#39;HOST&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个主机和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img49.avif"></p><h3 id="events-transactions-summary-by-thread-by-event-name"><a href="#events-transactions-summary-by-thread-by-event-name" class="headerlink" title="events_transactions_summary_by_thread_by_event_name"></a>events_transactions_summary_by_thread_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_transactions_summary_by_thread_by_event_name</code>表,用于按线程和事件名称汇总事务事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 执行事务的线程ID。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>COUNT_STAR</strong>: 该线程下该事件名称的事务执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该线程下该事件名称的事务总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该线程下该事件名称的事务最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该线程下该事件名称的事务平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该线程下该事件名称的事务最大等待时间。</li><li><strong>COUNT_READ_WRITE</strong>: 该线程下该事件名称的读写事务执行次数。</li><li><strong>SUM_TIMER_READ_WRITE</strong>: 该线程下该事件名称的读写事务总等待时间。</li><li><strong>MIN_TIMER_READ_WRITE</strong>: 该线程下该事件名称的读写事务最小等待时间。</li><li><strong>AVG_TIMER_READ_WRITE</strong>: 该线程下该事件名称的读写事务平均等待时间。</li><li><strong>MAX_TIMER_READ_WRITE</strong>: 该线程下该事件名称的读写事务最大等待时间。</li><li><strong>COUNT_READ_ONLY</strong>: 该线程下该事件名称的只读事务执行次数。</li><li><strong>SUM_TIMER_READ_ONLY</strong>: 该线程下该事件名称的只读事务总等待时间。</li><li><strong>MIN_TIMER_READ_ONLY</strong>: 该线程下该事件名称的只读事务最小等待时间。</li><li><strong>AVG_TIMER_READ_ONLY</strong>: 该线程下该事件名称的只读事务平均等待时间。</li><li><strong>MAX_TIMER_READ_ONLY</strong>: 该线程下该事件名称的只读事务最大等待时间。</li></ul><p>这些列提供了按线程和事件名称汇总的事务执行统计信息,有助于分析和优化数据库性能。表中还有一个主键<code>PRIMARY KEY (&#39;THREAD_ID&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个线程和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img50.avif"></p><h3 id="events-transactions-summary-by-user-by-event-name"><a href="#events-transactions-summary-by-user-by-event-name" class="headerlink" title="events_transactions_summary_by_user_by_event_name"></a>events_transactions_summary_by_user_by_event_name</h3><p>这个表是MySQL性能模式中的<code>events_transactions_summary_by_user_by_event_name</code>表,用于按用户和事件名称汇总事务事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 执行事务的数据库用户名。</li><li><strong>EVENT_NAME</strong>: 事务事件的名称。</li><li><strong>COUNT_STAR</strong>: 该用户下该事件名称的事务执行总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 该用户下该事件名称的事务总等待时间。</li><li><strong>MIN_TIMER_WAIT</strong>: 该用户下该事件名称的事务最小等待时间。</li><li><strong>AVG_TIMER_WAIT</strong>: 该用户下该事件名称的事务平均等待时间。</li><li><strong>MAX_TIMER_WAIT</strong>: 该用户下该事件名称的事务最大等待时间。</li><li><strong>COUNT_READ_WRITE</strong>: 该用户下该事件名称的读写事务执行次数。</li><li><strong>SUM_TIMER_READ_WRITE</strong>: 该用户下该事件名称的读写事务总等待时间。</li><li><strong>MIN_TIMER_READ_WRITE</strong>: 该用户下该事件名称的读写事务最小等待时间。</li><li><strong>AVG_TIMER_READ_WRITE</strong>: 该用户下该事件名称的读写事务平均等待时间。</li><li><strong>MAX_TIMER_READ_WRITE</strong>: 该用户下该事件名称的读写事务最大等待时间。</li><li><strong>COUNT_READ_ONLY</strong>: 该用户下该事件名称的只读事务执行次数。</li><li><strong>SUM_TIMER_READ_ONLY</strong>: 该用户下该事件名称的只读事务总等待时间。</li><li><strong>MIN_TIMER_READ_ONLY</strong>: 该用户下该事件名称的只读事务最小等待时间。</li><li><strong>AVG_TIMER_READ_ONLY</strong>: 该用户下该事件名称的只读事务平均等待时间。</li><li><strong>MAX_TIMER_READ_ONLY</strong>: 该用户下该事件名称的只读事务最大等待时间。</li></ul><p>这些列提供了按用户和事件名称汇总的事务执行统计信息,有助于分析和优化数据库性能。表中还有一个唯一键<code>UNIQUE KEY (&#39;USER&#39;, &#39;EVENT_NAME&#39;)</code>,用于确保每个用户和事件名称的组合在表中是唯一的。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img51.avif"></p><h3 id="events-transactions-summary-global-by-event-name"><a href="#events-transactions-summary-global-by-event-name" class="headerlink" title="events_transactions_summary_global_by_event_name"></a>events_transactions_summary_global_by_event_name</h3><p>这个表名为 <code>events_transactions_summary_global_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于汇总事务事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>EVENT_NAME</strong>: 事务事件的名称,表示事务的类型或名称。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li><li><strong>COUNT_READ_WRITE</strong>: 读和写操作的总次数。</li><li><strong>SUM_TIMER_READ_WRITE</strong>: 所有读和写操作的总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_READ_WRITE</strong>: 单个读和写操作的最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_READ_WRITE</strong>: 单个读和写操作的平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_READ_WRITE</strong>: 单个读和写操作的最大时间,以毫秒为单位。</li><li><strong>COUNT_READ_ONLY</strong>: 只读操作的总次数。</li><li><strong>SUM_TIMER_READ_ONLY</strong>: 所有只读操作的总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_READ_ONLY</strong>: 单个只读操作的最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_READ_ONLY</strong>: 单个只读操作的平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_READ_ONLY</strong>: 单个只读操作的最大时间,以毫秒为单位。</li></ul><p>这个表通过汇总事务事件的统计信息,帮助数据库管理员分析和优化数据库性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img52.avif"></p><h3 id="events-waits-current"><a href="#events-waits-current" class="headerlink" title="events_waits_current"></a>events_waits_current</h3><p>这个表名为 <code>events_waits_current</code>,是 MySQL Performance Schema 中的一个表,用于记录当前正在等待的事件的详细信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 线程的唯一标识符,表示正在执行的线程。</li><li><strong>EVENT_ID</strong>: 事件的唯一标识符,表示正在等待的事件。</li><li><strong>END_EVENT_ID</strong>: 事件结束的唯一标识符,表示等待事件的结束。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>SOURCE</strong>: 事件的来源,表示事件的来源信息。</li><li><strong>TIMER_START</strong>: 等待事件开始的时间戳,表示等待开始的时间。</li><li><strong>TIMER_END</strong>: 等待事件结束的时间戳,表示等待结束的时间。</li><li><strong>TIMER_WAIT</strong>: 等待事件的总时间,以毫秒为单位,表示等待的总时间。</li><li><strong>SPINS</strong>: 等待事件的自旋次数,表示线程在等待过程中自旋的次数。</li><li><strong>OBJECT_SCHEMA</strong>: 对象的模式名称,表示等待的对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 对象的名称,表示正在等待的对象名称。</li><li><strong>INDEX_NAME</strong>: 索引的名称,表示正在等待的索引名称。</li><li><strong>OBJECT_TYPE</strong>: 对象的类型,表示正在等待的对象类型。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始地址,表示对象实例的内存地址。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的唯一标识符,表示嵌套的等待事件。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,表示嵌套的等待事件类型,可以是 <code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code> 或 <code>WAIT</code>。</li><li><strong>OPERATION</strong>: 操作的名称,表示正在执行的操作。</li><li><strong>NUMBER_OF_BYTES</strong>: 字节数,表示操作涉及的字节数。</li><li><strong>FLAGS</strong>: 标志,表示事件的附加信息或标志。</li></ul><p>这个表通过记录当前正在等待的事件的详细信息,帮助数据库管理员分析和优化数据库性能,特别是了解线程等待的原因和等待时间。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img53.avif"></p><h3 id="events-waits-history"><a href="#events-waits-history" class="headerlink" title="events_waits_history"></a>events_waits_history</h3><p>这个表名为 <code>events_waits_history</code>,是 MySQL Performance Schema 中的一个表,用于记录线程等待事件的历史信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 线程的唯一标识符,表示执行等待操作的线程。</li><li><strong>EVENT_ID</strong>: 事件的唯一标识符,表示具体的等待事件。</li><li><strong>END_EVENT_ID</strong>: 事件结束的唯一标识符,表示等待事件结束的标识。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>SOURCE</strong>: 事件的来源,表示事件的来源信息。</li><li><strong>TIMER_START</strong>: 等待事件开始的时间戳,表示等待开始的时间。</li><li><strong>TIMER_END</strong>: 等待事件结束的时间戳,表示等待结束的时间。</li><li><strong>TIMER_WAIT</strong>: 等待事件的总时间,以毫秒为单位,表示等待的总时间。</li><li><strong>SPINS</strong>: 等待事件的自旋次数,表示线程在等待过程中自旋的次数。</li><li><strong>OBJECT_SCHEMA</strong>: 对象的模式名称,表示等待的对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 对象的名称,表示正在等待的对象名称。</li><li><strong>INDEX_NAME</strong>: 索引的名称,表示正在等待的索引名称。</li><li><strong>OBJECT_TYPE</strong>: 对象的类型,表示正在等待的对象类型。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始地址,表示对象实例的内存地址。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的唯一标识符,表示嵌套的等待事件。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,表示嵌套的等待事件类型,可以是 <code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code> 或 <code>WAIT</code>。</li><li><strong>OPERATION</strong>: 操作的名称,表示正在执行的操作。</li><li><strong>NUMBER_OF_BYTES</strong>: 字节数,表示操作涉及的字节数。</li><li><strong>FLAGS</strong>: 标志,表示事件的附加信息或标志。</li></ul><p>这个表通过记录线程等待事件的历史信息,帮助数据库管理员分析和优化数据库性能,特别是了解线程等待的原因和等待时间。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img54.avif"></p><h3 id="events-waits-history-long"><a href="#events-waits-history-long" class="headerlink" title="events_waits_history_long"></a>events_waits_history_long</h3><p>这个表名为 <code>events_waits_history_long</code>,是 MySQL Performance Schema 中的一个表,用于记录长时间运行的等待事件的历史信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 线程的唯一标识符,表示执行等待操作的线程。</li><li><strong>EVENT_ID</strong>: 事件的唯一标识符,表示具体的等待事件。</li><li><strong>END_EVENT_ID</strong>: 事件结束的唯一标识符,表示等待事件结束的标识。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>SOURCE</strong>: 事件的来源,表示事件的来源信息。</li><li><strong>TIMER_START</strong>: 等待事件开始的时间戳,表示等待开始的时间。</li><li><strong>TIMER_END</strong>: 等待事件结束的时间戳,表示等待结束的时间。</li><li><strong>TIMER_WAIT</strong>: 等待事件的总时间,以毫秒为单位,表示等待的总时间。</li><li><strong>SPINS</strong>: 等待事件的自旋次数,表示线程在等待过程中自旋的次数。</li><li><strong>OBJECT_SCHEMA</strong>: 对象的模式名称,表示等待的对象所在的数据库模式。</li><li><strong>OBJECT_NAME</strong>: 对象的名称,表示正在等待的对象名称。</li><li><strong>INDEX_NAME</strong>: 索引的名称,表示正在等待的索引名称。</li><li><strong>OBJECT_TYPE</strong>: 对象的类型,表示正在等待的对象类型。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始地址,表示对象实例的内存地址。</li><li><strong>NESTING_EVENT_ID</strong>: 嵌套事件的唯一标识符,表示嵌套的等待事件。</li><li><strong>NESTING_EVENT_TYPE</strong>: 嵌套事件的类型,表示嵌套的等待事件类型,可以是 <code>TRANSACTION</code>、<code>STATEMENT</code>、<code>STAGE</code> 或 <code>WAIT</code>。</li><li><strong>OPERATION</strong>: 操作的名称,表示正在执行的操作。</li><li><strong>NUMBER_OF_BYTES</strong>: 字节数,表示操作涉及的字节数。</li><li><strong>FLAGS</strong>: 标志,表示事件的附加信息或标志。</li></ul><p>这个表通过记录长时间运行的等待事件的历史信息,帮助数据库管理员分析和优化数据库性能,特别是了解线程等待的原因和等待时间。与 <code>events_waits_history</code> 表相比,这个表可能包含更多详细信息,或者用于存储更长时间范围内的数据。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img55.avif"></p><h3 id="events-waits-summary-by-account-by-event-name"><a href="#events-waits-summary-by-account-by-event-name" class="headerlink" title="events_waits_summary_by_account_by_event_name"></a>events_waits_summary_by_account_by_event_name</h3><p>这个表名为 <code>events_waits_summary_by_account_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按账户和事件名称汇总等待事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 用户名,表示执行等待操作的数据库用户。</li><li><strong>HOST</strong>: 主机名,表示执行等待操作的客户端主机。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个事务事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总按账户和事件名称的等待事件统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同用户和主机上的等待事件情况。通过这些信息,管理员可以识别出性能瓶颈和优化点。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img56.avif"></p><h3 id="events-waits-summary-by-host-by-event-name"><a href="#events-waits-summary-by-host-by-event-name" class="headerlink" title="events_waits_summary_by_host_by_event_name"></a>events_waits_summary_by_host_by_event_name</h3><p>这个表名为 <code>events_waits_summary_by_host_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按主机和事件名称汇总等待事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>HOST</strong>: 主机名,表示执行等待操作的客户端主机。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个事务事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总按主机和事件名称的等待事件统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同主机上的等待事件情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个主机的等待时间特别长,可能需要检查该主机的网络连接或数据库配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img57.avif"></p><h3 id="events-waits-summary-by-instance"><a href="#events-waits-summary-by-instance" class="headerlink" title="events_waits_summary_by_instance"></a>events_waits_summary_by_instance</h3><p>这个表名为 <code>events_waits_summary_by_instance</code>,是 MySQL Performance Schema 中的一个表,用于按实例汇总等待事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始地址,表示对象实例的内存地址。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个事务事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总按实例的等待事件统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同实例上的等待事件情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个实例的等待时间特别长,可能需要检查该实例的资源使用情况或配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img58.avif"></p><h3 id="events-waits-summary-by-thread-by-event-name"><a href="#events-waits-summary-by-thread-by-event-name" class="headerlink" title="events_waits_summary_by_thread_by_event_name"></a>events_waits_summary_by_thread_by_event_name</h3><p>这个表名为 <code>events_waits_summary_by_thread_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按线程和事件名称汇总等待事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 线程的唯一标识符,表示执行等待操作的线程。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个事务事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总按线程和事件名称的等待事件统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同线程上的等待事件情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个线程的等待时间特别长,可能需要检查该线程的执行逻辑或资源使用情况。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img59.avif"></p><h3 id="events-waits-summary-by-user-by-event-name"><a href="#events-waits-summary-by-user-by-event-name" class="headerlink" title="events_waits_summary_by_user_by_event_name"></a>events_waits_summary_by_user_by_event_name</h3><p>这个表名为 <code>events_waits_summary_by_user_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按用户和事件名称汇总等待事件的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 用户名,表示执行等待操作的数据库用户。</li><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>COUNT_STAR</strong>: 事务事件的总次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有事务事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个事务事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个事务事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个事务事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总按用户和事件名称的等待事件统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同用户上的等待事件情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个用户的等待时间特别长,可能需要检查该用户的查询效率或资源使用情况。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img60.avif"></p><h3 id="events-waits-summary-global-by-event-name"><a href="#events-waits-summary-global-by-event-name" class="headerlink" title="events_waits_summary_global_by_event_name"></a>events_waits_summary_global_by_event_name</h3><p>这个表名为 <code>events_waits_summary_global_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于全局汇总不同事件的等待统计信息。以下是表中每一列的含义:</p><ul><li><strong>EVENT_NAME</strong>: 等待事件的名称,表示正在等待的事件类型。</li><li><strong>COUNT_STAR</strong>: 该事件的总发生次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有该事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个该事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个该事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个该事件的最大等待时间,以毫秒为单位。</li></ul><p>这个表通过汇总所有事件的等待统计信息,帮助数据库管理员分析整个数据库实例的等待事件性能,识别可能的性能瓶颈和优化点。例如,如果某个事件的 <code>MAX_TIMER_WAIT</code> 值特别高,可能表明存在性能问题,需要进一步调查和优化。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img61.avif"></p><h3 id="file-instances"><a href="#file-instances" class="headerlink" title="file_instances"></a>file_instances</h3><p>这个表名为 <code>file_instances</code>,是 MySQL Performance Schema 中的一个表,用于记录文件实例的信息。以下是表中每一列的含义:</p><ul><li><strong>FILE_NAME</strong>: 文件的名称,表示被访问的文件的路径和名称。</li><li><strong>EVENT_NAME</strong>: 事件的名称,表示与文件操作相关的事件类型。</li><li><strong>OPEN_COUNT</strong>: 打开文件的次数,表示该文件被打开的总次数。</li></ul><p>这个表通过记录文件实例的信息,帮助数据库管理员了解数据库服务器对文件的访问情况,包括哪些文件被频繁访问以及它们的打开次数。这些信息可以用于性能分析和优化,例如,如果发现某个文件被频繁打开,可能需要检查相关的数据库操作是否高效,或者是否需要对文件进行缓存以提高性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img62.avif"></p><h3 id="file-summary-by-event-name"><a href="#file-summary-by-event-name" class="headerlink" title="file_summary_by_event_name"></a>file_summary_by_event_name</h3><p>这个表名为 <code>file_summary_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按事件名称汇总文件操作的统计信息。以下是表中每一列的含义:</p><ul><li><strong>EVENT_NAME</strong>: 事件的名称,表示文件操作相关的事件类型。</li><li><strong>COUNT_STAR</strong>: 该事件的总发生次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有该事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个该事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个该事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个该事件的最大等待时间,以毫秒为单位。</li><li><strong>COUNT_READ</strong>: 该事件的读操作次数。</li><li><strong>SUM_TIMER_READ</strong>: 所有该事件的读操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_READ</strong>: 单个该事件的读操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_READ</strong>: 单个该事件的读操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_READ</strong>: 单个该事件的读操作最大时间,以毫秒为单位。</li><li><strong>SUM_NUMBER_OF_BYTES_READ</strong>: 所有该事件的读操作总字节数。</li><li><strong>COUNT_WRITE</strong>: 该事件的写操作次数。</li><li><strong>SUM_TIMER_WRITE</strong>: 所有该事件的写操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WRITE</strong>: 单个该事件的写操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WRITE</strong>: 单个该事件的写操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WRITE</strong>: 单个该事件的写操作最大时间,以毫秒为单位。</li><li><strong>SUM_NUMBER_OF_BYTES_WRITE</strong>: 所有该事件的写操作总字节数。</li><li><strong>COUNT_MISC</strong>: 该事件的其他操作次数。</li><li><strong>SUM_TIMER_MISC</strong>: 所有该事件的其他操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_MISC</strong>: 单个该事件的其他操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_MISC</strong>: 单个该事件的其他操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_MISC</strong>: 单个该事件的其他操作最大时间,以毫秒为单位。</li></ul><p>这个表通过汇总按事件名称的文件操作统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同文件操作的等待时间和数据传输情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个事件的 <code>MAX_TIMER_WAIT</code> 值特别高,可能表明存在性能问题,需要进一步调查和优化。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img63.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img64.avif"></p><h3 id="file-summary-by-instance"><a href="#file-summary-by-instance" class="headerlink" title="file_summary_by_instance"></a>file_summary_by_instance</h3><p>这个表名为 <code>file_summary_by_instance</code>,是 MySQL Performance Schema 中的一个表,用于按文件实例汇总文件操作的统计信息。以下是表中每一列的含义:</p><ul><li><strong>FILE_NAME</strong>: 文件的名称,表示被访问的文件的路径和名称。</li><li><strong>EVENT_NAME</strong>: 事件的名称,表示文件操作相关的事件类型。</li><li><strong>OBJECT_INSTANCE_BEGIN</strong>: 对象实例的开始地址,表示对象实例的内存地址。</li><li><strong>COUNT_STAR</strong>: 该事件的总发生次数,即该事件被触发的总次数。</li><li><strong>SUM_TIMER_WAIT</strong>: 所有该事件的总等待时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WAIT</strong>: 单个该事件的最小等待时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WAIT</strong>: 单个该事件的平均等待时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WAIT</strong>: 单个该事件的最大等待时间,以毫秒为单位。</li><li><strong>COUNT_READ</strong>: 该事件的读操作次数。</li><li><strong>SUM_TIMER_READ</strong>: 所有该事件的读操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_READ</strong>: 单个该事件的读操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_READ</strong>: 单个该事件的读操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_READ</strong>: 单个该事件的读操作最大时间,以毫秒为单位。</li><li><strong>SUM_NUMBER_OF_BYTES_READ</strong>: 所有该事件的读操作总字节数。</li><li><strong>COUNT_WRITE</strong>: 该事件的写操作次数。</li><li><strong>SUM_TIMER_WRITE</strong>: 所有该事件的写操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_WRITE</strong>: 单个该事件的写操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_WRITE</strong>: 单个该事件的写操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_WRITE</strong>: 单个该事件的写操作最大时间,以毫秒为单位。</li><li><strong>SUM_NUMBER_OF_BYTES_WRITE</strong>: 所有该事件的写操作总字节数。</li><li><strong>COUNT_MISC</strong>: 该事件的其他操作次数。</li><li><strong>SUM_TIMER_MISC</strong>: 所有该事件的其他操作总时间,以毫秒为单位。</li><li><strong>MIN_TIMER_MISC</strong>: 单个该事件的其他操作最小时间,以毫秒为单位。</li><li><strong>AVG_TIMER_MISC</strong>: 单个该事件的其他操作平均时间,以毫秒为单位。</li><li><strong>MAX_TIMER_MISC</strong>: 单个该事件的其他操作最大时间,以毫秒为单位。</li></ul><p>这个表通过汇总按文件实例的文件操作统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同文件实例上的文件操作情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个文件实例的 <code>MAX_TIMER_WAIT</code> 值特别高,可能表明存在性能问题,需要进一步调查和优化。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img65.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img66.avif"></p><h3 id="global-status"><a href="#global-status" class="headerlink" title="global_status"></a>global_status</h3><p>这个表名为 <code>global_status</code>,是 MySQL Performance Schema 中的一个表,用于显示全局服务器状态信息。以下是表中每一列的含义:</p><ul><li><strong>VARIABLE_NAME</strong>: 变量的名称,表示服务器状态的特定指标。</li><li><strong>VARIABLE_VALUE</strong>: 变量的值,表示对应 <code>VARIABLE_NAME</code> 的具体数值。</li></ul><p>这个表通过记录服务器的全局状态信息,帮助数据库管理员了解数据库服务器的当前运行状态。例如,<code>Aborted_clients</code> 表示由于各种错误 如网络问题、超时等 被中断的客户端连接数。这些信息可以用于监控和诊断数据库服务器的性能问题。</p><p>在你提供的查询结果中,<code>Aborted_clients</code> 的值为 13,这意味着有 13 个客户端连接由于错误而被中断。这些信息可以帮助管理员识别可能的网络问题或配置问题,从而采取相应的措施来提高数据库的稳定性和性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img67.avif"></p><h3 id="global-variables"><a href="#global-variables" class="headerlink" title="global_variables"></a>global_variables</h3><p>这个表名为 <code>global_variables</code>,是 MySQL Performance Schema 中的一个表,用于显示全局变量的当前设置。以下是表中每一列的含义:</p><ul><li><strong>VARIABLE_NAME</strong>: 变量的名称,表示服务器配置的特定选项。</li><li><strong>VARIABLE_VALUE</strong>: 变量的值,表示对应 <code>VARIABLE_NAME</code> 的具体设置。</li></ul><p>这个表通过记录服务器的全局变量设置,帮助数据库管理员了解和管理系统的配置。例如,<code>activate_all_roles_on_login</code> 变量控制是否在用户</p><p>在你提供的查询结果中,<code>activate_all_roles_on_login</code> 的值为 <code>OFF</code>,这意味着在用户</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img68.avif"></p><h3 id="host-cache"><a href="#host-cache" class="headerlink" title="host_cache"></a>host_cache</h3><p>这个表名为 <code>host_cache</code>,是 MySQL Performance Schema 中的一个表,用于记录客户端主机的缓存信息。以下是表中每一列的含义:</p><ul><li><strong>IP</strong>: 客户端主机的 IP 地址。</li><li><strong>HOST</strong>: 客户端主机的名称,可以是主机名或 IP 地址。</li><li><strong>COUNT_VALIDATED</strong>: 验证次数,表示该主机名是否已通过验证的次数。</li><li><strong>COUNT_HOST_BLOCKED_ERRORS</strong>: 被阻止错误次数,表示由于主机名解析问题导致连接被阻止的次数。</li><li><strong>COUNT_NAMEINFO_TRANSIENT_ERRORS</strong>: 临时错误次数,表示在获取主机信息时遇到的临时错误次数。</li><li><strong>COUNT_NAMEINFO_PERMANENT_ERRORS</strong>: 永久错误次数,表示在获取主机信息时遇到的永久错误次数。</li><li><strong>COUNT_FORMAT_ERRORS</strong>: 格式错误次数,表示由于格式问题导致的错误次数。</li><li><strong>COUNT_ADDRINFO_TRANSIENT_ERRORS</strong>: 地址信息临时错误次数,表示在获取地址信息时遇到的临时错误次数。</li><li><strong>COUNT_ADDRINFO_PERMANENT_ERRORS</strong>: 地址信息永久错误次数,表示在获取地址信息时遇到的永久错误次数。</li><li><strong>COUNT_FCDNS_ERRORS</strong>: 全称 DNS 错误次数,表示在获取全称 DNS 时遇到的错误次数。</li><li><strong>COUNT_HOST_ACL_ERRORS</strong>: 主机访问控制错误次数,表示由于访问控制列表 ACL 导致的错误次数。</li><li><strong>COUNT_NO_AUTH_PLUGIN_ERRORS</strong>: 无认证插件错误次数,表示由于缺少认证插件导致的错误次数。</li><li><strong>COUNT_AUTH_PLUGIN_ERRORS</strong>: 认证插件错误次数,表示由于认证插件导致的错误次数。</li><li><strong>COUNT_HANDSHAKE_ERRORS</strong>: 握手错误次数,表示在 SSL&#x2F;TLS 握手过程中遇到的错误次数。</li><li><strong>COUNT_PROXY_USER_ACL_ERRORS</strong>: 代理用户访问控制错误次数,表示由于代理用户访问控制列表 ACL 导致的错误次数。</li><li><strong>COUNT_AUTHENTICATION_ERRORS</strong>: 认证错误次数,表示由于认证失败导致的错误次数。</li><li><strong>COUNT_SSL_ERRORS</strong>: SSL 错误次数,表示由于 SSL&#x2F;TLS 配置问题导致的错误次数。</li><li><strong>COUNT_MAX_USER_CONNECTIONS_ERRORS</strong>: 最大用户连接错误次数,表示由于达到最大用户连接数限制导致的错误次数。</li><li><strong>COUNT_MAX_USER_CONNECTIONS_PER_HOUR_ERRORS</strong>: 每小时最大用户连接错误次数,表示由于达到每小时最大用户连接数限制导致的错误次数。</li><li><strong>COUNT_DEFAULT_DATABASE_ERRORS</strong>: 默认数据库错误次数,表示由于默认数据库配置问题导致的错误次数。</li><li><strong>COUNT_INIT_CONNECT_ERRORS</strong>: 初始化连接错误次数,表示在初始化连接时遇到的错误次数。</li><li><strong>COUNT_LOCAL_ERRORS</strong>: 本地错误次数,表示由于本地配置问题导致的错误次数。</li><li><strong>COUNT_UNKNOWN_ERRORS</strong>: 未知错误次数,表示由于未知原因导致的错误次数。</li><li><strong>FIRST_SEEN</strong>: 首次出现时间,表示该主机首次出现错误的时间戳。</li><li><strong>LAST_SEEN</strong>: 最后一次出现时间,表示该主机最后一次出现错误的时间戳。</li><li><strong>FIRST_ERROR_SEEN</strong>: 首次错误时间,表示该主机首次出现错误的时间戳。</li><li><strong>LAST_ERROR_SEEN</strong>: 最后一次错误时间,表示该主机最后一次出现错误的时间戳。</li></ul><p>这个表通过记录客户端主机的缓存信息和错误统计,帮助数据库管理员分析和诊断连接问题,特别是了解不同主机上的连接错误情况。通过这些信息,管理员可以识别出性能瓶颈和优化点,例如,如果某个主机的 <code>COUNT_HOST_BLOCKED_ERRORS</code> 值特别高,可能需要检查该主机的网络连接或数据库配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img69.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img70.avif"></p><h3 id="hosts"><a href="#hosts" class="headerlink" title="hosts"></a>hosts</h3><p>这个表名为 <code>hosts</code>,是 MySQL Performance Schema 中的一个表,用于记录与数据库服务器连接的主机信息。以下是表中每一列的含义:</p><ul><li><strong>HOST</strong>: 主机名或 IP 地址,表示连接到数据库服务器的客户端主机。</li><li><strong>CURRENT_CONNECTIONS</strong>: 当前连接数,表示当前从该主机到数据库服务器的活跃连接数量。</li><li><strong>TOTAL_CONNECTIONS</strong>: 总连接数,表示从该主机到数据库服务器的连接总次数。</li><li><strong>MAX_SESSION_CONTROLLED_MEMORY</strong>: 最大会话控制内存,表示从该主机连接的会话可以使用的最大内存量。</li><li><strong>MAX_SESSION_TOTAL_MEMORY</strong>: 最大会话总内存,表示从该主机连接的所有会话可以使用的总内存量。</li></ul><p>这个表通过记录与数据库服务器连接的主机信息,帮助数据库管理员了解和监控不同主机的连接情况和资源使用情况。例如,如果某个主机的 <code>CURRENT_CONNECTIONS</code> 值特别高,可能表明该主机有大量的数据库访问需求,或者可能存在性能问题。管理员可以根据这些信息进行相应的优化和调整。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img71.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img72.avif"></p><h3 id="innodb-redo-log-files"><a href="#innodb-redo-log-files" class="headerlink" title="innodb_redo_log_files"></a>innodb_redo_log_files</h3><p>这个表名为 <code>innodb_redo_log_files</code>,是 MySQL Performance Schema 中的一个表,用于记录 InnoDB 存储引擎的重做日志文件的信息。以下是表中每一列的含义:</p><ul><li><strong>FILE_ID</strong>: 文件的唯一标识符,表示重做日志文件的 ID。</li><li><strong>FILE_NAME</strong>: 文件的名称,表示重做日志文件的路径和名称。</li><li><strong>START_LSN</strong>: 开始 LSN Log Sequence Number ,表示文件中第一个块的 LSN。</li><li><strong>END_LSN</strong>: 结束 LSN,表示文件中最后一个块的 LSN。</li><li><strong>SIZE_IN_BYTES</strong>: 文件大小,以字节为单位,表示文件的大小。</li><li><strong>IS_FULL</strong>: 是否已满,表示文件是否已满,1 表示已满,0 表示未满。</li><li><strong>CONSUMER_LEVEL</strong>: 消费者级别,表示所有重做日志操作的级别,级别低于此值的操作已经消费了该文件。</li></ul><p>这个表通过记录 InnoDB 重做日志文件的信息,帮助数据库管理员了解和监控重做日志文件的使用情况。例如,通过查看 <code>IS_FULL</code> 列,管理员可以了解哪些日志文件已经满了,可能需要进行归档或清理。通过 <code>CONSUMER_LEVEL</code> 列,管理员可以了解重做日志的消费情况,确保数据的一致性和恢复能力。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img73.avif"></p><p>在 MySQL 8.0 中,重做日志 redo log 的数量和临时文件的数量由以下参数控制:</p><ul><li><code>innodb_log_files_in_group</code>:控制重做日志磁盘上的文件个数,默认为2。这是在 MySQL 8.0.30 之前的版本中使用的参数。</li><li><code>innodb_log_file_size</code>:控制重做日志磁盘上单个文件的大小,默认为48MB。这也是在 MySQL 8.0.30 之前的版本中使用的参数。</li></ul><p>从 <em><strong>MySQL 8.0.30</strong></em> 版本开始,引入了一个新的参数 <code>innodb_redo_log_capacity</code> 来代替上述两个参数,用于控制重做日志总的大小。<code>innodb_redo_log_capacity</code> 的默认值是100MB,最大重做日志容量为128GB。这个参数会在数据目录下生成 <code>***#innodb_redo***</code> 的子目录,磁盘文件的存储形式不再是类似 <code>ib_logfileN</code> 这样的文件,而是替代为 <code>#ib_redoN</code> 这样新文件形式。这些新的文件一共有<em><strong>32</strong></em>个,按照参数 <code>innodb_redo_log_capacity</code> 来平均分配。因此,<code>innodb_redo_log_capacity</code> 参数控制了重做日志的总容量,从而间接控制了日志文件的数量和大小。</p><p>此外,<code>innodb_redo_log_capacity_resized</code> 状态变量用于在 MySQL 侧监控当前重做日志文件大小的调整情况。可以通过查询 <code>performance_schema.innodb_redo_log_files</code> 表来获取当前使用的重做日志文件的详细信息,包括 LSN 区间、实际写入大小、是否已满等统计数据。</p><p>总结来说,对于 MySQL 8.0.30 之前的版本,重做日志文件的数量和大小由 <code>innodb_log_files_in_group</code> 和 <code>innodb_log_file_size</code> 参数控制。而对于 MySQL 8.0.30 及之后的版本,使用 <code>innodb_redo_log_capacity</code> 参数来控制重做日志的总容量,这个参数会间接控制日志文件的数量和大小。同时,<code>innodb_redo_log_capacity_resized</code> 状态变量和 <code>performance_schema.innodb_redo_log_files</code> 表提供了监控和调整重做日志大小的额外信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img74.avif"></p><h3 id="keyring-component-status"><a href="#keyring-component-status" class="headerlink" title="keyring_component_status"></a>keyring_component_status</h3><p>这个表名为 <code>keyring_component_status</code>,是 MySQL Performance Schema 中的一个表,用于显示密钥环组件的状态信息。以下是表中每一列的含义:</p><ul><li><strong>STATUS_KEY</strong>: 状态键,表示密钥环组件的特定状态或属性。</li><li><strong>STATUS_VALUE</strong>: 状态值,表示对应 <code>STATUS_KEY</code> 的具体状态或属性值。</li></ul><p>这个表通过记录密钥环组件的状态信息,帮助数据库管理员了解和管理系统的密钥环组件。密钥环组件用于管理加密密钥,这些密钥可以用于加密存储在数据库中的敏感数据,如用户密码或其他加密材料。</p><p>在你提供的查询结果中,<code>keyring_component_status</code> 表是空的,这意味着当前没有记录任何密钥环组件的状态信息。这可能是因为密钥环组件未启用,或者当前没有相关的活动或状态需要记录。如果需要使用密钥环功能,管理员可能需要检查配置并确保密钥环组件已正确设置和启用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img75.avif"></p><h3 id="keyring-keys"><a href="#keyring-keys" class="headerlink" title="keyring_keys"></a>keyring_keys</h3><p>这个表名为 <code>keyring_keys</code>,是 MySQL Performance Schema 中的一个表,用于记录密钥环 Keyring 中的密钥信息。密钥环是 MySQL 8.0 引入的一个新特性,用于安全地存储和管理加密密钥。以下是表中每一列的含义:</p><ul><li><strong>KEY_ID</strong>: 密钥的唯一标识符,表示密钥环中的特定密钥。</li><li><strong>KEY_OWNER</strong>: 密钥所有者,表示拥有该密钥的用户或服务。</li><li><strong>BACKEND_KEY_ID</strong>: 后端密钥 ID,表示与该密钥关联的后端密钥的标识符。</li></ul><p>这个表通过记录密钥环中的密钥信息,帮助数据库管理员了解和管理系统的密钥。密钥环中的密钥可以用于加密和解密敏感数据,如用户密码或其他加密材料。</p><p>在你提供的查询结果中,<code>keyring_keys</code> 表是空的,这意味着当前没有记录任何密钥信息。这可能是因为密钥环功能未启用,或者当前没有相关的密钥需要记录。如果需要使用密钥环功能,管理员可能需要检查配置并确保密钥环组件已正确设置和启用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img76.avif"></p><h3 id="log-status"><a href="#log-status" class="headerlink" title="log_status"></a>log_status</h3><p>这个表名为 <code>log_status</code>,是 MySQL Performance Schema 中的一个表,用于记录服务器的日志状态信息。以下是表中每一列的含义:</p><ul><li><p><strong>SERVER_UUID</strong>: 服务器的唯一标识符,用于标识特定的 MySQL 实例。</p></li><li><p><strong>LOCAL</strong>: 包含有关本地事务日志状态的信息,包括:</p></li><li><p><code>gtid_executed</code>: 最后一个事务的全局事务标识符 GTID 。</p></li><li><p><code>binary_log_file</code>: 当前使用的二进制日志文件的名称。</p></li><li><p><code>binary_log_position</code>: 当前二进制日志文件中的位置。</p></li><li><p><strong>REPLICATION</strong>: 包含有关复制状态的信息,包括:</p></li><li><p><code>channels</code>: 复制通道的列表。</p></li><li><p><strong>STORAGE_ENGINES</strong>: 包含有关存储引擎状态的信息,例如 InnoDB 的 LSN Log Sequence Number 和检查点信息。</p></li></ul><p>这些信息可以帮助数据库管理员了解当前服务器的日志状态,包括事务日志、复制状态和存储引擎的状态。这对于监控和诊断数据库的运行情况非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img77.avif"></p><h3 id="memory-summary-by-account-by-event-name"><a href="#memory-summary-by-account-by-event-name" class="headerlink" title="memory_summary_by_account_by_event_name"></a>memory_summary_by_account_by_event_name</h3><p>这个表名为 <code>memory_summary_by_account_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按账户和事件名称汇总内存使用的统计信息。以下是表中每一列的含义:</p><ul><li><strong>USER</strong>: 用户名,表示执行操作的数据库用户。</li><li><strong>HOST</strong>: 主机名,表示执行操作的客户端主机。</li><li><strong>EVENT_NAME</strong>: 事件的名称,表示内存使用相关的事件类型。</li><li><strong>COUNT_ALLOC</strong>: 分配次数,表示该事件的内存分配次数。</li><li><strong>COUNT_FREE</strong>: 释放次数,表示该事件的内存释放次数。</li><li><strong>SUM_NUMBER_OF_BYTES_ALLOC</strong>: 总分配字节数,表示该事件的内存总分配量。</li><li><strong>SUM_NUMBER_OF_BYTES_FREE</strong>: 总释放字节数,表示该事件的内存总释放量。</li><li><strong>LOW_COUNT_USED</strong>: 最低使用次数,表示该事件的内存使用次数的最低值。</li><li><strong>CURRENT_COUNT_USED</strong>: 当前使用次数,表示该事件的当前内存使用次数。</li><li><strong>HIGH_COUNT_USED</strong>: 最高使用次数,表示该事件的内存使用次数的最高值。</li><li><strong>LOW_NUMBER_OF_BYTES_USED</strong>: 最低使用字节数,表示该事件的内存使用量的最低值。</li><li><strong>CURRENT_NUMBER_OF_BYTES_USED</strong>: 当前使用字节数,表示该事件的当前内存使用量。</li><li><strong>HIGH_NUMBER_OF_BYTES_USED</strong>: 最高使用字节数,表示该事件的内存使用量的最高值。</li></ul><p>这个表通过汇总按账户和事件名称的内存使用统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同用户和事件的内存使用情况。通过这些信息,管理员可以识别出内存使用的热点和潜在的性能问题,从而采取相应的优化措施。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img78.avif"></p><h3 id="memory-summary-by-host-by-event-name"><a href="#memory-summary-by-host-by-event-name" class="headerlink" title="memory_summary_by_host_by_event_name"></a>memory_summary_by_host_by_event_name</h3><p>这个表名为 <code>memory_summary_by_host_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按主机和事件名称汇总内存使用的统计信息。以下是表中每一列的含义:</p><ul><li><strong>HOST</strong>: 主机名,表示执行操作的客户端主机。</li><li><strong>EVENT_NAME</strong>: 事件的名称,表示内存使用相关的事件类型。</li><li><strong>COUNT_ALLOC</strong>: 分配次数,表示该事件的内存分配次数。</li><li><strong>COUNT_FREE</strong>: 释放次数,表示该事件的内存释放次数。</li><li><strong>SUM_NUMBER_OF_BYTES_ALLOC</strong>: 总分配字节数,表示该事件的内存总分配量。</li><li><strong>SUM_NUMBER_OF_BYTES_FREE</strong>: 总释放字节数,表示该事件的内存总释放量。</li><li><strong>LOW_COUNT_USED</strong>: 最低使用次数,表示该事件的内存使用次数的最低值。</li><li><strong>CURRENT_COUNT_USED</strong>: 当前使用次数,表示该事件的当前内存使用次数。</li><li><strong>HIGH_COUNT_USED</strong>: 最高使用次数,表示该事件的内存使用次数的最高值。</li><li><strong>LOW_NUMBER_OF_BYTES_USED</strong>: 最低使用字节数,表示该事件的内存使用量的最低值。</li><li><strong>CURRENT_NUMBER_OF_BYTES_USED</strong>: 当前使用字节数,表示该事件的当前内存使用量。</li><li><strong>HIGH_NUMBER_OF_BYTES_USED</strong>: 最高使用字节数,表示该事件的内存使用量的最高值。</li></ul><p>这个表通过汇总按主机和事件名称的内存使用统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同主机上的内存使用情况。通过这些信息,管理员可以识别出内存使用的热点和潜在的性能问题,从而采取相应的优化措施。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-08-05/img79.avif"></p><h3 id="memory-summary-by-thread-by-event-name"><a href="#memory-summary-by-thread-by-event-name" class="headerlink" title="memory_summary_by_thread_by_event_name"></a>memory_summary_by_thread_by_event_name</h3><p>这个表名为 <code>memory_summary_by_thread_by_event_name</code>,是 MySQL Performance Schema 中的一个表,用于按线程和事件名称汇总内存使用的统计信息。以下是表中每一列的含义:</p><ul><li><strong>THREAD_ID</strong>: 线程的唯一标识符,表示执行操作的线程。</li><li><strong>EVENT_NAME</strong>: 事件的名称,表示内存使用相关的事件类型。</li><li><strong>COUNT_ALLOC</strong>: 分配次数,表示该事件的内存分配次数。</li><li><strong>COUNT_FREE</strong>: 释放次数,表示该事件的内存释放次数。</li><li><strong>SUM_NUMBER_OF_BYTES_ALLOC</strong>: 总分配字节数,表示该事件的内存总分配量。</li><li><strong>SUM_NUMBER_OF_BYTES_FREE</strong>: 总释放字节数,表示该事件的内存总释放量。</li><li><strong>LOW_COUNT_USED</strong>: 最低使用次数,表示该事件的内存使用次数的最低值。</li><li><strong>CURRENT_COUNT_USED</strong>: 当前使用次数,表示该事件的当前内存使用次数。</li><li><strong>HIGH_COUNT_USED</strong>: 最高使用次数,表示该事件的内存使用次数的最高值。</li><li><strong>LOW_NUMBER_OF_BYTES_USED</strong>: 最低使用字节数,表示该事件的内存使用量的最低值。</li><li><strong>CURRENT_NUMBER_OF_BYTES_USED</strong>: 当前使用字节数,表示该事件的当前内存使用量。</li><li><strong>HIGH_NUMBER_OF_BYTES_USED</strong>: 最高使用字节数,表示该事件的内存使用量的最高值。</li></ul><p>这个表通过汇总按线程和事件名称的内存使用统计信息,帮助数据库管理员分析和优化数据库性能,特别是了解不同线程上的内存使用情况。通过这些信息,管理员可以识别出内存使用的热点和潜在的性能问题,从而采取相应的优化措施</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/08/05/767eb1d9/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL内置数据库】mysql_innodb_cluster_metadata</title>
      <link>https://blog.eucalyptus.cc/2025/07/25/81529a04/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/25/81529a04/</guid>
      <pubDate>Fri, 25 Jul 2025 05:40:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;code&gt;mysql_innodb_cluster_metadata&lt;/code&gt; 是 &lt;strong&gt;MySQL Shell &amp;#x2F; InnoDB Cluster &amp;#x2F; ClusterSet&lt;/strong&gt;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><code>mysql_innodb_cluster_metadata</code> 是 <strong>MySQL Shell &#x2F; InnoDB Cluster &#x2F; ClusterSet</strong> 的“<strong>系统目录库</strong>”。它里面每一张表都记录了 <strong>拓扑、状态、实例、路由器、版本号</strong> 等关键信息,<strong>千万不要手工改动</strong>,否则集群会直接报错或无法启动。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img1.avif"></p><h3 id="集群总体信息"><a href="#集群总体信息" class="headerlink" title="集群总体信息"></a>集群总体信息</h3><p>表名</p><table><thead><tr><th>关键字段</th><th>作用</th><th><code>clusters</code></th><th><code>cluster_id</code>, <code>cluster_name</code>, <code>topology_mode</code></th><th>当前 InnoDB Cluster 的名称、模式 单主&#x2F;多主</th><th><code>clustersets</code></th><th><code>clusterset_id</code>, <code>clusterset_name</code></th><th>当启用 <strong>ClusterSet</strong> 跨地域容灾 时,记录全局 ClusterSet 信息</th><th><code>schema_version</code></th><th><code>major</code>, <code>minor</code>, <code>patch</code></th><th>元数据 <strong>版本号</strong>,升级 Shell 或 MySQL 时会自动变更</th></tr></thead></table><h4 id="clusters"><a href="#clusters" class="headerlink" title="clusters"></a>clusters</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img2.avif"></p><h4 id="clustersets"><a href="#clustersets" class="headerlink" title="clustersets"></a>clustersets</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img3.avif"></p><h4 id="schema-version"><a href="#schema-version" class="headerlink" title="schema_version"></a>schema_version</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img4.avif"></p><h3 id="实例-节点-清单"><a href="#实例-节点-清单" class="headerlink" title="实例 节点 清单"></a>实例 节点 清单</h3><p>表名</p><table><thead><tr><th>关键字段</th><th>作用</th></tr></thead><tbody><tr><td>instances</td><td>mysql_server_uuid, hostname, port, role, weight — <strong>老版本</strong> v1 的节点清单,记录每个 MySQL 实例的地址、角色、权重</td></tr><tr><td>v2_instances</td><td>instance_id, addresses, attributes, version_token — <strong>新版本</strong> v2 的节点信息,字段更丰富,支持 <strong>IPV6、多地址</strong></td></tr><tr><td>日常用 <code>select * from v2_instances\G</code> 就能快速看出 <strong>哪个节点没上线</strong>。</td><td></td></tr></tbody></table><h4 id="instances"><a href="#instances" class="headerlink" title="instances"></a>instances</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img5.avif"></p><h4 id="v2-instances"><a href="#v2-instances" class="headerlink" title="v2_instances"></a>v2_instances</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img6.avif"></p><h3 id="GR-集群-视图"><a href="#GR-集群-视图" class="headerlink" title="GR 集群&#x2F;视图"></a>GR 集群&#x2F;视图</h3><p>表名</p><table><thead><tr><th>关键字段</th><th>作用</th><th><code>v2_gr_clusters</code></th><th><code>cluster_id</code>, <code>group_name</code>, <code>group_seeds</code>, <code>member_weight</code></th><th>与 <strong>Group Replication 参数</strong>一一对应,自动同步</th><th><code>v2_ar_clusters</code></th><th><code>cluster_id</code>, <code>topology</code></th><th><strong>异步复制集群</strong> ReplicaSet&#x2F;DR 场景 的元数据</th><th><code>async_cluster_members</code></th><th><code>member_id</code>, <code>member_role</code>, <code>member_host</code>, <code>member_port</code></th><th>异步集群的成员信息</th></tr></thead></table><h4 id="v2-clusters"><a href="#v2-clusters" class="headerlink" title="v2_clusters"></a>v2_clusters</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img7.avif"></p><h4 id="v2-ar-clusters"><a href="#v2-ar-clusters" class="headerlink" title="v2_ar_clusters"></a>v2_ar_clusters</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img8.avif"></p><h4 id="async-cluster-members"><a href="#async-cluster-members" class="headerlink" title="async_cluster_members"></a>async_cluster_members</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img9.avif"></p><h3 id="Router-相关"><a href="#Router-相关" class="headerlink" title="Router 相关"></a>Router 相关</h3><p>表名</p><table><thead><tr><th>关键字段</th><th>作用</th><th><code>routers</code> &#x2F; <code>v2_routers</code></th><th><code>router_id</code>, <code>hostname</code>, <code>last_check_in</code>, <code>version</code></th><th><strong>MySQL Router</strong> 的心跳、版本、最后一次上报时间</th><th><code>router_rest_accounts</code> &#x2F; <code>v2_router_rest_accounts</code></th><th><code>account</code>, <code>password</code></th><th>Router 连接元数据库用的 <strong>REST API 账号</strong></th><th><code>v2_this_instance</code></th><th><code>instance_id</code>, <code>cluster_id</code></th><th><strong>Router 本机</strong>属于哪个实例、哪个集群 快速定位</th></tr></thead></table><h4 id="routers"><a href="#routers" class="headerlink" title="routers"></a>routers</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img10.avif"></p><h4 id="v2-routers"><a href="#v2-routers" class="headerlink" title="v2_routers"></a>v2_routers</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img11.avif"></p><h4 id="router-rest-accounts"><a href="#router-rest-accounts" class="headerlink" title="router_rest_accounts"></a>router_rest_accounts</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img12.avif"></p><h4 id="v2-router-rest-accounts"><a href="#v2-router-rest-accounts" class="headerlink" title="v2_router_rest_accounts"></a>v2_router_rest_accounts</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img13.avif"></p><h4 id="v2-this-instance"><a href="#v2-this-instance" class="headerlink" title="v2_this_instance"></a>v2_this_instance</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img14.avif"></p><h3 id="ClusterSet-扩展-v2-专用"><a href="#ClusterSet-扩展-v2-专用" class="headerlink" title="ClusterSet 扩展 v2 专用"></a>ClusterSet 扩展 v2 专用</h3><p>表名</p><table><thead><tr><th>关键字段</th><th>作用</th><th><code>v2_cs_clustersets</code></th><th><code>clusterset_id</code>, <code>primary_cluster</code>, <code>failover_counter</code></th><th>整个 ClusterSet 的 <strong>主集群</strong>、<strong>故障切换次数</strong></th><th><code>v2_cs_members</code></th><th><code>member_cluster_id</code>, <code>member_role</code></th><th>每个集群在 ClusterSet 里的角色 PRIMARY &#x2F; REPLICA</th><th><code>v2_cs_router_options</code></th><th><code>option_name</code>, <code>option_value</code></th><th>Router 对 ClusterSet 的 <strong>路由策略</strong> 读写分离权重等</th></tr></thead></table><h4 id="v2-cs-clustersets"><a href="#v2-cs-clustersets" class="headerlink" title="v2_cs_clustersets"></a>v2_cs_clustersets</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img15.avif"></p><h4 id="v2-cs-members"><a href="#v2-cs-members" class="headerlink" title="v2_cs_members"></a>v2_cs_members</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img16.avif"></p><h4 id="v2-cs-router-options"><a href="#v2-cs-router-options" class="headerlink" title="v2_cs_router_options"></a>v2_cs_router_options</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-25/img17.avif"></p><h3 id="提示"><a href="#提示" class="headerlink" title="提示"></a>提示</h3><ul><li><strong>只读表</strong>:任何 UPDATE&#x2F;DELETE 都会导致 Shell 报错 <code>Metadata inconsistency</code>。</li><li><strong>升级 Shell</strong> 或 <strong>MySQL</strong> 时会自动 <strong>ALTER</strong> 这些表,无需手工干预。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/25/81529a04/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL Innodb Cluster配置</title>
      <link>https://blog.eucalyptus.cc/2025/07/18/fc669c55/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/18/fc669c55/</guid>
      <pubDate>Fri, 18 Jul 2025 07:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;配置规划&quot;&gt;&lt;a href=&quot;#配置规划&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="配置规划"><a href="#配置规划" class="headerlink" title="配置规划"></a>配置规划</h3><p>本篇文章中MySQL使用编译安装</p><table><thead><tr><th>主机名</th><th>角色</th><th>安装软件</th></tr></thead><tbody><tr><td>348aeb8077a8</td><td>主节点</td><td>Mysql8.0.30, mysql-shell, mysql-router</td></tr><tr><td>7ff037fcf001</td><td>从节点</td><td>Mysql8.0.30, mysql-shell, mysql-router</td></tr><tr><td>fc7b8078d23b</td><td>从节点</td><td>Mysql8.0.30, mysql-shell, mysql-router</td></tr></tbody></table><h3 id="三台实例分别创建’mingliang’-‘-’-用户并授权"><a href="#三台实例分别创建’mingliang’-‘-’-用户并授权" class="headerlink" title="三台实例分别创建’mingliang’ ‘%’ 用户并授权"></a>三台实例分别创建’mingliang’ ‘%’ 用户并授权</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;mingliang&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">with</span> mysql_native_password <span class="keyword">by</span> <span class="string">&#x27;123456&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> <span class="keyword">all</span> <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;mingliang&#x27;</span> <span class="string">&#x27;%&#x27;</span> <span class="keyword">with</span> <span class="keyword">grant</span> option;</span><br></pre></td></tr></table></figure><h3 id=""><a href="#" class="headerlink" title=""></a><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img1.avif"></h3><h3 id="安装mysql-shell-三台机器必须全部安装"><a href="#安装mysql-shell-三台机器必须全部安装" class="headerlink" title="安装mysql shell 三台机器必须全部安装"></a>安装mysql shell 三台机器必须全部安装</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">wget https://downloads.mysql.com/archives/get/p/43/file/mysql-shell-8.0.30-linux-glibc2.12-x86-64bit.tar.gz</span><br><span class="line">tar -xzvf mysql-shell-8.0.30-linux-glibc2.12-x86-64bit.tar.gz</span><br><span class="line"><span class="built_in">mv</span> mysql-shell-8.0.30-linux-glibc2.12-x86-64bit /usr/local/mysqlsh</span><br><span class="line"><span class="built_in">chown</span> mysql8:mysql8 -R /usr/local/mysqlsh</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img3.avif"></p><h4 id="在mysql8用户中配置环境变量"><a href="#在mysql8用户中配置环境变量" class="headerlink" title="在mysql8用户中配置环境变量"></a>在mysql8用户中配置环境变量</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">su - mysql8</span><br><span class="line">vim .bash_profile /添加下述内容</span><br><span class="line"></span><br><span class="line"><span class="built_in">export</span> PATH <span class="variable">$MYSQL_HOME</span>/bin:/usr/local/mysqlsh/bin:<span class="variable">$PATH</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#使文件生效</span></span><br><span class="line"><span class="built_in">source</span> .bash_profile</span><br></pre></td></tr></table></figure><h4 id="使用mysql-shell"><a href="#使用mysql-shell" class="headerlink" title="使用mysql shell"></a>使用mysql shell</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqlsh --mysqlx -h 192.168.3.2 -P 33060 -umingliang -p</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img4.avif"></p><blockquote><p>这里登录测试的时候出现了一个这样的错误</p><p>MySQL Error 2027: Requested session assumes MySQL X Protocol but ‘192.168.3.2:3306’ seems to speak the classic MySQL protocol (Unexpected response received from server, msg-id:10)</p><p>这个是因为上面连接的时候X协议的端口没有指定正确,可以使用mysql -u root -p -e select mysqlx_port 查看X协议端口,然后连接的时候指定正确的端口就可以成功&gt;</p><p>参考文档:<a href="https://stackoverflow.org.cn/questions/64326446">mysql - 如何为 mysql 8 docker 容器启用 x 协议_Stack Overflow中文网</a></p></blockquote><h3 id="安装mysql-router-三台主机必须全部安装"><a href="#安装mysql-router-三台主机必须全部安装" class="headerlink" title="安装mysql router 三台主机必须全部安装"></a>安装mysql router 三台主机必须全部安装</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">wget https://downloads.mysql.com/archives/get/p/41/file/mysql-router-8.0.30-linux-glibc2.12-x86_64.tar.xz</span><br><span class="line">tar -xvf mysql-router-8.0.30-linux-glibc2.12-x86_64.tar.xz</span><br><span class="line"></span><br><span class="line"><span class="comment">#没有xz的话需要安装下</span></span><br><span class="line">yum install -y xz</span><br><span class="line"></span><br><span class="line"><span class="built_in">mv</span> mysql-router-8.0.30-linux-glibc2.12-x86_64 /usr/local/mysqlrouter</span><br><span class="line"><span class="built_in">chown</span> mysql8:mysql8 /usr/local/mysqlrouter</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img7.avif"></p><h4 id="在MySQL8用户中配置环境变量"><a href="#在MySQL8用户中配置环境变量" class="headerlink" title="在MySQL8用户中配置环境变量"></a>在MySQL8用户中配置环境变量</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">su - mysql8</span><br><span class="line">vim .bash_profile /添加下述内容</span><br><span class="line"></span><br><span class="line"><span class="built_in">export</span> PATH <span class="variable">$MYSQL_HOME</span>/bin:/usr/local/mysqlsh/bin:/usr/local/mysqlrouter/bin:<span class="variable">$PATH</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#使文件生效</span></span><br><span class="line"><span class="built_in">source</span> .bash_profile</span><br></pre></td></tr></table></figure><h3 id="通过MySQLShell搭建MGR-下面步骤每个节点都执行"><a href="#通过MySQLShell搭建MGR-下面步骤每个节点都执行" class="headerlink" title="通过MySQLShell搭建MGR,下面步骤每个节点都执行"></a>通过MySQLShell搭建MGR,下面步骤每个节点都执行</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#192.168.3.2 root 348aeb8077a8 master</span></span><br><span class="line">su - mysql8</span><br><span class="line">mysqlsh --mysqlx -h 192.168.3.2 -P33060 -umingliang -p</span><br><span class="line">dba.configureInstance();</span><br><span class="line">dba.configureInstance();</span><br><span class="line"></span><br><span class="line"><span class="comment">#192.168.3.3 root 7ff037fcf001 slave1</span></span><br><span class="line">su - mysql8</span><br><span class="line">mysqlsh --mysqlx -h 192.168.3.3 -P33060 -umingliang -p</span><br><span class="line">dba.configureInstance();</span><br><span class="line">dba.configureInstance();</span><br><span class="line"></span><br><span class="line"><span class="comment">#192.168.3.4 root fc7b8078d23b slave2</span></span><br><span class="line">su - mysql8</span><br><span class="line">mysqlsh --mysqlx -h 192.168.3.4 -P33060 -umingliang -p</span><br><span class="line">dba.configureInstance();</span><br><span class="line">dba.configureInstance();</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img10.avif"></p><h4 id="创建集群实例-在master执行即可"><a href="#创建集群实例-在master执行即可" class="headerlink" title="创建集群实例 在master执行即可"></a>创建集群实例 在master执行即可</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#默认为单主模式,第一个加入为写节点</span></span><br><span class="line"><span class="comment">#---第一个节点创建集群实例(192.168.3.2)</span></span><br><span class="line"></span><br><span class="line">var cluster dba.createCluster(<span class="string">&#x27;DemoCluster&#x27;</span>)</span><br><span class="line"></span><br><span class="line"><span class="comment">#添加其他节点192.168.3.3和192.168.3.4,此时会进行数据库克隆,</span></span><br><span class="line"><span class="comment">#把节点1的数据库复制到其它数据库,同时进行同步。</span></span><br><span class="line"></span><br><span class="line">var cluster dba.getCluster()</span><br><span class="line">cluster.addInstance(<span class="string">&#x27;mingliang 192.168.3.3:3306&#x27;</span>)</span><br><span class="line">cluster.addInstance(<span class="string">&#x27;mingliang 192.168.3.4:3306&#x27;</span>)</span><br><span class="line"></span><br><span class="line"><span class="comment">#查看集群状态</span></span><br><span class="line">var cluster dba.getCluster()</span><br><span class="line">cluster.status();</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img11.avif"></p><blockquote><p>这里由于3个节点的UUID相同,导致添加集群节点的没有添加进去</p><p>Cluster.addInstance: Cannot add an instance with the same server UUID (1d6dd7c2-5ff7-11f0-bb22-0242c0a80302) of an active member of the cluster ‘348aeb8077a8:3306’. Please change the UUID of the instance to add, all members must have a unique server UUID. (RuntimeError)</p><p>更新uuid后,master节点执行了克隆恢复,但是发现一直处于* Waiting for server restart… 状态,直至超时,去slave查看error.log发现发生了crash,导致启动失败</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img12.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img13.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img14.avif"></p><p>最后重新配置了一次,在添加节点恢复的时候选择了增量恢复后,成功添加</p><p>#添加slave1</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img15.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img16.avif"></p><p>#添加slave2</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img17.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img18.avif"></p></blockquote><h3 id="配置MySQLRouter路由"><a href="#配置MySQLRouter路由" class="headerlink" title="配置MySQLRouter路由"></a>配置MySQLRouter路由</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#创建路由数据目录</span></span><br><span class="line">su - mysql8</span><br><span class="line"><span class="built_in">mkdir</span> myroyter</span><br><span class="line"></span><br><span class="line"><span class="comment">#路由初始化</span></span><br><span class="line"><span class="comment">#master</span></span><br><span class="line">mysqlrouter --bootstrap mingliang 172.0.0.1:3306 --directory /home/mysql8/myrouter --conf-use-sockets --user mysql8</span><br><span class="line"></span><br><span class="line"><span class="comment">#启动路由</span></span><br><span class="line">./myrouter/star.sh</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img19.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img20.avif"></p><h3 id="测试配置"><a href="#测试配置" class="headerlink" title="测试配置"></a>测试配置</h3><h4 id="连接测试"><a href="#连接测试" class="headerlink" title="连接测试"></a>连接测试</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u mingliang -p -P6446</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img21.avif"></p><h4 id="数据同步测试"><a href="#数据同步测试" class="headerlink" title="数据同步测试"></a>数据同步测试</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> database demo1;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img22.avif"></p><h4 id="故障测试"><a href="#故障测试" class="headerlink" title="故障测试"></a>故障测试</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img23.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img24.avif"></p><h4 id="手动HA"><a href="#手动HA" class="headerlink" title="手动HA"></a>手动HA</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">cluster.setPrimaryInstance(&#x27;mingliang 192.168.3.3:3306&#x27;)</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img25.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img26.avif"></p><h4 id="关闭和重启集群"><a href="#关闭和重启集群" class="headerlink" title="关闭和重启集群"></a>关闭和重启集群</h4><p>关闭的时候必须先关闭2个slave节点,然后再关闭master节点,重启也是一样</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img27.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img28.avif"></p><p>然后在master节点使用mysqlshell连接mysql然后重启集群</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">dba.rebootClusterFromCompleteOutage()</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img29.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img30.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/18/fc669c55/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL Innodb Cluster介绍</title>
      <link>https://blog.eucalyptus.cc/2025/07/18/5c156a39/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/18/5c156a39/</guid>
      <pubDate>Fri, 18 Jul 2025 06:55:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;MySQL InnoDB Cluster 是 MySQL 官方提供的高可用性解决方案,它结合了 MySQL Shell、MySQL Server 和 Group Replication 技术,使您能够部署和管理完整的集成高可用性解决方案。&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>MySQL InnoDB Cluster 是 MySQL 官方提供的高可用性解决方案,它结合了 MySQL Shell、MySQL Server 和 Group Replication 技术,使您能够部署和管理完整的集成高可用性解决方案。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-18/img1.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-introduction.html">https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-introduction.html</a></p><p>以下是对 MySQL InnoDB Cluster 的详细介绍:</p><h4 id="核心组件"><a href="#核心组件" class="headerlink" title="核心组件"></a>核心组件</h4><ul><li><strong>MySQL Shell</strong>:MySQL Shell 是一个现代化的命令行客户端,提供对 MySQL Server 的强大交互式访问,支持 JavaScript 和 Python 两种编程语言接口。在 InnoDB Cluster 环境中,MySQL Shell 充当了管理和监控集群的控制台工具,内置了 AdminAPI,用于简化群的创建、配置、扩展、维护等操作。</li><li><strong>MySQL Router</strong>:MySQL Router 是轻量级的服务代理,用于透明地路由客户端请求到正确的 MySQL 服务器实例。根据集的部署信息,MySQL Router 能自动生成合适的配置,确保客户端应用无需关心后端服务器的细节,即可无缝连接到群中的主节点 在单主模式下 或读写节点 在多主模式下 ,并根据集状态自动调整路由策略。</li><li><strong>MySQL Server 和 Group Replication</strong>:使一组 MySQL 实例能够提供高可用性。InnoDB Cluster 提供了一种替代的、易于使用的编程方式来使用组复制。</li></ul><h4 id="核心原理与优势"><a href="#核心原理与优势" class="headerlink" title="核心原理与优势"></a>核心原理与优势</h4><p>InnoDB Cluster 基于 MySQL Group Replication 构建,提供自动成员管理、容错、自动故障转移等功能。InnoDB Cluster 通常以单主模式运行,有一个主实例 读写 和多个辅助实例 只读 。高级用户还可以利用多主模式,其中所有实例都是主实例。您甚至可以在 InnoDB Cluster 在线时更改集的拓扑结构,以确保尽可能高的可用性。</p><h4 id="与经典主从复制的比较"><a href="#与经典主从复制的比较" class="headerlink" title="与经典主从复制的比较"></a>与经典主从复制的比较</h4><p>经典的主从复制是 MySQL 原生的复制功能,采用异步方式。主服务器执行更改数据的事务后,会产生 binlog,之后 binlog 会被发送到从服务器变成 relay log。与此同时,主服务器会对提交返回。从服务器接收到 relay log 后,会通过一个 applier 的线程对 日志 里面的内容进行施放,使产生的数据更改写入从服务器,之后产生自己的 binlog,进行提交。</p><p>与经典的主从复制相比,InnoDB Cluster 基于组复制,提供了更高的可用性。在 InnoDB Cluster 中,每个 MySQL 服务器实例都是组复制的成员,数据在集群内的同步更加可靠。此外,InnoDB Cluster 还提供了自动故障转移功能,能够在某个实例出现故障时自动将任务转移到其他实例上,避免了手动介入和业务中断。</p><h4 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h4><p>InnoDB Cluster 作为一种新兴的数据库解决方案,通过提供自动故障转移、易于管理的 API 和路由等功能,为企业提供了高可用性的数据库服务。在实际应用中,通过合理的配置和管理,InnoDB Cluster 能够确保业务的连续性和数据的可靠性。随着技术的发展和业务的不断扩展,InnoDB Cluster 将成为越来越多企业的首选数据库解决方案。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/18/5c156a39/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>SELECT ... INTO OUTFILE和LOAD DATA INFILE</title>
      <link>https://blog.eucalyptus.cc/2025/07/15/61ee9680/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/15/61ee9680/</guid>
      <pubDate>Tue, 15 Jul 2025 03:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;语法&quot;&gt;&lt;a href=&quot;#语法&quot; class=&quot;headerlink&quot; title=&quot;语法&quot;&gt;&lt;/a&gt;语法&lt;/h3&gt;&lt;h4 id=&quot;SELECT-…-INTO-OUTFILE&quot;&gt;&lt;a href=&quot;#SELECT-…-INTO-OUTFILE&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="语法"><a href="#语法" class="headerlink" title="语法"></a>语法</h3><h4 id="SELECT-…-INTO-OUTFILE"><a href="#SELECT-…-INTO-OUTFILE" class="headerlink" title="SELECT … INTO OUTFILE"></a>SELECT … INTO OUTFILE</h4><p>这个语句用于将查询结果导出到服务器的文件系统中。它将 <code>SELECT</code> 语句的结果集直接写入到一个文本文件中。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">column1, column2, ...</span><br><span class="line"><span class="keyword">INTO</span> OUTFILE <span class="string">&#x27;file_path&#x27;</span></span><br><span class="line">[<span class="keyword">character set</span> charset_name]</span><br><span class="line">[fields [enclosed <span class="keyword">by</span> <span class="string">&#x27;char&#x27;</span>] [escaped <span class="keyword">by</span> <span class="string">&#x27;char&#x27;</span>]]</span><br><span class="line">[lines [terminated <span class="keyword">by</span> <span class="string">&#x27;char&#x27;</span>]]</span><br><span class="line">[ignore lines number];</span><br></pre></td></tr></table></figure><ul><li><code>**file_path**</code>:指定导出文件的路径和文件名。需要注意的是,该路径必须是 MySQL 服务器有权限访问的路径。</li><li><code>**character set charset_name**</code>:指定导出文件的字符集。</li><li><code>**fields**</code>:定义字段的格式,如字段是否由特定字符包围。</li><li><code>**lines**</code>:定义行的格式,如行终止符。</li><li><code>**ignore lines number**</code>:忽略文件开头的若干行。</li></ul><h4 id="LOAD-DATA-INFILE"><a href="#LOAD-DATA-INFILE" class="headerlink" title="LOAD DATA INFILE"></a>LOAD DATA INFILE</h4><p>这个语句用于将文件中的数据导入到数据库表中。它直接从文件读取数据,并将数据插入到指定的表中。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">LOAD DATA INFILE <span class="string">&#x27;file_path&#x27;</span></span><br><span class="line"><span class="keyword">INTO</span> <span class="keyword">TABLE</span> table_name</span><br><span class="line">[<span class="keyword">character set</span> charset_name]</span><br><span class="line">[FIELDS [TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;char&#x27;</span>] [ENCLOSED <span class="keyword">BY</span> <span class="string">&#x27;char&#x27;</span>] [ESCAPED <span class="keyword">BY</span> <span class="string">&#x27;char&#x27;</span>]]</span><br><span class="line">[LINES [STARTING <span class="keyword">BY</span> <span class="string">&#x27;char&#x27;</span>] [TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;char&#x27;</span>]]</span><br><span class="line">[IGNORE number LINES]</span><br><span class="line">(列名列表)</span><br><span class="line">[<span class="keyword">SET</span> column_name <span class="keyword">value</span>, ...];</span><br></pre></td></tr></table></figure><ul><li><code>**file_path**</code>:指定要导入数据的文件路径。</li><li><code>**INTO TABLE table_name**</code>:指定目标表的名称。</li><li>**<code>character set charset_name</code>:指定文件的字符集。</li><li><code>**FIELDS**</code>:定义字段的格式,如字段分隔符、字段包围符等。</li><li><code>**LINES**</code>:定义行的格式,如行起始符和行终止符。</li><li><code>**IGNORE number LINES**</code>:忽略文件开头的若干行。</li><li><code>**(列名列表)**</code>:指定表中列的顺序。</li><li><code>**SET column_name value**</code>:为某些列指定默认值。</li></ul><h3 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h3><p>创建表</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> employees (</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">100</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">department <span class="type">VARCHAR</span>(<span class="number">100</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">salary <span class="type">DECIMAL</span>(<span class="number">10</span>, <span class="number">2</span>) <span class="keyword">NOT NULL</span></span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>插入数据</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> employees (name, department, salary) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="string">&#x27;John Doe&#x27;</span>, <span class="string">&#x27;Finance&#x27;</span>, <span class="number">50000</span>),</span><br><span class="line">(<span class="string">&#x27;Jane Smith&#x27;</span>, <span class="string">&#x27;IT&#x27;</span>, <span class="number">60000</span>),</span><br><span class="line">(<span class="string">&#x27;Bob Johnson&#x27;</span>, <span class="string">&#x27;HR&#x27;</span>, <span class="number">55000</span>);</span><br></pre></td></tr></table></figure><p>导出文件</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> employees <span class="keyword">INTO</span> OUTFILE <span class="string">&#x27;/var/lib/mysql-files/employees.csv&#x27;</span></span><br><span class="line">FIELDS TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;,&#x27;</span></span><br><span class="line">ENCLOSED <span class="keyword">BY</span> <span class="string">&#x27; &#x27;</span></span><br><span class="line">LINES TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;\n&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-15/img1.avif"></p><p>创建employees_1表准备导入数据</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create table</span> employees_1 <span class="keyword">like</span> employees;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-15/img2.avif"></p><p>导入数据</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">LOAD DATA INFILE <span class="string">&#x27;/var/lib/mysql-files/employees.csv&#x27;</span></span><br><span class="line"><span class="keyword">INTO</span> <span class="keyword">TABLE</span> employees_1</span><br><span class="line">FIELDS TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;,&#x27;</span></span><br><span class="line">ENCLOSED <span class="keyword">BY</span> <span class="string">&#x27; &#x27;</span></span><br><span class="line">LINES TERMINATED <span class="keyword">BY</span> <span class="string">&#x27;\n&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-15/img3.avif"></p><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><ul><li><strong>权限</strong>:使用这两个语句需要相应的权限。<code>SELECT ... INTO OUTFILE</code> 需要 <code>FILE</code> 权限,而 <code>LOAD DATA INFILE</code> 需要 <code>LOAD DATA</code> 权限。</li><li><strong>安全性</strong>:在生产环境中使用这些语句时,需要注意安全性,避免导出敏感数据或导入恶意数据。</li><li><strong>字符集</strong>:确保文件的字符集与数据库的字符集匹配,以避免数据乱码。</li></ul><p>通过使用 <code>SELECT ... INTO OUTFILE</code> 和 <code>LOAD DATA INFILE</code>,你可以方便地在 MySQL 数据库和文件系统之间导入和导出数据。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/15/61ee9680/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL密码管理器mysql_config_editor</title>
      <link>https://blog.eucalyptus.cc/2025/07/14/9565a5cc/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/14/9565a5cc/</guid>
      <pubDate>Mon, 14 Jul 2025 08:10:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;mysql_config_editor 是 MySQL 官方自带的一款&lt;strong&gt;命令行小工具&lt;/strong&gt;,作用一句话:&lt;strong&gt;把账号、密码、主机、端口等连接信息加密存起来,下次连接时只敲一个名字即可,不用再写明文密码&lt;/strong&gt;。&lt;/p&gt;
&lt;h4</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>mysql_config_editor 是 MySQL 官方自带的一款<strong>命令行小工具</strong>,作用一句话:<strong>把账号、密码、主机、端口等连接信息加密存起来,下次连接时只敲一个名字即可,不用再写明文密码</strong>。</p><h4 id="核心能力"><a href="#核心能力" class="headerlink" title="核心能力"></a>核心能力</h4><p>能力</p><table><thead><tr><th>说明</th><th><strong>加密存储</strong></th><th>把敏感信息 用户、密码、主机、端口、socket 等 加密后保存在 <code>~/.mylogin.cnf</code>,避免命令行或脚本里出现明文密码。</th><th><strong>多组配置</strong></th><th>可以存很多套连接参数,每套用一个“</th><th><strong>自动读取</strong></th><th>后续使用 <code>mysql</code>、<code>mysqldump</code> 等客户端时,只需加 <code>--login-path 名字</code>,即可自动加载对应配置。</th></tr></thead></table><h4 id="常用命令速查"><a href="#常用命令速查" class="headerlink" title="常用命令速查"></a>常用命令速查</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-14/img1.avif"></p><p><strong>添加&#x2F;修改一组配置</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">mysql_config_editor <span class="keyword">set</span> \</span><br><span class="line"><span class="comment">--login-path local \</span></span><br><span class="line"><span class="comment">--host 127.0.0.1 \</span></span><br><span class="line"><span class="comment">--user root \</span></span><br><span class="line"><span class="comment">--port 3306 \</span></span><br><span class="line"><span class="comment">--socket /var/lib/mysql/mysql.sock \</span></span><br><span class="line"><span class="comment">--password</span></span><br><span class="line"># 回车后交互输入密码</span><br></pre></td></tr></table></figure><p>示例:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-14/img2.avif"></p><p><strong>查看所有已存配置</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql_config_editor print --all</span><br></pre></td></tr></table></figure><p><strong>使用配置连接</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql --login-path local</span><br></pre></td></tr></table></figure><p>等同于 <code>mysql -h127.0.0.1 -uroot -p</code>,但密码不会出现在命令行或历史记录里。</p><p><strong>删除一组配置</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql_config_editor remove --login-path local</span><br></pre></td></tr></table></figure><h4 id="为什么更安全"><a href="#为什么更安全" class="headerlink" title="为什么更安全?"></a>为什么更安全?</h4><ul><li>文件 <code>~/.mylogin.cnf</code> <strong>0600 权限</strong>,别人读不到。</li><li>内容 <strong>混淆加密</strong>,即使被拷贝也无法直接看到密码。</li><li>命令行 **不再出现 **<code>-p密码</code>,避免被 <code>history</code> 或 <code>ps</code> 泄露。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-14/img3.avif"></p><h4 id="典型场景"><a href="#典型场景" class="headerlink" title="典型场景"></a>典型场景</h4><ul><li>脚本里定时备份:<br><code>mysqldump --login-path backup mydb &gt; mydb.sql</code></li><li>DBA 管理多台实例:<br>给每台机器建一个 <code>--login-path prod1</code>、<code>prod2</code>… 一键切换。</li></ul><p>一句话总结:<strong>mysql_config_editor 就是 MySQL 的“密码管理器”,写完配置后,连库只需敲名字,安全又省事。</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/14/9565a5cc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>mysql_multi多实例管理</title>
      <link>https://blog.eucalyptus.cc/2025/07/12/9002a947/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/12/9002a947/</guid>
      <pubDate>Sat, 12 Jul 2025 02:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;继上篇文章继续&lt;/p&gt;
&lt;p&gt;MySQL编译安装-CSDN博客&lt;/p&gt;
&lt;h4 id=&quot;配置-etc-my-cnf文件&quot;&gt;&lt;a href=&quot;#配置-etc-my-cnf文件&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>继上篇文章继续</p><p>MySQL编译安装-CSDN博客</p><h4 id="配置-etc-my-cnf文件"><a href="#配置-etc-my-cnf文件" class="headerlink" title="配置&#x2F;etc&#x2F;my.cnf文件"></a>配置&#x2F;etc&#x2F;my.cnf文件</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br></pre></td><td class="code"><pre><span class="line">[mysqld_multi]</span><br><span class="line"></span><br><span class="line">mysqld <span class="operator">/</span>usr<span class="operator">/</span><span class="keyword">local</span><span class="operator">/</span>mysql8<span class="number">.0</span><span class="number">.30</span><span class="operator">/</span>bin<span class="operator">/</span>mysqld_safe</span><br><span class="line">mysqladmin <span class="operator">/</span>usr<span class="operator">/</span><span class="keyword">local</span><span class="operator">/</span>mysql8<span class="number">.0</span><span class="number">.30</span><span class="operator">/</span>bin<span class="operator">/</span>mysqladmin</span><br><span class="line">log <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span>data30<span class="operator">/</span>mysqld_multi.log</span><br><span class="line"></span><br><span class="line">[mysqld]</span><br><span class="line"><span class="keyword">user</span> mysql8</span><br><span class="line">port <span class="number">3306</span></span><br><span class="line">server_id <span class="number">3306</span></span><br><span class="line">basedir <span class="operator">/</span>usr<span class="operator">/</span><span class="keyword">local</span><span class="operator">/</span>mysql8<span class="number">.0</span><span class="number">.30</span><span class="operator">/</span></span><br><span class="line">datadir <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span>data30<span class="operator">/</span></span><br><span class="line">socket <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span>data30<span class="operator">/</span>mysql.sock</span><br><span class="line"><span class="type">character</span><span class="operator">-</span><span class="keyword">set</span><span class="operator">-</span>server UTF8MB4</span><br><span class="line">lower_case_table_names <span class="number">1</span></span><br><span class="line">log_error <span class="operator">/</span>var<span class="operator">/</span>log<span class="operator">/</span>mysqld.log</span><br><span class="line"></span><br><span class="line">[mysqld3307]</span><br><span class="line"></span><br><span class="line"><span class="keyword">user</span> mysql8</span><br><span class="line">datadir <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3307</span><span class="operator">/</span>data</span><br><span class="line">port <span class="number">3307</span></span><br><span class="line">server_id <span class="number">3307</span></span><br><span class="line">socket <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3307</span><span class="operator">/</span>data<span class="operator">/</span>mysql_3307.sock</span><br><span class="line">log<span class="operator">-</span>bin <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3307</span><span class="operator">/</span>binlog<span class="operator">/</span>mysql3307_bin</span><br><span class="line">log_error <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3307</span><span class="operator">/</span>data<span class="operator">/</span>mysqld.log</span><br><span class="line"></span><br><span class="line">[mysqld3308]</span><br><span class="line"></span><br><span class="line"><span class="keyword">user</span> mysql8</span><br><span class="line">datadir <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3308</span><span class="operator">/</span>data</span><br><span class="line">port <span class="number">3308</span></span><br><span class="line">server_id <span class="number">3308</span></span><br><span class="line">socket <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3308</span><span class="operator">/</span>data<span class="operator">/</span>mysql_3308.sock</span><br><span class="line">log<span class="operator">-</span>bin <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3308</span><span class="operator">/</span>binlog<span class="operator">/</span>mysql3308_bin</span><br><span class="line">log_error <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span><span class="number">3308</span><span class="operator">/</span>data<span class="operator">/</span>mysqld.log</span><br><span class="line"></span><br><span class="line">[client]</span><br><span class="line">socket <span class="operator">/</span>home<span class="operator">/</span>mysql8<span class="operator">/</span>data30<span class="operator">/</span>mysql.sock</span><br></pre></td></tr></table></figure><h4 id="创建数据目录和日志目录"><a href="#创建数据目录和日志目录" class="headerlink" title="创建数据目录和日志目录"></a>创建数据目录和日志目录</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">su - mysql8</span><br><span class="line"><span class="built_in">mkdir</span> 3307 3308</span><br><span class="line"><span class="built_in">mkdir</span> 3307/binlog</span><br><span class="line"><span class="built_in">mkdir</span> 3307/data</span><br><span class="line"><span class="built_in">mkdir</span> 3308/binlog</span><br><span class="line"><span class="built_in">mkdir</span> 3308/data</span><br><span class="line"><span class="built_in">exit</span></span><br></pre></td></tr></table></figure><h4 id="初始化数据库"><a href="#初始化数据库" class="headerlink" title="初始化数据库"></a>初始化数据库</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line">mysqld <span class="comment">--user mysql8 \</span></span><br><span class="line"><span class="comment">--basedir /usr/local/mysql8.0.30/ \</span></span><br><span class="line"><span class="comment">--datadir /home/mysql8/3307/data \</span></span><br><span class="line"><span class="comment">--lower-case-table-names 1 \</span></span><br><span class="line"><span class="comment">--initialize</span></span><br><span class="line"></span><br><span class="line">mysqld <span class="comment">--user mysql8 \</span></span><br><span class="line"><span class="comment">--basedir /usr/local/mysql8.0.30/ \</span></span><br><span class="line"><span class="comment">--datadir /home/mysql8/3308/data \</span></span><br><span class="line"><span class="comment">--lower-case-table-names 1 \</span></span><br><span class="line"><span class="comment">--initialize </span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img1.avif"></p><h4 id="查看全部实例的状态"><a href="#查看全部实例的状态" class="headerlink" title="查看全部实例的状态"></a>查看全部实例的状态</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line">su - mysql8</span><br><span class="line">mysqld_multi report</span><br><span class="line"></span><br><span class="line"><span class="comment">#这里可能需要配置下mysql8的环境变量</span></span><br><span class="line">su - mysql8</span><br><span class="line">vim .bash_profile /添加下述内容</span><br><span class="line"></span><br><span class="line"><span class="built_in">export</span> MYSQL_HOME /usr/local/mysql8.0.30</span><br><span class="line"><span class="built_in">export</span> PATH <span class="variable">$MYSQL_HOME</span>/bin:<span class="variable">$PATH</span></span><br><span class="line"></span><br><span class="line"><span class="comment">#设置mysqld_multi.log文件的属主和属组</span></span><br><span class="line">su - root</span><br><span class="line"><span class="built_in">chown</span> mysql8.mysql8 /home/mysql8/data30/mysqld_multi.log</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img2.avif"></p><h4 id="启动单个实例"><a href="#启动单个实例" class="headerlink" title="启动单个实例"></a>启动单个实例</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi <span class="keyword">start</span> <span class="number">3307</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img3.avif"></p><h4 id="关闭单个实例"><a href="#关闭单个实例" class="headerlink" title="关闭单个实例"></a>关闭单个实例</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi stop <span class="number">3307</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img4.avif"></p><p>关闭失败了,查看mysqld_multi.log日志,发现’root’ ‘localhost’ 连接被拒绝了</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img5.avif"></p><p>那么就在关闭的时候指定用户和密码,但是要重置实例密码,不然密码是过期状态</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi <span class="comment">--user root --password &#x27;123456&#x27; stop 3307</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img6.avif"></p><p>重置密码</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">mysqladmin -S 3307/data/mysql_3307.sock -P 3307 -uroot -p&#x27;M&gt;_2k3fXO&amp;g7&#x27; password &#x27;123456&#x27;</span><br><span class="line">mysqladmin -S 3308/data/mysql_3308.sock -P 3308 -uroot -p&#x27;CriDygysI3*H&#x27; password &#x27;123456&#x27;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img7.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img8.avif"></p><p>最后再尝试关闭,已经OK</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi <span class="comment">--user root --password &#x27;123456&#x27; stop 3308</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img9.avif"></p><h4 id="启动多个实例"><a href="#启动多个实例" class="headerlink" title="启动多个实例"></a>启动多个实例</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi <span class="keyword">start</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img10.avif"></p><h4 id="关闭多个实例"><a href="#关闭多个实例" class="headerlink" title="关闭多个实例"></a>关闭多个实例</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line">mysqld_multi stop</span><br><span class="line"></span><br><span class="line">su - root</span><br><span class="line">vim /etc/my.cnf</span><br><span class="line"></span><br><span class="line"><span class="comment">#[mysqld_multi]模块中添加</span></span><br><span class="line">user root</span><br><span class="line">pass 123456</span><br><span class="line"></span><br><span class="line"><span class="comment">#如果每个MySQL服务器的密码不一样,只需要在[mysqld_multi]中添加多个密码即可</span></span><br><span class="line">user root</span><br><span class="line">pass 123456</span><br><span class="line">pass 123457</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img11.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img12.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/12/9002a947/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL二进制包安装</title>
      <link>https://blog.eucalyptus.cc/2025/07/12/dc82ac95/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/12/dc82ac95/</guid>
      <pubDate>Sat, 12 Jul 2025 01:45:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;创建属组和mysql8用户&lt;/p&gt;
&lt;figure class=&quot;highlight text&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;1&lt;/span&gt;&lt;br&gt;&lt;span</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>创建属组和mysql8用户</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">groupadd mysql8</span><br><span class="line">useradd -g mysql8 -d /home/mysql8 mysql8</span><br></pre></td></tr></table></figure><p>下载tar包</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">wget https://downloads.mysql.com/archives/get/p/23/file/mysql-8.0.30-el7-x86_64.tar.gz</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img1.avif"></p><p><a href="https://downloads.mysql.com/archives/community/">https://downloads.mysql.com/archives/community/</a></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#解压</span></span><br><span class="line">tar -xavf mysql-8.0.30-el7-x86_64.tar.gz</span><br><span class="line"></span><br><span class="line"><span class="comment">#将解压后的文件移动到/usr/local/目录下并命名为mysql8.0.30</span></span><br><span class="line"><span class="built_in">mv</span> mysql-8.0.30-el7-x86_64 /usr/local/mysql8.0.30</span><br><span class="line"></span><br><span class="line"><span class="comment">#修改/usr/local/mysql8.0.30属组</span></span><br><span class="line"><span class="built_in">chown</span> -R mysql8.mysql8 /usr/local/mysql8.0.30</span><br></pre></td></tr></table></figure><p>创建MySQL数据文件目录-使用刚才创建的mysql8用户</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">su - mysql8</span><br><span class="line"><span class="built_in">mkdir</span> data30</span><br><span class="line"><span class="built_in">exit</span></span><br></pre></td></tr></table></figure><p>配置环境变量</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">vim /root/.bash_profile</span><br><span class="line"><span class="comment">#添加下述内容</span></span><br><span class="line"><span class="built_in">export</span> MYSQL_HOME /usr/local/mysql8.0.30</span><br><span class="line"><span class="built_in">export</span> PATH <span class="variable">$MYSQL_HOME</span>/bin:<span class="variable">$PATH</span></span><br><span class="line"><span class="built_in">export</span> PATH <span class="variable">$PATH</span>:/usr/local/mysql8.0.30/bin</span><br><span class="line"></span><br><span class="line"><span class="comment">#使用source生效</span></span><br><span class="line"><span class="built_in">source</span> /root/.bash_profile</span><br></pre></td></tr></table></figure><p>初始化数据库</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"> mysqld <span class="comment">--user mysql8 \</span></span><br><span class="line"><span class="comment">--basedir /usr/local/mysql8.0.30/ \</span></span><br><span class="line"><span class="comment">--datadir /home/mysql8/data30/ \</span></span><br><span class="line"><span class="comment">--lower-case-table-names 1 \</span></span><br><span class="line"><span class="comment">--initialize</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img2.avif"></p><p>配置&#x2F;etc&#x2F;my.cnf文件</p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[mysqld]</span></span><br><span class="line">basedir /usr/local/mysql8.0.30/</span><br><span class="line">datadir /home/mysql8/data30/</span><br><span class="line">socket /home/mysql8/data30/mysql.sock</span><br><span class="line">character-set-server UTF8MB4</span><br><span class="line">lower_case_table_names 1</span><br><span class="line"></span><br><span class="line"><span class="section">[client]</span></span><br><span class="line">socket /home/mysql8/data30/mysql.sock</span><br></pre></td></tr></table></figure><p>这里可以直接启动</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/mysql8.0.30/bin/mysqld --defaults-file /home/mysql8/my.cnf &amp;</span><br></pre></td></tr></table></figure><p>也可以添加服务器然后再启动</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cp</span> /usr/local/mysql8.0.30/support-files/mysql.server /etc/init.d/mysql8</span><br></pre></td></tr></table></figure><p>添加mysql8服务</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">chkconfig --add mysql8</span><br></pre></td></tr></table></figure><p>启动mysql服务</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">su <span class="operator">-</span> mysql8</span><br><span class="line">service mysql8 <span class="keyword">start</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img3.avif"></p><p>修改初始密码然后登陆</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqladmin -u root -p&#x27;NgDK3)NCldDi&#x27; password &#x27;123456&#x27;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img5.avif"></p><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><p>在编译安装之后可以禁用自动重启,不然每次重启宿主机后,mysqld_safe都会以root运行,然后启动mysql。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl is-enabled mysql8</span><br><span class="line">systemctl <span class="built_in">disable</span> mysql8</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-12/img7.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/12/dc82ac95/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的分区表</title>
      <link>https://blog.eucalyptus.cc/2025/07/11/7d7b2050/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/11/7d7b2050/</guid>
      <pubDate>Fri, 11 Jul 2025 07:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;通常情况下,同一张表的数据在物理层面都是存放在一起的。随着业务增长,当同一张表的数据量过大时,会带来管理上的不便。而分区特性可以将一张表从物理层面根据一定的规则将数据划分为多个分区,多个分区可以单独管理,甚至存放在不同的磁盘&amp;#x2F;文件系统上,提升效率。&lt;/p&gt;
&lt;p&gt;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>通常情况下,同一张表的数据在物理层面都是存放在一起的。随着业务增长,当同一张表的数据量过大时,会带来管理上的不便。而分区特性可以将一张表从物理层面根据一定的规则将数据划分为多个分区,多个分区可以单独管理,甚至存放在不同的磁盘&#x2F;文件系统上,提升效率。</p><p>分区表的优点:</p><ul><li>数据可以跨磁盘&#x2F;文件系统存储,适合存储大量数据。</li><li>数据的管理非常方便,以分区为单位操作数据,不会影响其他分区的正常运行。</li><li>数据查询上在某些条件可以利用分区裁剪(partition pruning)特性,将搜索范围快速定位到特性分区,提升查询性能。</li></ul><p>对于应用来说,表依然是一个逻辑整体,但数据库可以针对不同的数据分区独立执行管理操作,不影响其他分区的运行。而数据划分的规则即称为分区函数,数据写入表时,会根据运算结果决定写入哪个分区。</p><p>MySQL的分区插件与存储引擎运行在不同的层,因此大部分存储引擎都可以利用MySQL的分区特性,只有少数存储引擎 merge,CSV,federated 不支持分区特性。若某张表使用的分区特性,则所有的分区都需要使用相同的存储引擎,且分区特性会同时应用到数据和索引上。</p><h2 id="分区表类型-主分区"><a href="#分区表类型-主分区" class="headerlink" title="分区表类型 主分区"></a>分区表类型 主分区</h2><h3 id="Range-partition-范围分区"><a href="#Range-partition-范围分区" class="headerlink" title="Range partition 范围分区"></a>Range partition 范围分区</h3><p>Range partition是按照分区表达式的运算结果,判断结果落在某个范围内,从而将数据存储在对应的分区。各个分区定义之间需要连续且不能重叠,范围分区通过partition by range子句定义,而分区的范围通过values less than子句划分。</p><p>例:定义一个员工表,根据员工ID分区,1<del>10号员工一个分区,11</del>20号员工一个分区,依次类推,共建立4个分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create table</span> employees (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">not null</span> <span class="keyword">primary key</span>,</span><br><span class="line">first_name <span class="type">varchar</span>(<span class="number">30</span>),</span><br><span class="line">last_name <span class="type">varchar</span>(<span class="number">30</span>))</span><br><span class="line"><span class="keyword">partition</span> <span class="keyword">by</span> <span class="keyword">range</span>(id)(</span><br><span class="line"><span class="keyword">partition</span> p0 <span class="keyword">values</span> less than (<span class="number">11</span>),</span><br><span class="line"><span class="keyword">partition</span> p1 <span class="keyword">values</span> less than (<span class="number">21</span>),</span><br><span class="line"><span class="keyword">partition</span> p2 <span class="keyword">values</span> less than (<span class="number">31</span>),</span><br><span class="line"><span class="keyword">partition</span> p3 <span class="keyword">values</span> less than (<span class="number">41</span>)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>现在随便插入几条数据:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> employees <span class="keyword">values</span>(<span class="number">1</span>,<span class="string">&#x27;Vincent&#x27;</span>,<span class="string">&#x27;Chen&#x27;</span>);</span><br><span class="line"><span class="keyword">insert into</span> employees <span class="keyword">values</span>(<span class="number">6</span>,<span class="string">&#x27;Victor&#x27;</span>,<span class="string">&#x27;Chen&#x27;</span>);</span><br><span class="line"><span class="keyword">insert into</span> employees <span class="keyword">values</span>(<span class="number">11</span>,<span class="string">&#x27;Grace&#x27;</span>,<span class="string">&#x27;Li&#x27;</span>);</span><br><span class="line"><span class="keyword">insert into</span> employees <span class="keyword">values</span>(<span class="number">16</span>,<span class="string">&#x27;San&#x27;</span>,<span class="string">&#x27;Zhang&#x27;</span>);</span><br></pre></td></tr></table></figure><h4 id="range-columns分区"><a href="#range-columns分区" class="headerlink" title="range columns分区"></a>range columns分区</h4><p>在5.7中,原生的range 分区只能使用整数 <code>INT</code>&#x2F;<code>BIGINT</code>&#x2F;<code>SMALLINT</code>… ,并且只能写列本身,不能添加任何函数和表达式。</p><p>在8.0中可以使用range columns,range columns针对数据类型放宽了很多 <code>CHAR</code>&#x2F;<code>VARCHAR</code>&#x2F;<code>DATE</code>&#x2F;<code>DATETIME</code>&#x2F;<code>INT</code>&#x2F;<code>DECIMAL</code> … ,但是仍然不能添加任何函数和表达式。</p><h4 id="分区查询"><a href="#分区查询" class="headerlink" title="分区查询"></a>分区查询</h4><p>如果在查询时候明确的知道数据所在的分区,我们可以直接指定分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> employees <span class="keyword">partition</span>(p0); <span class="comment">-- 查询p0分区</span></span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> employees <span class="keyword">partition</span>(p0,p1); <span class="comment">-- 查询p0和p1分区</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img1.avif"></p><h4 id="分区删除"><a href="#分区删除" class="headerlink" title="分区删除"></a>分区删除</h4><p>如果某分区数据不再需要的时候,我们可以用alter table … drop partition来删除指定分区,例如删除分区p1,采用drop partition的方式可以快速清除历史数据:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> employees <span class="keyword">drop</span> <span class="keyword">partition</span> p1;</span><br></pre></td></tr></table></figure><p>分区p1被删除后,所有p1分区的数据都已丢失,此时原p1分区的范围将由p2覆盖。</p><h4 id="分区新增"><a href="#分区新增" class="headerlink" title="分区新增"></a>分区新增</h4><p>对于range分区来说,分区新增只能在最大范围之上增加分区,因此p1分区被删除后就无法通过新增分区的方式加回了,下例试图对ID10~20的员工新增一个分区,系统会返还错误。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img2.avif"></p><h4 id="分区重组织"><a href="#分区重组织" class="headerlink" title="分区重组织"></a>分区重组织</h4><p>如果一定要在分区之间插入新的分区,则可以采用重组织的方式,将已有分区的数据重新划分,达到创建新分区的效果:</p><p>例如我要将p2划分为2个分区,分别是11<del>20,21</del>30:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> employees reorganize <span class="keyword">partition</span> p2 <span class="keyword">into</span> (</span><br><span class="line"><span class="keyword">partition</span> p1 <span class="keyword">values</span> less than(<span class="number">21</span>),</span><br><span class="line"><span class="keyword">partition</span> p2 <span class="keyword">values</span> less than(<span class="number">31</span>));</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img3.avif"></p><p>此时原p2分区被拆分为了p1,p2,数据也在2个分区间重新分布,保证不会丢失。效果就像我们在中间插入了一个分区一样。</p><p>目前定义的分区都是有上限的,如果有大于分区上限的值想插入表中,系统会返还错误,为了兼容这种情况,我们可以新增一个分区,上限为maxvalue。所有大于当前上限的值都会放入这个分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> employees <span class="keyword">add</span> <span class="keyword">partition</span>(<span class="keyword">partition</span> pmax <span class="keyword">values</span> less than(maxvalue));</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img4.avif"></p><p>范围分区的条件除了直接用值,还可以用函数来定义。一个常用的场景就是按时间分区,例如:在create table中使用partition by range(year(hire_date)),可以按照年份来进行分区。这种分区方式在需要定期清理过期数据的场景会非常方便。</p><p>Range columns分区:</p><p>Range分区还有一个变种,叫做range columns分区。此分区方式允许使用多个column来作为分区范围条件。但是此分区方式不能接受函数,只能直接用列的名称。但是对分区列的类型不再限制为整数,可以使用string,date等类型。</p><p>使用range columns对多个列进行分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> rc2 (</span><br><span class="line">a <span class="type">INT</span>,</span><br><span class="line">b <span class="type">INT</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> <span class="keyword">RANGE</span> COLUMNS(a,b) (</span><br><span class="line"><span class="keyword">PARTITION</span> p0 <span class="keyword">VALUES</span> LESS THAN (<span class="number">0</span>,<span class="number">10</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p1 <span class="keyword">VALUES</span> LESS THAN (<span class="number">10</span>,<span class="number">20</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p2 <span class="keyword">VALUES</span> LESS THAN (<span class="number">10</span>,<span class="number">30</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p3 <span class="keyword">VALUES</span> LESS THAN (MAXVALUE,MAXVALUE) );</span><br></pre></td></tr></table></figure><p>使用range columns直接对date类型进行分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> members (</span><br><span class="line">firstname <span class="type">VARCHAR</span>(<span class="number">25</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">lastname <span class="type">VARCHAR</span>(<span class="number">25</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">username <span class="type">VARCHAR</span>(<span class="number">16</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">joined <span class="type">DATE</span> <span class="keyword">NOT NULL</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> <span class="keyword">RANGE</span> COLUMNS(joined) (</span><br><span class="line"><span class="keyword">PARTITION</span> p0 <span class="keyword">VALUES</span> LESS THAN (<span class="string">&#x27;1960-01-01&#x27;</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p1 <span class="keyword">VALUES</span> LESS THAN (<span class="string">&#x27;1970-01-01&#x27;</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p2 <span class="keyword">VALUES</span> LESS THAN (<span class="string">&#x27;1980-01-01&#x27;</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p3 <span class="keyword">VALUES</span> LESS THAN (<span class="string">&#x27;1990-01-01&#x27;</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p4 <span class="keyword">VALUES</span> LESS THAN MAXVALUE);</span><br></pre></td></tr></table></figure><p><strong>Range partition和null:</strong></p><p>对range分区来说,如果插入数据分区键为null,是可以成功的,数据会被放到第一个分区中。</p><h3 id="List-partition-列表分区"><a href="#List-partition-列表分区" class="headerlink" title="List partition(列表分区)"></a><strong>List partition(列表分区)</strong></h3><p>列表分区和范围分区类似,主要区别是list partition的分区范围是预先定义好的一系列值,而不是连续的范围。列表分区采用partition by list和values in子句定义。</p><p>示例,创建一张员工表按照ID进行列表分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> employees (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">fname <span class="type">VARCHAR</span>(<span class="number">30</span>),</span><br><span class="line">lname <span class="type">VARCHAR</span>(<span class="number">30</span>)</span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> LIST(id) (</span><br><span class="line"><span class="keyword">PARTITION</span> p0 <span class="keyword">VALUES</span> <span class="keyword">IN</span> (<span class="number">1</span>,<span class="number">3</span>,<span class="number">5</span>,<span class="number">7</span>,<span class="number">9</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p1 <span class="keyword">VALUES</span> <span class="keyword">IN</span> (<span class="number">2</span>,<span class="number">4</span>,<span class="number">6</span>,<span class="number">8</span>,<span class="number">10</span>)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>和range分区一样,可以使用alter table … add&#x2F;drop partition新增&#x2F;删除分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees <span class="keyword">ADD</span> <span class="keyword">PARTITION</span>(<span class="keyword">PARTITION</span> p2 <span class="keyword">VALUES</span> <span class="keyword">IN</span> (<span class="number">11</span>,<span class="number">12</span>,<span class="number">13</span>,<span class="number">14</span>,<span class="number">15</span>));</span><br><span class="line"><span class="keyword">ALTER TABLE</span> employees <span class="keyword">DROP</span> <span class="keyword">PARTITION</span> p0;</span><br></pre></td></tr></table></figure><h4 id="List-columns分区"><a href="#List-columns分区" class="headerlink" title="List columns分区"></a><strong>L</strong>ist columns分区</h4><p>和range分区类似,list partition也有一个变种的list columns 分区,此分区类型可以使用多个列同时作为分区条件,且不再限制整数。并且可以使用string,date等数据类型作为分区条件。</p><p>list partition和null:</p><p>对于列表分区来说,必须有1个分区显示的指定可以包含null,否则插入会失败。</p><h3 id="Hash-partition-哈希分区"><a href="#Hash-partition-哈希分区" class="headerlink" title="Hash partition(哈希分区)"></a>Hash partition(哈希分区)</h3><p>Hash partition主要的应用场景是将数据平均的分布在指定数量的hash分区中。在range和list分区类型中,根据分区条件的计算结果,数据可以确定存储在哪个分区,而在hash分区中,数据存储在某个分区是由数据库自己决定的,你只需要指定分区的数量。</p><p>要创建hash分区,你需要使用create table的partition by hash(expr)子句,其中expr是整数类型的列或返还整数的表达式。另外还需要使用partions num来指定hash分区的数量(若忽略partitions子句则默认只创建1个hash分区)。</p><p>例:创建一个具有4个hash分区的表,按照ID进行分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> employees (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">first_name <span class="type">VARCHAR</span>(<span class="number">30</span>),</span><br><span class="line">last_name <span class="type">VARCHAR</span>(<span class="number">30</span>)</span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> HASH(id)</span><br><span class="line">PARTITIONS <span class="number">4</span>;</span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> employees (id, first_name, last_name) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">1</span>, <span class="string">&#x27;Alice&#x27;</span>, <span class="string">&#x27;Smith&#x27;</span>),</span><br><span class="line">(<span class="number">2</span>, <span class="string">&#x27;Bob&#x27;</span>, <span class="string">&#x27;Johnson&#x27;</span>),</span><br><span class="line">(<span class="number">3</span>, <span class="string">&#x27;Charlie&#x27;</span>, <span class="string">&#x27;Brown&#x27;</span>),</span><br><span class="line">(<span class="number">4</span>, <span class="string">&#x27;David&#x27;</span>, <span class="string">&#x27;Davis&#x27;</span>),</span><br><span class="line">(<span class="number">5</span>, <span class="string">&#x27;Eve&#x27;</span>, <span class="string">&#x27;Evans&#x27;</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img5.avif"></p><p><strong>Hash分区的性能考虑:</strong></p><p>对于hash分区,数据库决定将数据存储在哪个分区是采用取余的方式进行运算的。存储分区的编号n mod(expr, num),其中expr是分区值,num为定义的分区数量。</p><p>例如:对于4个hash分区,ID为5的记录,会存储在mod(5,4) 1,即1号分区中。</p><p>因此,最佳的分区键值的变化方式应该是线性变化,此时使用hash分区的效率最高,分布也会均匀。由于分区键值expr在每次insert&#x2F;update&#x2F;delete时都会运算,太复杂的表达式也会带来负面的性能影响,在选择时也需要考虑。</p><p><strong>Liner hash partition(线性哈希分区):</strong></p><p>以上的分区类型即普通hash分区,另外还有一类变种叫做liner hash partition(线性哈希分区),线性哈希分区的区别是其使用了更复杂的计算方法来确定数据的分布:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">1. 对于分区数量为num的分区表,先计算V:</span><br><span class="line">V POWER(2, CEILING(LOG(2, num)))</span><br><span class="line"></span><br><span class="line">2. 对于分区值与V-1进行位与运算</span><br><span class="line">N expr &amp; (V - 1) -- 位与运算</span><br><span class="line"></span><br><span class="line">3. 对于N&gt;num的情况,再次计算</span><br><span class="line">N N &amp; ((v/2)-1) </span><br></pre></td></tr></table></figure><p>函数算法:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">log 2,num ,2^n num</span><br><span class="line">ceiling n</span><br><span class="line">power 2,n ,2^n</span><br><span class="line">v 2^n</span><br></pre></td></tr></table></figure><p>位与运算跟进二进制来计算</p><p>示例</p><p>假设我们有两个整数 <code>A</code> 和 <code>B</code>,它们的二进制表示如下:</p><p><code>A 5</code>,二进制表示为 <code>0101</code></p><p><code>B 3</code>,二进制表示为 <code>0011</code></p><p>进行位与运算:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"> 0101</span><br><span class="line">&amp; 0011</span><br><span class="line">------</span><br><span class="line">0001</span><br></pre></td></tr></table></figure><p>结果是 <code>0001</code>,即十进制的 <code>1</code></p><p>例:假设分区数量为4</p><ul><li>先根据分区数量num计算V的值,先log再power,如果分区数量如果是2的次方,则此公式计算结果不变。</li></ul><p>V power(2,ceilling(log(2,4))) power(2,ceillling(2)) power(2,2) 4</p><ul><li>对于ID为5的记录:</li></ul><p>N 5 &amp; (V-1) 5 &amp; 3 1</p><ul><li>第二步计算出的结果为1,N&lt; num,不再需要第三步计算,数据存储在1号分区。</li></ul><p>计算机的位计算效率是非常高的,因此Liner hash在新增&#x2F;删除&#x2F;合并&#x2F;分裂分区场景 需要重新计算并分布数据 速度会快很多,非常适合特别大的数据存储场景 TB级别 。</p><p>Liner hash的缺点是数据的分布可能没有普通hash均匀</p><h4 id="管理hash分区数量"><a href="#管理hash分区数量" class="headerlink" title="管理hash分区数量"></a><strong>管理hash分区数量</strong></h4><p>Hash分区无法像range和list那样添加和删除分区,但是你可以用alter table的coalesce partition子句来减少hash分区的数量,用add partition partitions N来增加指定数量的分区。</p><p>例:将employees的hash分区数量由4调整为3:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees COALESCE <span class="keyword">PARTITION</span> <span class="number">1</span>; <span class="comment">-- 移除一个分区</span></span><br></pre></td></tr></table></figure><p>例:为employees表新增3个hash分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees <span class="keyword">ADD</span> <span class="keyword">PARTITION</span> PARTITIONS <span class="number">3</span>; <span class="comment">-- 新增3个hash分区</span></span><br></pre></td></tr></table></figure><p><strong>hahs partition和null:</strong></p><p>对于hash partition和key partition,任何表达式对null运算,都会被当做返回为0.</p><h3 id="Key-partition-键值分区"><a href="#Key-partition-键值分区" class="headerlink" title="Key partition(键值分区)"></a>Key partition(键值分区)</h3><p>Key paritition与hash分区类似,主要区别在于key partition的hash函数是由MySQL server提供的,且使用主键 或非空唯一键 作为分区列:</p><p>例如:创建一个2个分区的key partition table:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> k1 (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">NOT NULL</span> <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">20</span>)</span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> KEY() <span class="comment">-- 未指定分区列,自动使用主键</span></span><br><span class="line">PARTITIONS <span class="number">2</span>;</span><br><span class="line"><span class="keyword">INSERT INTO</span> k1 (id, name) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">1</span>, <span class="string">&#x27;Name1&#x27;</span>),</span><br><span class="line">(<span class="number">2</span>, <span class="string">&#x27;Name2&#x27;</span>),</span><br><span class="line">(<span class="number">3</span>, <span class="string">&#x27;Name3&#x27;</span>),</span><br><span class="line">(<span class="number">4</span>, <span class="string">&#x27;Name4&#x27;</span>),</span><br><span class="line">(<span class="number">5</span>, <span class="string">&#x27;Name5&#x27;</span>),</span><br><span class="line">(<span class="number">6</span>, <span class="string">&#x27;Name6&#x27;</span>),</span><br><span class="line">(<span class="number">7</span>, <span class="string">&#x27;Name7&#x27;</span>),</span><br><span class="line">(<span class="number">8</span>, <span class="string">&#x27;Name8&#x27;</span>),</span><br><span class="line">(<span class="number">9</span>, <span class="string">&#x27;Name9&#x27;</span>),</span><br><span class="line">(<span class="number">10</span>, <span class="string">&#x27;Name10&#x27;</span>),</span><br><span class="line">(<span class="number">11</span>, <span class="string">&#x27;Name11&#x27;</span>),</span><br><span class="line">(<span class="number">12</span>, <span class="string">&#x27;Name12&#x27;</span>),</span><br><span class="line">(<span class="number">13</span>, <span class="string">&#x27;Name13&#x27;</span>),</span><br><span class="line">(<span class="number">14</span>, <span class="string">&#x27;Name14&#x27;</span>),</span><br><span class="line">(<span class="number">15</span>, <span class="string">&#x27;Name15&#x27;</span>),</span><br><span class="line">(<span class="number">16</span>, <span class="string">&#x27;Name16&#x27;</span>),</span><br><span class="line">(<span class="number">17</span>, <span class="string">&#x27;Name17&#x27;</span>),</span><br><span class="line">(<span class="number">18</span>, <span class="string">&#x27;Name18&#x27;</span>),</span><br><span class="line">(<span class="number">19</span>, <span class="string">&#x27;Name19&#x27;</span>),</span><br><span class="line">(<span class="number">20</span>, <span class="string">&#x27;Name20&#x27;</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img6.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> k1 (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">NOT NULL</span>, <span class="comment">-- 如果未定义not null,创建表会失败</span></span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">20</span>),</span><br><span class="line"><span class="keyword">UNIQUE</span> KEY (id)</span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> KEY() <span class="comment">-- 未定义主键,自动使用unique key</span></span><br><span class="line">PARTITIONS <span class="number">2</span>;</span><br></pre></td></tr></table></figure><p>对于key partition,由于primary key需要同时作为partition key,所以执行alter table … drop partition会报错 NDB引擎表会重组织并生成隐藏的primary key,不受此限制 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img7.avif"></p><p>另外对于key partition,paritition key也不像其他分区类型那样限制为整数类型,例如,可以使用字符型作为分区键:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> tm1 (</span><br><span class="line">s1 <span class="type">CHAR</span>(<span class="number">32</span>) <span class="keyword">PRIMARY KEY</span> <span class="comment">-- 字符型主键,同时作为partition key</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> KEY(s1)</span><br><span class="line">PARTITIONS <span class="number">10</span>;</span><br><span class="line"><span class="keyword">INSERT INTO</span> tm1 (s1) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000000&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000001&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000002&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000003&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000004&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000005&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000006&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000007&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000008&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000009&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000A&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000B&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000C&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000D&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000E&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000000F&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000010&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000011&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000012&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000013&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000014&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000015&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000016&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000017&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000018&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;00000000000000000000000000000019&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000001A&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000001B&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000001C&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000001D&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;0000000000000000000000000000001E&#x27;</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img8.avif"></p><p>Key partition和hash partition一样,也有liner key分区</p><p>Key partition数量的管理方法与hash partition相同</p><h2 id="subpartitioning-子分区"><a href="#subpartitioning-子分区" class="headerlink" title="subpartitioning 子分区"></a>subpartitioning 子分区</h2><p>subpartitioning可以在原有分区表的基础上,对每个分区再次进行分区(子分区)。子分区的分区类型可以和父分区不同,因此也叫复合分区。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> ts (id <span class="type">INT</span>, purchased <span class="type">DATE</span>)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> <span class="keyword">RANGE</span>( <span class="keyword">YEAR</span>(purchased) ) <span class="comment">-- 父分区采用range partition</span></span><br><span class="line">SUBPARTITION <span class="keyword">BY</span> HASH( TO_DAYS(purchased) ) <span class="comment">-- 子分区采用hash partition</span></span><br><span class="line">SUBPARTITIONS <span class="number">2</span> <span class="comment">-- 子分区数量为2</span></span><br><span class="line">(</span><br><span class="line"><span class="keyword">PARTITION</span> p0 <span class="keyword">VALUES</span> LESS THAN (<span class="number">1990</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p1 <span class="keyword">VALUES</span> LESS THAN (<span class="number">2000</span>),</span><br><span class="line"><span class="keyword">PARTITION</span> p2 <span class="keyword">VALUES</span> LESS THAN MAXVALUE</span><br><span class="line">);</span><br><span class="line"><span class="keyword">INSERT INTO</span> ts (id, purchased) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">1</span>, <span class="string">&#x27;1985-01-01&#x27;</span>), (<span class="number">2</span>, <span class="string">&#x27;1986-02-01&#x27;</span>), (<span class="number">3</span>, <span class="string">&#x27;1987-03-01&#x27;</span>), (<span class="number">4</span>, <span class="string">&#x27;1988-04-01&#x27;</span>), (<span class="number">5</span>, <span class="string">&#x27;1989-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">6</span>, <span class="string">&#x27;1991-01-01&#x27;</span>), (<span class="number">7</span>, <span class="string">&#x27;1992-02-01&#x27;</span>), (<span class="number">8</span>, <span class="string">&#x27;1993-03-01&#x27;</span>), (<span class="number">9</span>, <span class="string">&#x27;1994-04-01&#x27;</span>), (<span class="number">10</span>, <span class="string">&#x27;1995-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">11</span>, <span class="string">&#x27;1996-01-01&#x27;</span>), (<span class="number">12</span>, <span class="string">&#x27;1997-02-01&#x27;</span>), (<span class="number">13</span>, <span class="string">&#x27;1998-03-01&#x27;</span>), (<span class="number">14</span>, <span class="string">&#x27;1999-04-01&#x27;</span>), (<span class="number">15</span>, <span class="string">&#x27;2000-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">16</span>, <span class="string">&#x27;2001-01-01&#x27;</span>), (<span class="number">17</span>, <span class="string">&#x27;2002-02-01&#x27;</span>), (<span class="number">18</span>, <span class="string">&#x27;2003-03-01&#x27;</span>), (<span class="number">19</span>, <span class="string">&#x27;2004-04-01&#x27;</span>), (<span class="number">20</span>, <span class="string">&#x27;2005-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">21</span>, <span class="string">&#x27;2006-01-01&#x27;</span>), (<span class="number">22</span>, <span class="string">&#x27;2007-02-01&#x27;</span>), (<span class="number">23</span>, <span class="string">&#x27;2008-03-01&#x27;</span>), (<span class="number">24</span>, <span class="string">&#x27;2009-04-01&#x27;</span>), (<span class="number">25</span>, <span class="string">&#x27;2010-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">26</span>, <span class="string">&#x27;2011-01-01&#x27;</span>), (<span class="number">27</span>, <span class="string">&#x27;2012-02-01&#x27;</span>), (<span class="number">28</span>, <span class="string">&#x27;2013-03-01&#x27;</span>), (<span class="number">29</span>, <span class="string">&#x27;2014-04-01&#x27;</span>), (<span class="number">30</span>, <span class="string">&#x27;2015-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">31</span>, <span class="string">&#x27;2016-01-01&#x27;</span>), (<span class="number">32</span>, <span class="string">&#x27;2017-02-01&#x27;</span>), (<span class="number">33</span>, <span class="string">&#x27;2018-03-01&#x27;</span>), (<span class="number">34</span>, <span class="string">&#x27;2019-04-01&#x27;</span>), (<span class="number">35</span>, <span class="string">&#x27;2020-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">36</span>, <span class="string">&#x27;2021-01-01&#x27;</span>), (<span class="number">37</span>, <span class="string">&#x27;2022-02-01&#x27;</span>), (<span class="number">38</span>, <span class="string">&#x27;2023-03-01&#x27;</span>), (<span class="number">39</span>, <span class="string">&#x27;2024-04-01&#x27;</span>), (<span class="number">40</span>, <span class="string">&#x27;2025-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">41</span>, <span class="string">&#x27;2026-01-01&#x27;</span>), (<span class="number">42</span>, <span class="string">&#x27;2027-02-01&#x27;</span>), (<span class="number">43</span>, <span class="string">&#x27;2028-03-01&#x27;</span>), (<span class="number">44</span>, <span class="string">&#x27;2029-04-01&#x27;</span>), (<span class="number">45</span>, <span class="string">&#x27;2030-05-01&#x27;</span>),</span><br><span class="line">(<span class="number">46</span>, <span class="string">&#x27;2031-01-01&#x27;</span>), (<span class="number">47</span>, <span class="string">&#x27;2032-02-01&#x27;</span>), (<span class="number">48</span>, <span class="string">&#x27;2033-03-01&#x27;</span>), (<span class="number">49</span>, <span class="string">&#x27;2034-04-01&#x27;</span>), (<span class="number">50</span>, <span class="string">&#x27;2035-05-01&#x27;</span>);</span><br></pre></td></tr></table></figure><p>MySQL 的分区表设计允许在查询时指定父分区,但不支持直接指定子分区。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img9.avif"></p><p>你也可以显示的定义每个子分区的名称,但如果采用这种方式定义,则必须显示指定所有子分区。且子分区的数量必须相同,子分区名称不能重复:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> ts (id <span class="type">INT</span>, purchased <span class="type">DATE</span>)</span><br><span class="line"><span class="keyword">PARTITION</span> <span class="keyword">BY</span> <span class="keyword">RANGE</span>( <span class="keyword">YEAR</span>(purchased) ) <span class="comment">--父分区为range partition</span></span><br><span class="line">SUBPARTITION <span class="keyword">BY</span> HASH( TO_DAYS(purchased) ) <span class="comment">--子分区为hash partition</span></span><br><span class="line">(</span><br><span class="line"><span class="keyword">PARTITION</span> p0 <span class="keyword">VALUES</span> LESS THAN (<span class="number">1990</span>) (</span><br><span class="line">SUBPARTITION s0, <span class="comment">-- 显式指定子分区名称和数量</span></span><br><span class="line">SUBPARTITION s1</span><br><span class="line">),</span><br><span class="line"><span class="keyword">PARTITION</span> p1 <span class="keyword">VALUES</span> LESS THAN (<span class="number">2000</span>) (</span><br><span class="line">SUBPARTITION s2,</span><br><span class="line">SUBPARTITION s3</span><br><span class="line">),</span><br><span class="line"><span class="keyword">PARTITION</span> p2 <span class="keyword">VALUES</span> LESS THAN MAXVALUE (</span><br><span class="line">SUBPARTITION s4,</span><br><span class="line">SUBPARTITION s5</span><br><span class="line">)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><h2 id="分区的基本维护"><a href="#分区的基本维护" class="headerlink" title="分区的基本维护"></a><strong>分区的基本维护</strong></h2><p>分区表的一大优势就是各个分区可以独立存储和管理。因此大部分在表级别上的管理操作都可以应该在分区上。</p><h3 id="重建分区"><a href="#重建分区" class="headerlink" title="重建分区"></a><strong>重建分区</strong></h3><p>重建分区功能相当于清除分区中所有记录,然后在重新插入。对于频繁的更新的分区,可以定期使用重建的方式清除碎片</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees REBUILD <span class="keyword">PARTITION</span> p0, p1; <span class="comment">-- 重建p0,p1分区</span></span><br><span class="line"><span class="keyword">ALTER TABLE</span> employees REBUILD <span class="keyword">PARTITION</span> <span class="keyword">ALL</span>; <span class="comment">-- 重建所有分区</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img10.avif"></p><h3 id="检查分区"><a href="#检查分区" class="headerlink" title="检查分区"></a>检查分区</h3><p>你可以用check table语句来检查指定分区是否存在损坏:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees <span class="keyword">CHECK</span> <span class="keyword">PARTITION</span> p1; <span class="comment">-- 检查p1分区</span></span><br><span class="line"><span class="keyword">ALTER TABLE</span> employees <span class="keyword">CHECK</span> <span class="keyword">PARTITION</span> <span class="keyword">all</span>; <span class="comment">-- 检查所有分区</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img11.avif"></p><h3 id="键值分布统计"><a href="#键值分布统计" class="headerlink" title="键值分布统计"></a>键值分布统计</h3><p>使用alter table … analyze partition可以统计指定分区的键值分布,已便更好的生成执行计划:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees ANALYZE <span class="keyword">PARTITION</span> p0; <span class="comment">-- 分析p0分区</span></span><br><span class="line"><span class="keyword">ALTER TABLE</span> employees ANALYZE <span class="keyword">PARTITION</span> <span class="keyword">ALL</span>; <span class="comment">-- 分析所有分区</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img12.avif"></p><h3 id="分区修复"><a href="#分区修复" class="headerlink" title="分区修复"></a>分区修复</h3><p>使用alter table … repair partition来修复损坏的分区:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees REPAIR <span class="keyword">PARTITION</span> p0; <span class="comment">-- 分析p0分区</span></span><br><span class="line"><span class="keyword">ALTER TABLE</span> employees REPAIR <span class="keyword">PARTITION</span> <span class="keyword">ALL</span>; <span class="comment">-- 修复所有分区</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img13.avif"></p><h3 id="优化分区"><a href="#优化分区" class="headerlink" title="优化分区"></a>优化分区</h3><p>如果分区存在大量的数据更新,你可以使用optimize partition来回收空间,收集统计信息。其效果相当于在分区上执执行check partition、analyze partition 和 repair partition一样。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> employees OPTIMIZE <span class="keyword">PARTITION</span> p0;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img14.avif"></p><p>但是对于innodb存储引擎来说,并不支持optimize partition操作,对单一分区执行会导致所有的分区都重建,谨慎使用 Table does not support optimize on partitions. All partitions will be rebuilt and analyzed. 。</p><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img15.avif"></p><p>1、分区数量上限</p><p>自 MySQL 5.6.7 版本起,每个表的分区数 包括主分区和子分区 最大为 8192 个</p><p>早期版本:MySQL 5.6.7 之前的分区数上限为 1024 个</p><p>已下测试版本:8.0.37</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-11/img16.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/11/7d7b2050/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL会话连接数消耗内存分析</title>
      <link>https://blog.eucalyptus.cc/2025/07/10/f0776e15/</link>
      <guid>https://blog.eucalyptus.cc/2025/07/10/f0776e15/</guid>
      <pubDate>Thu, 10 Jul 2025 03:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;关于连接数消耗内存情况&quot;&gt;&lt;a href=&quot;#关于连接数消耗内存情况&quot; class=&quot;headerlink&quot; title=&quot;关于连接数消耗内存情况&quot;&gt;&lt;/a&gt;关于连接数消耗内存情况&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;FROM</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="关于连接数消耗内存情况"><a href="#关于连接数消耗内存情况" class="headerlink" title="关于连接数消耗内存情况"></a>关于连接数消耗内存情况</h3><p><strong>FROM DEEPSEEK</strong></p><p>在 MySQL 中,每个单独的空闲连接所消耗的内存量取决于多个因素,包括连接的线程栈大小 由** thread_stack <strong>参数设置 和其他每个连接的缓冲区。根据测试结果来看,对于空闲连接的内存消耗并没有一个</strong>固定的数值**,因为它会根据连接的活跃状态和执行的查询类型而变化。然而,对于内存规划目的,推荐平均每个连接计划约10MB内存。</p><p>线程栈 Thread Stack 是操作系统为每个线程分配的一段内存区域,用于存储线程的局部变量、函数调用信息、返回地址等。在多线程环境中,每个线程都有自己的线程栈,以确保线程之间数据隔离,防止数据竞争和相互干扰。</p><p><strong>线程栈的大小:</strong></p><p>线程栈的大小对应用程序的性能和资源使用有重要影响。栈太小可能导致栈溢出 Stack Overflow ,而栈太大则可能导致内存浪费。</p><ul><li><p><strong>栈溢出</strong>:如果线程调用的函数太深或局部变量太大,可能会超出栈的限制,导致栈溢出错误。</p></li><li><p><strong>程序崩溃</strong>:当线程栈溢出时,程序可能会崩溃,导致正在执行的数据库操作失败。</p></li><li><p><strong>数据不一致</strong>:如果栈溢出发生在事务处理过程中,可能会导致数据不一致,因为事务可能无法正确提交或回滚。</p></li><li><p><strong>资源泄露</strong>:栈溢出可能导致资源未能正确释放,从而引发内存泄露或其他资源管理问题。</p></li><li><p><strong>内存浪费</strong>:如果栈大小设置得过大,会浪费内存资源,尤其是在创建大量线程的情况下。</p></li></ul><p><strong>MySQL中的线程栈:</strong></p><p>在 MySQL 中,可以通过配置参数 <code>thread_stack</code> 来设置线程栈的大小。这个参数影响 MySQL 服务器为每个新线程分配的内存量。MySQL 5.6 之前的版本中,<code>thread_stack</code> 的默认值通常是 128KB,而在 MySQL 5.7 及更高版本中,这个值增加到了 1MB。</p><p>此外,每个 MySQL 连接需要一定量的内存来维护连接状态、缓存查询结果和执行计划等,这个内存量相对较小,可能在<strong>几十KB到几百KB</strong>之间。对于连接池中的空闲连接,它们会占用一定的内存,但这个内存通常远小于活跃连接时的内存消耗。连接池可以显著减少创建和销毁连接的开销,从而提高数据库交互的效率。</p><p>总的来说,空闲连接的内存消耗相对较小,但随着连接数量的增加,累积的内存消耗可能会变得显著。因此,合理地管理数据库连接,例如通过使用连接池技术,对于优化数据库性能和资源使用非常重要。</p><h3 id="MySQL8-0-28新特性"><a href="#MySQL8-0-28新特性" class="headerlink" title="MySQL8.0.28新特性"></a>MySQL8.0.28新特性</h3><p>MySQL 8.0.28开始,新增一个特性,支持监控统计并限制各个连接 会话 的内存消耗,避免大量用户连接因为执行垃圾SQL消耗过多内存,造成可能被OOM kill的风险。</p><p>首先,需要先设置系统选项 global_connection_memory_tracking 1,之后可以通过系统状态变量 Global_connection_memory 查看当前所有连接消耗的内存总量</p><h4 id="相关参数介绍"><a href="#相关参数介绍" class="headerlink" title="相关参数介绍"></a>相关参数介绍</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">global_connection_memory_tracking</span><br><span class="line"></span><br><span class="line">Global_connection_memory</span><br><span class="line"></span><br><span class="line">connection_memory_chunk_size</span><br><span class="line"></span><br><span class="line">connection_memory_limit</span><br></pre></td></tr></table></figure><p>官方文档:</p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html">https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html</a></p><h4 id="问题分析"><a href="#问题分析" class="headerlink" title="问题分析"></a>问题分析</h4><p>开源 MySQL8.0.37 开启global_connection_memory_tracking参数</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img1.avif"></p><p>当前有3个连接存在,共消耗内存约1096KB</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img2.avif"></p><p>可以看到当新增一个空闲的连接,内存大概增加了8.05KB左右</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img3.avif"></p><p>并发测试:</p><p>待补充…..</p><p>可以调整每个会话连接可使用内存上限,由选项 <code>connection_memory_limit</code> 定义其限制,默认值及最大值都是 18446744073709551615,这个默认值太大了,等同于没有限制。</p><p>设置connection_memory_limit 209715即2MB</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img4.avif"></p><p>然后调用存储过程插入数据时会发现当前会话超出连接内存限制2097152字节,关闭连接</p><p>(4082, ‘Connection closed. Connection memory limit 2097152 bytes exceeded. Consumed 2563352 bytes.’)</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img5.avif"></p><p>除了上面提到的根据Global_connection_memory参数查看外,我们也可以启用performance_schema然后对线程消耗的内存的分析</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> t.PROCESSLIST_ID,</span><br><span class="line">t.PROCESSLIST_INFO,</span><br><span class="line">m.EVENT_NAME,</span><br><span class="line">m.CURRENT_NUMBER_OF_BYTES_USED <span class="operator">/</span> <span class="number">1024</span> <span class="operator">/</span> <span class="number">1024</span> <span class="keyword">AS</span> MB_used</span><br><span class="line"><span class="keyword">FROM</span> performance_schema.memory_summary_by_thread_by_event_name m</span><br><span class="line"><span class="keyword">JOIN</span> performance_schema.threads t <span class="keyword">USING</span> (THREAD_ID)</span><br><span class="line"><span class="keyword">ORDER</span> <span class="keyword">BY</span> MB_used <span class="keyword">DESC</span></span><br><span class="line">LIMIT <span class="number">10</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-07-10/img6.avif"></p><p>可以看到上面的这个DML消耗了大概2.5G的内存</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/07/10/f0776e15/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的隐式主键和隐藏列</title>
      <link>https://blog.eucalyptus.cc/2025/06/20/62e4493d/</link>
      <guid>https://blog.eucalyptus.cc/2025/06/20/62e4493d/</guid>
      <pubDate>Fri, 20 Jun 2025 06:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;从MySQL **8.0.30 **开始,MySQL支持为任何没有显式主键的InnoDB表生成不可见的主键。当sql_generate_invisible_primary_key服务器系统变量设置为&lt;code&gt;ON&lt;/code&gt;时,MySQL服务器会自动将生成的不可见主键</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>从MySQL **8.0.30 **开始,MySQL支持为任何没有显式主键的InnoDB表生成不可见的主键。当sql_generate_invisible_primary_key服务器系统变量设置为<code>ON</code>时,MySQL服务器会自动将生成的不可见主键 GIPK 添加到任何此类表中。此设置对使用除<code>InnoDB</code>以外的任何其他存储引擎创建的表没有影响。</p><p>默认情况下,<code>sql_generate_invisible_primary_key</code>的值为<code>OFF</code>,这意味着GIPK的自动添加被禁用。</p><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html">https://dev.mysql.com/doc/refman/8.0/en/create-table-gipks.html</a></p><h3 id="开源示例"><a href="#开源示例" class="headerlink" title="开源示例"></a>开源示例</h3><p><strong>MySQL 8.0.37</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img1.avif"></p><h4 id="sql-generate-invisible-primary-key-on"><a href="#sql-generate-invisible-primary-key-on" class="headerlink" title="sql_generate_invisible_primary_key on"></a>sql_generate_invisible_primary_key on</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img2.avif"></p><h4 id="sql-generate-invisible-primary-key-off"><a href="#sql-generate-invisible-primary-key-off" class="headerlink" title="sql_generate_invisible_primary_key off"></a>sql_generate_invisible_primary_key off</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img3.avif"></p><h3 id="AliSQL"><a href="#AliSQL" class="headerlink" title="AliSQL"></a>AliSQL</h3><p><strong>MySQL 8.0.36</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img4.avif"></p><h4 id="sql-generate-invisible-primary-key-off-1"><a href="#sql-generate-invisible-primary-key-off-1" class="headerlink" title="sql_generate_invisible_primary_key off"></a>sql_generate_invisible_primary_key off</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img5.avif"></p><p>AliSQL有自研的参数show_ipk_info用来控制是否显示隐式主键的信息</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img6.avif"></p><h3 id="思考"><a href="#思考" class="headerlink" title="思考?"></a>思考?</h3><p>那么为什么再上述sql_generate_invisible_primary_key off的情况下依然会生成一个GEN_CLUST_INDEX聚集索引?</p><p>这是因为 InnoDB 存储引擎要求每个表必须有一个聚集索引。如果表中没有显式定义主键,也没有合适的唯一索引,InnoDB 会内部生成一个隐藏的聚集索引,通常命名为 <code>GEN_CLUST_INDEX</code>。</p><p>这个隐藏的聚集索引是构建在一个包含<strong>行 ID 值的合成列上</strong>的,即使没有生成隐藏列,这个索引也会被创建以满足 InnoDB 对聚集索引的要求。因此,关闭 <code>sql_generate_invisible_primary_key</code> 选项并不影响聚集索引的自动创建,它只影响是否生成一个不可见的主键列。</p><p>row_id 再MVCC中有过介绍</p><p><a href="https://www.yuque.com/eucalyptus-byepv/epkbe4/bgohmgh5m2w69p0z">https://www.yuque.com/eucalyptus-byepv/epkbe4/bgohmgh5m2w69p0z</a></p><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><p><strong>当sql_generate_invisible_primary_key on时</strong>,创建的表有隐藏列 my_row_id 并且再该隐藏列上有primary key的情况下再去添加primary key是不被允许的</p><p>(1068, ‘Multiple primary key defined’)</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img7.avif"></p><p>并且删除隐藏列 my_row_id 和隐藏列 my_row_id 上的primary key都是不被允许的</p><p>(1235, This version of MySQL doesn’t yet support ‘existing primary key drop without adding a new primary key. In sql_generate_invisible_primary_key ON mode table should have a primary key. Please add a new primary key to be able to drop existing primary key.’ )</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img9.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/06/20/62e4493d/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中event突然不执行问题分析</title>
      <link>https://blog.eucalyptus.cc/2025/06/20/d5e54a09/</link>
      <guid>https://blog.eucalyptus.cc/2025/06/20/d5e54a09/</guid>
      <pubDate>Fri, 20 Jun 2025 03:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;分析&quot;&gt;&lt;a href=&quot;#分析&quot; class=&quot;headerlink&quot; title=&quot;分析&quot;&gt;&lt;/a&gt;分析&lt;/h3&gt;&lt;p&gt;1、检查事件调度器状态&lt;/p&gt;
&lt;figure class=&quot;highlight sql&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="分析"><a href="#分析" class="headerlink" title="分析"></a>分析</h3><p>1、检查事件调度器状态</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> variables <span class="keyword">like</span> <span class="string">&#x27;event%&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img1.avif"></p><p>2、检查event状态</p><p>如果event不是enabled的话则需要改为enabled</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> events\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img2.avif"></p><p>3、查看创建event语法,确定多久执行一次</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> <span class="keyword">create</span> event event_name\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img3.avif"></p><p>4、查看information_schema.events系统表确定event的状态,创建时间,修改时间,以及最后一次执行时间</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> information_schema.events <span class="keyword">where</span> event_name <span class="string">&#x27;UpdateEvent&#x27;</span>\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img4.avif"></p><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><p>总的来说event相当于一个定时任务,会定时的执行event中的procedure,但是procedure的存在与否其实并不会影响到event的执行,但是如果event中的procedure不存在的话,会在错误日志中会出现报错</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img7.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img8.avif"></p><p>当然event中还有2个关键的信息,即EVENT_TYPE和ON_COMPLETION,但是后者这里看起来event遇到错误,event并不会被禁用</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img11.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img12.avif"></p><p>一般来说再event突然不执行的情况下,大概率还是event_schema出现了问题</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img13.avif"></p><p>本文章已经生成可运行项目 一键运行**</p><p>生成项目</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/06/20/d5e54a09/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的CONVERT_TZ() 函数</title>
      <link>https://blog.eucalyptus.cc/2025/06/20/b233e1e8/</link>
      <guid>https://blog.eucalyptus.cc/2025/06/20/b233e1e8/</guid>
      <pubDate>Fri, 20 Jun 2025 01:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;code&gt;CONVERT_TZ()&lt;/code&gt; 是 MySQL 中用于在不同时区之间转换时间的函数。它能够将一个时间值从一个时区转换为另一个时区,非常适用于处理跨时区的时间数据。&lt;/p&gt;
&lt;h3 id=&quot;函数语法&quot;&gt;&lt;a href=&quot;#函数语法&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><code>CONVERT_TZ()</code> 是 MySQL 中用于在不同时区之间转换时间的函数。它能够将一个时间值从一个时区转换为另一个时区,非常适用于处理跨时区的时间数据。</p><h3 id="函数语法"><a href="#函数语法" class="headerlink" title="函数语法"></a>函数语法</h3><p><code>CONVERT_TZ()</code> 的语法如下:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">CONVERT_TZ(datetime_expr, from_tz, to_tz)</span><br></pre></td></tr></table></figure><ul><li><code>datetime_expr</code>:要转换的时间值,可以是 <code>DATE</code>、<code>TIME</code> 或 <code>DATETIME</code> 类型。</li><li><code>from_tz</code>:源时区,表示 <code>datetime_expr</code> 所在的时区。</li><li><code>to_tz</code>:目标时区,表示要将时间转换到的时区。</li></ul><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.4/en/date-and-time-functions.html#function_convert-tz">https://dev.mysql.com/doc/refman/8.4/en/date-and-time-functions.html#function_convert-tz</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img1.avif"></p><h4 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h4><p>以下是一些使用 <code>CONVERT_TZ()</code> 的示例:</p><h4 id="示例-1-将-UTC-时间转换为北京时间"><a href="#示例-1-将-UTC-时间转换为北京时间" class="headerlink" title="示例 1:将 UTC 时间转换为北京时间"></a>示例 1:将 UTC 时间转换为北京时间</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONVERT_TZ(<span class="string">&#x27;2025-01-01 00:00:00&#x27;</span>, <span class="string">&#x27;UTC&#x27;</span>, <span class="string">&#x27;Asia/Shanghai&#x27;</span>) <span class="keyword">AS</span> converted_time;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img2.avif"></p><h4 id="示例-2-将北京时间转换为-UTC-时间"><a href="#示例-2-将北京时间转换为-UTC-时间" class="headerlink" title="示例 2:将北京时间转换为 UTC 时间"></a>示例 2:将北京时间转换为 UTC 时间</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONVERT_TZ(<span class="string">&#x27;2025-01-01 08:00:00&#x27;</span>, <span class="string">&#x27;Asia/Shanghai&#x27;</span>, <span class="string">&#x27;UTC&#x27;</span>) <span class="keyword">AS</span> converted_time;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img3.avif"></p><h4 id="示例-3-使用时区偏移量"><a href="#示例-3-使用时区偏移量" class="headerlink" title="示例 3:使用时区偏移量"></a>示例 3:使用时区偏移量</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONVERT_TZ(<span class="string">&#x27;2025-01-01 00:00:00&#x27;</span>, <span class="string">&#x27; 00:00&#x27;</span>, <span class="string">&#x27; 08:00&#x27;</span>) <span class="keyword">AS</span> converted_time;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img4.avif"></p><h4 id="示例-4-处理无效输入"><a href="#示例-4-处理无效输入" class="headerlink" title="示例 4:处理无效输入"></a>示例 4:处理无效输入</h4><p>如果输入的时间格式不正确,或者时区名称无效,<code>CONVERT_TZ()</code> 将返回 <code>NULL</code>:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONVERT_TZ(<span class="string">&#x27;2025-01-01&#x27;</span>, <span class="string">&#x27;UTC&#x27;</span>, <span class="string">&#x27;Invalid/TimeZone&#x27;</span>) <span class="keyword">AS</span> converted_time;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img5.avif"></p><h3 id="相关时区表"><a href="#相关时区表" class="headerlink" title="相关时区表"></a>相关时区表</h3><ul><li>mysql.time_zone:存储时区的基本信息</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img7.avif"></p><ul><li>mysql.time_zone_leap_second:存储闰秒信息</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img9.avif"></p><ul><li>mysql.time_zone_name:存储时区名称与时区 ID 的映射关系</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img11.avif"></p><ul><li>mysql.time_zone_transition:记录时区转换的时间点和转换类型</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img12.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img13.avif"></p><ul><li>mysql.time_zone_transition_type:存储时区转换的具体规则</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img14.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img15.avif"></p><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h3><ul><li><strong>时区表必须已加载</strong>:<code>CONVERT_TZ()</code> 函数依赖于 MySQL 的时区表。如果时区表未加载,函数将无法正常工作。可以通过运行以下命令加载时区表:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img16.avif"></p><p><code>/usr/share/zoneinfo</code> 是 Linux 系统中时区文件的常见路径,具体路径可能因操作系统而异。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img17.avif"></p><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.4/en/time-zone-support.html">https://dev.mysql.com/doc/refman/8.4/en/time-zone-support.html</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-20/img18.avif"></p><ul><li><p><strong>时区名称大小写敏感</strong>:时区名称是大小写敏感的,必须与 MySQL 时区表中的名称完全一致。</p></li><li><p><strong>时区偏移量的限制</strong>:时区偏移量的范围是 <code>-14:00</code> 到 <code> 14:00</code>。</p></li><li><p><strong>MySQL 版本要求</strong>:<code>CONVERT_TZ()</code> 函数在 MySQL 5.5 及以上版本中可用。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/06/20/b233e1e8/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>深入解析 MySQL 中的 SHOW_ROUTINE 权限</title>
      <link>https://blog.eucalyptus.cc/2025/06/05/0710a7de/</link>
      <guid>https://blog.eucalyptus.cc/2025/06/05/0710a7de/</guid>
      <pubDate>Thu, 05 Jun 2025 08:40:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot; title=&quot;前言&quot;&gt;&lt;/a&gt;前言&lt;/h3&gt;&lt;p&gt;SHOW_ROUTINE 是 MySQL 中用于控制用户查看存储过程和函数定义的权限。拥有该权限的用户可以通过 SHOW CREATE</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h3><p>SHOW_ROUTINE 是 MySQL 中用于控制用户查看存储过程和函数定义的权限。拥有该权限的用户可以通过 SHOW CREATE PROCEDURE 和 SHOW CREATE FUNCTION 等语句查看存储过程和函数的详细定义,以及访问 INFORMATION_SCHEMA.ROUTINES 表中的相关信息。</p><p>此权限通常需要通过 GRANT 语句授予用户,且默认为<strong>全局权限</strong>,不能限制到特定数据库。</p><p>它在** MySQL 8.0.20 **版本中被引入,旨在提供一种更精细的权限管理方式,允许用户查看存储过程和函数的定义,而无需授予广泛的全局 SELECT 权限,从而增强了数据库的安全性和灵活性。</p><p>MySQL官网文档:<a href="http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-20.html">http://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-20.html</a></p><h3 id=""><a href="#" class="headerlink" title=""></a><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-05/img1.avif"></h3><h3 id="权限作用"><a href="#权限作用" class="headerlink" title="权限作用"></a>权限作用</h3><p><strong>查看存储过程和函数的定义</strong>:拥有 <code>SHOW_ROUTINE</code> 权限的用户可以通过以下语句查看存储过程和函数的定义:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> <span class="keyword">CREATE</span> <span class="keyword">PROCEDURE</span> procedure_name;</span><br><span class="line"><span class="keyword">SHOW</span> <span class="keyword">CREATE</span> <span class="keyword">FUNCTION</span> function_name;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-05/img2.avif"></p><p><strong>访问存储过程和函数的属性</strong>:该权限允许用户访问存储过程和函数的相关属性,包括:</p><ul><li><code>INFORMATION_SCHEMA.ROUTINES</code> 表的内容。</li><li><code>SHOW FUNCTION STATUS</code> 和 <code>SHOW PROCEDURE STATUS</code> 语句。</li><li><code>SHOW FUNCTION CODE</code> 和 <code>SHOW PROCEDURE CODE</code> 语句。</li></ul><h3 id="授权方法"><a href="#授权方法" class="headerlink" title="授权方法"></a>授权方法</h3><h4 id="MySQL8-0-20以上"><a href="#MySQL8-0-20以上" class="headerlink" title="MySQL8.0.20以上"></a>MySQL8.0.20以上</h4><p><strong>授予全局权限</strong>:可以使用以下语句授予用户全局的 <code>SHOW_ROUTINE</code> 权限:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> SHOW_ROUTINE <span class="keyword">ON</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">TO</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;host&#x27;</span>;</span><br></pre></td></tr></table></figure><p>其中,<code>*.*</code> 表示全局范围,<code>&#39;username&#39; &#39;host&#39;</code> 是指定的用户和主机。</p><p><strong>注意事项:MySQL版本必须大于8.0.20</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-05/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-05/img4.avif"></p><p><strong>注意事项:<code>SHOW_ROUTINE</code> 是一个全局权限,不能在库级别授予,否则会报错。</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-05/img5.avif"></p><h4 id="MySQL8-0-20以下"><a href="#MySQL8-0-20以下" class="headerlink" title="MySQL8.0.20以下"></a>MySQL8.0.20以下</h4><p>MySQL8.0.20以下的版本查看存储过程和函数定义则需要有全局select的权限</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span> <span class="keyword">ON</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">TO</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;host&#x27;</span>;</span><br></pre></td></tr></table></figure><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><p><strong>与全局 <strong><code>SELECT</code></strong> 权限的关系</strong>:在 MySQL 8.0.20 之前,用户需要拥有全局 <code>SELECT</code> 权限才能查看未定义的存储过程和函数的定义。</p><p>从 8.0.20 开始,<code>SHOW_ROUTINE</code> 权限提供了一种更受限制的权限,允许用户访问存储过程和函数的定义,而无需广泛的全局 <code>SELECT</code> 权限。</p><p><strong>适用范围</strong>:<code>SHOW_ROUTINE</code> 权限允许用户访问所有存储过程和函数的定义和属性,即使用户未被命名为存储过程或函数的 <code>DEFINER</code>。</p><p>通过合理授予和管理 <code>SHOW_ROUTINE</code> 权限,可以更好地控制用户对存储过程和函数的访问权限,从而增强数据库的安全性和管理灵活性。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/06/05/0710a7de/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中TCP和套接字SSL加密连接行为分析</title>
      <link>https://blog.eucalyptus.cc/2025/06/01/24af7214/</link>
      <guid>https://blog.eucalyptus.cc/2025/06/01/24af7214/</guid>
      <pubDate>Sun, 01 Jun 2025 02:15:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot; title=&quot;一、前言&quot;&gt;&lt;/a&gt;一、前言&lt;/h3&gt;&lt;p&gt;SSL Secure Sockets Layer 认证是客户端到云数据库服务器端的认证,对用户和服务器进行认证。开通</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h3><p>SSL Secure Sockets Layer 认证是客户端到云数据库服务器端的认证,对用户和服务器进行认证。开通 SSL 加密,可获取 CA 证书,将 CA 证书上传在服务端。在客户端访问数据库时,将激活 SSL 协议,在客户端和数据库服务端之间建立一条 SSL 安全通道,实现数据信息加密传输,防止数据在传输过程中被截取、篡改、窃听,保证双方传递信息的安全性。</p><p>SSL 协议要求建立在可靠的传输层协议 TCP 之上,其优势在于它是与应用层协议独立无关的,高层的应用层协议 例如:HTTP、FTP、TELNET 等 能透明地建立于 SSL 协议之上。SSL 协议在应用层协议通信之前就已经完成加密算法、通信密钥的协商及服务器认证工作,在此之后应用层协议所传送的数据都会被加密,从而保证通信的私密性。</p><h3 id="二、背景"><a href="#二、背景" class="headerlink" title="二、背景"></a>二、背景</h3><p>使用非加密方式连接数据库时,在网络中传输的所有信息都是明文,因此存在被非法用户窃听、篡改、冒充的三大风险;而 SSL 协议是为解决这三大风险而设计的,理论上可达到:</p><ul><li>信息是加密传播,第三方无法窃听。</li><li>具有校验机制,一旦被篡改,通信双方会立刻发现。</li><li>配备身份证书,防止身份被冒充。</li></ul><p>数据库 MySQL 支持通过开启 SSL 加密来增强链路安全性,并支持下载和安装 SSL CA 证书到需要的应用服务。</p><p>SSL 加密不保护数据本身,是确保来往于数据库和服务器之间的流量安全,在传输层对网络连接进行加密,能够提升通信数据的安全性和完整性,但会同时增加网络连接响应时间。</p><h3 id="三、参数介绍"><a href="#三、参数介绍" class="headerlink" title="三、参数介绍"></a>三、参数介绍</h3><h4 id="3-1、-have-openssl"><a href="#3-1、-have-openssl" class="headerlink" title="3.1、 have_openssl"></a>3.1、 have_openssl</h4><ul><li>这个变量表示 MySQL 服务器是否编译时包含了 OpenSSL 支持。OpenSSL 是一个开源的加密库,广泛用于实现 SSL 和 TLS 协议。</li><li>如果值为 <code>YES</code>,表示服务器支持 OpenSSL,可以用于建立安全的 SSL 连接。</li></ul><h4 id="3-2、have-ssl"><a href="#3-2、have-ssl" class="headerlink" title="3.2、have_ssl"></a>3.2、have_ssl</h4><ul><li>这个变量表示 MySQL 服务器是否编译时包含了 SSL 支持。SSL Secure Sockets Layer 用于在客户端和服务器之间建立安全的加密连接。</li><li>如果值为 <code>YES</code>,表示服务器支持 SSL,可以配置 SSL 加密连接。</li></ul><h4 id="3-3、require-secure-transport"><a href="#3-3、require-secure-transport" class="headerlink" title="3.3、require_secure_transport"></a>3.3、require_secure_transport</h4><ul><li>当 <code>require_secure_transport</code> 设置为 <code>ON</code> 时,MySQL 服务器会拒绝所有非加密的客户端连接。这意味着所有客户端连接都必须使用 SSL&#x2F;TLS 加密,以确保数据传输的安全性。</li><li>默认情况下,<code>require_secure_transport</code> 设置为 <code>OFF</code>,允许非加密连接。</li></ul><h3 id="四、–ssl-mode-mode"><a href="#四、–ssl-mode-mode" class="headerlink" title="四、–ssl-mode mode"></a>四、–ssl-mode mode</h3><p>8.0官方文档:<a href="https://dev.mysql.com/doc/refman/8.0/en/connection-options.html">https://dev.mysql.com/doc/refman/8.0/en/connection-options.html</a></p><ul><li><p>DISABLED:禁用 SSL 加密连接。客户端可以不使用 SSL 连接。</p></li><li><p>PREFERRED:首选 SSL 加密连接,如果服务器不支持 SSL,客户端会退回到非加密连接。这是默认值。<br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-01/img1.avif"></p></li><li><p>REQUIRED:必须使用 SSL 加密连接,如果服务器不支持 SSL,连接将失败。</p></li><li><p>VERIFY_CA:必须使用 SSL 加密连接,并验证服务器证书是否由受信任的证书颁发机构签发。</p></li><li><p>VERIFY_IDENTITY:必须使用 SSL 加密连接,并验证服务器证书的主机名或 IP 地址是否与实际连接的主机名或 IP 地址匹配。<br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-01/img2.avif"></p></li></ul><h3 id="五、CREATE-USER-SSL-TLS选项"><a href="#五、CREATE-USER-SSL-TLS选项" class="headerlink" title="五、CREATE USER SSL&#x2F;TLS选项"></a>五、CREATE USER SSL&#x2F;TLS选项</h3><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.0/en/create-user.html#create-user-tls">https://dev.mysql.com/doc/refman/8.0/en/create-user.html#create-user-tls</a></p><p>create user 允许tls_option的值有多个,下面只介绍SSL</p><ul><li><code>SSL</code></li></ul><p>通知服务器只允许语句指定的所有帐户进行加密连接。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">USER</span> <span class="string">&#x27;jeffrey&#x27;</span> <span class="string">&#x27;localhost&#x27;</span> REQUIRE SSL;</span><br></pre></td></tr></table></figure><p>默认情况下,客户端尝试建立安全连接。对于具有<code>REQUIRE SSL</code>的帐户,如果无法建立安全连接,则连接尝试失败。</p><h3 id="六、问题验证"><a href="#六、问题验证" class="headerlink" title="六、问题验证"></a>六、问题验证</h3><h4 id="6-1、使用套接字连接"><a href="#6-1、使用套接字连接" class="headerlink" title="6.1、使用套接字连接"></a>6.1、使用套接字连接</h4><p>这里创建一个demo4的用户并设置该账号进行加密连接</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-01/img3.avif"></p><p>尝试使用套接字进行连接,可以看到这里没有进行安全连接导致连接失败,而指定–ssl-ca后则连接成功,并且使用了ssl加密</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-01/img4.avif"></p><h4 id="6-2、使用TCP连接"><a href="#6-2、使用TCP连接" class="headerlink" title="6.2、使用TCP连接"></a>6.2、使用TCP连接</h4><p>可以看到使用TCP连接时,没有指定–ssl-mode的模式,也没有指定–ssl-ca,但是可以连接成功,没有被拒绝掉,并且连接后发现实际链路还是加密了的</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-06-01/img5.avif"></p><h3 id="七、分析与总结"><a href="#七、分析与总结" class="headerlink" title="七、分析与总结"></a>七、分析与总结</h3><p>问题分析:</p><ul><li>首先TCP 连接是网络层的连接方式,而 SSL 加密是应用层的安全协议。</li><li>其次REQUIRE SSL 仅是账号级别的限制,而非协议级别的强制。</li><li>最后发现当关闭have_ssl和have_openssl后,使用TCP连接后查看实际链路上并没有加密</li></ul><p>实际连接行为:</p><p>当 <code>have_ssl</code> 和 <code>have_openssl</code> 被禁用时:</p><ul><li>无论是使用 TCP 连接还是套接字连接,都不会进行加密连接。</li></ul><p>当 <code>have_ssl</code> 和 <code>have_openssl</code> 被启用时:</p><ul><li>TCP 连接:MySQL 服务器会默认尝试使用加密连接,即使客户端没有显式指定 <code>--ssl-ca</code> 或其他 SSL 参数。这是因为服务器配置为支持 SSL,客户端驱动程序可能会自动协商使用 SSL。</li><li>套接字连接:默认情况下,套接字连接 Unix socket 通常不使用 SSL 加密,因为它是一种本地通信方式。如果用户被设置为 <code>REQUIRE SSL</code>,而客户端没有显式指定 SSL 参数 如 <code>--ssl-ca</code> ,连接将失败,因为套接字连接默认不使用 SSL。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/06/01/24af7214/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>WPCode添加代码启用后网站报错怎么处理</title>
      <link>https://blog.eucalyptus.cc/2025/05/31/3497658a/</link>
      <guid>https://blog.eucalyptus.cc/2025/05/31/3497658a/</guid>
      <pubDate>Sat, 31 May 2025 13:25:07 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;有时候我们使用WPCode插件添加的代码可能会出现问题，或者与其他代码产生冲突，这就可能导致网站出现报错的情况。&lt;/p&gt;
&lt;!-- 这是一张图片，ocr 内容为： --&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>有时候我们使用WPCode插件添加的代码可能会出现问题，或者与其他代码产生冲突，这就可能导致网站出现报错的情况。</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-05-31/1.avif"></p><p>这种时候通常可以采取两种不同的应对方式：</p><h2 id="一、修改文件"><a href="#一、修改文件" class="headerlink" title="一、修改文件"></a>一、修改文件</h2><p>如果在添加代码后网站出现报错，可以尝试通过登录后台服务器或者使用FTP删除或重命名 WPCode 插件的文件夹，这个文件夹的名称通常是 “insert-headers-and-footers”，操作前建议先备份相关数据，以确保网站的安全。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#重命名</span></span><br><span class="line"> <span class="built_in">mv</span> insert-headers-and-footers insert-headers-and-footers-mv</span><br></pre></td></tr></table></figure><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-05-31/2.avif"></p><p>其实不建议使用这种方法，如果你是把代码添加到了functions.php文件中，可以直接编辑并删除。但这种情况涉及的是插件，使用的是WPCode插件，一旦你重新启用它，之前添加的代码又会被载入并保持开启状态，这样一来，你网站上的报错问题还会再次出现。</p><h2 id="二、进入WPCode插件的安全模式"><a href="#二、进入WPCode插件的安全模式" class="headerlink" title="二、进入WPCode插件的安全模式"></a>二、进入WPCode插件的安全模式</h2><p>在网站域名后面加上 <code>/wp-admin/?wpcode-safe-mode=1</code> 即可进入安全模式，例如：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">https://blog.eucalyptus.cc//wp-admin/?wpcode-safe-mode=1</span><br></pre></td></tr></table></figure><p>进入安全模式后可以看到网站将不再执行 WPCode 插件所添加的任何代码。</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-05-31/4.avif"></p><p>这时你可以在后台的WPCode插件中找到刚刚添加并导致错误的代码片段，直接删除或禁用，以恢复正常运行。</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-05-31/3.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%8F%92%E4%BB%B6/">插件</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/05/31/3497658a/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>深入 MySQL 查询优化器：Optimizer Trace 分析</title>
      <link>https://blog.eucalyptus.cc/2025/05/25/7e7ca4d5/</link>
      <guid>https://blog.eucalyptus.cc/2025/05/25/7e7ca4d5/</guid>
      <pubDate>Sun, 25 May 2025 07:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h3><p>我们在日常维护数据库的时候,如果遇到慢语句查询的时候,我们一般会怎么做?执行EXPLAIN去查看它的执行计划?<br>是的。我们经常会这么做,然后看到执行计划展示给我们的一些信息,告诉我们MySQL是如何执行语句的。</p><p>但是执行计划往往只给我们带来了最基础的分析信息,比如是否有使用索引,还有一些其他供我们分析的信息,比如使用了临时表、排序等等。我们能从这些信息里面找一些优化点,这样就足够了吗?</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img1.avif"></p><p>看看这张图里的执行计划,我们可以提很多问题:为什么t1表上明明使用了索引在Extra列中还是能看到filesort?如果possible_keys列中有多个索引的话,优化器是基于什么选定使用的索引?这些问题,并不能非常直观地从执行计划中看出来更多的信息,这个时候,我们可以开启OPTIMIZER_TRACE,基于OPTIMIZER_TRACE捕获的信息,去做更细致的追踪分析。一起来看看吧~</p><h3 id="二、参数详解"><a href="#二、参数详解" class="headerlink" title="二、参数详解"></a>二、参数详解</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img2.avif"></p><h4 id="optimizer-trace"><a href="#optimizer-trace" class="headerlink" title="optimizer_trace"></a><strong>optimizer_trace</strong></h4><ul><li>enabled:启用&#x2F;禁用optimizer_trace功能</li><li>one_line:决定了跟踪信息的存储方式,为on表示使用单行存储,否则以json树的标准展示形式存储</li></ul><h4 id="optimizer-trace-features"><a href="#optimizer-trace-features" class="headerlink" title="optimizer_trace_features"></a><strong>optimizer_trace_features</strong></h4><p>该变量中存储了跟踪信息中可控的打印项,可以通过调整该变量,控制在INFORMATION_SCHEMA.OPTIMIZER_TRACE表中的trace列需要打印的JSON项和不需要打印的JSON项。默认打开该参数下的所有项。</p><ul><li>greedy_search: 对于有N个表的join操作,可能产生N的阶乘的查询计划路径。如果禁用,则不跟踪贪婪搜索</li><li>range_optimizer: range优化,如果禁用,则不会跟踪范围优化器</li><li>dynamic_range: dynamic range optimizer,如果关闭该选项的话,只有第一次调用JOIN_TAB::SQL_SELECT才被跟踪</li><li>repeated_subselect :子查询,如果关闭的话,只有第一次调用Item_subselect才被跟踪</li></ul><h4 id="optimizer-trace-max-mem-size"><a href="#optimizer-trace-max-mem-size" class="headerlink" title="optimizer_trace_max_mem_size"></a><strong>optimizer_trace_max_mem_size</strong></h4><ul><li>optimizer_trace内存的大小,如果跟踪信息超过这个大小,信息将会被截断</li></ul><h4 id="optimizer-trace-limit"><a href="#optimizer-trace-limit" class="headerlink" title="optimizer_trace_limit"></a><strong>optimizer_trace_limit</strong></h4><ul><li>optimizer_trace_limit,约束跟踪信息存储的个数</li></ul><h4 id="optimizer-trace-offset"><a href="#optimizer-trace-offset" class="headerlink" title="**optimizer_trace_offset **"></a>**optimizer_trace_offset **</h4><ul><li>optimizer_trace_offset,约束偏移量</li></ul><h3 id="三、Optimizer-Trace"><a href="#三、Optimizer-Trace" class="headerlink" title="三、Optimizer Trace"></a>三、<strong>Optimizer Trace</strong></h3><p>在Optimizer Trace的输出中,主要分为三个部分:</p><ul><li>join_preparation SQL的准备阶段</li><li>join_optimization SQL优化阶段</li><li>join_execution SQL执行阶段</li></ul><h4 id="join-preparation"><a href="#join-preparation" class="headerlink" title="join_preparation"></a>join_preparation</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img3.avif"></p><p>第一部分是完成SQL的准备工作。在这个阶段,SQL语句会被格式化输出,通配符*会被具体字段代替,但不会进行等价改写动作。如上图中传入的SQL语句是”select * from dept”的结果。在完成了语句的补充、格式化后,准备阶段结束并进入下一阶段。</p><h4 id="join-optimization"><a href="#join-optimization" class="headerlink" title="join_optimization"></a>join_optimization</h4><p>第二部分,是完成SQL语句的逻辑与物理优化的过程,这其中的优化步骤比较多</p><p>在展开具体内容之前,先解释下”select #”的问题。在输出中经常会看到有”select#:N”的字样,它表示当前跟踪的结构体是属于第几个SELECT。</p><p>如果语句中使用多个SELECT语句拼接 如UNION 或者有嵌套子查询中有SELECT,会产生多个序号。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img4.avif"></p><h5 id="condition-processing"><a href="#condition-processing" class="headerlink" title="condition_processing"></a><strong>condition_processing</strong></h5><p>这一部分是完成对条件语句的优化,包括对WHERE子句或HAVING子句的优化。在后面的”condition”部分就标识出是对哪类子句的优化,如下图就是对WHERE子句的优化。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img5.avif"></p><p>在后面是三个优化过程,每步都写明了转换类型 transformation ,明确转换做的事情,以及转换之后的结果语句 resulting_condition 。这三个转换分别是:</p><ul><li>equality_propagation 等值条件句转换</li><li>constant_propagation 常量条件句转换</li><li>trivial_condition_removal 无效条件移除的转换</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img6.avif"></p><h5 id="substitute-generated-columns"><a href="#substitute-generated-columns" class="headerlink" title="substitute_generated_columns"></a><strong>substitute_generated_columns</strong></h5><p>用于替换虚拟生成列</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img7.avif"></p><h5 id="table-dependencies"><a href="#table-dependencies" class="headerlink" title="table_dependencies"></a><strong>table_dependencies</strong></h5><p>这部分是要找出表之间的相互依赖关系。如查询中存在多个表且之间是有依赖关系,会影响优化行为。这部分信息更多是提示作用,没有实质优化动作。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img8.avif"></p><p>在具体字段含义上:</p><ul><li>table:涉及的表名 如果有别名,也会显示出来</li><li>row_may_be_null:列是否允许为NULL,这里并不是指表中的列属性是否允许为NULL,而是指JOIN操作之后的列是否为NULL。比如说原始语句中如果使用了LEFT JOIN,那么后一张表的row_may_be_null则会显示为true。</li><li>map_bit:表的映射编号,从0开始递增。</li><li>depends_on_map_bits:依赖的映射表,这里主要是在使用STRAIGHT_JOIN进行强制连接顺序或者是LEFT JOIN&#x2F;RIGHT JOIN有顺序差别时,会在depends_on_map_bits中列出前置表的map_bit。</li></ul><h5 id="ref-optimizer-key-uses"><a href="#ref-optimizer-key-uses" class="headerlink" title="ref_optimizer_key_uses"></a><strong>ref_optimizer_key_uses</strong></h5><p>列出了所有可用的ref类型的索引,在图中显示可过滤的字段</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img9.avif"></p><h5 id="rows-estimation"><a href="#rows-estimation" class="headerlink" title="rows_estimation"></a><strong>rows_estimation</strong></h5><p>在这一阶段会评估各种扫描方式的成本,包括全表扫描机索引扫描的代价估算。这一段以表对象作为结构体进行展开</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img10.avif"></p><h6 id="potential-range-indexes"><a href="#potential-range-indexes" class="headerlink" title="potential_range_indexes"></a>potential_range_indexes</h6><p>该阶段会列出表中所有的索引并分析其是否可用,并且还会列出索引中可用的列字段;如果不可用,则列出不可用的原因</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img11.avif"></p><h6 id="setup-range-conditions"><a href="#setup-range-conditions" class="headerlink" title="setup_range_conditions"></a>setup_range_conditions</h6><p>如果有可下推的条件,则带条件考虑范围查询</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img12.avif"></p><h6 id="group-index-range"><a href="#group-index-range" class="headerlink" title="group_index_range"></a>group_index_range</h6><p>评估在使用了GROUP BY或者是DISTINCT的时候是否有适合的索引可用</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img13.avif"></p><h6 id="skip-scan-range"><a href="#skip-scan-range" class="headerlink" title="skip_scan_range"></a>skip_scan_range</h6><p>8.0新增,是否使用了skip scan</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img14.avif"></p><p>在 MySQL 中,<code>skip_scan_range</code> 是优化器跟踪输出中的一个元素,它表示优化器使用了跳过扫描 Skip Scan 访问方法。跳过扫描是一种范围访问方法,它在查询过程中跳过不满足条件的行,从而减少需要扫描的行数,提高查询效率</p><h6 id="analyzing-range-alternatives"><a href="#analyzing-range-alternatives" class="headerlink" title="analyzing_range_alternatives"></a>analyzing_range_alternatives</h6><p>分析各索引使用成本,包括range_scan_alternatives range扫描分析 、analyzing_roworder_intersect index merge分析 两个阶段,分别针对不同的情况进行执行代价的分析,从中选择出更优的执行计划</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img15.avif"></p><p>在有了上述对比之后,在下面chosen_range_access_summary给出这部分的最终结论,使用了 index : customer_id</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img16.avif"></p><h5 id="considered-execution-plans"><a href="#considered-execution-plans" class="headerlink" title="considered_execution_plans"></a>considered_execution_plans</h5><p>对比实际的不同路径的成本。如果是多表关联,且有存在执行顺序(如left&#x2F;right join或straight_join来强制指定顺序),则在plan_prefix部分会有前置条件;否则,就按照所有可能性评估</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img17.avif"></p><h5 id="attaching-conditions-to-tables"><a href="#attaching-conditions-to-tables" class="headerlink" title="attaching_conditions_to_tables"></a>attaching_conditions_to_tables</h5><p>这一步是在上面的基础上,尽量通过绑定条件到对应表上来获取更好的数据筛选。如果能做ICP(索引条件推入)则更佳</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img18.avif"></p><h5 id="finalizing-table-conditions"><a href="#finalizing-table-conditions" class="headerlink" title="finalizing_table_conditions"></a>finalizing_table_conditions</h5><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img19.avif"></p><h5 id="refine-plan"><a href="#refine-plan" class="headerlink" title="refine_plan"></a>refine_plan</h5><p>最后的优化后的结果,如果只是展示对应的表对象没有其他字段,则说明之前已经确定的执行计划已经是最优的结果</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img20.avif"></p><h4 id="join-execution"><a href="#join-execution" class="headerlink" title="join_execution"></a>join_execution</h4><p>在SQL在阶段,大部分都是空白的</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img21.avif"></p><p>只有当语句中包含有排序等操作时,才会在此部分显示</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-05-25/img22.avif"></p><h3 id="附件"><a href="#附件" class="headerlink" title="附件"></a>附件</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> t1 (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">NOT NULL</span> AUTO_INCREMENT,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">20</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">id1 <span class="type">INT</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB AUTO_INCREMENT <span class="number">9</span> <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci;</span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> t1 (name, id1) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="string">&#x27;Alice&#x27;</span>, <span class="number">101</span>),</span><br><span class="line">(<span class="string">&#x27;Bob&#x27;</span>, <span class="number">102</span>),</span><br><span class="line">(<span class="string">&#x27;Charlie&#x27;</span>, <span class="number">103</span>),</span><br><span class="line">(<span class="string">&#x27;David&#x27;</span>, <span class="number">104</span>),</span><br><span class="line">(<span class="string">&#x27;Eve&#x27;</span>, <span class="number">105</span>),</span><br><span class="line">(<span class="string">&#x27;Frank&#x27;</span>, <span class="number">106</span>),</span><br><span class="line">(<span class="string">&#x27;George&#x27;</span>, <span class="number">107</span>),</span><br><span class="line">(<span class="string">&#x27;Hannah&#x27;</span>, <span class="number">108</span>),</span><br><span class="line">(<span class="string">&#x27;Ivan&#x27;</span>, <span class="number">109</span>),</span><br><span class="line">(<span class="string">&#x27;Jack&#x27;</span>, <span class="number">110</span>),</span><br><span class="line">(<span class="string">&#x27;Kevin&#x27;</span>, <span class="number">111</span>);</span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> orders (order_date, amount, customer_id) <span class="keyword">VALUES</span></span><br><span class="line">(<span class="string">&#x27;2023-01-01&#x27;</span>, <span class="number">100.00</span>, <span class="number">1</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-02&#x27;</span>, <span class="number">200.50</span>, <span class="number">2</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-03&#x27;</span>, <span class="number">300.75</span>, <span class="number">3</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-04&#x27;</span>, <span class="number">400.00</span>, <span class="number">4</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-05&#x27;</span>, <span class="number">500.00</span>, <span class="number">5</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-06&#x27;</span>, <span class="number">600.25</span>, <span class="number">6</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-07&#x27;</span>, <span class="number">700.50</span>, <span class="number">7</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-08&#x27;</span>, <span class="number">800.00</span>, <span class="number">8</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-09&#x27;</span>, <span class="number">900.75</span>, <span class="number">9</span>),</span><br><span class="line">(<span class="string">&#x27;2023-01-10&#x27;</span>, <span class="number">1000.00</span>, <span class="number">10</span>);</span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">t1.id <span class="keyword">AS</span> customer_id,</span><br><span class="line">t1.name <span class="keyword">AS</span> customer_name,</span><br><span class="line">GROUP_CONCAT(o.amount <span class="keyword">ORDER</span> <span class="keyword">BY</span> o.amount SEPARATOR <span class="string">&#x27;,&#x27;</span>) <span class="keyword">AS</span> grouped_amount, <span class="comment">-- 使用 GROUP_CONCAT() 函数并确保它在 SELECT 列表中</span></span><br><span class="line"><span class="built_in">COUNT</span>(o.order_id) <span class="keyword">AS</span> order_count</span><br><span class="line"><span class="keyword">FROM</span></span><br><span class="line">(<span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> t1 <span class="keyword">WHERE</span> id <span class="number">1</span>) <span class="keyword">AS</span> t1</span><br><span class="line"><span class="keyword">JOIN</span></span><br><span class="line">orders <span class="keyword">AS</span> o <span class="keyword">ON</span> t1.id o.customer_id</span><br><span class="line"><span class="keyword">GROUP</span> <span class="keyword">BY</span></span><br><span class="line">amount; </span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">t1.id <span class="keyword">AS</span> customer_id,</span><br><span class="line">t1.name <span class="keyword">AS</span> customer_name,</span><br><span class="line">GROUP_CONCAT(<span class="keyword">DISTINCT</span> o.amount <span class="keyword">ORDER</span> <span class="keyword">BY</span> o.amount SEPARATOR <span class="string">&#x27;,&#x27;</span>) <span class="keyword">AS</span> grouped_amount, <span class="comment">-- 使用 GROUP_CONCAT() 函数并确保它在 SELECT 列表中,添加 DISTINCT 以去重</span></span><br><span class="line"><span class="built_in">COUNT</span>(o.order_id) <span class="keyword">AS</span> order_count</span><br><span class="line"><span class="keyword">FROM</span></span><br><span class="line">(<span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> t1 <span class="keyword">WHERE</span> id <span class="number">1</span>) <span class="keyword">AS</span> t1</span><br><span class="line"><span class="keyword">JOIN</span></span><br><span class="line">orders <span class="keyword">AS</span> o <span class="keyword">ON</span> t1.id o.customer_id</span><br><span class="line"><span class="keyword">GROUP</span> <span class="keyword">BY</span></span><br><span class="line">amount;</span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br><span class="line">143</span><br><span class="line">144</span><br><span class="line">145</span><br><span class="line">146</span><br><span class="line">147</span><br><span class="line">148</span><br><span class="line">149</span><br><span class="line">150</span><br><span class="line">151</span><br><span class="line">152</span><br><span class="line">153</span><br><span class="line">154</span><br><span class="line">155</span><br><span class="line">156</span><br><span class="line">157</span><br><span class="line">158</span><br><span class="line">159</span><br><span class="line">160</span><br><span class="line">161</span><br><span class="line">162</span><br><span class="line">163</span><br><span class="line">164</span><br><span class="line">165</span><br><span class="line">166</span><br><span class="line">167</span><br><span class="line">168</span><br><span class="line">169</span><br><span class="line">170</span><br><span class="line">171</span><br><span class="line">172</span><br><span class="line">173</span><br><span class="line">174</span><br><span class="line">175</span><br><span class="line">176</span><br><span class="line">177</span><br><span class="line">178</span><br><span class="line">179</span><br><span class="line">180</span><br><span class="line">181</span><br><span class="line">182</span><br><span class="line">183</span><br><span class="line">184</span><br><span class="line">185</span><br><span class="line">186</span><br><span class="line">187</span><br><span class="line">188</span><br><span class="line">189</span><br><span class="line">190</span><br><span class="line">191</span><br><span class="line">192</span><br><span class="line">193</span><br><span class="line">194</span><br><span class="line">195</span><br><span class="line">196</span><br><span class="line">197</span><br><span class="line">198</span><br><span class="line">199</span><br><span class="line">200</span><br><span class="line">201</span><br><span class="line">202</span><br><span class="line">203</span><br><span class="line">204</span><br><span class="line">205</span><br><span class="line">206</span><br><span class="line">207</span><br><span class="line">208</span><br><span class="line">209</span><br><span class="line">210</span><br><span class="line">211</span><br><span class="line">212</span><br><span class="line">213</span><br><span class="line">214</span><br><span class="line">215</span><br><span class="line">216</span><br><span class="line">217</span><br><span class="line">218</span><br><span class="line">219</span><br><span class="line">220</span><br><span class="line">221</span><br><span class="line">222</span><br><span class="line">223</span><br><span class="line">224</span><br><span class="line">225</span><br><span class="line">226</span><br><span class="line">227</span><br><span class="line">228</span><br><span class="line">229</span><br><span class="line">230</span><br><span class="line">231</span><br><span class="line">232</span><br><span class="line">233</span><br><span class="line">234</span><br><span class="line">235</span><br><span class="line">236</span><br><span class="line">237</span><br><span class="line">238</span><br><span class="line">239</span><br><span class="line">240</span><br><span class="line">241</span><br><span class="line">242</span><br><span class="line">243</span><br><span class="line">244</span><br><span class="line">245</span><br><span class="line">246</span><br><span class="line">247</span><br><span class="line">248</span><br><span class="line">249</span><br><span class="line">250</span><br><span class="line">251</span><br><span class="line">252</span><br><span class="line">253</span><br><span class="line">254</span><br><span class="line">255</span><br><span class="line">256</span><br><span class="line">257</span><br><span class="line">258</span><br><span class="line">259</span><br><span class="line">260</span><br><span class="line">261</span><br><span class="line">262</span><br><span class="line">263</span><br><span class="line">264</span><br><span class="line">265</span><br><span class="line">266</span><br><span class="line">267</span><br><span class="line">268</span><br><span class="line">269</span><br><span class="line">270</span><br><span class="line">271</span><br><span class="line">272</span><br><span class="line">273</span><br><span class="line">274</span><br><span class="line">275</span><br><span class="line">276</span><br><span class="line">277</span><br><span class="line">278</span><br><span class="line">279</span><br><span class="line">280</span><br><span class="line">281</span><br><span class="line">282</span><br><span class="line">283</span><br><span class="line">284</span><br><span class="line">285</span><br><span class="line">286</span><br><span class="line">287</span><br><span class="line">288</span><br><span class="line">289</span><br><span class="line">290</span><br><span class="line">291</span><br><span class="line">292</span><br><span class="line">293</span><br><span class="line">294</span><br><span class="line">295</span><br><span class="line">296</span><br><span class="line">297</span><br><span class="line">298</span><br><span class="line">299</span><br><span class="line">300</span><br><span class="line">301</span><br><span class="line">302</span><br><span class="line">303</span><br><span class="line">304</span><br><span class="line">305</span><br><span class="line">306</span><br><span class="line">307</span><br><span class="line">308</span><br><span class="line">309</span><br><span class="line">310</span><br><span class="line">311</span><br><span class="line">312</span><br><span class="line">313</span><br><span class="line">314</span><br><span class="line">315</span><br><span class="line">316</span><br><span class="line">317</span><br><span class="line">318</span><br><span class="line">319</span><br><span class="line">320</span><br><span class="line">321</span><br><span class="line">322</span><br><span class="line">323</span><br><span class="line">324</span><br><span class="line">325</span><br><span class="line">326</span><br><span class="line">327</span><br><span class="line">328</span><br><span class="line">329</span><br><span class="line">330</span><br><span class="line">331</span><br><span class="line">332</span><br><span class="line">333</span><br><span class="line">334</span><br><span class="line">335</span><br><span class="line">336</span><br><span class="line">337</span><br><span class="line">338</span><br><span class="line">339</span><br><span class="line">340</span><br><span class="line">341</span><br><span class="line">342</span><br></pre></td><td class="code"><pre><span class="line">QUERY <span class="operator">|</span> <span class="keyword">SELECT</span></span><br><span class="line">t1.id <span class="keyword">AS</span> customer_id,</span><br><span class="line">t1.name <span class="keyword">AS</span> customer_name,</span><br><span class="line">GROUP_CONCAT(<span class="keyword">DISTINCT</span> o.amount <span class="keyword">ORDER</span> <span class="keyword">BY</span> o.amount SEPARATOR <span class="string">&#x27;,&#x27;</span>) <span class="keyword">AS</span> grouped_amount, <span class="comment">-- 使用 GROUP_CONCAT() 函数并确保它在 SELECT 列表中,添加 DISTINCT 以去重</span></span><br><span class="line"><span class="built_in">COUNT</span>(o.order_id) <span class="keyword">AS</span> order_count</span><br><span class="line"><span class="keyword">FROM</span></span><br><span class="line">(<span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> t1 <span class="keyword">WHERE</span> id <span class="number">1</span>) <span class="keyword">AS</span> t1 <span class="comment">-- 子查询,先从 t1 表中选出 id 为 1 的记录</span></span><br><span class="line"><span class="keyword">JOIN</span></span><br><span class="line">orders <span class="keyword">AS</span> o <span class="keyword">ON</span> t1.id o.customer_id <span class="comment">-- 将子查询的结果与 orders 表进行连接</span></span><br><span class="line"><span class="keyword">GROUP</span> <span class="keyword">BY</span></span><br><span class="line">amount</span><br><span class="line">TRACE <span class="operator">|</span> &#123;</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">join_preparation : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">join_preparation : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">2</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">expanded_query : <span class="comment">/* select#2 */</span> <span class="keyword">select</span> t1 . id <span class="keyword">AS</span> id , t1 . name <span class="keyword">AS</span> name , t1 . id1 <span class="keyword">AS</span> id1 <span class="keyword">from</span> t1 <span class="keyword">where</span> ( t1 . id <span class="number">1</span>)</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">derived : &#123;</span><br><span class="line"><span class="keyword">table</span> : t1 ,</span><br><span class="line"><span class="keyword">select</span># : <span class="number">2</span>,</span><br><span class="line">merged : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">expanded_query : <span class="comment">/* select#1 */</span> <span class="keyword">select</span> t1 . id <span class="keyword">AS</span> customer_id , t1 . name <span class="keyword">AS</span> customer_name ,group_concat(<span class="keyword">distinct</span> o . amount <span class="keyword">order</span> <span class="keyword">by</span> o . amount <span class="keyword">ASC</span> separator <span class="string">&#x27;,&#x27;</span>) <span class="keyword">AS</span> grouped_amount ,<span class="built_in">count</span>( o . order_id ) <span class="keyword">AS</span> order_count <span class="keyword">from</span> (<span class="operator">&lt;</span>constant <span class="keyword">table</span><span class="operator">&gt;</span> <span class="keyword">join</span> ( t1 ) <span class="keyword">on</span>(( t1 . id <span class="number">1</span>)) <span class="keyword">join</span> orders o <span class="keyword">on</span>(( t1 . id o . customer_id ))) <span class="keyword">group</span> <span class="keyword">by</span> o . amount</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">transformations_to_nested_joins : &#123;</span><br><span class="line">transformations : [</span><br><span class="line">JOIN_condition_to_WHERE ,</span><br><span class="line">parenthesis_removal</span><br><span class="line">],</span><br><span class="line">expanded_query : <span class="comment">/* select#1 */</span> <span class="keyword">select</span> t1 . id <span class="keyword">AS</span> customer_id , t1 . name <span class="keyword">AS</span> customer_name ,group_concat(<span class="keyword">distinct</span> o . amount <span class="keyword">order</span> <span class="keyword">by</span> o . amount <span class="keyword">ASC</span> separator <span class="string">&#x27;,&#x27;</span>) <span class="keyword">AS</span> grouped_amount ,<span class="built_in">count</span>( o . order_id ) <span class="keyword">AS</span> order_count <span class="keyword">from</span> t1 <span class="keyword">join</span> orders o <span class="keyword">where</span> (( t1 . id o . customer_id ) <span class="keyword">and</span> ( t1 . id <span class="number">1</span>)) <span class="keyword">group</span> <span class="keyword">by</span> o . amount</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">functional_dependencies_of_GROUP_columns : &#123;</span><br><span class="line">all_columns_of_table_map_bits : [</span><br><span class="line"><span class="number">0</span></span><br><span class="line">],</span><br><span class="line">columns : [</span><br><span class="line">demo3.o.amount ,</span><br><span class="line">demo3.t1.id</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">join_optimization : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">condition_processing : &#123;</span><br><span class="line"><span class="keyword">condition</span> : <span class="keyword">WHERE</span> ,</span><br><span class="line">original_condition : (( t1 . id o . customer_id ) <span class="keyword">and</span> ( t1 . id <span class="number">1</span>)) ,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">transformation : equality_propagation ,</span><br><span class="line">resulting_condition : (multiple equal(<span class="number">1</span>, t1 . id , o . customer_id ))</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">transformation : constant_propagation ,</span><br><span class="line">resulting_condition : (multiple equal(<span class="number">1</span>, t1 . id , o . customer_id ))</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">transformation : trivial_condition_removal ,</span><br><span class="line">resulting_condition : multiple equal(<span class="number">1</span>, t1 . id , o . customer_id )</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">substitute_generated_columns : &#123;</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">table_dependencies : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : t1 ,</span><br><span class="line">row_may_be_null : <span class="literal">false</span>,</span><br><span class="line">map_bit : <span class="number">0</span>,</span><br><span class="line">depends_on_map_bits : [</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">row_may_be_null : <span class="literal">false</span>,</span><br><span class="line">map_bit : <span class="number">1</span>,</span><br><span class="line">depends_on_map_bits : [</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">ref_optimizer_key_uses : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : t1 ,</span><br><span class="line">field : id ,</span><br><span class="line"><span class="keyword">equals</span> : <span class="number">1</span> ,</span><br><span class="line">null_rejecting : <span class="literal">true</span></span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">field : customer_id ,</span><br><span class="line"><span class="keyword">equals</span> : <span class="number">1</span> ,</span><br><span class="line">null_rejecting : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">rows_estimation : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : t1 ,</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">1</span>,</span><br><span class="line">cost : <span class="number">1</span>,</span><br><span class="line">table_type : const ,</span><br><span class="line"><span class="keyword">empty</span> : <span class="literal">false</span></span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">range_analysis : &#123;</span><br><span class="line">table_scan : &#123;</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">2</span>,</span><br><span class="line">cost : <span class="number">2.55</span></span><br><span class="line">&#125;,</span><br><span class="line">potential_range_indexes : [</span><br><span class="line">&#123;</span><br><span class="line">index : <span class="keyword">PRIMARY</span> ,</span><br><span class="line">usable : <span class="literal">false</span>,</span><br><span class="line">cause : not_applicable</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">index : customer_id ,</span><br><span class="line">usable : <span class="literal">true</span>,</span><br><span class="line">key_parts : [</span><br><span class="line">customer_id ,</span><br><span class="line">order_id</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">],</span><br><span class="line">setup_range_conditions : [</span><br><span class="line">],</span><br><span class="line">group_index_range : &#123;</span><br><span class="line">chosen : <span class="literal">false</span>,</span><br><span class="line">cause : not_single_table</span><br><span class="line">&#125;,</span><br><span class="line">skip_scan_range : &#123;</span><br><span class="line">chosen : <span class="literal">false</span>,</span><br><span class="line">cause : not_single_table</span><br><span class="line">&#125;,</span><br><span class="line">analyzing_range_alternatives : &#123;</span><br><span class="line">range_scan_alternatives : [</span><br><span class="line">&#123;</span><br><span class="line">index : customer_id ,</span><br><span class="line">ranges : [</span><br><span class="line">customer_id <span class="number">1</span></span><br><span class="line">],</span><br><span class="line">index_dives_for_eq_ranges : <span class="literal">true</span>,</span><br><span class="line">rowid_ordered : <span class="literal">true</span>,</span><br><span class="line">using_mrr : <span class="literal">false</span>,</span><br><span class="line">index_only : <span class="literal">false</span>,</span><br><span class="line">in_memory : <span class="number">1</span>,</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">1</span>,</span><br><span class="line">cost : <span class="number">0.61</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">],</span><br><span class="line">analyzing_roworder_intersect : &#123;</span><br><span class="line">usable : <span class="literal">false</span>,</span><br><span class="line">cause : too_few_roworder_scans</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">chosen_range_access_summary : &#123;</span><br><span class="line">range_access_plan : &#123;</span><br><span class="line">type : range_scan ,</span><br><span class="line">index : customer_id ,</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">1</span>,</span><br><span class="line">ranges : [</span><br><span class="line">customer_id <span class="number">1</span></span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">rows_for_plan : <span class="number">1</span>,</span><br><span class="line">cost_for_plan : <span class="number">0.61</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">considered_execution_plans : [</span><br><span class="line">&#123;</span><br><span class="line">plan_prefix : [</span><br><span class="line">t1</span><br><span class="line">],</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">best_access_path : &#123;</span><br><span class="line">considered_access_paths : [</span><br><span class="line">&#123;</span><br><span class="line">access_type : <span class="keyword">ref</span> ,</span><br><span class="line">index : customer_id ,</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">1</span>,</span><br><span class="line">cost : <span class="number">0.35</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">access_type : <span class="keyword">range</span> ,</span><br><span class="line">range_details : &#123;</span><br><span class="line">used_index : customer_id</span><br><span class="line">&#125;,</span><br><span class="line">chosen : <span class="literal">false</span>,</span><br><span class="line">cause : heuristic_index_cheaper</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">condition_filtering_pct : <span class="number">100</span>,</span><br><span class="line">rows_for_plan : <span class="number">1</span>,</span><br><span class="line">cost_for_plan : <span class="number">0.35</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">attaching_conditions_to_tables : &#123;</span><br><span class="line">original_condition : ( o . customer_id <span class="number">1</span>) ,</span><br><span class="line">attached_conditions_computation : [</span><br><span class="line">],</span><br><span class="line">attached_conditions_summary : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">attached : ( o . customer_id <span class="number">1</span>)</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">optimizing_distinct_group_by_order_by : &#123;</span><br><span class="line">simplifying_group_by : &#123;</span><br><span class="line">original_clause : o . amount ,</span><br><span class="line">items : [</span><br><span class="line">&#123;</span><br><span class="line">item : o . amount</span><br><span class="line">&#125;</span><br><span class="line">],</span><br><span class="line">resulting_clause_is_simple : <span class="literal">true</span>,</span><br><span class="line">resulting_clause : o . amount</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">finalizing_table_conditions : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o ,</span><br><span class="line">original_table_condition : ( o . customer_id <span class="number">1</span>) ,</span><br><span class="line">final_table_condition : <span class="keyword">null</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">refine_plan : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : orders o</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">considering_tmp_tables : [</span><br><span class="line">&#123;</span><br><span class="line">creating_tmp_table : &#123;</span><br><span class="line">tmp_table_info : &#123;</span><br><span class="line"><span class="keyword">table</span> : intermediate_tmp_table ,</span><br><span class="line">columns : <span class="number">1</span>,</span><br><span class="line">row_length : <span class="number">6</span>,</span><br><span class="line">key_length : <span class="number">0</span>,</span><br><span class="line">unique_constraint : <span class="literal">false</span>,</span><br><span class="line">makes_grouped_rows : <span class="literal">false</span>,</span><br><span class="line">cannot_insert_duplicates : <span class="literal">false</span>,</span><br><span class="line">location : TempTable</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">adding_sort_to_table : o</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">join_execution : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">sorting_table : o ,</span><br><span class="line">filesort_information : [</span><br><span class="line">&#123;</span><br><span class="line">direction : <span class="keyword">asc</span> ,</span><br><span class="line">expression : o . amount</span><br><span class="line">&#125;</span><br><span class="line">],</span><br><span class="line">filesort_priority_queue_optimization : &#123;</span><br><span class="line">usable : <span class="literal">false</span>,</span><br><span class="line">cause : <span class="keyword">not</span> applicable (<span class="keyword">no</span> LIMIT)</span><br><span class="line">&#125;,</span><br><span class="line">filesort_execution : [</span><br><span class="line">],</span><br><span class="line">filesort_summary : &#123;</span><br><span class="line">memory_available : <span class="number">262144</span>,</span><br><span class="line">key_size : <span class="number">5</span>,</span><br><span class="line">row_size : <span class="number">18</span>,</span><br><span class="line">max_rows_per_buffer : <span class="number">15</span>,</span><br><span class="line">num_rows_estimate : <span class="number">15</span>,</span><br><span class="line">num_rows_found : <span class="number">1</span>,</span><br><span class="line">num_initial_chunks_spilled_to_disk : <span class="number">0</span>,</span><br><span class="line">peak_memory_used : <span class="number">32776</span>,</span><br><span class="line">sort_algorithm : <span class="keyword">none</span> ,</span><br><span class="line">unpacked_addon_fields : skip_heuristic ,</span><br><span class="line">sort_mode : <span class="operator">&lt;</span>fixed_sort_key, additional_fields<span class="operator">&gt;</span></span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">MISSING_BYTES_BEYOND_MAX_MEM_SIZE <span class="operator">|</span> <span class="number">0</span></span><br><span class="line">INSUFFICIENT_PRIVILEGES <span class="operator">|</span> <span class="number">0</span></span><br><span class="line"></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/05/25/7e7ca4d5/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>选主算法、多版本兼容性及滚动升级｜深入浅出MGR</title>
      <link>https://blog.eucalyptus.cc/2025/04/28/ce40cc95/</link>
      <guid>https://blog.eucalyptus.cc/2025/04/28/ce40cc95/</guid>
      <pubDate>Mon, 28 Apr 2025 06:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;本文介绍MGR的选主算法,以及当MGR集群中有多个不同版本混搭时,如何才能正常运行,有什么注意事项。&lt;/p&gt;
&lt;h4 id=&quot;1-选主算法&quot;&gt;&lt;a href=&quot;#1-选主算法&quot; class=&quot;headerlink&quot; title=&quot;1. 选主算法&quot;&gt;&lt;/a&gt;1.</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>本文介绍MGR的选主算法,以及当MGR集群中有多个不同版本混搭时,如何才能正常运行,有什么注意事项。</p><h4 id="1-选主算法"><a href="#1-选主算法" class="headerlink" title="1. 选主算法"></a>1. 选主算法</h4><p>MGR运行在单主模式时,当发生主节点切换,就需要进行选主工作。多主模式下,所有节点都是主节点,就不需要选主了。</p><p>MGR的选主工作是自动的,每个节点都会参与。选主时会检查当前最新的组视图,对潜在的新主节点 各个备选节点 进行排序,最后选出最合适的那个作为新的主节点。</p><p>不同的MySQL版本选主算法略有不同,各节点选主时会根据当前的MySQL版本选主算法而决定,因此当MGR集群中有多个版本并存时,则此时MGR会做出调整,以便各个不同版本的节点都能就选主达成算法一致。</p><p>通常而言,选主算法的各个因素优先级顺序如下:</p><ul><li><p>根据MySQL版本号排序,低版本的优先级更高 因为要向下兼容 。如果是MySQL 8.0.17及以上版本,则优先根据补丁版本号排序 例如17、18、20 。如果是8.0.16及以下版本,则优先根据主版本号排序 例如5.7、8.0 。</p></li><li><p>版本号相同的各节点则根据各节点的权重值排序,权重越高优先级也越高。节点的权重值可通过设置 <code>group_replication_member_weight</code> 选项来调整。这个选项是MySQL 8.0版本引入的,如果是5.7版本则不支持。</p></li><li><p>当版本号和节点权重值都一样时,再根据 <code>server_uuid</code> 或者说是 <code>MEMBER_ID</code> 排序 注意,不是 <code>server_id</code> ,排在前面的优先级越高。MySQL Server在启动时,会生成一个随机的UUID值,其值记录在文件 <em>datadir&#x2F;auto.cnf</em> 文件中,实际上可以在实例启动前,通过修改这个UUID值来改变 <code>server_uuid</code> 的值,只要符合UUID数据格式即可。因此,相当于是可以认为调整 <code>server_uuid</code> 以调整选主时节点的排序优先级。</p></li></ul><p>从上面可知,当有MySQL 8.0和5.7的节点混搭运行MGR集群时,运行5.7版本的节点会优先被选中,其次再根据 <code>group_replication_member_weight</code> 选择权重搞的节点,最后再根据 <code>server_uuid</code> 排序。</p><p>因此,运行MGR集群时最好各节点版本号相同,选主规则就简单多了。</p><p>在MySQL 8.0中,通过查询 <code>performance_schema.replication_group_members</code> 表的<code>MEMBER_ROLE</code> 即可知道哪个是主节点:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> performance_schema.replication_group_members;</span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- -------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> CHANNEL_NAME <span class="operator">|</span> MEMBER_ID <span class="operator">|</span> MEMBER_HOST <span class="operator">|</span> MEMBER_PORT <span class="operator">|</span> MEMBER_STATE <span class="operator">|</span> MEMBER_ROLE <span class="operator">|</span> MEMBER_VERSION <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- -------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> <span class="number">4</span>ebd3504<span class="number">-11</span>d9<span class="number">-11</span>ec<span class="number">-8</span>f92<span class="number">-70</span>b5e873a570 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.10</span> <span class="operator">|</span> <span class="number">3306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> <span class="keyword">PRIMARY</span> <span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span> <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">---主节点</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> <span class="number">549</span>b92bf<span class="number">-11</span>d9<span class="number">-11</span>ec<span class="number">-88e1</span><span class="number">-70</span>b5e873a570 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.11</span> <span class="operator">|</span> <span class="number">3307</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> <span class="number">5596116</span>c<span class="number">-11</span>d9<span class="number">-11</span>ec<span class="number">-8624</span><span class="number">-70</span>b5e873a570 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.12</span> <span class="operator">|</span> <span class="number">3308</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- -------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p>如果是在MySQL 5.7中,则需要通过查询 <code>group_replication_primary_member</code> 这个 status 才能知道,比8.0麻烦。所以说,还是尽量使用MySQL 8.0来构建MGR集群。</p><p>在一个MySQL 5.7和8.0混搭的MGR集群中,从运行MySQL 8.0版本的节点上看到的状态是这样的:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> performance_schema.replication_group_members;</span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- --------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> CHANNEL_NAME <span class="operator">|</span> MEMBER_ID <span class="operator">|</span> MEMBER_HOST <span class="operator">|</span> MEMBER_PORT <span class="operator">|</span> MEMBER_STATE <span class="operator">|</span> MEMBER_ROLE <span class="operator">|</span> MEMBER_VERSION <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- --------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> af39db70<span class="number">-6850</span><span class="number">-11</span>ec<span class="number">-94</span>c9<span class="number">-00155</span>d064000 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.13</span> <span class="operator">|</span> <span class="number">3306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> d9833e7e<span class="number">-6</span>ecc<span class="number">-11</span>ec<span class="operator">-</span>a3f6<span class="operator">-</span>d08e7908bcb1 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.10</span> <span class="operator">|</span> <span class="number">3306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> <span class="keyword">PRIMARY</span> <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> fe55e195<span class="number">-6</span>ecc<span class="number">-11</span>ec<span class="operator">-</span>a2e9<span class="operator">-</span>d08e7908bcb1 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.11</span> <span class="operator">|</span> <span class="number">3306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> ff19317f<span class="number">-6</span>ecc<span class="number">-11</span>ec<span class="operator">-</span>b17d<span class="operator">-</span>d08e7908bcb1 <span class="operator">|</span> <span class="number">172.16</span><span class="number">.16</span><span class="number">.12</span> <span class="operator">|</span> <span class="number">3306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- --------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p>可以看到,即便是运行MySQL 8.0版本的节点的 <code>server_uuid</code> 排序在前面,但在自动选主时,也不会被选中作为主节点。此外,运行MySQL 5.7版本的节点是无法加入主节点运行MySQL 8.0的MGR集群的,会报告类似下面的错误:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">[ERROR] Plugin group_replication reported: &#x27;Member version is incompatible with the group&#x27;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>提示版本不兼容。</p><h4 id="2-多版本兼容性"><a href="#2-多版本兼容性" class="headerlink" title="2. 多版本兼容性"></a>2. 多版本兼容性</h4><p>正常地,为了MGR的兼容性及性能,所有节点的MySQL版本最好保持一致。尤其是在多主模式下,各节点都提供写入服务,如果兼容性方面存在问题,则可能会导致MGR集群异常或写入异常。为了避免这种情况发生,新加入节点时,会和其他节点进行版本兼容性检查。</p><p>目前MGR支持3个通信协议版本号:5.7.14、8.0.16、8.0.27,这几个版本的主要变化有:</p><ul><li><p>从5.7.14开始,支持消息压缩。</p></li><li><p>从8.0.16开始,支持消息分片。</p></li><li><p>从8.0.27开始,支持在单主模式下,设置唯一的leader节点。</p></li></ul><p>MGR集群中,各节点间的通信协议版本号必须一致,这样才能保证即使是MySQL版本号不一致,但MGR通信依然不受影响。新加入节点的通信协议版本号必须高于当前集群中使用的通信协议版本。节点加入时会检查协议版本,并向其广播当前集群中使用的协议版本,如果可以兼容,则允许加入,否则会将其踢出。</p><p>当两个节点同时加入时,只有当两个节点的通信协议版本和集群兼容时,才能同时加入成功。和当前集群不同协议版本的节点需要单独加入才行,例如:</p><ul><li><p>一个使用8.0.16版本的实例可以成功加入使用通信协议版本5.7.24的集群。</p></li><li><p>一个5.7.24实例无法加入使用8.0.16的集群。</p></li><li><p>两个8.0.16实例无法同时加入使用5.7.24的集群。</p></li><li><p>两个8.0.16实例可以同时加入使用8.0.16的集群。</p></li></ul><p>如果有需要,还可以在线修改通信协议版本号,使用 <code>group_replication_set_communication_protocol()</code> 这个UDF即可 MySQL 8.0以上支持 ,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> version();</span><br><span class="line"><span class="comment">-----------</span></span><br><span class="line"><span class="operator">|</span> version() <span class="operator">|</span></span><br><span class="line"><span class="comment">-----------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span><span class="number">-15</span> <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">-- 当前MySQL版本是8.0.25</span></span><br><span class="line"><span class="comment">-----------</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> group_replication_get_communication_protocol();</span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_get_communication_protocol() <span class="operator">|</span></span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">8.0</span><span class="number">.16</span> <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">-- 当前MGR通信协议版本是8.0.16</span></span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> group_replication_set_communication_protocol(<span class="string">&#x27;5.7.14&#x27;</span>);</span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_set_communication_protocol(<span class="string">&#x27;5.7.14&#x27;</span>) <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">-- 手动修改通信协议版本为5.7.14,可以成功</span></span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> The operation group_replication_set_communication_protocol completed successfully <span class="operator">|</span></span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> group_replication_set_communication_protocol(<span class="string">&#x27;8.0.25&#x27;</span>);</span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_set_communication_protocol(<span class="string">&#x27;8.0.25&#x27;</span>) <span class="operator">|</span></span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> The operation group_replication_set_communication_protocol completed successfully <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">-- 修改协议版本为8.0.25,接下来看看会发生什么</span></span><br><span class="line"><span class="comment">-----------------------------------------------------------------------------------</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> group_replication_get_communication_protocol();</span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_get_communication_protocol() <span class="operator">|</span></span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">8.0</span><span class="number">.16</span> <span class="operator">|</span> <span class="operator">&lt;</span><span class="comment">-- 重置为8.0.16</span></span><br><span class="line"><span class="comment">------------------------------------------------</span></span><br><span class="line"></span><br><span class="line"># 尝试修改为<span class="number">8.0</span><span class="number">.27</span>,会报错</span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> group_replication_set_communication_protocol(<span class="string">&#x27;8.0.27&#x27;</span>);</span><br><span class="line">ERROR <span class="number">1123</span> (HY000): Can<span class="string">&#x27;t initialize function &#x27;</span>group_replication_set_communication_protocol<span class="string">&#x27;; 8.0.27 is not between 5.7.14 and 8.0.25</span></span><br><span class="line"><span class="string"></span></span><br></pre></td></tr></table></figure><p>其实说这么多版本兼容性的话题,还不如一个简单的原则:<strong>让所有节点的版本号都一致</strong>。这样构建MGR集群更简单,节点间通信也不会被复杂化。</p><h4 id="3-MGR-5-7滚动升级至8-0"><a href="#3-MGR-5-7滚动升级至8-0" class="headerlink" title="3. MGR 5.7滚动升级至8.0"></a>3. MGR 5.7滚动升级至8.0</h4><p>MGR 5.7集群滚动升级至8.0可以参考这篇文章:<strong>MySQL MGR从5.7滚动升级至8.0</strong>,简言之,可以分为以下几步:</p><ul><li><p>在现有MGR 5.7集群中,新增MySQL 8.0的Secondary节点。</p></li><li><p>一比一下线一个MySQL 5.7的Secondary节点。</p></li><li><p>如此往复,直到剩下最后一个MySQL 5.7的Primary节点。</p></li><li><p>再次上线一个MySQL 8.0的Secondary节点。</p></li><li><p>停止最后一个MySQL 5.7的Primary节点,这是会切换主节点,并且选择其中一个MySQL 8.0节点作为新的Primary节点,这就完成升级了。</p></li></ul><p>在这里实操演示大概的过程。</p><p>在MGR 5.7的集群中,增加一个MySQL 8.0的Secondary节点:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br></pre></td><td class="code"><pre><span class="line">#在<span class="number">5.7</span>节点上看节点状态</span><br><span class="line">#原生的MySQL <span class="number">5.7</span> MGR看不到 MEMBER_ROLE 这列</span><br><span class="line">#这是GreatSQL <span class="number">5.7</span>新增的特性</span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> performance_schema.replication_group_members;</span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- ------------- ------------- -------------- -------------</span></span><br><span class="line"><span class="operator">|</span> CHANNEL_NAME <span class="operator">|</span> MEMBER_ID <span class="operator">|</span> MEMBER_HOST <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> MEMBER_PORT <span class="operator">|</span> MEMBER_STATE <span class="operator">|</span> MEMBER_ROLE <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-111111111111</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">4306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> <span class="keyword">PRIMARY</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-222222222222</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">4307</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-333333333333</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">4308</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-888888888333</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">3309</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- ------------- ------------- -------------- -------------</span></span><br><span class="line"></span><br><span class="line">#在<span class="number">8.0</span>节点上看</span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> CHANNEL_NAME <span class="operator">|</span> MEMBER_ID <span class="operator">|</span> MEMBER_HOST <span class="operator">|</span> MEMBER_PORT <span class="operator">|</span> MEMBER_STATE <span class="operator">|</span> MEMBER_ROLE <span class="operator">|</span> MEMBER_VERSION <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-111111111111</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span> <span class="number">4306</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> <span class="keyword">PRIMARY</span> <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-222222222222</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span> <span class="number">4307</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-333333333333</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span> <span class="number">4308</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">5.7</span><span class="number">.36</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> group_replication_applier <span class="operator">|</span> c8ec34c4<span class="number">-78</span>fc<span class="number">-11</span>ec<span class="number">-864</span>a<span class="number">-888888888333</span> <span class="operator">|</span> <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span> <span class="operator">|</span> <span class="number">3309</span> <span class="operator">|</span> ONLINE <span class="operator">|</span> SECONDARY <span class="operator">|</span> <span class="number">8.0</span><span class="number">.25</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p>现在,利用MySQL Shell删除一个旧节点:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line">c.removeInstance(<span class="string">&#x27;127.0.0.1:4308&#x27;</span>);</span><br><span class="line">The instance will be removed <span class="keyword">from</span> the InnoDB cluster. Depending <span class="keyword">on</span> the instance</span><br><span class="line">being the Seed <span class="keyword">or</span> <span class="keyword">not</span>, the Metadata session might become invalid. If so, please</span><br><span class="line"><span class="keyword">start</span> a <span class="keyword">new</span> session <span class="keyword">to</span> the Metadata Storage R<span class="operator">/</span>W instance.</span><br><span class="line"></span><br><span class="line">Instance <span class="string">&#x27;127.0.0.1:4308&#x27;</span> <span class="keyword">is</span> attempting <span class="keyword">to</span> leave the cluster...</span><br><span class="line">WARNING: <span class="keyword">On</span> instance <span class="string">&#x27;127.0.0.1:4308&#x27;</span> configuration cannot be persisted since MySQL version <span class="number">5.7</span><span class="number">.36</span> does <span class="keyword">not</span> support the <span class="keyword">SET</span> PERSIST command (MySQL version <span class="operator">&gt;</span> <span class="number">8.0</span><span class="number">.11</span> required). Please <span class="keyword">set</span> the <span class="string">&#x27;group_replication_start_on_boot&#x27;</span> variable <span class="keyword">to</span> <span class="string">&#x27;OFF&#x27;</span> <span class="keyword">in</span> the server configuration file, otherwise it might rejoin the cluster upon restart.</span><br><span class="line">WARNING: Instance <span class="string">&#x27;127.0.0.1:4306&#x27;</span> cannot persist configuration since MySQL version <span class="number">5.7</span><span class="number">.36</span> does <span class="keyword">not</span> support the <span class="keyword">SET</span> PERSIST command (MySQL version <span class="operator">&gt;</span> <span class="number">8.0</span><span class="number">.11</span> required). Please use the dba.configureLocalInstance() command locally <span class="keyword">to</span> persist the changes.</span><br><span class="line"></span><br><span class="line">The instance <span class="string">&#x27;127.0.0.1:4308&#x27;</span> was successfully removed <span class="keyword">from</span> the cluster.</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>之后再查看节点状态:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"> --------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-111111111111 | 127.0.0.1 | 4306 | ONLINE | PRIMARY | 5.7.36 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-222222222222 | 127.0.0.1 | 4307 | ONLINE | SECONDARY | 5.7.36 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888333 | 127.0.0.1 | 3309 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>如此往复,直到只剩最后一个5.7节点:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"> --------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-111111111111 | 127.0.0.1 | 4306 | ONLINE | PRIMARY | 5.7.36 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888333 | 127.0.0.1 | 3309 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888444 | 127.0.0.1 | 3310 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888555 | 127.0.0.1 | 3311 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>关闭最后一个5.7节点,会自动切换主节点:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"> MySQL <span class="number">127.0</span><span class="number">.0</span><span class="number">.1</span>:<span class="number">4306</span> ssl JS <span class="operator">&gt;</span> c.removeInstance(<span class="string">&#x27;127.0.0.1:4306&#x27;</span>);</span><br><span class="line">The instance will be removed <span class="keyword">from</span> the InnoDB cluster. Depending <span class="keyword">on</span> the instance</span><br><span class="line">being the Seed <span class="keyword">or</span> <span class="keyword">not</span>, the Metadata session might become invalid. If so, please</span><br><span class="line"><span class="keyword">start</span> a <span class="keyword">new</span> session <span class="keyword">to</span> the Metadata Storage R<span class="operator">/</span>W instance.</span><br><span class="line"></span><br><span class="line">Instance <span class="string">&#x27;127.0.0.1:4306&#x27;</span> <span class="keyword">is</span> attempting <span class="keyword">to</span> leave the cluster...</span><br><span class="line">WARNING: <span class="keyword">On</span> instance <span class="string">&#x27;127.0.0.1:4306&#x27;</span> configuration cannot be persisted since MySQL version <span class="number">5.7</span><span class="number">.36</span> does <span class="keyword">not</span> support the <span class="keyword">SET</span> PERSIST command (MySQL version <span class="operator">&gt;</span> <span class="number">8.0</span><span class="number">.11</span> required). Please <span class="keyword">set</span> the <span class="string">&#x27;group_replication_start_on_boot&#x27;</span> variable <span class="keyword">to</span> <span class="string">&#x27;OFF&#x27;</span> <span class="keyword">in</span> the server configuration file, otherwise it might rejoin the cluster upon restart.</span><br><span class="line"></span><br><span class="line">The instance <span class="string">&#x27;127.0.0.1:4306&#x27;</span> was successfully removed <span class="keyword">from</span> the cluster.</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>之后可以看到5.7节点全部下线了,只剩下8.0节点:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"> --------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | MEMBER_ROLE | MEMBER_VERSION |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888333 | 127.0.0.1 | 3309 | ONLINE | PRIMARY | 8.0.25 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888444 | 127.0.0.1 | 3310 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">| group_replication_applier | c8ec34c4-78fc-11ec-864a-888888888555 | 127.0.0.1 | 3311 | ONLINE | SECONDARY | 8.0.25 |</span><br><span class="line">--------------------------- -------------------------------------- ------------- ------------- -------------- ------------- ----------------</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>查看切换过程:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br></pre></td><td class="code"><pre><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">10.753644</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [Warning] [MY<span class="number">-011499</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Members removed from the group: 127.0.0.1:4306&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">10.753648</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [<span class="keyword">System</span>] [MY<span class="number">-011500</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Primary server with address 127.0.0.1:4306 left the group. Electing new Primary.&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">10.753705</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [Note] [MY<span class="number">-011071</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;handle_leader_election_if_neede</span></span><br><span class="line"><span class="string">d is activated,suggested_primary:&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">10.754747</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [Note] [MY<span class="number">-013519</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Elected primary member gtid_exe</span></span><br><span class="line"><span class="string">cuted: 082b900b-79d5-11ec-8fe2-00155d064000:1-32, 36ab409a-79d6-11ec-9cd5-00155d064000:1-37&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">10.754790</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [Note] [MY<span class="number">-013519</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Elected primary member applier</span></span><br><span class="line"><span class="string">channel received_transaction_set: 082b900b-79d5-11ec-8fe2-00155d064000:1-32, 36ab409a-79d6-11ec-9cd5-00155d064000:1-37&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">11.754969</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [<span class="keyword">System</span>] [MY<span class="number">-011507</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;A new primary with address ye</span></span><br><span class="line"><span class="string">jr.run:3309 was elected. The new primary will execute all previous group transactions before allowing writes.&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">11.755803</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">92</span> [<span class="keyword">System</span>] [MY<span class="number">-011566</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Setting super_read_only OFF.</span></span><br><span class="line"><span class="string">&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">12.752517</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [Note] [MY<span class="number">-011735</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;[GCS] Failure reading from fd 5</span></span><br><span class="line"><span class="string">3 n 0&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">12.755961</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">0</span> [<span class="keyword">System</span>] [MY<span class="number">-011503</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Group membership changed to y</span></span><br><span class="line"><span class="string">ejr.run:3309, 127.0.0.1:3310, 127.0.0.1:3311 on view 16426721489193731:9.&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">12.756296</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">91</span> [<span class="keyword">System</span>] [MY<span class="number">-011566</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Setting super_read_only OFF.</span></span><br><span class="line"><span class="string">&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">12.756744</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">91</span> [<span class="keyword">System</span>] [MY<span class="number">-011510</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;This server is working as pr</span></span><br><span class="line"><span class="string">imary member.&#x27;</span></span><br><span class="line"><span class="number">2022</span><span class="number">-01</span><span class="number">-20</span>T22:<span class="number">19</span>:<span class="number">12.756787</span> <span class="number">08</span>:<span class="number">00</span> <span class="number">30</span> [Note] [MY<span class="number">-011485</span>] [Repl] Plugin group_replication reported: <span class="string">&#x27;Primary had applied all relay</span></span><br><span class="line"><span class="string">logs, disabled conflict detection.&#x27;</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p>这就完成滚动升级了。</p><h4 id="4-小结"><a href="#4-小结" class="headerlink" title="4. 小结"></a>4. 小结</h4><p>本文介绍了MGR集群中是如何进行选主的,当有5.7、8.0版本混合时的兼容性,以及如何把MGR 5.7滚动升级到8.0。最后多说一句,哪怕是不用MGR,8.0相对5.7还是有很多企业级特性,5.6、5.7也只能是过渡版本,最终还是强烈建议升级到8.0版本。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/04/28/ce40cc95/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MGR高可用脚本</title>
      <link>https://blog.eucalyptus.cc/2025/04/28/7da255f4/</link>
      <guid>https://blog.eucalyptus.cc/2025/04/28/7da255f4/</guid>
      <pubDate>Mon, 28 Apr 2025 03:10:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在之前的讨论中,我们探讨了基于容器节点的 MySQL Group Replication</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在之前的讨论中,我们探讨了基于容器节点的 MySQL Group Replication 配置。在后续的测试过程中,我们发现如果某个容器节点意外挂掉,该节点会自动从组内退出。这可能会导致组复制的可用性和稳定性受到影响。为了确保组复制的高可用性,本文将介绍如何实现对容器节点可用性的实时检测,以及在节点意外挂掉后如何自动拉起并重新加入组复制。</p><h2 id="脚本目录结构"><a href="#脚本目录结构" class="headerlink" title="脚本目录结构"></a>脚本目录结构</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#容器节点检测恢复脚本</span></span><br><span class="line">monitor_container.sh</span><br><span class="line"><span class="comment">#容器节点检测恢复脚本日志文件</span></span><br><span class="line">container_monitor</span><br><span class="line"><span class="comment">#容器节点检测恢复脚本打印日志文件</span></span><br><span class="line">container_monitor.log</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-28/img1.avif"></p><h3 id="容器节点检测恢复脚本"><a href="#容器节点检测恢复脚本" class="headerlink" title="容器节点检测恢复脚本"></a>容器节点检测恢复脚本</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">#!/bin/bash</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 定义要监控的容器名称数组</span></span><br><span class="line">CONTAINERS ( mysql_mgr_slave1_8.0.37 mysql_mgr_slave2_8.0.37 mysql_mgr_master_8.0.37 )</span><br><span class="line"></span><br><span class="line"><span class="comment"># 定义日志文件路径</span></span><br><span class="line">LOG_DIR /var/lib/docker/resume_startup/container_monitor</span><br><span class="line"></span><br><span class="line"><span class="comment"># 确保日志目录存在</span></span><br><span class="line"><span class="built_in">mkdir</span> -p <span class="variable">$LOG_DIR</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 检查容器状态的函数</span></span><br><span class="line"><span class="function"><span class="title">check_container_status</span></span>() &#123;</span><br><span class="line"><span class="built_in">local</span> container_name <span class="variable">$1</span></span><br><span class="line"><span class="built_in">local</span> log_file <span class="variable">$LOG_DIR</span>/<span class="variable">$&#123;container_name&#125;</span>.<span class="built_in">log</span></span><br><span class="line"><span class="built_in">local</span> status $(docker inspect --format <span class="string">&#x27;&#123;&#123;.State.Status&#125;&#125;&#x27;</span> <span class="variable">$container_name</span> 2&gt;/dev/null)</span><br><span class="line"><span class="keyword">if</span> [ <span class="variable">$status</span> running ]; <span class="keyword">then</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span> <span class="string">&#x27;%Y-%m-%d %H:%M:%S&#x27;</span>) - 容器 <span class="variable">$container_name</span> 正在运行。 &gt;&gt; <span class="variable">$log_file</span></span><br><span class="line"><span class="keyword">else</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span> <span class="string">&#x27;%Y-%m-%d %H:%M:%S&#x27;</span>) - 容器 <span class="variable">$container_name</span> 已停止,尝试重新启动... &gt;&gt; <span class="variable">$log_file</span></span><br><span class="line">docker start <span class="variable">$container_name</span> &gt;&gt; <span class="variable">$log_file</span> 2&gt;&amp;1</span><br><span class="line"><span class="keyword">if</span> [ $? -eq 0 ]; <span class="keyword">then</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span> <span class="string">&#x27;%Y-%m-%d %H:%M:%S&#x27;</span>) - 容器 <span class="variable">$container_name</span> 已成功重新启动。 &gt;&gt; <span class="variable">$log_file</span></span><br><span class="line"><span class="keyword">else</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span> <span class="string">&#x27;%Y-%m-%d %H:%M:%S&#x27;</span>) - 容器 <span class="variable">$container_name</span> 重新启动失败。 &gt;&gt; <span class="variable">$log_file</span></span><br><span class="line"><span class="keyword">fi</span></span><br><span class="line"><span class="keyword">fi</span></span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="comment"># 主循环</span></span><br><span class="line"><span class="keyword">while</span> <span class="literal">true</span>; <span class="keyword">do</span></span><br><span class="line"><span class="keyword">for</span> container <span class="keyword">in</span> <span class="variable">$&#123;CONTAINERS[ ]&#125;</span> ; <span class="keyword">do</span></span><br><span class="line">check_container_status <span class="variable">$container</span></span><br><span class="line"><span class="keyword">done</span></span><br><span class="line"><span class="built_in">sleep</span> 60 <span class="comment"># 每隔 60 秒检查一次</span></span><br><span class="line"><span class="keyword">done</span></span><br></pre></td></tr></table></figure><h3 id="定时任务实现脚本自动执行"><a href="#定时任务实现脚本自动执行" class="headerlink" title="定时任务实现脚本自动执行"></a>定时任务实现脚本自动执行</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">*/5 * * * * /var/lib/docker/resume_startup/./monitor_container.sh &gt;&gt; /var/lib/docker/resume_startup/container_monitor.log 2&gt;&amp;1</span><br></pre></td></tr></table></figure><h3 id="节点重新加入组内策略"><a href="#节点重新加入组内策略" class="headerlink" title="节点重新加入组内策略"></a>节点重新加入组内策略</h3><p>只要在MySQL配置文件中将自动启动组复制的参数设置为ON</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">loose-group_replication_start_on_boot ON</span><br></pre></td></tr></table></figure><h2 id="实验模拟"><a href="#实验模拟" class="headerlink" title="实验模拟"></a>实验模拟</h2><p>开启会话1查看组内成员的状态,开启会话2模拟mgr_slave1节点挂掉的情况 这时在会话1中发现mgr_slave1节点已经离开组内 ,会话2中查看脚本日志发现mgr_slave1挂掉后很快就会拉起,并且在会话1中看到mgr_slave1节点已重新加入组内</p><p>会话1</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-28/img2.avif"></p><p>会话2</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-28/img3.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/04/28/7da255f4/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0.37组复制MGR配置详解</title>
      <link>https://blog.eucalyptus.cc/2025/04/24/ac7d2b86/</link>
      <guid>https://blog.eucalyptus.cc/2025/04/24/ac7d2b86/</guid>
      <pubDate>Thu, 24 Apr 2025 08:50:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;属性&lt;/th&gt;
&lt;th&gt;master&lt;/th&gt;
&lt;th&gt;slave1&lt;/th&gt;
&lt;th&gt;slave2&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;&lt;tr&gt;
&lt;td&gt;IP&lt;/td&gt;
&lt;td&gt;172.17.0.5&lt;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><table><thead><tr><th>属性</th><th>master</th><th>slave1</th><th>slave2</th></tr></thead><tbody><tr><td>IP</td><td>172.17.0.5</td><td>172.17.0.6</td><td>172.17.0.7</td></tr><tr><td>VERSION</td><td>8.0.37</td><td>8.0.37</td><td>8.0.37</td></tr></tbody></table><h2 id="环境准备"><a href="#环境准备" class="headerlink" title="环境准备"></a>环境准备</h2><h3 id="拉起容器节点"><a href="#拉起容器节点" class="headerlink" title="拉起容器节点"></a>拉起容器节点</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#拉起master节点</span></span><br><span class="line">docker run -itd --name mysql_mgr_master_8.0.37 -e MYSQL_ROOT_PASSWORD 123456 -p 3310:3306 -v /var/lib/docker/mysql-mgr-master-8.0.37:/var/lib/mysql 8279f68ee77d</span><br><span class="line"><span class="comment">#拉起slave1节点</span></span><br><span class="line">docker run -itd --name mysql_mgr_slave1_8.0.37 -e MYSQL_ROOT_PASSWORD 123456 -p 3320:3306 -v /var/lib/docker/mysql-mgr-slave1-8.0.37:/var/lib/mysql 8279f68ee77d</span><br><span class="line"><span class="comment">#拉起slave2节点</span></span><br><span class="line">docker run -itd --name mysql_mgr_slave2_8.0.37 -e MYSQL_ROOT_PASSWORD 123456 -p 3330:3306 -v /var/lib/docker/mysql-mgr-slave2-8.0.37:/var/lib/mysql 8279f68ee77d</span><br></pre></td></tr></table></figure><h3 id="容器中安装用到的工具"><a href="#容器中安装用到的工具" class="headerlink" title="容器中安装用到的工具"></a>容器中安装用到的工具</h3><p>拉起三个节点后进入容器使用<strong>microndnf命令</strong>安装下面两个工具,等会配置的时候需要用到</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">microdnf install -y vim net-tools</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img1.avif"></p><h3 id="配置hosts文件"><a href="#配置hosts文件" class="headerlink" title="配置hosts文件"></a>配置hosts文件</h3><p>三个节点都要配置</p><blockquote><p>这里有个遗留问题,不知道为什么每次容器重启后hosts文件都会重置,导致MGR复制出错,详见问题分析</p><p>error log</p><p><strong>Error connecting to source ‘rep fd8fe63cc738:3306’. This was attempt 1&#x2F;1, with a delay of 60 seconds between attempts. Message: Unknown MySQL server host ‘fd8fe63cc738’ (-2)</strong></p></blockquote><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#容器节点ip #容器id</span><br><span class="line">172.17.0.5 fd8fe63cc738</span><br><span class="line">172.17.0.6 e5b0f9986741</span><br><span class="line">172.17.0.7 6d570814d8bb</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img2.avif"></p><h3 id="安装插件"><a href="#安装插件" class="headerlink" title="安装插件"></a>安装插件</h3><p>三个节点中分别安装MGR插件</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">INSTALL PLUGIN group_replication SONAME <span class="string">&#x27;group_replication.so&#x27;</span>;</span><br></pre></td></tr></table></figure><h3 id="创建复制用户"><a href="#创建复制用户" class="headerlink" title="创建复制用户"></a>创建复制用户</h3><p>创建用来复制的用户</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;rep&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;123456&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> replication slave <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;rep&#x27;</span> <span class="string">&#x27;%&#x27;</span> ;</span><br><span class="line">flush privileges;</span><br></pre></td></tr></table></figure><h2 id="my-cnf文件配置"><a href="#my-cnf文件配置" class="headerlink" title="my.cnf文件配置"></a>my.cnf文件配置</h2><p>下面文件中使用的UUID随机生成就可以</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> uuid();</span><br></pre></td></tr></table></figure><h3 id="master节点"><a href="#master节点" class="headerlink" title="master节点"></a>master节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br></pre></td><td class="code"><pre><span class="line">port <span class="number">3306</span></span><br><span class="line">bind<span class="operator">-</span>address <span class="number">0.0</span><span class="number">.0</span><span class="number">.0</span></span><br><span class="line"></span><br><span class="line">log<span class="operator">-</span>bin</span><br><span class="line">server<span class="operator">-</span>id <span class="number">1</span></span><br><span class="line">gtid_mode <span class="keyword">ON</span></span><br><span class="line">enforce_gtid_consistency <span class="number">1</span></span><br><span class="line"></span><br><span class="line">#Plugin_dir <span class="operator">/</span>usr<span class="operator">/</span>lib64<span class="operator">/</span>mysql<span class="operator">/</span>plugin</span><br><span class="line"></span><br><span class="line">#禁用二进制日志事件校验,MGR不支持带checksum的binlog event</span><br><span class="line">binlog_checksum <span class="keyword">NONE</span></span><br><span class="line"></span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_get_public_key <span class="keyword">ON</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_use_ssl <span class="keyword">ON</span></span><br><span class="line"></span><br><span class="line">#使用哈希算法</span><br><span class="line">transaction_write_set_extraction XXHASH64</span><br><span class="line">#组复制的组名</span><br><span class="line">loose<span class="operator">-</span>group_replication_group_name ba3350b0<span class="number">-0</span>abc<span class="number">-11</span>f0<span class="operator">-</span>a872<span class="number">-0242</span>ac110006</span><br><span class="line">#不自动启动组复制</span><br><span class="line">loose<span class="operator">-</span>group_replication_start_on_boot OFF</span><br><span class="line">#本机地址和端口</span><br><span class="line">loose<span class="operator">-</span>group_replication_local_address <span class="number">172.17</span><span class="number">.0</span><span class="number">.5</span>:<span class="number">33061</span></span><br><span class="line">#组中成员</span><br><span class="line">loose<span class="operator">-</span>group_replication_group_seeds <span class="number">172.17</span><span class="number">.0</span><span class="number">.5</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.6</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.7</span>:<span class="number">33061</span></span><br><span class="line">#不启用引导组,手动引导启动</span><br><span class="line">loose<span class="operator">-</span>group_replication_bootstrap_group OFF</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img3.avif"></p><h3 id="slave1节点"><a href="#slave1节点" class="headerlink" title="slave1节点"></a>slave1节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br></pre></td><td class="code"><pre><span class="line">port <span class="number">3306</span></span><br><span class="line">bind<span class="operator">-</span>address <span class="number">0.0</span><span class="number">.0</span><span class="number">.0</span></span><br><span class="line"></span><br><span class="line">log<span class="operator">-</span>bin</span><br><span class="line">server<span class="operator">-</span>id <span class="number">2</span></span><br><span class="line">gtid_mode <span class="keyword">ON</span></span><br><span class="line">enforce_gtid_consistency <span class="number">1</span></span><br><span class="line"></span><br><span class="line">binlog_checksum <span class="keyword">NONE</span></span><br><span class="line"></span><br><span class="line">#这个参数决定<span class="keyword">primary</span>节点到secondary节点的请求是否为基于 RSA 密钥对的密码交换所需的公钥</span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_get_public_key <span class="keyword">ON</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_use_ssl <span class="keyword">ON</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_group_name ba3350b0<span class="number">-0</span>abc<span class="number">-11</span>f0<span class="operator">-</span>a872<span class="number">-0242</span>ac110006</span><br><span class="line">loose<span class="operator">-</span>group_replication_start_on_boot OFF</span><br><span class="line"></span><br><span class="line">loose<span class="operator">-</span>group_replication_local_address <span class="number">172.17</span><span class="number">.0</span><span class="number">.6</span>:<span class="number">33061</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_group_seeds <span class="number">172.17</span><span class="number">.0</span><span class="number">.5</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.6</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.7</span>:<span class="number">33061</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_bootstrap_group OFF</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img4.avif"></p><h3 id="slave2节点"><a href="#slave2节点" class="headerlink" title="slave2节点"></a>slave2节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br></pre></td><td class="code"><pre><span class="line">port <span class="number">3306</span></span><br><span class="line">bind<span class="operator">-</span>address <span class="number">0.0</span><span class="number">.0</span><span class="number">.0</span></span><br><span class="line"></span><br><span class="line">log<span class="operator">-</span>bin</span><br><span class="line">server<span class="operator">-</span>id <span class="number">3</span></span><br><span class="line">gtid_mode <span class="keyword">ON</span></span><br><span class="line">enforce_gtid_consistency <span class="number">1</span></span><br><span class="line"></span><br><span class="line">binlog_checksum <span class="keyword">NONE</span></span><br><span class="line"></span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_get_public_key <span class="keyword">ON</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_recovery_use_ssl <span class="keyword">ON</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_group_name ba3350b0<span class="number">-0</span>abc<span class="number">-11</span>f0<span class="operator">-</span>a872<span class="number">-0242</span>ac110006</span><br><span class="line">loose<span class="operator">-</span>group_replication_start_on_boot OFF</span><br><span class="line"></span><br><span class="line">loose<span class="operator">-</span>group_replication_local_address <span class="number">172.17</span><span class="number">.0</span><span class="number">.7</span>:<span class="number">33061</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_group_seeds <span class="number">172.17</span><span class="number">.0</span><span class="number">.5</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.6</span>:<span class="number">33061</span>,<span class="number">172.17</span><span class="number">.0</span><span class="number">.7</span>:<span class="number">33061</span></span><br><span class="line">loose<span class="operator">-</span>group_replication_bootstrap_group OFF</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img5.avif"></p><h2 id="启动MGR"><a href="#启动MGR" class="headerlink" title="启动MGR"></a>启动MGR</h2><h3 id="master节点-1"><a href="#master节点-1" class="headerlink" title="master节点"></a>master节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> group_replication_bootstrap_group <span class="keyword">ON</span>;</span><br><span class="line"><span class="keyword">START</span> GROUP_REPLICATION;</span><br><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> group_replication_bootstrap_group OFF;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img6.avif"></p><h3 id="slave1节点-1"><a href="#slave1节点-1" class="headerlink" title="slave1节点"></a>slave1节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#指定主从账户与指定通信频道</span><br><span class="line">CHANGE MASTER <span class="keyword">TO</span></span><br><span class="line">MASTER_USER <span class="string">&#x27;rep&#x27;</span>,</span><br><span class="line">MASTER_PASSWORD <span class="string">&#x27;123456&#x27;</span></span><br><span class="line"><span class="keyword">FOR</span> CHANNEL <span class="string">&#x27;group_replication_recovery&#x27;</span>;</span><br><span class="line">#启动组复制</span><br><span class="line"><span class="keyword">START</span> GROUP_REPLICATION;</span><br></pre></td></tr></table></figure><h3 id="slave2节点-1"><a href="#slave2节点-1" class="headerlink" title="slave2节点"></a>slave2节点</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#指定主从账户与指定通信频道</span><br><span class="line">CHANGE MASTER <span class="keyword">TO</span></span><br><span class="line">MASTER_USER <span class="string">&#x27;rep&#x27;</span>,</span><br><span class="line">MASTER_PASSWORD <span class="string">&#x27;123456&#x27;</span></span><br><span class="line"><span class="keyword">FOR</span> CHANNEL <span class="string">&#x27;group_replication_recovery&#x27;</span>;</span><br><span class="line">#启动组复制</span><br><span class="line"><span class="keyword">START</span> GROUP_REPLICATION;</span><br></pre></td></tr></table></figure><h3 id="查看三个节点是否加入组内"><a href="#查看三个节点是否加入组内" class="headerlink" title="查看三个节点是否加入组内"></a>查看三个节点是否加入组内</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> performance_schema.replication_group_members;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img7.avif"></p><h2 id="问题分析"><a href="#问题分析" class="headerlink" title="问题分析"></a>问题分析</h2><h3 id="端口问题"><a href="#端口问题" class="headerlink" title="端口问题"></a>端口问题</h3><p>mysql没有监听tcp4的3306端口,导致MGR复制失,再配置文件中开启即可</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">port 3306</span><br><span class="line">bind-address 0.0.0.0</span><br></pre></td></tr></table></figure><h3 id="端口参数配置问题"><a href="#端口参数配置问题" class="headerlink" title="端口参数配置问题"></a>端口参数配置问题</h3><p>下面的这两个参数配置错误导致组成员无法加入复制组</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">loose-group_replication_local_address 172.17.0.5:3306</span><br><span class="line">loose-group_replication_group_seeds 172.17.0.5:3306,172.17.0.6:3306,172.17.0.7:3306 </span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img8.avif"></p><p>修该端口号即可</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">loose-group_replication_local_address 172.17.0.5:33061</span><br><span class="line">loose-group_replication_group_seeds 172.17.0.5:33061,172.17.0.6:33061,172.17.0.7:33061 </span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img9.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img10.avif"></p><h3 id="连接到源服务器时用户名无效"><a href="#连接到源服务器时用户名无效" class="headerlink" title="连接到源服务器时用户名无效"></a>连接到源服务器时用户名无效</h3><p>这里报错是因为再指定主从账户与指定通信频道的时候还是使用了异步复制的那套配置,查看官方文档后发现这里其实是有区别的</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img11.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/group-replication-adding-instances.html">https://dev.mysql.com/doc/refman/8.0/en/group-replication-adding-instances.html</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img12.avif"></p><p>但是这里改变之后又遇到了另一个问题,<strong>无法在通道“group_REPLICATION_recovery”上使用给定参数更改复制源</strong>,起初以为是复制通道名称的问题,但是换掉名称还是不行,后来查看官网后发现这里没有获取公钥的配置** GET_MASTER_PUBLIC_KEY 1 **,去掉后果然成功了,但是为什么?</p><blockquote><p>最初*<em>GET_MASTER_PUBLIC_KEY 1是为了解决MySQL8.0中密码插件改变导致异步复制的时候slave节点使用rep复制账号连接失败的问题,但是为什么这里指定通道后会出现这个问题?</em>***(待分析 **</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img13.avif"></p><p>error log</p><p><strong>ERROR 3139 (HY000): CHANGE REPLICATION SOURCE with the given parameters cannot be performed on channel ‘group_replication_recovery’.</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img14.avif"></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/change-master-to.html">https://dev.mysql.com/doc/refman/8.0/en/change-master-to.html</a></p><p>嗯,经过一段的时间的排查确定了<strong>group_replication_recovery</strong>通道有自己的安全机制和配置要求,所以在配置通道的时候不允许使用get_master_public_key</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img15.avif"></p><p>昨天搭建好后,今天去看发现master节点的容器挂掉了,slave1节点选举成了新的master节点,</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img16.avif"></p><p>嗯,发现这个问题后手动的拉起了之前挂掉的master节点,但是拉起之前挂掉master节点后,发现处于recovering状态,于是赶紧去看error log,这就出现了之前提到了8.0密码插件的问题** 在从库连接主库的时候使用的是不被 caching_sha2_password认可的RSA公钥,所以主库MySQL拒绝了数据库连接的请求,从而,从库报错’caching_sha2_password’ reported error:Authentication require secure connection。 **</p><p>select * from performance_schema.replication_connection_status\G</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img17.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img18.avif"></p><p>嗯,在组复制中要解决这个问题其实也很简单只需要在MySQL的配置文件中加入</p><p>loose-group_replication_recovery_get_public_key ON就可以了</p></blockquote><h3 id="hosts文件配置问题"><a href="#hosts文件配置问题" class="headerlink" title="hosts文件配置问题"></a>hosts文件配置问题</h3><p>最开始的时候其实是没有去配置hosts文件的,导致出现找不到主机的报错,再容器节点的hosts文件中添加主机映射就可以了,</p><blockquote><p>error log</p><p><strong>2025-03-27T08:59:18.354273Z 25 [ERROR] [MY-010584] [Repl] Replica I&#x2F;O for channel ‘group_replication_recovery’: Error connecting to source ‘rep fd8fe63cc738:3306’. This was attempt 1&#x2F;1, with a delay of 60 seconds between attempts. Message: Unknown MySQL server host ‘fd8fe63cc738’ (-2), Error_code: MY-002005</strong></p></blockquote><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img19.avif"></p><p>但是这里又遇到一个问题,容器节点重启的时候会重置hosts文件,</p><blockquote><p>嗯,经过一段时间的定位,原因找到了,但是怎么解决呐</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img20.avif"></p><p>csdn:docker容器重启之后&#x2F;etc下某些配置文件被重置的问题_docker run gitlab重启配置文件被还原-CSDN博客</p><p>解决方法:可以再容器中写个脚本去自动修改hosts文件,然后再容器启动的时候自动执行这个脚本 &#x2F;etc&#x2F;rc.local),最后在&#x2F;root&#x2F;.bashrc文件中重新加载下就可以了</p></blockquote><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#/etc/rc.local</span></span><br><span class="line"><span class="built_in">echo</span> 127.0.0.1 localhost</span><br><span class="line">::1 localhost ip6-localhost ip6-loopback</span><br><span class="line">fe00::0 ip6-localnet</span><br><span class="line">ff00::0 ip6-mcastprefix</span><br><span class="line">ff02::1 ip6-allnodes</span><br><span class="line">ff02::2 ip6-allrouters</span><br><span class="line">172.17.0.5 fd8fe63cc738</span><br><span class="line">172.17.0.6 e5b0f9986741</span><br><span class="line">172.17.0.7 6d570814d8bb &gt; /etc/hosts</span><br><span class="line"><span class="comment">#/root/.bashrc</span></span><br><span class="line"><span class="built_in">source</span> /etc/rc.local</span><br></pre></td></tr></table></figure><h3 id="slave节点执行的事务比组中存在的事务多"><a href="#slave节点执行的事务比组中存在的事务多" class="headerlink" title="slave节点执行的事务比组中存在的事务多"></a>slave节点执行的事务比组中存在的事务多</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2025-04-24/img21.avif"></p><p>解决方法:</p><p>停止组复制-清除事务日志-重启组复制</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">STOP GROUP_REPLICATION;</span><br><span class="line">RESET MASTER;</span><br><span class="line"><span class="keyword">START</span> GROUP_REPLICATION;</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/04/24/ac7d2b86/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>WordPress通过简码插入bilibili视频</title>
      <link>https://blog.eucalyptus.cc/2025/03/25/36a91bba/</link>
      <guid>https://blog.eucalyptus.cc/2025/03/25/36a91bba/</guid>
      <pubDate>Tue, 25 Mar 2025 15:24:09 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>B站是国内非常受欢迎的视频分享平台，上面不仅内容丰富，而且很多视频制作精良、趣味十足。很多人，比如我，就喜欢将B站的视频通过 iframe 嵌入到自己的网页中，但这段代码又长又复杂，字符长度大约有230个，每次使用都很麻烦。为了让大家更方便地在 WordPress 网站中插入B站视频，我准备了一个简单实用的短代码教程，轻松几步就能搞定。</p><h2 id="二、代码"><a href="#二、代码" class="headerlink" title="二、代码"></a>二、代码</h2><p>将以下代码复制到网站主题的 functions.php 文件末尾即可完成添加。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br></pre></td><td class="code"><pre><span class="line">/**</span><br><span class="line"> * 添加插入Bilibili视频的短代码</span><br><span class="line"> *</span><br><span class="line"> * @param array <span class="variable">$atts</span> 短代码属性数组</span><br><span class="line"> * @param string|null <span class="variable">$content</span> 短代码内容（未使用）</span><br><span class="line"> * @<span class="built_in">return</span> string 返回生成的HTML代码</span><br><span class="line"> */</span><br><span class="line"><span class="keyword">function</span> vbilibili_shortcode( <span class="variable">$atts</span>, <span class="variable">$content</span> = null ) &#123;</span><br><span class="line">    // 默认参数值</span><br><span class="line">    <span class="variable">$defaults</span> = array(</span><br><span class="line">        <span class="string">&#x27;av&#x27;</span> =&gt; <span class="string">&#x27;&#x27;</span>,    // Bilibili视频的AV号</span><br><span class="line">        <span class="string">&#x27;bv&#x27;</span> =&gt; <span class="string">&#x27;&#x27;</span>,    // Bilibili视频的BV号</span><br><span class="line">        <span class="string">&#x27;w&#x27;</span>  =&gt; <span class="string">&#x27;100%&#x27;</span>, // 默认宽度为100%</span><br><span class="line">    );</span><br><span class="line"></span><br><span class="line">    // 解析短代码中的参数</span><br><span class="line">    <span class="variable">$atts</span> = shortcode_atts( <span class="variable">$defaults</span>, <span class="variable">$atts</span> );</span><br><span class="line">    </span><br><span class="line">    // 如果参数 av 和 bv 都为空，则返回错误信息</span><br><span class="line">    <span class="keyword">if</span> ( empty( <span class="variable">$atts</span>[<span class="string">&#x27;av&#x27;</span>] ) &amp;&amp; empty( <span class="variable">$atts</span>[<span class="string">&#x27;bv&#x27;</span>] ) ) &#123;</span><br><span class="line">        <span class="built_in">return</span> <span class="string">&#x27;&lt;p&gt;av 和 bv 不可为空&lt;/p&gt;&#x27;</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    // 如果参数 av 和 bv 同时存在，则返回错误信息</span><br><span class="line">    <span class="keyword">if</span> ( ! empty( <span class="variable">$atts</span>[<span class="string">&#x27;av&#x27;</span>] ) &amp;&amp; ! empty( <span class="variable">$atts</span>[<span class="string">&#x27;bv&#x27;</span>] ) ) &#123;</span><br><span class="line">        <span class="built_in">return</span> <span class="string">&#x27;&lt;p&gt;av 和 bv 不可同时存在&lt;/p&gt;&#x27;</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    // 根据参数 av 或 bv 构建 iframe 的 URL</span><br><span class="line">    <span class="keyword">if</span> ( ! empty( <span class="variable">$atts</span>[<span class="string">&#x27;av&#x27;</span>] ) ) &#123;</span><br><span class="line">        <span class="variable">$iframe_url</span> = <span class="string">&#x27;https://player.bilibili.com/player.html?aid=&#x27;</span> . esc_attr( <span class="variable">$atts</span>[<span class="string">&#x27;av&#x27;</span>] ) . <span class="string">&#x27;&amp;high_quality=1&#x27;</span>;</span><br><span class="line">    &#125; elseif ( ! empty( <span class="variable">$atts</span>[<span class="string">&#x27;bv&#x27;</span>] ) ) &#123;</span><br><span class="line">        <span class="variable">$iframe_url</span> = <span class="string">&#x27;https://player.bilibili.com/player.html?bvid=&#x27;</span> . esc_attr( <span class="variable">$atts</span>[<span class="string">&#x27;bv&#x27;</span>] ) . <span class="string">&#x27;&amp;high_quality=1&#x27;</span>;</span><br><span class="line">    &#125;</span><br><span class="line"></span><br><span class="line">    // 构建 iframe 的 HTML 代码，并直接应用内联样式</span><br><span class="line">    <span class="variable">$iframe</span> = <span class="string">&#x27;&lt;div style=&quot;position:relative; padding-bottom:56.25%; height:0; overflow:hidden; margin:0 auto;&quot;&gt;&lt;iframe src=&quot;&#x27;</span> . <span class="variable">$iframe_url</span> . <span class="string">&#x27;&quot; style=&quot;position:absolute; top:0; left:0; width:100%; height:100%;&quot; frameborder=&quot;no&quot; scrolling=&quot;no&quot; allowfullscreen=&quot;allowfullscreen&quot;&gt;&lt;/iframe&gt;&lt;/div&gt;&#x27;</span>;</span><br><span class="line"></span><br><span class="line">    // 返回 iframe 的 HTML 代码</span><br><span class="line">    <span class="built_in">return</span> <span class="variable">$iframe</span>;</span><br><span class="line">&#125;</span><br><span class="line">add_shortcode( <span class="string">&#x27;vbilibili&#x27;</span>, <span class="string">&#x27;vbilibili_shortcode&#x27;</span> );</span><br></pre></td></tr></table></figure><p>将内容嵌入到<code>&lt;iframe&gt;</code>中，并通过设置相关属性来限制<code>&lt;iframe&gt;</code> 内的页面无法在新窗口或新标签页中打开，从而防止跳转到 B 站。可以通过在 <code>&lt;iframe&gt;</code> 标签中添加 sandbox 属性，结合 allow 属性精确控制权限，确保用户在当前页面内浏览，不被引导至其他网站。这种方式有助于提升用户体验的连续性，同时防止意外跳转带来的干扰。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sandbox=<span class="string">&quot;allow-top-navigation allow-same-origin allow-forms allow-scripts&quot;</span></span><br></pre></td></tr></table></figure><h2 id="三、WPCode"><a href="#三、WPCode" class="headerlink" title="三、WPCode"></a>三、WPCode</h2><p>如果你使用的是一个经常更新的主题，每次更新后都需要将代码添加到 functions.php 文件中，这显然十分麻烦。为了解决这个问题，你可以使用 WPCode 插件，在不修改主题文件的情况下，轻松实现自定义代码片段的添加和管理。</p><h3 id="3-1、WPCode介绍"><a href="#3-1、WPCode介绍" class="headerlink" title="3.1、WPCode介绍"></a>3.1、WPCode介绍</h3><p>WPCode 是一款流行的WordPress插件，它允许用户在不修改主题文件的情况下，向WordPress网站添加自定义代码片段。这款插件非常适合需要在网站中添加额外功能的站长，例如，添加Google分析或百度统计的代码，或者插入自定义CSS、JavaScript等。</p><p>WPCode插件还提供了一个代码片段库，您可以在这个库里面找到经过验证的PHP代码片段，例如：禁用REST API、禁用 XML-RPC、禁用注释、允许 SVG 文件上传、禁用 Gutenberg、添加经典编辑器等，而无需为每个请求安装单独的插件。使用这个插件，还可以控制代码的激活状态，如果需要在调试情况下先不适用某个功能，可以先不激活，而不是直接删除。</p><p>总之非常方便，如果您的网站也是WordPress网站，那么站长建议您可以安装下这个插件试一试。</p><h3 id="3-2、自定义代码到WPCode"><a href="#3-2、自定义代码到WPCode" class="headerlink" title="3.2、自定义代码到WPCode"></a>3.2、自定义代码到WPCode</h3><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-03-25/1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-03-25/2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-03-25/2.avif"></p><h3 id="3-3、使用简码"><a href="#3-3、使用简码" class="headerlink" title="3.3、使用简码"></a>3.3、使用简码</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">[vbilibili 参数名=<span class="string">&quot;参数值&quot;</span>][/vbilibili]</span><br></pre></td></tr></table></figure><p>参数：</p><table><thead><tr><th>参数名</th><th>可选值</th><th>默认值</th><th>解释</th><th>是否必须</th></tr></thead><tbody><tr><td>av</td><td>–</td><td>–</td><td>Bilibili 视频的 AV 号</td><td>是</td></tr><tr><td>bv</td><td>–</td><td>–</td><td>Bilibili 视频的 BV 号</td><td>是</td></tr></tbody></table><p>示例：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">[vbilibili bv=BV1SoZ5YVEJg][/vbilibili]</span><br></pre></td></tr></table></figure><div style="position: relative; width: 100%; height: 0; padding-bottom: 56.25%;">  <iframe     src="https://player.bilibili.com/player.html?bvid=BV1SoZ5YVEJg&page=1&high_quality=1&as_wide=1&allowfullscreen=true&autoplay=0"     style="position: absolute; width: 100%; height: 100%; left: 0; top: 0;"     frameborder="0"     scrolling="no"     allowfullscreen>  </iframe></div><p>注意：  </p><ul><li>Bilibili 视频的 AV 号或 BV 号是必须的，但只要输入 AV 号或 BV 号的其中一个即可。  </li><li>Bilibili 视频的 AV 号不要带上 av</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E7%AE%80%E7%A0%81/">简码</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/03/25/36a91bba/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker–容器报错 Error response from daemon: driver failed programming external connectivity on endpoint</title>
      <link>https://blog.eucalyptus.cc/2025/03/19/c63aed66/</link>
      <guid>https://blog.eucalyptus.cc/2025/03/19/c63aed66/</guid>
      <pubDate>Wed, 19 Mar 2025 06:34:53 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;error-log&quot;&gt;&lt;a href=&quot;#error-log&quot; class=&quot;headerlink&quot; title=&quot;error log&quot;&gt;&lt;/a&gt;error log&lt;/h2&gt;&lt;p&gt;从报错日志来看是iptables的转发规则有问题&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="error-log"><a href="#error-log" class="headerlink" title="error log"></a>error log</h2><p>从报错日志来看是iptables的转发规则有问题</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2025-03-19/img1.avif"></p><p>docker logs centos9查看容器日志，没看出什么异常</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2025-03-19/img2.avif"></p><p>CSDN文章参考</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2025-03-19/img3.avif"></p><p>看了上述文章之后，想起来昨天在配置k8s的时候关闭了firewalld。嗯，然后把docker服务重启，后在启动容器果然没有报错了</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2025-03-19/img4.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/03/19/c63aed66/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL 16.3基于pg_basebackup实现异步流复制</title>
      <link>https://blog.eucalyptus.cc/2025/01/22/da24c457/</link>
      <guid>https://blog.eucalyptus.cc/2025/01/22/da24c457/</guid>
      <pubDate>Wed, 22 Jan 2025 03:44:12 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;本文主要介绍基于pg_basebackup实现主从复制（异步流复制）。&lt;/p&gt;
&lt;p&gt;MASTER节点安装的方法可以看这篇文章：PostgreSQL YUM安装&lt;/p&gt;
&lt;p&gt;关于基本的配置就不作过多的介绍了，直接开始。&lt;/p&gt;
&lt;h4 id=&quot;MASTER节点&quot;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>本文主要介绍基于pg_basebackup实现主从复制（异步流复制）。</p><p>MASTER节点安装的方法可以看这篇文章：PostgreSQL YUM安装</p><p>关于基本的配置就不作过多的介绍了，直接开始。</p><h4 id="MASTER节点"><a href="#MASTER节点" class="headerlink" title="MASTER节点"></a>MASTER节点</h4><p>首先在master节点创建一个用于复制的用户rep，设置密码123456，并授予rolcanlogin权限</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> ROLE rep <span class="keyword">WITH</span> REPLICATION LOGIN PASSWORD <span class="string">&#x27;123456&#x27;</span>;</span><br></pre></td></tr></table></figure><p>接下来需要配置pg_hba.conf文件，配置完后记得重启PG</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img1.avif"></p><p>由于我们的SLAVE节点是一个DOCKER PG的容器，下面就需要使用pg_basebackup来备份MASTER节点的数据目录用来启动SLAVE节点，先备份</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_basebackup -D /opt/pg_basebackup/ -h 172.17.0.2 -p 5432 -U rep -Fp -R -X s -P -v</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img2.avif"></p><h4 id="SLAVE节点"><a href="#SLAVE节点" class="headerlink" title="SLAVE节点"></a>SLAVE节点</h4><p>接下来在DOCKER的数据目录下创建一个SLAVE的本地映射文件用于启动SLAVE节点</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img3.avif"></p><p>接下来将MASTER节点中pg_basebackup备份的数据COPY到我们准备的本地映射centos9_pg目录下</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">cp</span> centos9:/opt/pg_basebackup /var/lib/docker/centos9_pg/</span><br></pre></td></tr></table></figure><p>然后启动SLAVE节点即可</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --name pg.slave.16.3 -e POSTGRES_PASSWORD=123456 -v /var/lib/docker/centos9_pg:/var/lib/postgresql/data 07a4ee949b9e</span><br></pre></td></tr></table></figure><p>进入容器，看到从数据目录下多了一个<code>standby.signal</code>文件，这默认是一个空文件，其实是一个标识文件。</p><p>这是因为上面备份的时候使用了<code>-R</code>参数，所以在同步的数据里，会在<code>postgresql.auto.conf</code>里配置上 <code>primary_conninfo</code>信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img5.avif"></p><h4 id="验证主从同步"><a href="#验证主从同步" class="headerlink" title="验证主从同步"></a>验证主从同步</h4><p>在MASTER节点上可以看到流复制的监控信息，其中 state &#x3D; streaming 表示流复制状态正常</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> pg_stat_replication;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img6.avif"></p><p>下面执行DML语句进行验证（验证的数据在备份之前就可以准备好）</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img7.avif"></p><h4 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h4><p>在配置的过程中如果遇到报错一定要去看下错误日志，错误日志中会记录详细信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-22/img9.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/01/22/da24c457/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>使用pgcli实现PostgreSQL命令自动补全功能（Python-3.9.0）</title>
      <link>https://blog.eucalyptus.cc/2025/01/06/0769506e/</link>
      <guid>https://blog.eucalyptus.cc/2025/01/06/0769506e/</guid>
      <pubDate>Mon, 06 Jan 2025 05:33:29 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;安装和配置python-3.9.0可以参考之前发布的这篇文章。&lt;/p&gt;
&lt;p&gt;下面我们直接来安装pgcli&lt;/p&gt;
&lt;figure class=&quot;highlight bash&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>安装和配置python-3.9.0可以参考之前发布的这篇文章。</p><p>下面我们直接来安装pgcli</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pip install pgcli</span><br></pre></td></tr></table></figure><p>安装好后使用pgcli登陆的时候会发现有个报错</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-06/img1.avif"></p><p>这里我们参考提示移动下这个文件的位置就好了</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mv</span> /root/.pgclirc /root/.config/pgcli/</span><br></pre></td></tr></table></figure><p>然后登陆到postgres用户来登陆我们的postgresql</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#登陆postgres用户</span></span><br><span class="line"></span><br><span class="line">su - postgres</span><br><span class="line"></span><br><span class="line"><span class="comment">#登陆postgresql数据库</span></span><br><span class="line"></span><br><span class="line">pgcli</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2025-01-06/img2.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/01/06/0769506e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Wordpress登录页面插件</title>
      <link>https://blog.eucalyptus.cc/2025/01/03/3cc792f2/</link>
      <guid>https://blog.eucalyptus.cc/2025/01/03/3cc792f2/</guid>
      <pubDate>Fri, 03 Jan 2025 03:36:28 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot; title=&quot;一、前言&quot;&gt;&lt;/a&gt;一、前言&lt;/h2&gt;&lt;p&gt;&lt;code&gt;LoginPress | wp-login Custom Login Page</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p><code>LoginPress | wp-login Custom Login Page Customizer</code> 是一款WordPress插件，它提供了丰富的自定义字段来改变WordPress登录页面的布局。使用该插件，您可以完全修改登录页面的外观和感觉，包括登录错误消息、忘记密码错误消息、注册错误消息、忘记密码提示消息等。LoginPress 插件使用 Customizer API 构建，允许您实时预览登录页面的更改。该插件非常易于使用，不需要任何编码技能，只需为登录表单的每个元素设置选项，就可以在几秒钟内创建一个新的自定义登录页面。</p><p>LoginPress 提供了免费和专业版插件，专业版提供了更多的功能，如Google字体、Google reCaptcha、选择主题等。如果您希望为您的WordPress网站添加一个外观酷炫的登录页面，LoginPress 是一个必备的插件。</p><h2 id="二、LoginPress功能"><a href="#二、LoginPress功能" class="headerlink" title="二、LoginPress功能"></a>二、LoginPress功能</h2><p>Logo：可以更改登录Logo {image，width，height，padding，URL and Title}。<br>背景：您可以自定义背景图像或颜色。设置其位置、大小和可重复属性。<br>登录表单：即使你可以自定义登录表单{图像或颜色，宽度，高度，填充和边框}。自定义输入文本字段{宽度，边距，文本颜色，标签颜色和背景颜色}。<br>忘记形式：美丽的插件在这里你可以改变背景或颜色的忘记形式。<br>按钮：您可以设置按钮所见即所得的颜色。<br>错误消息：插件的主要功能.您可以更改错误日志消息，因为您希望在LoginPress→ Error Messages中向用户显示。<br>欢迎消息：与错误日志消息相同，您可以通过LoginPress→ Welcome Messages自定义欢迎消息。<br>表单页脚：登录按钮后，这里是表单页脚.您可以自定义页脚{文本、显示、文本装饰、文本颜色、文本悬停颜色和文本大小}。在此部分中，您还可以自定义页脚文本。</p><p>定制后使WordPress登录页面移动的友好<br>这个插件也是响应式的。这意味着，当您自定义登录页面，它会在移动的上看起来不错，即它是响应式的.</p><h2 id="三、演示"><a href="#三、演示" class="headerlink" title="三、演示"></a>三、演示</h2><p>使用reCAPTCHA和Google Fonts需要购买LoginPressPro版，而系统中其他所有工具和服务均可免费使用。无论是进行基础的表单验证、网站数据分析，还是应用多样化的字体样式，平台都为用户提供了全面支持，让在线项目的创建和管理更加高效便捷。</p><p>LoginPress默认主题</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-01-03/1.avif"></p><p>LoginPressPro主题</p><!-- 这是一张图片，ocr 内容为： --><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2025-01-03/2.avif"></p><h2 id="四、LoginPressPro百度网盘下载"><a href="#四、LoginPressPro百度网盘下载" class="headerlink" title="四、LoginPressPro百度网盘下载"></a>四、LoginPressPro百度网盘下载</h2><p>为了确保功能完整使用，建议将LoginPress默认主题与其付费升级版本LoginPressPro一并安装，这样可以充分发挥其全部潜力并提升用户体验。</p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://pan.baidu.com/s/1gm3aBamBy7o9_7bRZ_WcZg?pwd=xqqn">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://pan.baidu.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://pan.baidu.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">LoginPressPro 百度网盘下载</div>            <div class="tag-link-sitename">提取码：xqqn</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><blockquote><p>提取码：xqqn</p></blockquote>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%8F%92%E4%BB%B6/">插件</category>
      
      
      <comments>https://blog.eucalyptus.cc/2025/01/03/3cc792f2/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>轻博客的粒子浪漫</title>
      <link>https://blog.eucalyptus.cc/2024/12/13/d6c7ec05/</link>
      <guid>https://blog.eucalyptus.cc/2024/12/13/d6c7ec05/</guid>
      <pubDate>Fri, 13 Dec 2024 02:50:50 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、鼠标点击烟花特效&quot;&gt;&lt;a href=&quot;#一、鼠标点击烟花特效&quot; class=&quot;headerlink&quot; title=&quot;一、鼠标点击烟花特效&quot;&gt;&lt;/a&gt;一、鼠标点击烟花特效&lt;/h2&gt;&lt;div class=&#39;anzhiyu-tag-link&#39;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、鼠标点击烟花特效"><a href="#一、鼠标点击烟花特效" class="headerlink" title="一、鼠标点击烟花特效"></a>一、鼠标点击烟花特效</h2><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://juejin.cn/post/7106018120036253710">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://juejin.cn/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://juejin.cn/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">掘金 - 鼠标点击烟花特效</div>            <div class="tag-link-sitename">粒子特效教程</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br></pre></td><td class="code"><pre><span class="line"><span class="tag">&lt;<span class="name">html</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">body</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">script</span>&gt;</span><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript"><span class="keyword">function</span> <span class="title function_">clickEffect</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> balls = [];</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> longPressed = <span class="literal">false</span>;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> longPress;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> multiplier = <span class="number">0</span>;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> width, height;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> origin;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> normal;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">let</span> ctx;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">const</span> colours = [<span class="string">&quot;#F73859&quot;</span>, <span class="string">&quot;#14FFEC&quot;</span>, <span class="string">&quot;#00E0FF&quot;</span>, <span class="string">&quot;#FF99FE&quot;</span>, <span class="string">&quot;#FAF15D&quot;</span>];</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">const</span> canvas = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&quot;canvas&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">  <span class="variable language_">document</span>.<span class="property">body</span>.<span class="title function_">appendChild</span>(canvas);</span></span><br><span class="line"><span class="language-javascript">  canvas.<span class="title function_">setAttribute</span>(<span class="string">&quot;style&quot;</span>, <span class="string">&quot;width: 100%; height: 100%; top: 0; left: 0; z-index: 99999; position: fixed; pointer-events: none;&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">const</span> pointer = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&quot;span&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">  pointer.<span class="property">classList</span>.<span class="title function_">add</span>(<span class="string">&quot;pointer&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">  <span class="variable language_">document</span>.<span class="property">body</span>.<span class="title function_">appendChild</span>(pointer);</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">if</span> (canvas.<span class="property">getContext</span> &amp;&amp; <span class="variable language_">window</span>.<span class="property">addEventListener</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    ctx = canvas.<span class="title function_">getContext</span>(<span class="string">&quot;2d&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">updateSize</span>();</span></span><br><span class="line"><span class="language-javascript">    <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;resize&#x27;</span>, updateSize, <span class="literal">false</span>);</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">loop</span>();</span></span><br><span class="line"><span class="language-javascript">    <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&quot;mousedown&quot;</span>, <span class="keyword">function</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="title function_">pushBalls</span>(<span class="title function_">randBetween</span>(<span class="number">10</span>, <span class="number">20</span>), e.<span class="property">clientX</span>, e.<span class="property">clientY</span>);</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">document</span>.<span class="property">body</span>.<span class="property">classList</span>.<span class="title function_">add</span>(<span class="string">&quot;is-pressed&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">      longPress = <span class="built_in">setTimeout</span>(<span class="keyword">function</span>(<span class="params"></span>)&#123;</span></span><br><span class="line"><span class="language-javascript">        <span class="variable language_">document</span>.<span class="property">body</span>.<span class="property">classList</span>.<span class="title function_">add</span>(<span class="string">&quot;is-longpress&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">        longPressed = <span class="literal">true</span>;</span></span><br><span class="line"><span class="language-javascript">      &#125;, <span class="number">500</span>);</span></span><br><span class="line"><span class="language-javascript">    &#125;, <span class="literal">false</span>);</span></span><br><span class="line"><span class="language-javascript">    <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&quot;mouseup&quot;</span>, <span class="keyword">function</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="built_in">clearInterval</span>(longPress);</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">if</span> (longPressed == <span class="literal">true</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">        <span class="variable language_">document</span>.<span class="property">body</span>.<span class="property">classList</span>.<span class="title function_">remove</span>(<span class="string">&quot;is-longpress&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">        <span class="title function_">pushBalls</span>(<span class="title function_">randBetween</span>(<span class="number">50</span> + <span class="title class_">Math</span>.<span class="title function_">ceil</span>(multiplier), <span class="number">100</span> + <span class="title class_">Math</span>.<span class="title function_">ceil</span>(multiplier)), e.<span class="property">clientX</span>, e.<span class="property">clientY</span>);</span></span><br><span class="line"><span class="language-javascript">        longPressed = <span class="literal">false</span>;</span></span><br><span class="line"><span class="language-javascript">      &#125;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">document</span>.<span class="property">body</span>.<span class="property">classList</span>.<span class="title function_">remove</span>(<span class="string">&quot;is-pressed&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">    &#125;, <span class="literal">false</span>);</span></span><br><span class="line"><span class="language-javascript">    <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&quot;mousemove&quot;</span>, <span class="keyword">function</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">let</span> x = e.<span class="property">clientX</span>;</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">let</span> y = e.<span class="property">clientY</span>;</span></span><br><span class="line"><span class="language-javascript">      pointer.<span class="property">style</span>.<span class="property">top</span> = y + <span class="string">&quot;px&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">      pointer.<span class="property">style</span>.<span class="property">left</span> = x + <span class="string">&quot;px&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">    &#125;, <span class="literal">false</span>);</span></span><br><span class="line"><span class="language-javascript">  &#125; <span class="keyword">else</span> &#123;</span></span><br><span class="line"><span class="language-javascript">    <span class="variable language_">console</span>.<span class="title function_">log</span>(<span class="string">&quot;canvas or addEventListener is unsupported!&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">function</span> <span class="title function_">updateSize</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    canvas.<span class="property">width</span> = <span class="variable language_">window</span>.<span class="property">innerWidth</span> * <span class="number">2</span>;</span></span><br><span class="line"><span class="language-javascript">    canvas.<span class="property">height</span> = <span class="variable language_">window</span>.<span class="property">innerHeight</span> * <span class="number">2</span>;</span></span><br><span class="line"><span class="language-javascript">    canvas.<span class="property">style</span>.<span class="property">width</span> = <span class="variable language_">window</span>.<span class="property">innerWidth</span> + <span class="string">&#x27;px&#x27;</span>;</span></span><br><span class="line"><span class="language-javascript">    canvas.<span class="property">style</span>.<span class="property">height</span> = <span class="variable language_">window</span>.<span class="property">innerHeight</span> + <span class="string">&#x27;px&#x27;</span>;</span></span><br><span class="line"><span class="language-javascript">    ctx.<span class="title function_">scale</span>(<span class="number">2</span>, <span class="number">2</span>);</span></span><br><span class="line"><span class="language-javascript">    width = (canvas.<span class="property">width</span> = <span class="variable language_">window</span>.<span class="property">innerWidth</span>);</span></span><br><span class="line"><span class="language-javascript">    height = (canvas.<span class="property">height</span> = <span class="variable language_">window</span>.<span class="property">innerHeight</span>);</span></span><br><span class="line"><span class="language-javascript">    origin = &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="attr">x</span>: width / <span class="number">2</span>,</span></span><br><span class="line"><span class="language-javascript">      <span class="attr">y</span>: height / <span class="number">2</span></span></span><br><span class="line"><span class="language-javascript">    &#125;;</span></span><br><span class="line"><span class="language-javascript">    normal = &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="attr">x</span>: width / <span class="number">2</span>,</span></span><br><span class="line"><span class="language-javascript">      <span class="attr">y</span>: height / <span class="number">2</span></span></span><br><span class="line"><span class="language-javascript">    &#125;;</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">class</span> <span class="title class_">Ball</span> &#123;</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">constructor</span>(<span class="params">x = origin.x, y = origin.y</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">x</span> = x;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">y</span> = y;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">angle</span> = <span class="title class_">Math</span>.<span class="property">PI</span> * <span class="number">2</span> * <span class="title class_">Math</span>.<span class="title function_">random</span>();</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">if</span> (longPressed == <span class="literal">true</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">        <span class="variable language_">this</span>.<span class="property">multiplier</span> = <span class="title function_">randBetween</span>(<span class="number">14</span> + multiplier, <span class="number">15</span> + multiplier);</span></span><br><span class="line"><span class="language-javascript">      &#125; <span class="keyword">else</span> &#123;</span></span><br><span class="line"><span class="language-javascript">        <span class="variable language_">this</span>.<span class="property">multiplier</span> = <span class="title function_">randBetween</span>(<span class="number">6</span>, <span class="number">12</span>);</span></span><br><span class="line"><span class="language-javascript">      &#125;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">vx</span> = (<span class="variable language_">this</span>.<span class="property">multiplier</span> + <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">0.5</span>) * <span class="title class_">Math</span>.<span class="title function_">cos</span>(<span class="variable language_">this</span>.<span class="property">angle</span>);</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">vy</span> = (<span class="variable language_">this</span>.<span class="property">multiplier</span> + <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">0.5</span>) * <span class="title class_">Math</span>.<span class="title function_">sin</span>(<span class="variable language_">this</span>.<span class="property">angle</span>);</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">r</span> = <span class="title function_">randBetween</span>(<span class="number">8</span>, <span class="number">12</span>) + <span class="number">3</span> * <span class="title class_">Math</span>.<span class="title function_">random</span>();</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">color</span> = colours[<span class="title class_">Math</span>.<span class="title function_">floor</span>(<span class="title class_">Math</span>.<span class="title function_">random</span>() * colours.<span class="property">length</span>)];</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">update</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">x</span> += <span class="variable language_">this</span>.<span class="property">vx</span> - normal.<span class="property">x</span>;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">y</span> += <span class="variable language_">this</span>.<span class="property">vy</span> - normal.<span class="property">y</span>;</span></span><br><span class="line"><span class="language-javascript">      normal.<span class="property">x</span> = -<span class="number">2</span> / <span class="variable language_">window</span>.<span class="property">innerWidth</span> * <span class="title class_">Math</span>.<span class="title function_">sin</span>(<span class="variable language_">this</span>.<span class="property">angle</span>);</span></span><br><span class="line"><span class="language-javascript">      normal.<span class="property">y</span> = -<span class="number">2</span> / <span class="variable language_">window</span>.<span class="property">innerHeight</span> * <span class="title class_">Math</span>.<span class="title function_">cos</span>(<span class="variable language_">this</span>.<span class="property">angle</span>);</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">r</span> -= <span class="number">0.3</span>;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">vx</span> *= <span class="number">0.9</span>;</span></span><br><span class="line"><span class="language-javascript">      <span class="variable language_">this</span>.<span class="property">vy</span> *= <span class="number">0.9</span>;</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">function</span> <span class="title function_">pushBalls</span>(<span class="params">count = <span class="number">1</span>, x = origin.x, y = origin.y</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; count; i++) &#123;</span></span><br><span class="line"><span class="language-javascript">      balls.<span class="title function_">push</span>(<span class="keyword">new</span> <span class="title class_">Ball</span>(x, y));</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">function</span> <span class="title function_">randBetween</span>(<span class="params">min, max</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    <span class="keyword">return</span> <span class="title class_">Math</span>.<span class="title function_">floor</span>(<span class="title class_">Math</span>.<span class="title function_">random</span>() * max) + min;</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">function</span> <span class="title function_">loop</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    ctx.<span class="property">fillStyle</span> = <span class="string">&quot;rgba(255, 255, 255, 0)&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">    ctx.<span class="title function_">clearRect</span>(<span class="number">0</span>, <span class="number">0</span>, canvas.<span class="property">width</span>, canvas.<span class="property">height</span>);</span></span><br><span class="line"><span class="language-javascript">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; balls.<span class="property">length</span>; i++) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">let</span> b = balls[i];</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">if</span> (b.<span class="property">r</span> &lt; <span class="number">0</span>) <span class="keyword">continue</span>;</span></span><br><span class="line"><span class="language-javascript">      ctx.<span class="property">fillStyle</span> = b.<span class="property">color</span>;</span></span><br><span class="line"><span class="language-javascript">      ctx.<span class="title function_">beginPath</span>();</span></span><br><span class="line"><span class="language-javascript">      ctx.<span class="title function_">arc</span>(b.<span class="property">x</span>, b.<span class="property">y</span>, b.<span class="property">r</span>, <span class="number">0</span>, <span class="title class_">Math</span>.<span class="property">PI</span> * <span class="number">2</span>, <span class="literal">false</span>);</span></span><br><span class="line"><span class="language-javascript">      ctx.<span class="title function_">fill</span>();</span></span><br><span class="line"><span class="language-javascript">      b.<span class="title function_">update</span>();</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">    <span class="keyword">if</span> (longPressed == <span class="literal">true</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      multiplier += <span class="number">0.2</span>;</span></span><br><span class="line"><span class="language-javascript">    &#125; <span class="keyword">else</span> <span class="keyword">if</span> (!longPressed &amp;&amp; multiplier &gt;= <span class="number">0</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">      multiplier -= <span class="number">0.4</span>;</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">removeBall</span>();</span></span><br><span class="line"><span class="language-javascript">    <span class="title function_">requestAnimationFrame</span>(loop);</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">  <span class="keyword">function</span> <span class="title function_">removeBall</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; balls.<span class="property">length</span>; i++) &#123;</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">let</span> b = balls[i];</span></span><br><span class="line"><span class="language-javascript">      <span class="keyword">if</span> (b.<span class="property">x</span> + b.<span class="property">r</span> &lt; <span class="number">0</span> || b.<span class="property">x</span> - b.<span class="property">r</span> &gt; width || b.<span class="property">y</span> + b.<span class="property">r</span> &lt; <span class="number">0</span> || b.<span class="property">y</span> - b.<span class="property">r</span> &gt; height || b.<span class="property">r</span> &lt; <span class="number">0</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">        balls.<span class="title function_">splice</span>(i, <span class="number">1</span>);</span></span><br><span class="line"><span class="language-javascript">      &#125;</span></span><br><span class="line"><span class="language-javascript">    &#125;</span></span><br><span class="line"><span class="language-javascript">  &#125;</span></span><br><span class="line"><span class="language-javascript">&#125;</span></span><br><span class="line"><span class="language-javascript"><span class="title function_">clickEffect</span>();<span class="comment">//调用特效函数</span></span></span><br><span class="line"><span class="language-javascript"></span><span class="tag">&lt;/<span class="name">script</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">body</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">html</span>&gt;</span></span><br></pre></td></tr></table></figure><h2 id="二、鼠标点击爱心特效"><a href="#二、鼠标点击爱心特效" class="headerlink" title="二、鼠标点击爱心特效"></a>二、鼠标点击爱心特效</h2><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;!DOCTYPE <span class="keyword">html</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">html</span> <span class="attr">lang</span>=<span class="string">&quot;en&quot;</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">head</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">meta</span> <span class="attr">charset</span>=<span class="string">&quot;UTF-8&quot;</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">meta</span> <span class="attr">name</span>=<span class="string">&quot;viewport&quot;</span> <span class="attr">content</span>=<span class="string">&quot;width=device-width, initial-scale=1.0&quot;</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">title</span>&gt;</span>Document<span class="tag">&lt;/<span class="name">title</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">head</span>&gt;</span></span><br><span class="line"> </span><br><span class="line"><span class="tag">&lt;<span class="name">body</span>&gt;</span></span><br><span class="line">    <span class="comment">&lt;!-- 网页鼠标点击特效（爱心） --&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">script</span> <span class="attr">type</span>=<span class="string">&quot;text/javascript&quot;</span>&gt;</span><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">         ! <span class="keyword">function</span> (<span class="params">e, t, a</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">r</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">for</span> (<span class="keyword">var</span> e = <span class="number">0</span>; e &lt; s.<span class="property">length</span>; e++) s[e].<span class="property">alpha</span> &lt;= <span class="number">0</span> ? (t.<span class="property">body</span>.<span class="title function_">removeChild</span>(s[e].<span class="property">el</span>), s.<span class="title function_">splice</span>(e, <span class="number">1</span>)) : (s[</span></span><br><span class="line"><span class="language-javascript">                        e].<span class="property">y</span>--, s[e].<span class="property">scale</span> += <span class="number">.004</span>, s[e].<span class="property">alpha</span> -= <span class="number">.013</span>, s[e].<span class="property">el</span>.<span class="property">style</span>.<span class="property">cssText</span> = <span class="string">&quot;left:&quot;</span> + s[e].<span class="property">x</span> +</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;px;top:&quot;</span> + s[e].<span class="property">y</span> + <span class="string">&quot;px;opacity:&quot;</span> + s[e].<span class="property">alpha</span> + <span class="string">&quot;;transform:scale(&quot;</span> + s[e].<span class="property">scale</span> + <span class="string">&quot;,&quot;</span> + s[e]</span></span><br><span class="line"><span class="language-javascript">                    .<span class="property">scale</span> + <span class="string">&quot;) rotate(45deg);background:&quot;</span> + s[e].<span class="property">color</span> + <span class="string">&quot;;z-index:99999&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">requestAnimationFrame</span>(r)</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">n</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> t = <span class="string">&quot;function&quot;</span> == <span class="keyword">typeof</span> e.<span class="property">onclick</span> &amp;&amp; e.<span class="property">onclick</span>;</span></span><br><span class="line"><span class="language-javascript">                e.<span class="property">onclick</span> = <span class="keyword">function</span> (<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                    t &amp;&amp; <span class="title function_">t</span>(), <span class="title function_">o</span>(e)</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">o</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> a = t.<span class="title function_">createElement</span>(<span class="string">&quot;div&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">                a.<span class="property">className</span> = <span class="string">&quot;heart&quot;</span>, s.<span class="title function_">push</span>(&#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">el</span>: a,</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">x</span>: e.<span class="property">clientX</span> - <span class="number">5</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">y</span>: e.<span class="property">clientY</span> - <span class="number">5</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">scale</span>: <span class="number">1</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">alpha</span>: <span class="number">1</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="attr">color</span>: <span class="title function_">c</span>()</span></span><br><span class="line"><span class="language-javascript">                &#125;), t.<span class="property">body</span>.<span class="title function_">appendChild</span>(a)</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">i</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> a = t.<span class="title function_">createElement</span>(<span class="string">&quot;style&quot;</span>);</span></span><br><span class="line"><span class="language-javascript">                a.<span class="property">type</span> = <span class="string">&quot;text/css&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">try</span> &#123;</span></span><br><span class="line"><span class="language-javascript">                    a.<span class="title function_">appendChild</span>(t.<span class="title function_">createTextNode</span>(e))</span></span><br><span class="line"><span class="language-javascript">                &#125; <span class="keyword">catch</span> (t) &#123;</span></span><br><span class="line"><span class="language-javascript">                    a.<span class="property">styleSheet</span>.<span class="property">cssText</span> = e</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript">                t.<span class="title function_">getElementsByTagName</span>(<span class="string">&quot;head&quot;</span>)[<span class="number">0</span>].<span class="title function_">appendChild</span>(a)</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">c</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">return</span> <span class="string">&quot;rgb(&quot;</span> + ~~(<span class="number">255</span> * <span class="title class_">Math</span>.<span class="title function_">random</span>()) + <span class="string">&quot;,&quot;</span> + ~~(<span class="number">255</span> * <span class="title class_">Math</span>.<span class="title function_">random</span>()) + <span class="string">&quot;,&quot;</span> + ~~(<span class="number">255</span> * <span class="title class_">Math</span></span></span><br><span class="line"><span class="language-javascript">                    .<span class="title function_">random</span>()) + <span class="string">&quot;)&quot;</span></span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> s = [];</span></span><br><span class="line"><span class="language-javascript">            e.<span class="property">requestAnimationFrame</span> = e.<span class="property">requestAnimationFrame</span> || e.<span class="property">webkitRequestAnimationFrame</span> || e</span></span><br><span class="line"><span class="language-javascript">                .<span class="property">mozRequestAnimationFrame</span> || e.<span class="property">oRequestAnimationFrame</span> || e.<span class="property">msRequestAnimationFrame</span> || <span class="keyword">function</span> (<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="built_in">setTimeout</span>(e, <span class="number">1e3</span> / <span class="number">60</span>)</span></span><br><span class="line"><span class="language-javascript">                &#125;, <span class="title function_">i</span>(</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;.heart&#123;width: 10px;height: 10px;position: fixed;background: #f00;transform: rotate(45deg);-webkit-transform: rotate(45deg);-moz-transform: rotate(45deg);&#125;.heart:after,.heart:before&#123;content: &#x27;&#x27;;width: inherit;height: inherit;background: inherit;border-radius: 50%;-webkit-border-radius: 50%;-moz-border-radius: 50%;position: fixed;&#125;.heart:after&#123;top: -5px;&#125;.heart:before&#123;left: -5px;&#125;&quot;</span></span></span><br><span class="line"><span class="language-javascript">                ), <span class="title function_">n</span>(), <span class="title function_">r</span>()</span></span><br><span class="line"><span class="language-javascript">        &#125;(<span class="variable language_">window</span>, <span class="variable language_">document</span>);</span></span><br><span class="line"><span class="language-javascript">    </span><span class="tag">&lt;/<span class="name">script</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">body</span>&gt;</span></span><br><span class="line"> </span><br><span class="line"><span class="tag">&lt;/<span class="name">html</span>&gt;</span></span><br></pre></td></tr></table></figure><h2 id="三、鼠标点击文字特效"><a href="#三、鼠标点击文字特效" class="headerlink" title="三、鼠标点击文字特效"></a>三、鼠标点击文字特效</h2><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;!DOCTYPE <span class="keyword">html</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">html</span> <span class="attr">lang</span>=<span class="string">&quot;en&quot;</span>&gt;</span></span><br><span class="line"> </span><br><span class="line"><span class="tag">&lt;<span class="name">head</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">meta</span> <span class="attr">charset</span>=<span class="string">&quot;UTF-8&quot;</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">title</span>&gt;</span>Document<span class="tag">&lt;/<span class="name">title</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">head</span>&gt;</span></span><br><span class="line"> </span><br><span class="line"><span class="tag">&lt;<span class="name">body</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">script</span>&gt;</span><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">        (<span class="keyword">function</span> (<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> a_idx = <span class="number">0</span>;</span></span><br><span class="line"><span class="language-javascript">            <span class="variable language_">window</span>.<span class="property">onclick</span> = <span class="keyword">function</span> (<span class="params">event</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> a = <span class="keyword">new</span> <span class="title class_">Array</span>(<span class="string">&quot;❤富强❤&quot;</span>, <span class="string">&quot;❤民主❤&quot;</span>, <span class="string">&quot;❤文明❤&quot;</span>, <span class="string">&quot;❤和谐❤&quot;</span>, <span class="string">&quot;❤自由❤&quot;</span>, <span class="string">&quot;❤平等❤&quot;</span>, <span class="string">&quot;❤公正❤&quot;</span>, <span class="string">&quot;❤法治❤&quot;</span>, <span class="string">&quot;❤爱国❤&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;❤敬业❤&quot;</span>, <span class="string">&quot;❤诚信❤&quot;</span>, <span class="string">&quot;❤友善❤&quot;</span>);</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> heart = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&quot;b&quot;</span>); <span class="comment">//创建b元素</span></span></span><br><span class="line"><span class="language-javascript">                heart.<span class="property">onselectstart</span> = <span class="keyword">new</span> <span class="title class_">Function</span>(<span class="string">&#x27;event.returnValue=false&#x27;</span>); <span class="comment">//防止拖动</span></span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">document</span>.<span class="property">body</span>.<span class="title function_">appendChild</span>(heart).<span class="property">innerHTML</span> = a[a_idx]; <span class="comment">//将b元素添加到页面上</span></span></span><br><span class="line"><span class="language-javascript">                a_idx = (a_idx + <span class="number">1</span>) % a.<span class="property">length</span>;</span></span><br><span class="line"><span class="language-javascript">                heart.<span class="property">style</span>.<span class="property">cssText</span> = <span class="string">&quot;position: fixed;left:-100%;&quot;</span>; <span class="comment">//给p元素设置样式</span></span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> f = <span class="number">16</span>, <span class="comment">// 字体大小</span></span></span><br><span class="line"><span class="language-javascript">                    x = event.<span class="property">clientX</span> - f / <span class="number">2</span>, <span class="comment">// 横坐标</span></span></span><br><span class="line"><span class="language-javascript">                    y = event.<span class="property">clientY</span> - f, <span class="comment">// 纵坐标</span></span></span><br><span class="line"><span class="language-javascript">                    c = <span class="title function_">randomColor</span>(), <span class="comment">// 随机颜色</span></span></span><br><span class="line"><span class="language-javascript">                    a = <span class="number">1</span>, <span class="comment">// 透明度</span></span></span><br><span class="line"><span class="language-javascript">                    s = <span class="number">1.2</span>; <span class="comment">// 放大缩小</span></span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> timer = <span class="built_in">setInterval</span>(<span class="keyword">function</span> (<span class="params"></span>) &#123; <span class="comment">//添加定时器</span></span></span><br><span class="line"><span class="language-javascript">                    <span class="keyword">if</span> (a &lt;= <span class="number">0</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                        <span class="variable language_">document</span>.<span class="property">body</span>.<span class="title function_">removeChild</span>(heart);</span></span><br><span class="line"><span class="language-javascript">                        <span class="built_in">clearInterval</span>(timer);</span></span><br><span class="line"><span class="language-javascript">                    &#125; <span class="keyword">else</span> &#123;</span></span><br><span class="line"><span class="language-javascript">                        heart.<span class="property">style</span>.<span class="property">cssText</span> = <span class="string">&quot;font-size:16px;cursor: default;position: fixed;color:&quot;</span> +</span></span><br><span class="line"><span class="language-javascript">                            c + <span class="string">&quot;;left:&quot;</span> + x + <span class="string">&quot;px;top:&quot;</span> + y + <span class="string">&quot;px;opacity:&quot;</span> + a + <span class="string">&quot;;transform:scale(&quot;</span> +</span></span><br><span class="line"><span class="language-javascript">                            s + <span class="string">&quot;);&quot;</span>;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                        y--;</span></span><br><span class="line"><span class="language-javascript">                        a -= <span class="number">0.016</span>;</span></span><br><span class="line"><span class="language-javascript">                        s += <span class="number">0.002</span>;</span></span><br><span class="line"><span class="language-javascript">                    &#125;</span></span><br><span class="line"><span class="language-javascript">                &#125;, <span class="number">15</span>)</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript">            <span class="comment">// 随机颜色</span></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">randomColor</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">return</span> <span class="string">&quot;rgb(&quot;</span> + (~~(<span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">255</span>)) + <span class="string">&quot;,&quot;</span> + (~~(<span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">255</span>)) + <span class="string">&quot;,&quot;</span> + (~~(<span class="title class_">Math</span></span></span><br><span class="line"><span class="language-javascript">                .<span class="title function_">random</span>() * <span class="number">255</span>)) + <span class="string">&quot;)&quot;</span>;</span></span><br><span class="line"><span class="language-javascript"> </span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript">        &#125;());</span></span><br><span class="line"><span class="language-javascript">    </span><span class="tag">&lt;/<span class="name">script</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">body</span>&gt;</span></span><br><span class="line"> </span><br><span class="line"><span class="tag">&lt;/<span class="name">html</span>&gt;</span></span><br></pre></td></tr></table></figure><h2 id="四、鼠标星星拖尾特效"><a href="#四、鼠标星星拖尾特效" class="headerlink" title="四、鼠标星星拖尾特效"></a>四、鼠标星星拖尾特效</h2><blockquote><p>鸣谢：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://blog.csdn.net/weixin_44461275/article/details/131402453">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://blog.csdn.net/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://blog.csdn.net/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">鼠标星星拖尾特效</div>            <div class="tag-link-sitename">CSDN文章</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></p></blockquote><h3 id="JS"><a href="#JS" class="headerlink" title="JS"></a>JS</h3><figure class="highlight js"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br><span class="line">140</span><br><span class="line">141</span><br><span class="line">142</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">function</span> <span class="title function_">drawStar</span>(<span class="params"></span>) &#123;</span><br><span class="line">  <span class="comment">//定义数组，arr存放每个小星星的信息，colour为颜色数组，存几个好看的颜色</span></span><br><span class="line">  <span class="keyword">var</span> arr = [];</span><br><span class="line">  <span class="keyword">var</span> colours = [<span class="string">&quot;#ffff00&quot;</span>, <span class="string">&quot;#66ffff&quot;</span>, <span class="string">&quot;#3399ff&quot;</span>, <span class="string">&quot;#99ff00&quot;</span>, <span class="string">&quot;#ff9900&quot;</span>];</span><br><span class="line">  <span class="keyword">var</span> timeoutList = []; <span class="comment">// 计时器列表-用于后续清理计时器</span></span><br><span class="line"></span><br><span class="line">  <span class="comment">// 创建画布</span></span><br><span class="line">  <span class="keyword">const</span> canvas = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&#x27;canvas&#x27;</span>)</span><br><span class="line">  <span class="variable language_">document</span>.<span class="property">body</span>.<span class="title function_">appendChild</span>(canvas)</span><br><span class="line">  <span class="keyword">var</span> ctx = canvas.<span class="title function_">getContext</span>(<span class="string">&quot;2d&quot;</span>);</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 让画布自适应窗口大小，这个复制即可</span></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">resizeCanvas</span>(<span class="params"></span>) &#123;</span><br><span class="line">    canvas.<span class="property">width</span> = <span class="variable language_">window</span>.<span class="property">innerWidth</span>;</span><br><span class="line">    canvas.<span class="property">height</span> = <span class="variable language_">window</span>.<span class="property">innerHeight</span>;</span><br><span class="line">  &#125;</span><br><span class="line">  <span class="title function_">resizeCanvas</span>();</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 给画布css样式，固定定位，且阻止用户的鼠标事件</span></span><br><span class="line">  canvas.<span class="property">style</span>.<span class="property">cssText</span> = <span class="string">`</span></span><br><span class="line"><span class="string">    position: fixed;</span></span><br><span class="line"><span class="string">    z-index: 1000;</span></span><br><span class="line"><span class="string">    top: 0;</span></span><br><span class="line"><span class="string">    left: 0;</span></span><br><span class="line"><span class="string">    pointer-events: none;</span></span><br><span class="line"><span class="string">  `</span>;</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 封装绘制一个五角星函数</span></span><br><span class="line">  <span class="comment">// x是圆心横坐标，y是圆心纵坐标，其实就是鼠标位置（x ，y）</span></span><br><span class="line">  <span class="comment">// r是里面小圆半径 ，l是大圆半径</span></span><br><span class="line">  <span class="comment">// rot是初始旋转角度</span></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">star</span>(<span class="params">x, y, r, l, rot</span>) &#123;</span><br><span class="line">    ctx.<span class="title function_">beginPath</span>();</span><br><span class="line">    <span class="comment">// 循环5次，因为5个点</span></span><br><span class="line">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; <span class="number">5</span>; i++) &#123;</span><br><span class="line">      <span class="comment">//先绘制小圆上一个点</span></span><br><span class="line">      ctx.<span class="title function_">lineTo</span>(</span><br><span class="line">        <span class="title class_">Math</span>.<span class="title function_">cos</span>(((<span class="number">18</span> + i * <span class="number">72</span> - rot) * <span class="title class_">Math</span>.<span class="property">PI</span>) / <span class="number">180</span>) * r + x,</span><br><span class="line">        -<span class="title class_">Math</span>.<span class="title function_">sin</span>(((<span class="number">18</span> + i * <span class="number">72</span> - rot) * <span class="title class_">Math</span>.<span class="property">PI</span>) / <span class="number">180</span>) * r + y</span><br><span class="line">      );</span><br><span class="line">      <span class="comment">//连线到大圆上一个点</span></span><br><span class="line">      ctx.<span class="title function_">lineTo</span>(</span><br><span class="line">        <span class="title class_">Math</span>.<span class="title function_">cos</span>(((<span class="number">54</span> + i * <span class="number">72</span> - rot) * <span class="title class_">Math</span>.<span class="property">PI</span>) / <span class="number">180</span>) * l + x,</span><br><span class="line">        -<span class="title class_">Math</span>.<span class="title function_">sin</span>(((<span class="number">54</span> + i * <span class="number">72</span> - rot) * <span class="title class_">Math</span>.<span class="property">PI</span>) / <span class="number">180</span>) * l + y</span><br><span class="line">      );</span><br><span class="line">    &#125;</span><br><span class="line">    ctx.<span class="title function_">closePath</span>();</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 绘制一堆星星</span></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">draw</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="comment">//循环数组</span></span><br><span class="line">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; arr.<span class="property">length</span>; i++) &#123;</span><br><span class="line">      <span class="keyword">let</span> temp = arr[i];</span><br><span class="line">      <span class="comment">//调用绘制一个星星函数</span></span><br><span class="line">      <span class="title function_">star</span>(temp.<span class="property">x</span>, temp.<span class="property">y</span>, temp.<span class="property">r</span>, temp.<span class="property">r</span> * <span class="number">3</span>, temp.<span class="property">rot</span>);</span><br><span class="line">      <span class="comment">//星星颜色</span></span><br><span class="line">      ctx.<span class="property">fillStyle</span> = temp.<span class="property">color</span>;</span><br><span class="line">      <span class="comment">//星星边框颜色</span></span><br><span class="line">      ctx.<span class="property">strokeStyle</span> = temp.<span class="property">color</span>;</span><br><span class="line">      <span class="comment">//线宽度</span></span><br><span class="line">      ctx.<span class="property">lineWidth</span> = <span class="number">0.1</span>;</span><br><span class="line">      <span class="comment">//角有弧度</span></span><br><span class="line">      ctx.<span class="property">lineJoin</span> = <span class="string">&quot;round&quot;</span>;</span><br><span class="line">      <span class="comment">// 填充</span></span><br><span class="line">      ctx.<span class="title function_">fill</span>();</span><br><span class="line">      <span class="comment">// 绘制路径</span></span><br><span class="line">      ctx.<span class="title function_">stroke</span>();</span><br><span class="line">    &#125;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="comment">//更新动画</span></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">update</span>(<span class="params"></span>) &#123;</span><br><span class="line">    <span class="comment">//循环数组</span></span><br><span class="line">    <span class="keyword">for</span> (<span class="keyword">let</span> i = <span class="number">0</span>; i &lt; arr.<span class="property">length</span>; i++) &#123;</span><br><span class="line">      <span class="comment">// x坐标+dx移动距离</span></span><br><span class="line">      arr[i].<span class="property">x</span> += arr[i].<span class="property">dx</span>;</span><br><span class="line">      <span class="comment">// y坐标+dy移动距离</span></span><br><span class="line">      arr[i].<span class="property">y</span> += arr[i].<span class="property">dy</span>;</span><br><span class="line">      <span class="comment">// 加上旋转角度</span></span><br><span class="line">      arr[i].<span class="property">rot</span> += arr[i].<span class="property">td</span>;</span><br><span class="line">      <span class="comment">// 半径慢慢减小</span></span><br><span class="line">      arr[i].<span class="property">r</span> -= <span class="number">0.015</span>;</span><br><span class="line">      <span class="comment">// 当半径小于0时</span></span><br><span class="line">      <span class="keyword">if</span> (arr[i].<span class="property">r</span> &lt; <span class="number">0</span>) &#123;</span><br><span class="line">        <span class="comment">//删除该星星</span></span><br><span class="line">        arr.<span class="title function_">splice</span>(i, <span class="number">1</span>);</span><br><span class="line">      &#125;</span><br><span class="line">    &#125;</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 添加当前位置星星数据</span></span><br><span class="line">  <span class="keyword">function</span> <span class="title function_">addStarts</span>(<span class="params">e</span>) &#123;</span><br><span class="line">    <span class="comment">// 每移动触发一次事件给arr数组添加一个星星</span></span><br><span class="line">    arr.<span class="title function_">push</span>(&#123;</span><br><span class="line">      <span class="comment">// x是初始横坐标</span></span><br><span class="line">      <span class="attr">x</span>: e.<span class="property">clientX</span>,</span><br><span class="line">      <span class="comment">//y是初始纵坐标</span></span><br><span class="line">      <span class="attr">y</span>: e.<span class="property">clientY</span>,</span><br><span class="line">      <span class="comment">//r是星星里面那个小圆半径，哪来的小圆等会说</span></span><br><span class="line">      <span class="attr">r</span>: <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">0.5</span> + <span class="number">1.5</span>,</span><br><span class="line">      <span class="comment">//运动时旋转的角度</span></span><br><span class="line">      <span class="attr">td</span>: <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">4</span> - <span class="number">2</span>,</span><br><span class="line">      <span class="comment">// X轴移动距离</span></span><br><span class="line">      <span class="attr">dx</span>: <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">2</span> - <span class="number">1</span>,</span><br><span class="line">      <span class="comment">// y轴移动距离</span></span><br><span class="line">      <span class="attr">dy</span>: <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">1</span> + <span class="number">1</span>,</span><br><span class="line">      <span class="comment">// 初始的旋转角度</span></span><br><span class="line">      <span class="attr">rot</span>: <span class="title class_">Math</span>.<span class="title function_">random</span>() * <span class="number">90</span> + <span class="number">90</span>,</span><br><span class="line">      <span class="comment">// 颜色</span></span><br><span class="line">      <span class="attr">color</span>: colours[<span class="title class_">Math</span>.<span class="title function_">floor</span>(<span class="title class_">Math</span>.<span class="title function_">random</span>() * colours.<span class="property">length</span>)],</span><br><span class="line">    &#125;);</span><br><span class="line">  &#125;</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 监听屏幕变化事件</span></span><br><span class="line">  <span class="variable language_">window</span>.<span class="property">onresize</span> = resizeCanvas;</span><br><span class="line"></span><br><span class="line">  <span class="comment">// 监听鼠标移动事件</span></span><br><span class="line">  <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&quot;mousemove&quot;</span>, <span class="function">(<span class="params">e</span>) =&gt;</span> &#123;</span><br><span class="line">    <span class="comment">// 添加星星数据</span></span><br><span class="line">    <span class="title function_">addStarts</span>(e);</span><br><span class="line"></span><br><span class="line">    <span class="comment">//设置100毫秒内效果</span></span><br><span class="line">    <span class="keyword">for</span> (<span class="keyword">let</span> index = <span class="number">0</span>; index &lt; <span class="number">200</span>; index++) &#123;</span><br><span class="line">      <span class="keyword">if</span> (index === <span class="number">0</span> &amp;&amp; timeoutList.<span class="property">length</span> &gt; <span class="number">0</span>) &#123;</span><br><span class="line">        <span class="keyword">for</span> (<span class="keyword">const</span> timeoutName <span class="keyword">of</span> timeoutList) &#123;</span><br><span class="line">          <span class="built_in">clearTimeout</span>(timeoutName)</span><br><span class="line">        &#125;</span><br><span class="line">      &#125;</span><br><span class="line">      timeoutList[index] = <span class="built_in">setTimeout</span>(<span class="function">() =&gt;</span> &#123;</span><br><span class="line">        <span class="comment">//清屏</span></span><br><span class="line">        ctx.<span class="title function_">clearRect</span>(<span class="number">0</span>, <span class="number">0</span>, canvas.<span class="property">width</span>, canvas.<span class="property">height</span>);</span><br><span class="line">        <span class="comment">//绘制</span></span><br><span class="line">        <span class="title function_">draw</span>();</span><br><span class="line">        <span class="comment">//更新</span></span><br><span class="line">        <span class="title function_">update</span>();</span><br><span class="line">      &#125;, index * <span class="number">20</span>);</span><br><span class="line">    &#125;</span><br><span class="line">  &#125;);</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line"><span class="title function_">drawStar</span>()</span><br></pre></td></tr></table></figure><h3 id="HTML"><a href="#HTML" class="headerlink" title="HTML"></a>HTML</h3><figure class="highlight html"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br><span class="line">107</span><br><span class="line">108</span><br><span class="line">109</span><br><span class="line">110</span><br><span class="line">111</span><br><span class="line">112</span><br><span class="line">113</span><br><span class="line">114</span><br><span class="line">115</span><br><span class="line">116</span><br><span class="line">117</span><br><span class="line">118</span><br><span class="line">119</span><br><span class="line">120</span><br><span class="line">121</span><br><span class="line">122</span><br><span class="line">123</span><br><span class="line">124</span><br><span class="line">125</span><br><span class="line">126</span><br><span class="line">127</span><br><span class="line">128</span><br><span class="line">129</span><br><span class="line">130</span><br><span class="line">131</span><br><span class="line">132</span><br><span class="line">133</span><br><span class="line">134</span><br><span class="line">135</span><br><span class="line">136</span><br><span class="line">137</span><br><span class="line">138</span><br><span class="line">139</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">&lt;!DOCTYPE <span class="keyword">html</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;<span class="name">html</span> <span class="attr">lang</span>=<span class="string">&quot;en&quot;</span>&gt;</span></span><br><span class="line"></span><br><span class="line"><span class="tag">&lt;<span class="name">head</span>&gt;</span></span><br><span class="line">    </span><br><span class="line"><span class="tag">&lt;/<span class="name">head</span>&gt;</span></span><br><span class="line"></span><br><span class="line"><span class="tag">&lt;<span class="name">body</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">span</span> <span class="attr">class</span>=<span class="string">&quot;js-cursor-container&quot;</span>&gt;</span><span class="tag">&lt;/<span class="name">span</span>&gt;</span></span><br><span class="line">    <span class="tag">&lt;<span class="name">script</span>&gt;</span><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">        (<span class="keyword">function</span> <span class="title function_">fairyDustCursor</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> possibleColors = [<span class="string">&quot;#D61C59&quot;</span>, <span class="string">&quot;#E7D84B&quot;</span>, <span class="string">&quot;#1B8798&quot;</span>]</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> width = <span class="variable language_">window</span>.<span class="property">innerWidth</span>;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> height = <span class="variable language_">window</span>.<span class="property">innerHeight</span>;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> cursor = &#123; <span class="attr">x</span>: width / <span class="number">2</span>, <span class="attr">y</span>: width / <span class="number">2</span> &#125;;</span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">var</span> particles = [];</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">init</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">bindEvents</span>();</span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">loop</span>();</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="comment">// Bind events that are needed</span></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">bindEvents</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">document</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;mousemove&#x27;</span>, onMouseMove);</span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">window</span>.<span class="title function_">addEventListener</span>(<span class="string">&#x27;resize&#x27;</span>, onWindowResize);</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">onWindowResize</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                width = <span class="variable language_">window</span>.<span class="property">innerWidth</span>;</span></span><br><span class="line"><span class="language-javascript">                height = <span class="variable language_">window</span>.<span class="property">innerHeight</span>;</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">onMouseMove</span>(<span class="params">e</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                cursor.<span class="property">x</span> = e.<span class="property">clientX</span>;</span></span><br><span class="line"><span class="language-javascript">                cursor.<span class="property">y</span> = e.<span class="property">clientY</span>;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">addParticle</span>(cursor.<span class="property">x</span>, cursor.<span class="property">y</span>, possibleColors[<span class="title class_">Math</span>.<span class="title function_">floor</span>(<span class="title class_">Math</span>.<span class="title function_">random</span>() * possibleColors.<span class="property">length</span>)]);</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">addParticle</span>(<span class="params">x, y, color</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">var</span> particle = <span class="keyword">new</span> <span class="title class_">Particle</span>();</span></span><br><span class="line"><span class="language-javascript">                particle.<span class="title function_">init</span>(x, y, color);</span></span><br><span class="line"><span class="language-javascript">                particles.<span class="title function_">push</span>(particle);</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">updateParticles</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="comment">// Updated</span></span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">for</span> (<span class="keyword">var</span> i = <span class="number">0</span>; i &lt; particles.<span class="property">length</span>; i++) &#123;</span></span><br><span class="line"><span class="language-javascript">                    particles[i].<span class="title function_">update</span>();</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="comment">// Remove dead particles</span></span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">for</span> (<span class="keyword">var</span> i = particles.<span class="property">length</span> - <span class="number">1</span>; i &gt;= <span class="number">0</span>; i-) &#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="keyword">if</span> (particles[i].<span class="property">lifeSpan</span> &lt; <span class="number">0</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                        particles[i].<span class="title function_">die</span>();</span></span><br><span class="line"><span class="language-javascript">                        particles.<span class="title function_">splice</span>(i, <span class="number">1</span>);</span></span><br><span class="line"><span class="language-javascript">                    &#125;</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">loop</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">requestAnimationFrame</span>(loop);</span></span><br><span class="line"><span class="language-javascript">                <span class="title function_">updateParticles</span>();</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="comment">/**</span></span></span><br><span class="line"><span class="comment"><span class="language-javascript">             * Particles</span></span></span><br><span class="line"><span class="comment"><span class="language-javascript">             */</span></span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">Particle</span>(<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">character</span> = <span class="string">&quot;*&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">lifeSpan</span> = <span class="number">120</span>; <span class="comment">//ms</span></span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">initialStyles</span> = &#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;position&quot;</span>: <span class="string">&quot;fixed&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;display&quot;</span>: <span class="string">&quot;inline-block&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;top&quot;</span>: <span class="string">&quot;0px&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;left&quot;</span>: <span class="string">&quot;0px&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;pointerEvents&quot;</span>: <span class="string">&quot;none&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;touch-action&quot;</span>: <span class="string">&quot;none&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;z-index&quot;</span>: <span class="string">&quot;10000000&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;fontSize&quot;</span>: <span class="string">&quot;25px&quot;</span>,</span></span><br><span class="line"><span class="language-javascript">                    <span class="string">&quot;will-change&quot;</span>: <span class="string">&quot;transform&quot;</span></span></span><br><span class="line"><span class="language-javascript">                &#125;;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="comment">// Init, and set properties</span></span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">init</span> = <span class="keyword">function</span> (<span class="params">x, y, color</span>) &#123;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">velocity</span> = &#123;</span></span><br><span class="line"><span class="language-javascript">                        <span class="attr">x</span>: (<span class="title class_">Math</span>.<span class="title function_">random</span>() &lt; <span class="number">0.5</span> ? -<span class="number">1</span> : <span class="number">1</span>) * (<span class="title class_">Math</span>.<span class="title function_">random</span>() / <span class="number">2</span>),</span></span><br><span class="line"><span class="language-javascript">                        <span class="attr">y</span>: <span class="number">1</span></span></span><br><span class="line"><span class="language-javascript">                    &#125;;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">position</span> = &#123; <span class="attr">x</span>: x + <span class="number">10</span>, <span class="attr">y</span>: y + <span class="number">10</span> &#125;;</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">initialStyles</span>.<span class="property">color</span> = color;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">element</span> = <span class="variable language_">document</span>.<span class="title function_">createElement</span>(<span class="string">&#x27;span&#x27;</span>);</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">element</span>.<span class="property">innerHTML</span> = <span class="variable language_">this</span>.<span class="property">character</span>;</span></span><br><span class="line"><span class="language-javascript">                    <span class="title function_">applyProperties</span>(<span class="variable language_">this</span>.<span class="property">element</span>, <span class="variable language_">this</span>.<span class="property">initialStyles</span>);</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="title function_">update</span>();</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">document</span>.<span class="title function_">querySelector</span>(<span class="string">&#x27;.js-cursor-container&#x27;</span>).<span class="title function_">appendChild</span>(<span class="variable language_">this</span>.<span class="property">element</span>);</span></span><br><span class="line"><span class="language-javascript">                &#125;;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">update</span> = <span class="keyword">function</span> (<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">position</span>.<span class="property">x</span> += <span class="variable language_">this</span>.<span class="property">velocity</span>.<span class="property">x</span>;</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">position</span>.<span class="property">y</span> += <span class="variable language_">this</span>.<span class="property">velocity</span>.<span class="property">y</span>;</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">lifeSpan</span>-;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">element</span>.<span class="property">style</span>.<span class="property">transform</span> = <span class="string">&quot;translate3d(&quot;</span> + <span class="variable language_">this</span>.<span class="property">position</span>.<span class="property">x</span> + <span class="string">&quot;px,&quot;</span> + <span class="variable language_">this</span>.<span class="property">position</span>.<span class="property">y</span> + <span class="string">&quot;px, 0) scale(&quot;</span> + (<span class="variable language_">this</span>.<span class="property">lifeSpan</span> / <span class="number">120</span>) + <span class="string">&quot;)&quot;</span>;</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">                <span class="variable language_">this</span>.<span class="property">die</span> = <span class="keyword">function</span> (<span class="params"></span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                    <span class="variable language_">this</span>.<span class="property">element</span>.<span class="property">parentNode</span>.<span class="title function_">removeChild</span>(<span class="variable language_">this</span>.<span class="property">element</span>);</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="comment">/**</span></span></span><br><span class="line"><span class="comment"><span class="language-javascript">             * Utils</span></span></span><br><span class="line"><span class="comment"><span class="language-javascript">             */</span></span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="comment">// Applies css `properties` to an element.</span></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">function</span> <span class="title function_">applyProperties</span>(<span class="params">target, properties</span>) &#123;</span></span><br><span class="line"><span class="language-javascript">                <span class="keyword">for</span> (<span class="keyword">var</span> key <span class="keyword">in</span> properties) &#123;</span></span><br><span class="line"><span class="language-javascript">                    target.<span class="property">style</span>[key] = properties[key];</span></span><br><span class="line"><span class="language-javascript">                &#125;</span></span><br><span class="line"><span class="language-javascript">            &#125;</span></span><br><span class="line"><span class="language-javascript"></span></span><br><span class="line"><span class="language-javascript">            <span class="keyword">if</span> (!(<span class="string">&#x27;ontouchstart&#x27;</span> <span class="keyword">in</span> <span class="variable language_">window</span> || navigator.<span class="property">msMaxTouchPoints</span>)) <span class="title function_">init</span>();</span></span><br><span class="line"><span class="language-javascript">        &#125;)();    </span></span><br><span class="line"><span class="language-javascript">    </span><span class="tag">&lt;/<span class="name">script</span>&gt;</span></span><br><span class="line"><span class="tag">&lt;/<span class="name">body</span>&gt;</span></span><br><span class="line"></span><br><span class="line"><span class="tag">&lt;/<span class="name">html</span>&gt;</span></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E9%BC%A0%E6%A0%87%E7%89%B9%E6%95%88/">鼠标特效</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/12/13/d6c7ec05/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL内置数据库】 mysql</title>
      <link>https://blog.eucalyptus.cc/2024/09/25/bd20fbdf/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/25/bd20fbdf/</guid>
      <pubDate>Wed, 25 Sep 2024 02:30:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;p&gt;MySQL8.0.37&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;统计&quot;&gt;&lt;a href=&quot;#统计&quot; class=&quot;headerlink&quot; title=&quot;统计&quot;&gt;&lt;/a&gt;统计&lt;/h3&gt;&lt;p&gt;共 38</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><p>MySQL8.0.37</p></blockquote><h3 id="统计"><a href="#统计" class="headerlink" title="统计"></a>统计</h3><p>共 38 张表</p><table><thead><tr><th>序号</th><th>表名</th><th>描述</th></tr></thead><tbody><tr><td>1</td><td>columns_priv</td><td>存储列级别的权限信息</td></tr><tr><td>2</td><td>component</td><td>存储服务器组件信息</td></tr><tr><td>3</td><td>db</td><td>存储数据库级别的权限信息</td></tr><tr><td>4</td><td>default_roles</td><td>存储用户默认角色信息</td></tr><tr><td>5</td><td>engine_cost</td><td>存储存储引擎成本常数</td></tr><tr><td>6</td><td>func</td><td>存储用户定义函数</td></tr><tr><td>7</td><td>general_log</td><td>存储一般查询日志</td></tr><tr><td>8</td><td>global_grants</td><td>存储动态全局权限</td></tr><tr><td>9</td><td>gtid_executed</td><td>存储GTID执行信息</td></tr><tr><td>10</td><td>help_category</td><td>存储帮助类别</td></tr><tr><td>11</td><td>help_keyword</td><td>存储帮助关键字</td></tr><tr><td>12</td><td>help_relation</td><td>存储帮助主题与关键字的关系</td></tr><tr><td>13</td><td>help_topic</td><td>存储帮助主题详细信息</td></tr><tr><td>14</td><td>innodb_index_stats</td><td>存储InnoDB索引统计信息</td></tr><tr><td>15</td><td>innodb_table_stats</td><td>存储InnoDB表统计信息</td></tr><tr><td>16</td><td>ndb_binlog_index</td><td>存储NDB Cluster二进制日志索引</td></tr><tr><td>17</td><td>password_history</td><td>存储密码历史记录</td></tr><tr><td>18</td><td>plugin</td><td>存储服务器插件信息</td></tr><tr><td>19</td><td>procs_priv</td><td>存储存储过程和函数的权限</td></tr><tr><td>20</td><td>proxies_priv</td><td>存储代理用户权限</td></tr><tr><td>21</td><td>replication_asynchronous_connection_failover</td><td>存储异步连接故障转移配置</td></tr><tr><td>22</td><td>replication_asynchronous_connection_failover_managed</td><td>存储托管异步连接故障转移配置</td></tr><tr><td>23</td><td>replication_group_configuration_version</td><td>存储复制组配置版本信息</td></tr><tr><td>24</td><td>replication_group_member_actions</td><td>配置和管理组复制成员动作</td></tr><tr><td>25</td><td>role_edges</td><td>存储角色之间的关系</td></tr><tr><td>26</td><td>server_cost</td><td>存储服务器操作优化器成本估算</td></tr><tr><td>27</td><td>servers</td><td>存储FEDERATED引擎服务器定义</td></tr><tr><td>28</td><td>slave_master_info</td><td>存储从库的主库连接信息</td></tr><tr><td>29</td><td>slave_relay_log_info</td><td>记录从库SQL线程的位置信息</td></tr><tr><td>30</td><td>slave_worker_info</td><td>记录从库并行复制工作线程信息</td></tr><tr><td>31</td><td>slow_log</td><td>存储慢查询日志</td></tr><tr><td>32</td><td>tables_priv</td><td>存储表级别权限</td></tr><tr><td>33</td><td>time_zone</td><td>存储时区信息</td></tr><tr><td>34</td><td>time_zone_leap_second</td><td>存储闰秒数据</td></tr><tr><td>35</td><td>time_zone_name</td><td>存储时区名称与ID映射</td></tr><tr><td>36</td><td>time_zone_transition</td><td>存储时区转换信息</td></tr><tr><td>37</td><td>time_zone_transition_type</td><td>存储时区转换类型</td></tr><tr><td>38</td><td>user</td><td>存储用户账号信息和权限</td></tr></tbody></table><h3 id="columns-priv"><a href="#columns-priv" class="headerlink" title="columns_priv"></a>columns_priv</h3><p><code>columns_priv</code> 表是 MySQL 的系统表之一,位于 <code>mysql</code> 数据库中,用于存储列级别的权限信息。这意味着它可以控制用户对特定表中特定列的访问权限。以下是 <code>columns_priv</code> 表的一些关键字段及其描述:</p><ul><li><strong>Host</strong>: 记录用户从哪个主机进行连接,通常是一个 IP 地址或者域名。</li><li><strong>Db</strong>: 数据库的名称。</li><li><strong>User</strong>: 用户名。</li><li><strong>Table_name</strong>: 表的名称。</li><li><strong>Column_name</strong>: 列的名称。</li><li><strong>Timestamp</strong>: 记录权限被授权或更改的时间戳。</li><li><strong>Column_priv</strong>: 列权限集合,包括但不限于 <code>SELECT</code>、<code>INSERT</code>、<code>UPDATE</code> 和 <code>REFERENCES</code> 权限。</li></ul><p>例如,如果你想要授予用户 <code>username</code> 对数据库 <code>database_name</code> 中的 <code>table_name</code> 表的 <code>column_name</code> 列的 <code>SELECT</code> 权限,你可以使用以下 SQL 命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span> (column_name) <span class="keyword">ON</span> database_name.table_name <span class="keyword">TO</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;host&#x27;</span>;</span><br></pre></td></tr></table></figure><p>反之,如果你想要撤销这个权限,可以使用 <code>REVOKE</code> 命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">REVOKE</span> <span class="keyword">SELECT</span> (column_name) <span class="keyword">ON</span> database_name.table_name <span class="keyword">FROM</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;host&#x27;</span>;</span><br></pre></td></tr></table></figure><p><code>columns_priv</code> 表通常与 <code>db</code> 表和 <code>tables_priv</code> 表一起使用,以实现更细粒度的权限控制。<code>db</code> 表控制数据库级别的权限,而 <code>tables_priv</code> 表控制表级别的权限。当使用 <code>REVOKE</code> 命令时,必须指定与被授权列相同的列名,这是因为列级别的权限是针对单个列的 。</p><p>要查看 <code>columns_priv</code> 表的内容,你可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.columns_priv <span class="keyword">WHERE</span> Db <span class="string">&#x27;database_name&#x27;</span> <span class="keyword">AND</span> Table_name <span class="string">&#x27;table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回指定数据库和表的所有列权限信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img1.avif"></p><h3 id="component"><a href="#component" class="headerlink" title="component"></a>component</h3><p>在MySQL数据库中, component 一词通常指的是服务器的组件化架构,这是MySQL 8.0版本引入的一个新特性。这种架构允许通过安装和卸载组件来扩展服务器的功能。每个组件都提供服务器和其他组件可以使用的服务。组件之间仅通过它们提供的服务进行交互。</p><p>组件可以用于多种用途,例如配置错误日志记录、密码验证、提供安全存储敏感信息的密钥环、将应用程序的消息事件添加到审计日志、实现用于访问查询属性的可加载函数等。</p><p>要获取有关当前加载的组件的信息,可以查询<code>mysql.component</code>系统表。例如,以下SQL语句可以列出所有已加载的组件:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.component;</span><br></pre></td></tr></table></figure><p>此外,组件的安装和卸载可以通过<code>INSTALL COMPONENT</code>和<code>UNINSTALL COMPONENT</code>语句来完成。例如,要安装一个密码验证组件,可以使用以下命令:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">INSTALL COMPONENT &#x27;file://component_validate_password&#x27;;</span><br></pre></td></tr></table></figure><p>要卸载该组件,可以使用:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">UNINSTALL COMPONENT &#x27;file://component_validate_password&#x27;;</span><br></pre></td></tr></table></figure><p>组件的引入为MySQL数据库提供了更高的灵活性和扩展性,使得用户可以根据自己的需要来定制数据库服务器的功能。</p><ul><li><code>component_id</code> 是该组件的唯一标识符。</li><li><code>component_group_id</code> 可能表示该组件所属的组或类别。</li><li><code>component_urn</code> 是一个统一资源名称 Uniform Resource Name ,通常用于标识资源的位置,这里是一个文件路径,可能指向一个用于验证密码的组件或服务。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img2.avif"></p><h3 id="db"><a href="#db" class="headerlink" title="db"></a>db</h3><p>在 MySQL 中,<code>db</code> 表是 <code>mysql</code> 数据库中的一个系统表,它存储了数据库级别的权限信息。这个表允许你查看和管理系统级别的权限,这些权限决定了哪些用户可以从哪些主机访问哪些数据库。</p><p>以下是 <code>db</code> 表中的一些关键列:</p><ul><li><strong>Host</strong>: 指定允许连接的主机名或 IP 地址。使用通配符 如 <code>%</code> 可以表示任意主机。</li><li><strong>Db</strong>: 数据库的名称,如果数据库名是 <code>%</code>,则表示该权限适用于所有数据库。</li><li><strong>User</strong>: 用户名,与 <code>Host</code> 列结合使用,以确定特定主机上的特定用户。</li><li><strong>Select_priv</strong>: 是否允许用户执行 <code>SELECT</code> 语句。</li><li><strong>Insert_priv</strong>: 是否允许用户执行 <code>INSERT</code> 语句。</li><li><strong>Update_priv</strong>: 是否允许用户执行 <code>UPDATE</code> 语句。</li><li><strong>Delete_priv</strong>: 是否允许用户执行 <code>DELETE</code> 语句。</li><li><strong>Create_priv</strong>: 是否允许用户创建新的数据库和表。</li><li><strong>Drop_priv</strong>: 是否允许用户删除数据库和表。</li><li><strong>Grant_priv</strong>: 是否允许用户授予或撤销权限。</li><li><strong>References_priv</strong>: 是否允许用户创建外键。</li><li><strong>Index_priv</strong>: 是否允许用户创建或删除索引。</li><li><strong>Alter_priv</strong>: 是否允许用户修改表结构。</li><li><strong>Create_tmp_table_priv</strong>: 是否允许用户创建临时表。</li><li><strong>Lock_tables_priv</strong>: 是否允许用户锁定表。</li><li><strong>Create_view_priv</strong>: 是否允许用户创建视图。</li><li><strong>Show_view_priv</strong>: 是否允许用户查看视图的定义。</li><li><strong>Create_routine_priv</strong>: 是否允许用户创建存储过程和函数。</li><li><strong>Alter_routine_priv</strong>: 是否允许用户修改存储过程和函数。</li><li><strong>Execute_priv</strong>: 是否允许用户执行存储过程和函数。</li></ul><p>这些权限可以单独设置,以提供精细的访问控制。例如,你可以允许某个用户从特定主机访问特定数据库,但不允许他们创建或删除表。</p><p>要查看 <code>db</code> 表中的权限信息,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.db <span class="keyword">WHERE</span> Db <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 替换为你想要查询的数据库名称。这将返回指定数据库的权限信息。</p><p><code>db</code> 表是 MySQL 权限系统的核心组成部分,它与 <code>user</code> 表 全局权限 和 <code>tables_priv</code> 表 表级权限 一起使用,为 MySQL 数据库提供强大的访问控制机制。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img3.avif"></p><h3 id="default-roles"><a href="#default-roles" class="headerlink" title="default_roles"></a>default_roles</h3><p><code>default_roles</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它用于存储用户账户的默认角色信息。在 MySQL 8.0 及更高版本中,角色 Role 是权限的集合,可以授予用户以简化权限管理。默认角色是在用户</p><p>以下是 <code>default_roles</code> 表中的一些关键列:</p><ul><li><strong>Host</strong>: 用户账户的主机部分。</li><li><strong>User</strong>: 用户账户的用户名。</li><li><strong>Default_role</strong>: 用户的默认角色名称,可以在<br>默认角色的概念是在 MySQL 8.0 中引入的,它允许管理员为用户设置一组默认激活的角色,这样在用户</li></ul><p>要设置用户的默认角色,可以使用 <code>SET DEFAULT ROLE</code> 语句,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">DEFAULT</span> ROLE <span class="string">&#x27;role_name&#x27;</span> <span class="keyword">FOR</span> <span class="string">&#x27;user_name&#x27;</span> <span class="string">&#x27;host_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>或者在创建用户或修改用户时使用 <code>ALTER USER</code> 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER</span> <span class="keyword">USER</span> <span class="string">&#x27;user_name&#x27;</span> <span class="string">&#x27;host_name&#x27;</span> <span class="keyword">DEFAULT</span> ROLE <span class="string">&#x27;role_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>用户</p><p>需要注意的是,<code>default_roles</code> 表通常由 MySQL 服务器内部维护,不建议直接修改这个表,而是应该使用 MySQL 提供的账户管理语句来管理角色和权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img4.avif"></p><h3 id="engine-cost"><a href="#engine-cost" class="headerlink" title="engine_cost"></a>engine_cost</h3><p>在 MySQL 中,<code>engine_cost</code> 表是 <code>mysql</code> 系统数据库的一部分,它用于存储与特定存储引擎相关的成本常数。这些成本常数代表了不同存储引擎操作的成本,优化器在生成执行计划时会使用这些成本来决定最佳的执行策略。</p><p>以下是 <code>engine_cost</code> 表中可能包含的一些关键列:</p><ul><li><strong>engine_name</strong>: 存储引擎的名称,如 <code>InnoDB</code>。如果值为 <code>default</code>,则表示该成本适用于所有没有特定条目的存储引擎。</li><li><strong>device_type</strong>: 表示存储设备的类型,目前这个字段的值通常是 0,因为 MySQL 尚未区分不同类型的存储设备 如 HDD 和 SSD 的成本。</li><li><strong>cost_name</strong>: 成本常数的名称,如 <code>io_block_read_cost</code>。</li><li><strong>cost_value</strong>: 成本常数的值。如果这个字段的值为 <code>NULL</code>,则表示优化器将使用默认的成本值。</li><li><strong>last_update</strong>: 最后一次更新成本常数的时间。</li><li><strong>comment</strong>: 对该成本常数的描述或注释。</li></ul><p><code>engine_cost</code> 表中存储的成本常数包括但不限于:</p><ul><li><strong>io_block_read_cost</strong>: 从磁盘读取一个块的成本。</li><li><strong>memory_block_read_cost</strong>: 从内存读取一个块的成本。</li></ul><p>管理员可以通过更新 <code>engine_cost</code> 表中的 <code>cost_value</code> 来调整成本常数,以影响优化器的决策。例如,增加 <code>io_block_read_cost</code> 的值可能会使优化器更倾向于使用索引而不是执行全表扫描。</p><p>要使对 <code>engine_cost</code> 表的更改生效,需要执行 <code>FLUSH OPTIMIZER_COSTS;</code> 命令,这样优化器就会重新读取成本表并更新其内部的成本估算。</p><p>例如,如果你想要增加 InnoDB 存储引擎的磁盘读取成本,可以这样做:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">UPDATE</span> mysql.engine_cost</span><br><span class="line"><span class="keyword">SET</span> cost_value <span class="number">2.0</span></span><br><span class="line"><span class="keyword">WHERE</span> engine_name <span class="string">&#x27;InnoDB&#x27;</span> <span class="keyword">AND</span> cost_name <span class="string">&#x27;io_block_read_cost&#x27;</span>;</span><br><span class="line">FLUSH OPTIMIZER_COSTS;</span><br></pre></td></tr></table></figure><p>请注意,这些更改应该谨慎进行,因为不恰当的成本调整可能会导致优化器生成非最优的执行计划。通常建议在充分测试和监控的基础上进行调整。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img5.avif"></p><h3 id="func"><a href="#func" class="headerlink" title="func"></a>func</h3><p>在 MySQL 中,<code>func</code> 表是 <code>mysql</code> 数据库中的一个系统表,用于存储用户定义的函数 User-Defined Functions,UDF 。这些函数是用 C 或 C 编写的,可以被加载到 MySQL 服务器中,以便在 SQL 语句中使用。</p><p>以下是 <code>func</code> 表中的一些关键列:</p><ul><li><strong>name</strong>: 函数的名称。</li><li><strong>ret</strong>: 函数返回值的类型。</li><li><strong>dl</strong>: 包含该函数的动态链接库 Dynamic Link Library,DLL 或共享对象 Shared Object,SO 的文件名。</li><li><strong>type</strong>: 函数的类型,例如 <code>function</code> 或 <code>aggregate</code> 聚合函数 。</li><li><strong>flags</strong>: 函数的标志,用于指示函数的特性。</li></ul><p>用户定义的函数可以用于执行各种操作,如字符串处理、数学计算、数据转换等。这些函数在 SQL 语句中被调用时,会由 MySQL 服务器动态加载并执行。</p><p>要创建用户定义的函数,可以使用 <code>CREATE FUNCTION</code> 语句,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">FUNCTION</span> my_add_func <span class="keyword">RETURNS</span> <span class="type">INTEGER</span> SONAME <span class="string">&#x27;my_udf_library.so&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个语句创建了一个名为 <code>my_add_func</code> 的函数,它返回一个整数类型的值,并且由 <code>my_udf_library.so</code> 共享库提供实现。</p><p>要查看系统中定义的所有用户定义函数,可以查询 <code>func</code> 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.func;</span><br></pre></td></tr></table></figure><p>这将返回所有用户定义函数的详细信息。需要注意的是,创建和删除用户定义函数需要相应的权限。</p><p>用户定义函数可以提高 SQL 语句的复用性和灵活性,但同时也需要注意安全性和性能影响,因为它们是服务器端的扩展功能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img6.avif"></p><h3 id="general-log"><a href="#general-log" class="headerlink" title="general_log"></a>general_log</h3><p>MySQL中的<code>general_log</code>是一个用于记录所有到达MySQL服务器的SQL语句的日志系统。默认情况下,<code>general_log</code>是关闭的,因为它可能会产生大量的日志数据,从而对服务器性能产生影响。当需要对数据库进行故障排查时,可以临时开启<code>general_log</code>。</p><p><strong>如何开启和配置general_log:</strong></p><ul><li><p><strong>开启</strong><code>general_log</code>:</p></li><li><p>通过设置系统变量:<code>SET GLOBAL general_log ON;</code></p></li><li><p>修改配置文件 如<code>my.cnf</code>或<code>my.ini</code> ,在<code>[mysqld]</code>部分添加<code>general_log 1</code>,然后重启MySQL服务。</p></li><li><p><strong>设置日志文件路径</strong>:</p></li><li><p>通过设置系统变量:<code>SET GLOBAL general_log_file &#39;path/to/your/logfile.log&#39;;</code></p></li><li><p>在配置文件中指定日志文件路径。</p></li><li><p><strong>查看日志状态</strong>:</p></li><li><p>使用命令:<code>SHOW VARIABLES LIKE &#39;general_log%&#39;;</code></p></li></ul><p><strong>日志文件内容</strong>:<br><code>general_log</code>文件记录了包括客户端连接和断开、执行的SQL语句等信息。每条记录通常包含时间戳、线程ID、服务器ID、命令类型和参数 即完整的SQL语句 。</p><p><strong>日志输出位置</strong>:</p><ul><li>默认情况下,日志文件存储在MySQL数据目录中,文件名为<code>hostname.log</code>,其中<code>hostname</code>是主机名。</li><li>可以通过<code>general_log_file</code>变量指定日志文件的名称和路径。</li></ul><p><strong>日志存储方式</strong>:</p><ul><li><code>log_output</code>变量控制日志的存储方式,可以是<code>FILE</code>或<code>TABLE</code>。默认情况下,日志存储在文件中。</li><li>如果设置为<code>TABLE</code>,则日志信息会被写入到<code>mysql.general_log</code>表中。</li></ul><p><strong>注意事项</strong>:</p><ul><li>开启<code>general_log</code>可能会对性能有较大影响,因此建议仅在必要时开启,并在完成后及时关闭。</li><li>如果需要清空日志文件,可以关闭日志记录,然后重命名或删除日志文件,并重新开启日志记录。</li></ul><p>更多详细信息可以参考MySQL官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img7.avif"></p><h3 id="global-grants"><a href="#global-grants" class="headerlink" title="global_grants"></a>global_grants</h3><p><code>global_grants</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,用于存储动态全局权限。这些权限是全局的,意味着它们适用于整个 MySQL 服务器的所有数据库。动态权限是在运行时定义的,与静态权限 如 SELECT、INSERT 等 相对。</p><p>以下是 <code>global_grants</code> 表中的一些关键列:</p><ul><li><strong>USER</strong>: 用户名,这里是 <code>root</code>。</li><li><strong>HOST</strong>: 用户连接的主机名或 IP 地址。<code>%</code> 表示任何主机,<code>localhost</code> 表示本地主机。</li><li><strong>PRIV</strong>: 授予的动态权限名称,例如 <code>BACKUP_ADMIN</code>、<code>SYSTEM_USER</code>、<code>APPLICATION_PASSWORD_ADMIN</code> 等。</li><li><strong>WITH_GRANT_OPTION</strong>: 表示是否授予了 <code>GRANT OPTION</code>,即是否允许该用户将权限授予其他用户。<code>Y</code> 表示是,<code>N</code> 表示否。</li></ul><p>动态权限通常与特定的 MySQL 功能或组件相关联,例如复制、审计、加密等。它们可以在运行时通过 <code>GRANT</code> 和 <code>REVOKE</code> 语句进行管理。</p><p>要查看 <code>global_grants</code> 表中的权限信息,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.global_grants;</span><br></pre></td></tr></table></figure><p>这将返回所有动态全局权限的列表。需要注意的是,查询这个表通常需要有 <code>PROCESS</code> 权限。</p><p><code>global_grants</code> 表是 MySQL 权限系统的重要组成部分,它允许管理员灵活地控制用户权限,特别是在需要精细控制特定功能或组件的访问时。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img8.avif"></p><h3 id="gtid-executed"><a href="#gtid-executed" class="headerlink" title="gtid_executed"></a>gtid_executed</h3><p><code>gtid_executed</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,用于存储全局事务标识符 GTID 的执行信息。这个表有三个主要字段:</p><ul><li><strong>source_uuid</strong>: 表示生成这些 GTID 的 MySQL 服务器实例的 UUID。</li><li><strong>interval_start</strong>: GTID 的开始间隔。</li><li><strong>interval_end</strong>: GTID 的结束间隔。</li></ul><p>这个表在 MySQL 启动阶段会读取,以获取 <code>gtid_executed</code> 变量的值,该变量存储在内存中,用于记录 MySQL 数据库已经执行了哪些 GTID 事务。<code>gtid_executed</code> 变量是实时更新的,无论主库和从库都会更新这个变量。</p><p>在 MySQL 5.7 及更高版本中,GTID 事务是唯一标识每个事务的全局标识符,格式为 <code>UUID:NUMBER</code>。例如,服务器 UUID 为 <code>3E11FA47-71CA-11E1-9E33-C80AA9429562</code> 的第一个事务的 GTID 是 <code>3E11FA47-71CA-11E1-9E33-C80AA9429562:1</code>。</p><p><code>gtid_executed</code> 表的作用包括:</p><ul><li>确保数据一致性:同一个 GTID 的事务不会在一个服务器上执行两次。</li><li>故障恢复:在主从复制中,如果一台服务器宕机,可以通过 GTID 来确定哪些事务需要执行,以保证数据的一致性。</li><li>简化复制配置:使用 GTID 复制时,可以通过 <code>CHANGE MASTER TO MASTER_AUTO_POSITION 1</code> 来简化从库的配置。</li></ul><p>在 MySQL 8.0 版本中,<code>gtid_executed</code> 表还支持压缩,可以通过 <code>gtid_executed_compression_period</code> 系统变量来控制压缩周期。表中的 GTID 信息会定期被压缩,以节省空间。</p><p>要查看 <code>gtid_executed</code> 表中的 GTID 信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.gtid_executed;</span><br></pre></td></tr></table></figure><p>这将返回所有已经执行的 GTID 事务的信息。如果需要检查数据一致性,可以比较不同服务器上的 <code>gtid_executed</code> 表的内容,确保它们之间没有数据分叉或冲突。</p><p>需要注意的是,<code>gtid_executed</code> 表是 MySQL 服务器内部使用的,通常情况下不需要手动干预或修改。如果需要手动设置 GTID 信息,可以使用 <code>RESET MASTER</code> 或 <code>RESET SLAVE</code> 命令,或者通过设置 <code>gtid_purged</code> 变量来提示 MySQL 服务器哪些 GTID 事务已经执行过了。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img9.avif"></p><h3 id="help-category"><a href="#help-category" class="headerlink" title="help_category"></a>help_category</h3><p><code>help_category</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它存储了 MySQL 帮助命令 <code>HELP</code> 使用的帮助主题类别信息。这些类别对应于 MySQL 参考手册中不同的部分,使得用户可以通过 <code>HELP</code> 命令查找相关主题的帮助信息。</p><p>以下是 <code>help_category</code> 表中的一些关键字段:</p><ul><li><strong>help_category_id</strong>: 帮助类别的唯一标识符。</li><li><strong>name</strong>: 帮助类别的名称,例如 Data Definition 、 Data Manipulation 、 Functions 等。</li><li><strong>parent_category_id</strong>: 父类别的标识符,用于表示类别之间的层级关系。</li><li><strong>url</strong>: 对应的帮助主题在 MySQL 官方文档中的 URL 地址。</li></ul><p>当用户执行 <code>HELP</code> 命令时,MySQL 会搜索这些表以提供相关的帮助信息。例如,用户可以执行 <code>HELP &#39;functions&#39;</code> 来获取有关 MySQL 函数的相关信息。</p><p>这些帮助表在数据库初始化时通过加载 <code>fill_help_tables.sql</code> 文件创建,并且通常在 MySQL 安装过程的一部分执行。如果需要更新帮助表,可以手动加载这个文件。</p><p>要查看 <code>help_category</code> 表中的类别信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.help_category;</span><br></pre></td></tr></table></figure><p>这将返回所有帮助主题类别的列表。用户可以根据返回的类别名称来进一步查询特定类别下的关键字或主题。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img10.avif"></p><h3 id="help-keyword"><a href="#help-keyword" class="headerlink" title="help_keyword"></a>help_keyword</h3><p><code>help_keyword</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它是服务器端帮助系统的一部分。这个表存储了与帮助主题相关的关键字信息,这些关键字用于 <code>HELP</code> 命令在 MySQL 命令行客户端中搜索帮助信息时使用。</p><p>以下是 <code>help_keyword</code> 表中的一些关键字段:</p><ul><li><strong>help_keyword_id</strong>: 帮助关键字的唯一标识符。</li><li><strong>name</strong>: 关键字的名称,这个名称对应于用户可能搜索的帮助主题的关键字。</li></ul><p>当用户在 MySQL 命令行客户端中执行 <code>HELP</code> 命令时,系统会使用这些关键字来搜索相关的帮助主题。例如,用户可以执行 <code>HELP &#39;SELECT&#39;;</code> 来获取有关 <code>SELECT</code> 语句的帮助信息。</p><p><code>help_keyword</code> 表通常与 <code>help_category</code>、<code>help_relation</code> 和 <code>help_topic</code> 表一起使用,以提供完整的帮助信息检索功能。这些表共同构成了 MySQL 服务器的帮助系统,允许用户快速查找和浏览 MySQL 的各种命令、功能和主题的文档。</p><p>要查看 <code>help_keyword</code> 表中的关键字列表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.help_keyword;</span><br></pre></td></tr></table></figure><p>这将返回所有帮助关键字的列表。需要注意的是,查询这个表通常需要有相应的权限。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img11.avif"></p><h3 id="help-relation"><a href="#help-relation" class="headerlink" title="help_relation"></a>help_relation</h3><p><code>help_relation</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它是服务器端帮助系统的一部分。这个表存储了帮助主题 <code>help_topic</code> 和帮助关键字 <code>help_keyword</code> 之间的关系,使得用户可以通过 <code>HELP</code> 命令搜索相关的帮助信息。</p><p>以下是 <code>help_relation</code> 表中的一些关键字段:</p><ul><li><strong>help_topic_id</strong>: 帮助主题的唯一标识符。</li><li><strong>help_keyword_id</strong>: 与帮助主题相关联的关键字的唯一标识符。</li></ul><p>这个表通常与 <code>help_category</code>、<code>help_topic</code> 和 <code>help_keyword</code> 表一起使用,以提供完整的帮助信息检索功能。当用户执行 <code>HELP</code> 命令时,系统会使用这些表来搜索相关的帮助主题和信息。</p><p>要查看 <code>help_relation</code> 表中的信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.help_relation;</span><br></pre></td></tr></table></figure><p>这将返回所有帮助主题和关键字之间的关系列表。需要注意的是,查询这个表通常需要有相应的权限。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img12.avif"></p><h3 id="help-topic"><a href="#help-topic" class="headerlink" title="help_topic"></a>help_topic</h3><p><code>help_topic</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它存储了 MySQL 帮助主题的详细信息。这个表是 MySQL 帮助系统的一部分,包含了关于 MySQL 命令、函数、对象的描述和用法的信息。</p><p>以下是 <code>help_topic</code> 表中的一些关键字段:</p><ul><li><strong>help_topic_id</strong>: 帮助主题的唯一标识符。</li><li><strong>name</strong>: 帮助主题的名称或标识符。</li><li><strong>help_category_id</strong>: 帮助主题所属的分类ID。</li><li><strong>description</strong>: 提供关于帮助主题的简短描述。</li><li><strong>help_text</strong>: 包含关于帮助主题的详细描述或说明。</li><li><strong>example</strong>: 提供帮助主题的使用示例。</li><li><strong>url</strong>: 指向 MySQL 官方文档中相应帮助主题的 URL 地址。</li></ul><p>通过查询 <code>help_topic</code> 表,用户可以获取有关 MySQL 各种特性和命令的帮助信息。例如,如果你想获取关于 <code>JOIN</code> 语句的帮助信息,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> help_text <span class="keyword">FROM</span> mysql.help_topic <span class="keyword">WHERE</span> name <span class="string">&#x27;JOIN&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回有关 <code>JOIN</code> 语句的详细帮助文本。</p><p><code>help_topic</code> 表通常与 <code>help_category</code>、<code>help_keyword</code> 和 <code>help_relation</code> 表一起使用,以提供完整的帮助信息检索功能。这些表共同构成了 MySQL 的帮助系统,允许用户通过 <code>HELP</code> 命令在 MySQL 命令行客户端中搜索帮助信息。</p><p>要查看 <code>help_topic</code> 表中的所有帮助主题,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.help_topic;</span><br></pre></td></tr></table></figure><p>这将返回所有帮助主题的详细信息列表。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img13.avif"></p><h3 id="innodb-index-stats"><a href="#innodb-index-stats" class="headerlink" title="innodb_index_stats"></a>innodb_index_stats</h3><p><code>innodb_index_stats</code> 表是 MySQL <code>mysql</code> 数据库中的一个系统表,它存储了 InnoDB 存储引擎索引的统计信息。这些统计信息对于 MySQL 查询优化器来说非常重要,因为它们帮助优化器确定索引对于给定查询计划的有效性。</p><p>以下是 <code>innodb_index_stats</code> 表中的一些关键字段:</p><ul><li><strong>database_name</strong>: 索引所属的数据库名称。</li><li><strong>table_name</strong>: 索引所属的表名称。</li><li><strong>index_name</strong>: 索引的名称。</li><li><strong>last_update</strong>: 最后一次更新统计信息的时间。</li><li><strong>stat_name</strong>: 统计项的名称,如 <code>n_leaf_pages</code> 叶子页数 、<code>size</code> 索引大小 等。</li><li><strong>stat_value</strong>: 统计项的值。</li><li><strong>sample_size</strong>: 用于统计的采样页面数量。</li><li><strong>stat_description</strong>: 对统计项的描述。</li></ul><p>例如,<code>n_diff_pfx01</code> 可能表示某一列的不同前缀数量,<code>n_diff_pfx02</code> 可能表示前两列组合的不同前缀数量。<code>n_leaf_pages</code> 表示索引叶子节点的页数,<code>size</code> 表示索引占用的总页数。</p><p>统计信息的准确性对于查询性能至关重要。如果统计信息过时或不准确,优化器可能会做出错误的决策,导致查询性能下降。因此,定期更新统计信息是数据库维护的重要部分。</p><p>要查看特定索引的统计信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.innodb_index_stats</span><br><span class="line"><span class="keyword">WHERE</span> database_name <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> table_name <span class="string">&#x27;your_table_name&#x27;</span> <span class="keyword">AND</span> index_name <span class="string">&#x27;your_index_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code>、<code>your_table_name</code> 和 <code>your_index_name</code> 替换为你要查询的数据库名称、表名称和索引名称。</p><p>MySQL 提供了 <code>ANALYZE TABLE</code> 命令来手动更新统计信息,也可以通过设置 <code>innodb_stats_auto_recalc</code> 系统变量为 <code>ON</code> 来自动更新统计信息。</p><p>更多详细信息可以参考 MySQL 官方文档 。</p><p><em><strong>GEN_CLUST_INDEX 是隐藏的主键索引</strong></em></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img14.avif"></p><h3 id="innodb-table-stats"><a href="#innodb-table-stats" class="headerlink" title="innodb_table_stats"></a>innodb_table_stats</h3><p><code>mysql.innodb_table_stats</code> 是 MySQL 数据库中的一个重要表,它存储了与 InnoDB 存储引擎表统计信息相关的数据。这些统计信息对于 MySQL 的查询优化器 Optimizer 来说至关重要,因为它们帮助优化器决定执行查询时使用哪个索引。</p><p>以下是 <code>mysql.innodb_table_stats</code> 表中一些关键字段的说明:</p><ul><li><strong>database_name</strong>: 数据库名称。</li><li><strong>table_name</strong>: 表名、分区名或子分区名。</li><li><strong>last_update</strong>: 一个时间戳,指示该行最后一次更新的时间。</li><li><strong>n_rows</strong>: 表中的行数。</li><li><strong>clustered_index_size</strong>: 主索引的大小 以页为单位 。</li><li><strong>sum_of_other_index_sizes</strong>: 非主索引的总大小 以页为单位 。</li></ul><p>这些统计数据可以是持久化的,也可以是非持久化的。持久化统计数据在服务器重启后依然存在,而非持久化统计数据则在服务器关闭时会被清除。系统变量 <code>innodb_stats_persistent</code> 控制是否使用持久化统计数据,默认情况下这个变量是开启的 ON ,这意味着统计数据默认会被存储到磁盘上。</p><p>统计数据的更新可以通过 <code>ANALYZE TABLE</code> 语句来手动触发,也可以通过系统变量 <code>innodb_stats_auto_recalc</code> 来自动更新。当表中的数据发生变化,且变化的行数超过了表大小的一定比例 默认是10% ,MySQL 会自动重新计算统计数据。</p><p>此外,<code>mysql.innodb_table_stats</code> 表和 <code>mysql.innodb_index_stats</code> 表可以手动更新,以便在不修改数据库的情况下强制或测试不同的查询优化计划。手动更新统计信息后,需要使用 <code>FLUSH TABLE</code> 语句来加载更新后的统计信息。</p><p>需要注意的是,<code>mysql.innodb_table_stats</code> 表不会被复制,即它不参与 MySQL 的复制过程,但它对于查询优化器的性能至关重要。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img15.avif"></p><h3 id="ndb-binlog-index"><a href="#ndb-binlog-index" class="headerlink" title="ndb_binlog_index"></a>ndb_binlog_index</h3><p><code>mysql.ndb_binlog_index</code> 表是 MySQL NDB Cluster 版本特有的系统表,用于存储 NDB Cluster 复制的二进制日志信息。这个表对于 NDB Cluster 复制机制来说非常重要,因为它提供了关于二进制日志事件的索引数据,这些数据可以用来追踪和定位复制过程中的事件。</p><p>以下是 <code>ndb_binlog_index</code> 表的一些关键字段:</p><ul><li><strong>Position</strong>: 二进制日志中的位置。</li><li><strong>File</strong>: 二进制日志文件的名称。</li><li><strong>epoch</strong>: 一个时间戳,表示该条记录的创建时间。</li><li><strong>inserts</strong>, <strong>updates</strong>, <strong>deletes</strong>: 分别表示该日志条目中的插入、更新和删除操作的数量。</li><li><strong>schemaops</strong>: 模式操作的数量。</li><li><strong>orig_server_id</strong>: 原始服务器的 ID。</li><li><strong>orig_epoch</strong>: 原始服务器上事件发生的时代。</li><li><strong>gci</strong>: 全局事务标识符,用于在复制过程中标识事务。</li><li><strong>next_position</strong>: 下一个二进制日志事件的位置。</li><li><strong>next_file</strong>: 下一个二进制日志文件的名称。</li></ul><p>这个表通常是由 MySQL 服务器自动维护的,不需要用户手动干预。它使用 InnoDB 存储引擎,并且每个 MySQL 服务器实例上都会有这样一个本地表。在 NDB Cluster 复制中,这个表对于确定副本上最高应用纪元的二进制日志位置非常有用,特别是在多源复制设置中。</p><p>在某些情况下,为了提高性能,可能需要对这个表的某些列添加索引,例如 <code>orig_server_id</code> 和 <code>orig_epoch</code>,以便快速查找特定源服务器的事件。这是因为在多源复制环境中,这些列没有索引可能会导致性能问题,因为查询必须执行表扫描来查找相关的二进制日志位置 。</p><p>此外,<code>ndb_binlog_index</code> 表的大小取决于每个二进制日志文件的纪元数和二进制日志文件的数量。如果 NDB Cluster 非常繁忙,它可能会比安静的集群更频繁地写入二进制日志,并且可能会更快地轮换二进制日志文件 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img16.avif"></p><h3 id="password-history"><a href="#password-history" class="headerlink" title="password_history"></a>password_history</h3><p><code>mysql.password_history</code> 是 MySQL 8.0 及以上版本中引入的系统表,用于实现密码重用策略。当用户更改密码时,这个表会记录用户之前使用过的密码及其更改时间,以防止用户重复使用旧密码。</p><p>以下是 <code>mysql.password_history</code> 表中一些关键字段的说明:</p><ul><li><strong>Host</strong>: 用户所属的主机。</li><li><strong>User</strong>: 用户名。</li><li><strong>Password_timestamp</strong>: 密码更改的时间戳。</li><li><strong>Password</strong>: 存储的密码哈希值。</li></ul><p>通过设置 <code>password_history</code> 系统变量,可以定义用户在设置新密码时不能使用最近多少次更改过的密码。例如,如果 <code>password_history</code> 设置为 5,则用户在更改密码时,不能使用最近 5 次更改过的密码。</p><p>此外,还有一个相关的系统变量 <code>password_reuse_interval</code>,它定义了密码重用的时间间隔。如果设置了这个变量,用户在指定的时间内不能重复使用旧密码。</p><p>这些功能有助于提高数据库的安全性,通过防止用户重复使用旧密码,可以减少密码被破解的风险。管理员可以通过查看 <code>mysql.password_history</code> 表来审计用户的密码更改历史。</p><p>需要注意的是,这些密码策略功能仅适用于使用 MySQL 内置身份验证插件 如 <code>mysql_native_password</code>、<code>sha256_password</code> 或 <code>caching_sha2_password</code> 的帐户。如果帐户使用外部身份验证系统进行身份验证,则密码管理也必须针对该系统在外部进行处理。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img17.avif"></p><h3 id="plugin"><a href="#plugin" class="headerlink" title="plugin"></a>plugin</h3><p><code>mysql.plugin</code> 是 MySQL 数据库中的一个系统表,用于存储和管理 MySQL 服务器插件的信息。插件可以是存储引擎、身份验证插件或其他类型的服务器扩展。该表在 MySQL 5.7 及更高版本中可用,并且它在 MySQL 安装过程中被创建。</p><p>以下是 <code>mysql.plugin</code> 表的一些关键字段:</p><ul><li><strong>name</strong>: 插件的名称。</li><li><strong>dl</strong>: 插件库文件的名称,通常是一个 <code>.so</code> 文件 在类 Unix 系统中 或 <code>.dll</code> 文件 在 Windows 系统中 。</li><li><strong>load_option</strong>: 插件加载选项,例如 <code>FORCE</code>、<code>ON</code>、<code>OFF</code> 等。</li></ul><p>该表通常由以下 MySQL 语句管理:</p><ul><li><code>INSTALL PLUGIN</code>: 安装插件并将插件信息注册到 <code>mysql.plugin</code> 表中。</li><li><code>UNINSTALL PLUGIN</code>: 从 <code>mysql.plugin</code> 表中移除插件信息并卸载插件。</li></ul><p><code>mysql.plugin</code> 表不包含内置插件的信息,因为内置插件不需要注册。它只包含通过 <code>INSTALL PLUGIN</code> 语句安装的插件信息。当服务器启动时,它会检查 <code>mysql.plugin</code> 表,并根据表中的内容加载插件。</p><p>如果 <code>mysql.plugin</code> 表不存在,可能是因为 MySQL 没有正确安装或初始化,或者该表被意外删除。在这种情况下,可能需要重新安装 MySQL 或修复数据库 。</p><p>此外,可以通过 <code>SHOW PLUGINS</code> 语句或查询 <code>INFORMATION_SCHEMA.PLUGINS</code> 表来查看服务器上所有插件的信息,包括那些内置插件 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img18.avif"></p><h3 id="procs-priv"><a href="#procs-priv" class="headerlink" title="procs_priv"></a>procs_priv</h3><p><code>mysql.procs_priv</code> 表用于存储 MySQL 数据库中关于存储过程和存储函数的权限信息。这个表在 MySQL 5.7 及更高版本中可用,并且在 MySQL 实例启动时会将这些权限信息加载到内存中。</p><p>以下是 <code>mysql.procs_priv</code> 表中的一些关键字段:</p><ul><li><strong>Host</strong>: 指出可以执行存储过程的主机。</li><li><strong>Db</strong>: 指出存储过程所在的数据库。</li><li><strong>User</strong>: 指出具有执行存储过程权限的用户名。</li><li><strong>Routine_name</strong>: 存储过程或函数的名称。</li><li><strong>Routine_type</strong>: 指出是存储过程 (PROCEDURE) 还是函数 (FUNCTION)。</li><li><strong>Proc_priv</strong>: 指出授予的权限集合,可能包括执行 (Execute)、修改 (Alter Routine) 和授权 (Grant) 等权限。</li><li><strong>Timestamp</strong>: 记录这条权限记录被修改的时间。</li><li><strong>Grantor</strong>: 指出授予这些权限的用户。</li></ul><p>例如,如果要给用户 ‘bob’ ‘localhost’ 授予对存储过程 ‘myproc’ 的执行权限,可以在 <code>procs_priv</code> 表中插入一条记录,包含 ‘localhost’,’bob’,’mydb’ 假设存储过程在 ‘mydb’ 数据库中 ,’myproc’,’PROCEDURE’,以及相应的权限集。</p><p>当涉及存储过程和函数的权限请求时,MySQL 服务器会查询 <code>procs_priv</code> 表来验证权限。这个表允许管理员对数据库中的存储过程和函数进行细粒度的权限控制。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img19.avif"></p><h3 id="proxies-priv"><a href="#proxies-priv" class="headerlink" title="proxies_priv"></a>proxies_priv</h3><p><code>mysql.proxies_priv</code> 表在 MySQL 数据库中用于存储代理用户 Proxy Users 的权限信息。代理用户是一种特殊的用户,它可以代表其他用户执行操作。这种机制可以用于实现类似用户组的管理,即多个用户可以拥有相同的权限集,而不需要为每个用户单独授予权限。</p><p>以下是 <code>mysql.proxies_priv</code> 表中的一些关键字段:</p><ul><li><strong>Host</strong>: 代理用户的主机名。</li><li><strong>User</strong>: 代理用户的用户名。</li><li><strong>Proxied_host</strong>: 被代理用户的主机名。</li><li><strong>Proxied_user</strong>: 被代理的用户名。</li><li><strong>With_grant</strong>: 一个布尔值,表示代理用户是否有权限将 <code>PROXY</code> 特权授予其他用户。</li><li><strong>Grantor</strong>: 授予代理权限的用户。</li><li><strong>Timestamp</strong>: 代理权限记录的更新时间戳。</li></ul><p>例如,如果用户 <code>A</code> 想要代理用户 <code>B</code> 执行某些操作,可以在 <code>proxies_priv</code> 表中插入一条记录,指定 <code>Host</code>、<code>User</code> 为 <code>A</code> 的信息,<code>Proxied_host</code>、<code>Proxied_user</code> 为 <code>B</code> 的信息,并且设置 <code>With_grant</code> 来决定 <code>A</code> 是否可以将代理权限授予其他用户。</p><p>需要注意的是,<code>proxies_priv</code> 表的 <code>Grantor</code> 和 <code>Timestamp</code> 字段通常不使用。此外,为了使用代理功能,需要在 MySQL 配置中启用 <code>check_proxy_users</code> 变量。</p><p>在实际使用中,可以通过 <code>GRANT</code> 语句来授予代理权限,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> PROXY <span class="keyword">ON</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;host&#x27;</span> <span class="keyword">TO</span> <span class="string">&#x27;proxyuser&#x27;</span> <span class="string">&#x27;proxyhost&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这条命令允许 <code>proxyuser</code> ‘proxyhost’ 代理 <code>username</code> ‘host’ 的权限。代理用户可以用于数据库的权限管理和审计,以便更灵活地控制用户权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img20.avif"></p><h3 id="replication-asynchronous-connection-failover"><a href="#replication-asynchronous-connection-failover" class="headerlink" title="replication_asynchronous_connection_failover"></a>replication_asynchronous_connection_failover</h3><p><code>mysql.replication_asynchronous_connection_failover</code> 表是在 MySQL 8.0.22 及更高版本中引入的,用于存储异步连接故障转移的配置信息。这个表是与异步复制连接故障转移机制相关联的,该机制允许在从副本到其源的现有连接失败后,自动建立到新源的异步复制连接。</p><p>以下是 <code>mysql.replication_asynchronous_connection_failover</code> 表中的一些关键字段:</p><ul><li><strong>CHANNEL_NAME</strong>: 复制通道的名称。</li><li><strong>HOST</strong>: 潜在源服务器的主机名。</li><li><strong>PORT</strong>: 潜在源服务器的端口号。</li><li><strong>NETWORK_NAMESPACE</strong>: 网络命名空间 当前版本中不使用 。</li><li><strong>WEIGHT</strong>: 服务器的加权优先级,用于故障转移决策。</li></ul><p>当启用异步连接故障转移机制时,如果副本与源服务器的连接失败,MySQL 副本会尝试根据在 <code>mysql.replication_asynchronous_connection_failover</code> 表中设置的加权优先级列表,自动连接到新的源服务器。这个过程是异步的,意味着它不会阻塞副本上的其他操作。</p><p>管理员可以使用 <code>asynchronous_connection_failover_add_source</code> 和 <code>asynchronous_connection_failover_delete_source</code> 函数来添加或删除源服务器的配置。此外,对于托管组 如 Group Replication ,可以使用 <code>asynchronous_connection_failover_add_managed</code> 和 <code>asynchronous_connection_failover_delete_managed</code> 函数来管理源服务器列表。</p><p>此功能要求在源和副本上使用 GTID,并且副本上必须启用 <code>SOURCE_AUTO_POSITION</code> 或 <code>MASTER_AUTO_POSITION</code> 选项,以便 GTID 自动定位用于与源的连接。此外,所有源服务器上必须存在相同的复制用户帐户和密码,该帐户用于连接到每个源。</p><p><code>mysql.replication_asynchronous_connection_failover</code> 表和相关的异步连接故障转移机制为 MySQL 复制提供了更高的可用性和容错能力,特别是在多数据中心的环境中。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img21.avif"></p><h3 id="replication-asynchronous-connection-failover-managed"><a href="#replication-asynchronous-connection-failover-managed" class="headerlink" title="replication_asynchronous_connection_failover_managed"></a>replication_asynchronous_connection_failover_managed</h3><p><code>mysql.replication_asynchronous_connection_failover_managed</code> 表是在 MySQL 8.0.23 及更高版本中引入的,用于存储异步连接故障转移的配置信息,特别是当副本 replica 需要与组复制 Group Replication 的成员进行同步时。</p><p>此表允许管理员定义一个受管理的组,例如一个组复制集群,并且指定该组的成员 MySQL 服务器 在异步复制连接故障转移时如何被对待。表中记录了组复制成员的身份信息和权重,以便在当前源服务器不可用时,副本可以根据这些信息自动选择另一个源服务器进行连接。</p><p>关键字段可能包括:</p><ul><li><strong>CHANNEL_NAME</strong>: 应用故障转移配置的复制通道名称。</li><li><strong>MANAGED_TYPE</strong>: 管理的类型,目前唯一有效的值是 <code>GroupReplication</code>。</li><li><strong>MANAGED_NAME</strong>: 管理组的名称,对应于组复制的 <code>group_replication_group_name</code> 系统变量的值。</li><li><strong>HOST</strong>: 组复制成员的主机名。</li><li><strong>PORT</strong>: 组复制成员的端口号。</li><li><strong>NETWORK_NAMESPACE</strong>: 网络命名空间,当前版本中不使用。</li><li><strong>PRIMARY_WEIGHT</strong>: 主服务器的权重。</li><li><strong>SECONDARY_WEIGHT</strong>: 辅助服务器的权重。</li></ul><p>使用 <code>asynchronous_connection_failover_add_managed</code> 函数可以向此表添加新的受管理组配置,而 <code>asynchronous_connection_failover_delete_managed</code> 函数可以删除现有的配置。</p><p>当组复制的成员身份发生变化时,例如有新的成员加入或现有成员离开,副本将自动更新其源列表,以保持与组复制成员的最新状态同步。如果副本与当前源的连接失败,它将根据 <code>PRIMARY_WEIGHT</code> 和 <code>SECONDARY_WEIGHT</code> 字段中定义的权重自动选择新的源进行连接。</p><p>这个功能增强了 MySQL 复制的高可用性,尤其是在涉及组复制的场景中。通过自动故障转移,减少了人为干预的需要,并提高了系统的容错能力 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img22.avif"></p><h3 id="replication-group-configuration-version"><a href="#replication-group-configuration-version" class="headerlink" title="replication_group_configuration_version"></a>replication_group_configuration_version</h3><p><code>mysql.replication_group_configuration_version</code> 表用于显示复制组成员操作配置的版本信息。这个表只有在安装了 Group Replication 时才可用。每当使用 <code>group_replication_enable_member_action()</code> 和 <code>group_replication_disable_member_action()</code> 函数启用或禁用成员操作时,版本号就会递增。如果使用 <code>group_replication_reset_member_actions()</code> 函数重置成员操作配置,将其设置为默认设置,版本号也会重置为1。</p><p><code>replication_group_configuration_version</code> 表包含以下列:</p><ul><li><code>NAME</code>: 配置的名称。</li><li><code>VERSION</code>: 配置的版本号。</li></ul><p>这个表没有索引,并且不允许对 <code>replication_group_configuration_version</code> 表执行 <code>TRUNCATE TABLE</code> 操作 。</p><p>此表用于追踪组复制配置的变更历史,以便于管理员能够了解当前配置的版本状态,从而更好地管理和维护 MySQL 组复制的配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img23.avif"></p><h3 id="replication-group-member-actions"><a href="#replication-group-member-actions" class="headerlink" title="replication_group_member_actions"></a>replication_group_member_actions</h3><p><code>mysql.replication_group_member_actions</code> 表是在 MySQL 8.0.26 及更高版本中引入的,用于配置和管理组复制 Group Replication 成员的动作。这个表允许管理员为组成员在特定情况下设置自动化动作,例如在主节点选举后执行特定的操作。</p><p>以下是 <code>mysql.replication_group_member_actions</code> 表中的一些关键字段:</p><ul><li><strong>NAME</strong>: 成员动作的名称。</li><li><strong>EVENT</strong>: 触发成员动作的事件。</li><li><strong>ENABLED</strong>: 表示成员动作当前是否启用。</li><li><strong>TYPE</strong>: 成员动作的类型,例如 <code>INTERNAL</code> 表示由组复制插件提供的操作。</li><li><strong>PRIORITY</strong>: 成员动作的优先级,较低的值表示优先级更高,将首先执行。</li><li><strong>ERROR_HANDLING</strong>: 如果在执行成员动作时发生错误,组复制将采取的操作。例如,<code>IGNORE</code> 表示记录错误消息但不采取进一步操作,而 <code>CRITICAL</code> 表示成员将进入 <code>ERROR</code> 状态,并执行 <code>group_replication_exit_state_action</code> 系统变量指定的操作。</li></ul><p>成员动作配置在组内通过组消息传播,因此所有组成员都有相同的成员动作配置。这个配置不会赋予 GTID,也不会写入二进制日志,因此不会传播到组外的服务器。</p><p>管理员可以使用 <code>group_replication_enable_member_action()</code> 和 <code>group_replication_disable_member_action()</code> 函数来启用或禁用特定的成员动作。此外,可以使用 <code>group_replication_reset_member_actions()</code> 函数将成员动作配置重置为默认设置。</p><p>这个表是组复制管理的重要组成部分,提供了对组成员行为的细粒度控制,有助于实现高可用性和自动化的故障恢复。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img24.avif"></p><h3 id="role-edges"><a href="#role-edges" class="headerlink" title="role_edges"></a>role_edges</h3><p><code>mysql.role_edges</code> 表是 MySQL 8.0 版本引入的,用于存储角色 Role 之间的关系。在 MySQL 8.0 中,角色是一种新的权限管理方式,可以看作是权限的集合,可以授予用户,以简化权限的管理。角色类似于用户,但是不能用来直接</p><p><code>role_edges</code> 表包含角色之间的层次关系,即哪个角色是另一个角色的成员。这个关系可以是有向的,表示一种继承关系,例如,如果角色 B 被定义为角色 A 的成员,那么拥有角色 A 的用户同时也会拥有角色 B 的权限。</p><p>以下是 <code>mysql.role_edges</code> 表中的一些关键字段:</p><ul><li><strong>FROM_ROLE</strong>: 源角色的名称。</li><li><strong>TO_ROLE</strong>: 目标角色的名称,源角色是目标角色的成员。</li></ul><p>通过这个表,可以方便地查询和维护角色之间的继承关系。例如,可以使用以下 SQL 语句来查看当前数据库中的角色关系:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.role_edges;</span><br></pre></td></tr></table></figure><p>这将返回角色之间的所有关系,从而可以了解角色的层次结构。</p><p>角色管理的一些基本操作包括创建角色、授予角色权限、将角色授予用户、激活角色等。例如,创建角色和授予权限的语句如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> ROLE <span class="string">&#x27;read_SC&#x27;</span>;</span><br><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span> <span class="keyword">ON</span> lab2.SC <span class="keyword">TO</span> <span class="string">&#x27;read_SC&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将角色授予用户:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="string">&#x27;read_SC&#x27;</span> <span class="keyword">TO</span> <span class="string">&#x27;test&#x27;</span>;</span><br></pre></td></tr></table></figure><p>激活角色:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> ROLE <span class="string">&#x27;read_SC&#x27;</span>;</span><br></pre></td></tr></table></figure><p>角色功能在 MySQL 8.0 中是一个重要的增强,它提供了一种更加灵活和强大的方式来管理用户权限。通过角色,可以简化权限的分配和撤销,特别是在有多用户需要相同权限的情况下。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img25.avif"></p><h3 id="server-cost"><a href="#server-cost" class="headerlink" title="server_cost"></a>server_cost</h3><p><code>mysql.server_cost</code> 表是 MySQL 数据库中的一个系统表,它包含了一般服务器操作的优化器成本估算。这些成本估算值被优化器在执行计划构建期间使用,以帮助决定最佳的查询执行策略。表中的非 NULL 值的优先级高于编译好的默认值,如果表中的值为 NULL,则优化器会使用默认的成本估算值。</p><p>以下是 <code>mysql.server_cost</code> 表中的一些关键字段:</p><ul><li><strong>cost_name</strong>: 成本估算的名称,如 <code>disk_temptable_create_cost</code>、<code>disk_temptable_row_cost</code>、<code>key_compare_cost</code>、<code>memory_temptable_create_cost</code>、<code>memory_temptable_row_cost</code> 和 <code>row_evaluate_cost</code> 等。这些名称不区分大小写 。</li><li><strong>cost_value</strong>: 成本估算的值。如果这个值是非 NULL,服务器会使用它作为成本。否则,将使用默认估计值 已编译的值 。管理员可以通过更新此列来更改成本估算 。</li><li><strong>last_update</strong>: 记录最后一次更新的时间。</li><li><strong>comment</strong>: 与成本估计相关的描述性<br>例如,<code>disk_temptable_create_cost</code> 的默认值是 40.0,表示在磁盘上创建临时表的成本;<code>memory_temptable_create_cost</code> 的默认值是 2.0,表示在内存中创建临时表的成本。这些值可以由数据库管理员根据系统的实际性能进行调整,以影响优化器的决策 。</li></ul><p>通过修改这些成本值,可以对 MySQL 的查询优化器进行微调,以适应特定的硬件和使用场景,从而提高查询性能。在修改了 <code>server_cost</code> 表中的值之后,需要执行 <code>FLUSH OPTIMIZER_COSTS</code> 语句来通知服务器重新读取成本表 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img26.avif"></p><h3 id="servers"><a href="#servers" class="headerlink" title="servers"></a>servers</h3><p><code>mysql.servers</code> 表是在 MySQL 8.0 版本中引入的,用于存储使用 <code>CREATE SERVER</code> 语句创建的服务器定义。这些定义是用于 <code>FEDERATED</code> 存储引擎的,允许你定义远程服务器的连接信息,以便创建 <code>FEDERATED</code> 表,从而允许 MySQL 访问远程 MySQL 服务器上的表。</p><p>以下是 <code>mysql.servers</code> 表中的一些关键字段:</p><ul><li><strong>Server_name</strong>: 服务器定义的唯一名称。</li><li><strong>Host</strong>: 远程服务器的主机名或 IP 地址。</li><li><strong>Db</strong>: 远程服务器上的数据库名。</li><li><strong>Username</strong>: 用于连接远程服务器的用户名。</li><li><strong>Password</strong>: 用户的密码。</li><li><strong>Port</strong>: 远程服务器上的端口号 如果未指定,则使用默认 MySQL 端口 3306 。</li><li><strong>Socket</strong>: 远程服务器上的套接字文件路径。</li></ul><p>通过 <code>CREATE SERVER</code> 语句创建的服务器定义会存储在 <code>mysql.servers</code> 表中。当创建 <code>FEDERATED</code> 表时,可以使用这个表中的信息来建立与远程服务器的连接。</p><p>例如,创建一个服务器定义的语句可能如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> SERVER s <span class="keyword">FOREIGN</span> DATA WRAPPER mysql</span><br><span class="line">OPTIONS (<span class="keyword">USER</span> <span class="string">&#x27;Remote&#x27;</span>, HOST <span class="string">&#x27;198.51.100.106&#x27;</span>, DATABASE <span class="string">&#x27;test&#x27;</span>);</span><br></pre></td></tr></table></figure><p>然后,可以使用存储在 <code>mysql.servers</code> 表中的信息来创建一个 <code>FEDERATED</code> 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> t (</span><br><span class="line">s1 <span class="type">INT</span></span><br><span class="line">) ENGINE FEDERATED CONNECTION <span class="string">&#x27;s&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这样,<code>FEDERATED</code> 表 <code>t</code> 就可以通过定义的服务器 <code>s</code> 连接到远程服务器上的 <code>test</code> 数据库。</p><p><code>mysql.servers</code> 表的引入,为 MySQL 提供了一种灵活的方式来访问远程服务器上的表,这对于实现数据的分布式存储和访问非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img27.avif"></p><h3 id="slave-master-info"><a href="#slave-master-info" class="headerlink" title="slave_master_info"></a>slave_master_info</h3><p><code>mysql.slave_master_info</code> 表是 MySQL 数据库复制架构中的一个重要系统表,用于存储从服务器 slave 关于其对应的主服务器 master 的信息。这个表的信息通常在执行 <code>CHANGE MASTER TO</code> 命令时被设置,并且在从服务器的 I&#x2F;O 线程启动时被读取。</p><p>以下是 <code>mysql.slave_master_info</code> 表中的一些关键字段:</p><ul><li><strong>Number_of_lines</strong>: 表中的信息行数。</li><li><strong>Master_log_name</strong>: 主服务器上当前读取的二进制日志文件的名称。</li><li><strong>Master_log_pos</strong>: 在上述二进制日志文件中当前读取的位置。</li><li><strong>Host</strong>: 主服务器的主机名或 IP 地址。</li><li><strong>User_name</strong>: 用于连接主服务器的复制用户的用户名。</li><li><strong>User_password</strong>: 复制用户的密码。</li><li><strong>Port</strong>: 主服务器上的端口号。</li><li><strong>Connect_retry</strong>: 从服务器 I&#x2F;O 线程在连接失败后重试连接的间隔时间。</li><li><strong>Enabled_ssl</strong>: 是否启用了 SSL 加密连接。</li><li><strong>Ssl_ca</strong>, <strong>Ssl_capath</strong>, <strong>Ssl_cert</strong>, <strong>Ssl_cipher</strong>, <strong>Ssl_key</strong>: SSL 连接的相关配置。</li><li><strong>Heartbeat</strong>: 复制心跳包的间隔时间。</li><li><strong>Ignored_server_ids</strong>: 指定从服务器在复制过程中应该忽略的服务器 ID 列表。</li><li><strong>Uuid</strong>: 主服务器的 UUID。</li><li><strong>Retry_count</strong>: 从服务器尝试重新连接主服务器的次数。</li><li><strong>Ssl_crl</strong>, <strong>Ssl_crlpath</strong>: SSL 证书撤销列表的配置。</li><li><strong>Enabled_auto_position</strong>: 是否启用了基于 GTID 的自动位置查找功能。</li><li><strong>Channel_name</strong>: 复制通道的名称。</li></ul><p>这个表的信息对于从服务器正确连接到主服务器并开始复制过程至关重要。表中的信息通常由 MySQL 维护,不应手动修改。如果需要修改复制配置,应使用 <code>CHANGE MASTER TO</code> 命令来更新配置,并由系统自动反映到这个表中 。</p><p>在 MySQL 复制过程中,<code>mysql.slave_master_info</code> 表与 <code>mysql.slave_relay_log_info</code> 表和 <code>mysql.slave_worker_info</code> 表一起工作,后两个表分别存储了中继日志信息和多线程复制的相关信息。这些表共同支持了 MySQL 的复制功能,确保了数据从一个服务器到另一个服务器的一致性传输 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img28.avif"></p><h3 id="slave-relay-log-info"><a href="#slave-relay-log-info" class="headerlink" title="slave_relay_log_info"></a>slave_relay_log_info</h3><p><code>mysql.slave_relay_log_info</code> 表在 MySQL 的复制架构中扮演着重要的角色,它用于记录从服务器 slave 的 SQL 线程的位置信息。这个表存储了当前中继日志文件的名称和 SQL 线程读取的位置,以及对应的主服务器 master 的二进制日志文件名称和位置。以下是该表的一些关键信息:</p><ul><li><strong>Number_of_lines</strong>: 表中的信息行数。</li><li><strong>Relay_log_name</strong>: 当前正在使用的中继日志文件的名称。</li><li><strong>Relay_log_pos</strong>: SQL 线程在当前中继日志文件中的位置。</li><li><strong>Master_log_name</strong>: 对应于当前中继日志事件的主服务器的二进制日志文件的名称。</li><li><strong>Master_log_pos</strong>: 对应于当前中继日志事件的主服务器的二进制日志文件中的位置。</li></ul><p>当从服务器的 SQL 线程执行中继日志中的事件时,它会更新这个表中的信息。如果从服务器意外停止,SQL 线程会根据这个表中记录的位置来恢复,确保数据的一致性。</p><p>在 MySQL 5.6 版本之前,复制位点信息通常存储在文件系统中的 <code>relay-log.info</code> 文件中。从 MySQL 5.6 开始,可以设置 <code>relay_log_info_repository</code> 为 <code>TABLE</code>,将这些信息存储在 <code>mysql.slave_relay_log_info</code> 表中,以便使用事务型存储引擎 如 InnoDB 来保证数据的持久性。这样,在从服务器发生故障时,可以更容易地恢复到一个一致的状态。</p><p><code>mysql.slave_relay_log_info</code> 表通常由 MySQL 内部管理,不需要手动编辑。在复制配置中,通常还会涉及到 <code>mysql.slave_master_info</code> 表,它存储了与主服务器相关的连接信息和二进制日志的位置信息。这两个表共同支持了 MySQL 的复制功能,确保了数据从一个服务器到另一个服务器的一致性传输 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img29.avif"></p><h3 id="slave-worker-info"><a href="#slave-worker-info" class="headerlink" title="slave_worker_info"></a>slave_worker_info</h3><p><code>mysql.slave_worker_info</code> 表是在 MySQL 5.7 版本引入的,用于存储关于从服务器上并行复制工作线程的信息。在 MySQL 复制架构中,当配置了并行复制 也称为多线程复制 时,SQL 线程会被拆分为一个协调器线程和多个工作线程。这些工作线程负责并行执行中继日志中的事件。</p><p>以下是 <code>mysql.slave_worker_info</code> 表中的一些关键字段:</p><ul><li><strong>Id</strong>: 工作线程的唯一标识符。</li><li><strong>Relay_log_name</strong>: 工作线程当前正在执行的中继日志文件的名称。</li><li><strong>Relay_log_pos</strong>: 工作线程在当前中继日志文件中的位置。</li><li><strong>Master_log_name</strong>: 对应于工作线程当前执行的中继日志事件的主服务器的二进制日志文件的名称。</li><li><strong>Master_log_pos</strong>: 工作线程在对应主服务器二进制日志文件中的位置。</li><li><strong>Checkpoint_relay_log_name</strong>: 工作线程的检查点中继日志文件的名称。</li><li><strong>Checkpoint_relay_log_pos</strong>: 工作线程的检查点在中继日志文件中的位置。</li><li><strong>Checkpoint_master_log_name</strong>: 工作线程的检查点对应的主服务器二进制日志文件的名称。</li><li><strong>Checkpoint_master_log_pos</strong>: 工作线程的检查点在主服务器二进制日志文件中的位置。</li><li><strong>Checkpoint_seqno</strong>: 工作线程执行的事务的序列号。</li><li><strong>Checkpoint_group_size</strong>: 工作线程的执行队列的大小。</li><li><strong>Checkpoint_group_bitmap</strong>: 表示工作线程已经执行的事务的位图。</li><li><strong>Channel_name</strong>: 复制通道的名称。</li></ul><p>这个表的信息对于监控和故障排除并行复制非常有用。例如,如果从服务器发生故障,<code>mysql.slave_worker_info</code> 表中记录的信息可以帮助确定哪些事务已经被工作线程执行,以及在恢复过程中应该从何处开始重新执行事务。</p><p>在正常情况下,这个表是由 MySQL 内部管理的,不需要手动编辑。它为从服务器的并行复制提供了重要的支持,确保了复制过程的高效性和数据的一致性 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img30.avif"></p><h3 id="slow-log"><a href="#slow-log" class="headerlink" title="slow_log"></a>slow_log</h3><p><code>mysql.slow_log</code> 表是 MySQL 5.6 及更高版本中引入的功能,用于存储慢查询日志。当查询语句的执行时间超过了 <code>long_query_time</code> 指定的阈值,且扫描的行数大于或等于 <code>min_examined_row_limit</code> 时,该查询语句将被记录到慢查询日志中。这个表通常用于分析和优化数据库性能。</p><p>以下是 <code>mysql.slow_log</code> 表中的一些关键字段:</p><ul><li><strong>start_time</strong>: 记录查询开始的时间。</li><li><strong>user_host</strong>: 执行查询的用户名和主机名。</li><li><strong>query_time</strong>: 查询执行的时间。</li><li><strong>lock_time</strong>: 查询执行过程中锁定行的时间。</li><li><strong>rows_sent</strong>: 查询发送给客户端的行数。</li><li><strong>rows_examined</strong>: 查询检查的行数。</li><li><strong>db</strong>: 执行查询的数据库名。</li><li><strong>last_insert_id</strong>: 查询执行后,最后插入行的ID。</li><li><strong>insert_id</strong>: 用于插入操作的ID。</li><li><strong>server_id</strong>: 服务器的唯一ID。</li><li><strong>sql_text</strong>: 执行的查询语句。</li></ul><p>慢查询日志对于数据库管理员来说是非常重要的,因为它可以帮助他们识别和优化那些执行效率低下的查询语句。通过分析慢查询日志,可以发现潜在的性能瓶颈,并采取相应的措施,如添加索引、优化查询语句或调整系统配置。</p><p>默认情况下,慢查询日志是禁用的,需要手动开启。可以通过设置 <code>slow_query_log</code> 系统变量为 <code>ON</code> 来启用慢查询日志,并通过 <code>slow_query_log_file</code> 指定日志文件的存放路径。另外,可以通过 <code>log_output</code> 变量设置慢查询日志的输出位置,可以是 <code>FILE</code> 或 <code>TABLE</code>,或者两者兼有。</p><p>MySQL 还提供了 <code>mysqldumpslow</code> 工具来分析慢查询日志文件,它可以按不同的标准汇总和排序慢查询日志内容,从而帮助快速定位性能问题。</p><p>在某些情况下,可能希望清空慢查询日志,以释放空间或重新开始收集数据。如果是存储在表中,可以重命名旧表并创建一个新表来继续收集慢查询日志。</p><p>慢查询日志是数据库性能调优的重要工具之一,合理使用可以显著提高数据库的响应速度和整体性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img31.avif"></p><h3 id="tables-priv"><a href="#tables-priv" class="headerlink" title="tables_priv"></a>tables_priv</h3><p><code>mysql.tables_priv</code> 表是 MySQL 数据库中的一个系统表,用于存储数据库表级别的权限信息。这个表允许数据库管理员对用户访问特定表的权限进行细粒度的控制。</p><p>以下是 <code>mysql.tables_priv</code> 表中的一些关键字段:</p><ul><li><strong>Host</strong>: 指出允许访问表的主机名或 IP 地址。</li><li><strong>Db</strong>: 指出数据库名。</li><li><strong>User</strong>: 指出用户名。</li><li><strong>Table_name</strong>: 指出表名。</li><li><strong>Grantor</strong>: 指出授予权限的用户。</li><li><strong>Timestamp</strong>: 记录权限被修改的时间戳。</li><li><strong>Table_priv</strong>: 指出授予的表级权限集合,可能包括 SELECT、INSERT、UPDATE、DELETE、CREATE、DROP、GRANT、REFERENCES、INDEX、ALTER、CREATE VIEW、SHOW VIEW、TRIGGER 等权限。</li><li><strong>Column_priv</strong>: 指出授予的列级权限集合,可能包括 SELECT、INSERT、UPDATE、REFERENCES 等权限。</li></ul><p>通过 <code>GRANT</code> 和 <code>REVOKE</code> 语句可以修改这个表中的权限信息。例如,可以通过以下 SQL 语句给用户授予对特定表的 SELECT 权限:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span> <span class="keyword">ON</span> database_name.table_name <span class="keyword">TO</span> <span class="string">&#x27;username&#x27;</span> <span class="string">&#x27;hostname&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个表的信息通常由 MySQL 的授权管理过程自动维护,不需要手动编辑。它为数据库管理员提供了一个强大的工具,以确保数据的安全性和适当的访问控制 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img32.avif"></p><h3 id="time-zone"><a href="#time-zone" class="headerlink" title="time_zone"></a>time_zone</h3><p><code>mysql.time_zone</code> 表是 MySQL 数据库中用于存储时区信息的系统表之一。它通常与 <code>mysql.time_zone_name</code>、<code>mysql.time_zone_transitions</code> 和 <code>mysql.time_zone_leap_second</code> 表一起使用,以提供关于时区的完整信息。</p><p>以下是 <code>mysql.time_zone</code> 表的一些关键字段:</p><ul><li><strong>Time_zone_id</strong>: 时区的唯一标识符。</li><li><strong>Use_leap_seconds</strong>: 一个枚举值,表示该时区是否使用闰秒 ‘Y’ 表示使用,’N’ 表示不使用 。</li></ul><p>这个表通常在系统安装 MySQL 时自动填充,或者可以通过使用 <code>mysql_tzinfo_to_sql</code> 工具从操作系统的时区数据库 如 <code>/usr/share/zoneinfo</code> 导入时区信息来填充。</p><p>在 MySQL 中,时区信息对于处理时间相关的函数和存储时间类型的数据 如 <code>TIMESTAMP</code> 和 <code>DATETIME</code> 至关重要。例如,<code>NOW()</code>、<code>CURTIME()</code> 等函数返回的值会根据当前会话的时区设置进行调整。</p><p>默认情况下,<code>mysql.time_zone</code> 表可能不包含任何记录,您可以通过 <code>mysql_tzinfo_to_sql</code> 工具添加时区信息。此外,还可以使用 <code>SET time_zone</code> 命令在运行时设置会话或全局时区。</p><p>值得注意的是,如果您的系统不支持时区,或者您需要确保 MySQL 与其他应用程序在时区处理上保持一致,可能需要手动填充这些时区表。您可以从 MySQL 官方网站下载时区表的 SQL 文件,并将其导入到数据库中。</p><p>在处理时区问题时,建议明确设置时区 例如 <code>&#39; 08:00&#39;</code> 或 <code>&#39;Asia/Shanghai&#39;</code> ,避免使用 <code>&#39;SYSTEM&#39;</code> 选项,因为这可能会导致时区计算依赖于操作系统设置,从而可能引入错误或性能问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img33.avif"></p><h3 id="time-zone-leap-second"><a href="#time-zone-leap-second" class="headerlink" title="time_zone_leap_second"></a>time_zone_leap_second</h3><p><code>mysql.time_zone_leap_second</code> 表是 MySQL 系统表之一,用于存储时区信息中涉及闰秒的数据。闰秒是用于调整地球自转速度变化的一种时间校正,通常在有必要的时候添加到协调世界时 UTC 中。这个表通常在系统安装 MySQL 时自动创建,但默认是空的,因为大多数情况下系统时区可以处理闰秒问题。</p><p>在 <code>mysql.time_zone_leap_second</code> 表中,包含以下字段:</p><ul><li><strong>Transition_time</strong>: 表示闰秒添加的时刻,用时间戳表示。</li><li><strong>Correction</strong>: 表示闰秒的修正值,通常是 1 或 -1 秒。</li></ul><p>这个表在使用时通常与其他时区相关的表一起使用,例如 <code>mysql.time_zone_name</code>、<code>mysql.time_zone</code>、<code>mysql.time_zone_transition</code> 和 <code>mysql.time_zone_transition_type</code> 表,以提供完整的时区信息。如果需要考虑闰秒,可以使用 <code>mysql_tzinfo_to_sql</code> 工具来填充这个表。</p><p>在 MariaDB 10.4 及更高版本中,<code>mysql.time_zone_leap_second</code> 表使用 Aria 存储引擎。而在 MariaDB 10.3 及之前的版本中,使用的是 MyISAM 存储引擎 。</p><p>需要注意的是,如果系统没有自己的时区信息数据库 例如 Windows ,可以使用包含 SQL 语句的包来填充时区表,这些包可以从 MySQL 官方网站下载。如果系统有自己的时区数据库,则应使用 <code>mysql_tzinfo_to_sql</code> 工具来加载时区表,以避免 MySQL 与其他应用程序在日期时间处理上存在差异 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img34.avif"></p><h3 id="time-zone-name"><a href="#time-zone-name" class="headerlink" title="time_zone_name"></a>time_zone_name</h3><p><code>mysql.time_zone_name</code> 表是 MySQL 数据库中用于存储时区名称和时区 ID 的映射关系的系统表。这个表通常与 <code>mysql.time_zone</code>、<code>mysql.time_zone_transitions</code> 和 <code>mysql.time_zone_leap_second</code> 表一起使用,以提供完整的时区信息。</p><p>以下是 <code>mysql.time_zone_name</code> 表中的字段:</p><ul><li><strong>Name</strong>: 时区的名称,例如 <code>America/New_York</code> 或 <code>Asia/Shanghai</code>。这个名称对应于 <code>time_zone</code> 系统变量的有效值之一 。</li><li><strong>Time_zone_id</strong>: 关联的时区 ID,这个 ID 用于在其他时区相关的表中引用特定的时区。</li></ul><p>默认情况下,<code>mysql.time_zone_name</code> 表可能是空的,因为它依赖于系统时区数据库或手动导入的时区数据。如果需要,可以使用 <code>mysql_tzinfo_to_sql</code> 工具从操作系统的时区数据库填充这个表 。</p><p>填充时区表后,MySQL 能够正确处理与时区相关的函数和存储时间类型的数据。这对于确保跨时区的应用程序能够正确地存储和显示时间至关重要 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img35.avif"></p><h3 id="time-zone-transition"><a href="#time-zone-transition" class="headerlink" title="time_zone_transition"></a>time_zone_transition</h3><p><code>mysql.time_zone_transition</code> 表是 MySQL 数据库中的一个系统表,用于记录时区转换信息。这个表通常与 <code>mysql.time_zone_name</code>、<code>mysql.time_zone</code>、<code>mysql.time_zone_transition_type</code> 和 <code>mysql.time_zone_leap_second</code> 表一起使用,以提供完整的时区信息。</p><p>以下是 <code>mysql.time_zone_transition</code> 表中的字段:</p><ul><li><strong>Time_zone_id</strong>: 时区的唯一标识符,与 <code>mysql.time_zone_name</code> 表中的 <code>Time_zone_id</code> 字段相对应。</li><li><strong>Transition_time</strong>: 时区转换的时间点,通常表示为 Unix 时间戳 格林威治标准时间 。</li><li><strong>Transition_type_id</strong>: 时区转换类型的 ID,与 <code>mysql.time_zone_transition_type</code> 表中的 <code>Transition_type_id</code> 字段相对应。</li></ul><p>这个表的信息对于处理历史时区变化和夏令时转换非常重要,它确保了时间相关的查询可以正确地考虑这些变化。默认情况下,这个表可能不包含任何记录,需要通过 <code>mysql_tzinfo_to_sql</code> 工具从操作系统的时区数据库导入时区信息来填充。</p><p>例如,你可以使用以下 SQL 语句查询 <code>mysql.time_zone_transition</code> 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.time_zone_transition;</span><br></pre></td></tr></table></figure><p>这将返回时区转换的记录,包括时区 ID、转换时间和转换类型 ID。</p><p><code>mysql.time_zone_transition</code> 表使用 Aria 存储引擎,并且在 MySQL 8.0 版本中引入。这个表对于确保跨时区的应用程序能够正确地存储和显示时间至关重要 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img36.avif"></p><h3 id="time-zone-transition-type"><a href="#time-zone-transition-type" class="headerlink" title="time_zone_transition_type"></a>time_zone_transition_type</h3><p><code>mysql.time_zone_transition_type</code> 表是 MySQL 系统表之一,用于存储时区转换类型的详细信息。这个表通常与 <code>mysql.time_zone_name</code>、<code>mysql.time_zone</code>、<code>mysql.time_zone_transitions</code> 和 <code>mysql.time_zone_leap_second</code> 表一起使用,以提供完整的时区信息。</p><p>以下是 <code>mysql.time_zone_transition_type</code> 表中的字段:</p><ul><li><strong>Time_zone_id</strong>: 时区的唯一标识符,与 <code>mysql.time_zone_name</code> 表中的 <code>Time_zone_id</code> 字段相对应。</li><li><strong>Transition_type_id</strong>: 时区转换类型的唯一标识符。</li><li><strong>Offset</strong>: 时区相对于协调世界时 UTC 的偏移量,单位为秒。</li><li><strong>Is_DST</strong>: 表示当前时区是否为夏令时的标识,通常 <code>1</code> 表示是夏令时,<code>0</code> 表示不是。</li><li><strong>Abbreviation</strong>: 时区的缩写,例如 EST 代表东部标准时间, PST 代表太平洋标准时间。</li></ul><p>这个表的信息对于处理历史时区变化和夏令时转换非常重要,它确保了时间相关的查询可以正确地考虑这些变化。默认情况下,这个表可能不包含任何记录,需要通过 <code>mysql_tzinfo_to_sql</code> 工具从操作系统的时区数据库导入时区信息来填充。</p><p>例如,你可以使用以下 SQL 语句查询 <code>mysql.time_zone_transition_type</code> 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> mysql.time_zone_transition_type;</span><br></pre></td></tr></table></figure><p>这将返回时区转换类型的记录,包括时区 ID、转换类型 ID、偏移量、是否为夏令时以及时区缩写。</p><p><code>mysql.time_zone_transition_type</code> 表使用 Aria 存储引擎,并且在 MySQL 8.0 版本中引入。这个表对于确保跨时区的应用程序能够正确地存储和显示时间至关重要 。</p><h3 id="user"><a href="#user" class="headerlink" title="user"></a>user</h3><p><code>mysql.user</code> 表是 MySQL 数据库中非常重要的系统表,它存储了数据库用户的账户信息和权限。这个表中的信息决定了哪些用户可以连接到 MySQL 服务器,以及他们可以执行哪些操作。</p><p>以下是 <code>mysql.user</code> 表中的一些关键字段:</p><ul><li><strong>Host</strong>: 用户所在的主机。MySQL 使用这个字段来限制只有来自特定主机的用户才能连接到服务器。这个字段可以是具体的主机名,如 <code>localhost</code>,或者是一个 IP 地址,或者是使用通配符的模式,如 <code>%</code> 表示任何主机。</li><li><strong>User</strong>: 用户名,用于- <strong>authentication_string</strong>: 存储用户密码的字段。在 MySQL 5.7.6 之前的版本中,密码通常以明文或加密形式存储在 <code>Password</code> 字段中。从 MySQL 5.7.6 开始,推荐使用 <code>authentication_string</code> 字段存储密码,它支持更安全的身份验证插件和方法。</li><li><strong>Password</strong>: 在旧版本中用于存储密码的字段。从安全角度考虑,现在建议使用 <code>authentication_string</code> 字段。</li><li><strong>Select_priv</strong>: 是否允许用户执行 <code>SELECT</code> 语句。</li><li><strong>Insert_priv</strong>: 是否允许用户执行 <code>INSERT</code> 语句。</li><li><strong>Update_priv</strong>: 是否允许用户执行 <code>UPDATE</code> 语句。</li><li><strong>Delete_priv</strong>: 是否允许用户执行 <code>DELETE</code> 语句。</li><li><strong>Create_priv</strong>: 是否允许用户创建新数据库和表。</li><li><strong>Drop_priv</strong>: 是否允许用户删除数据库和表。</li><li><strong>Grant_priv</strong>: 是否允许用户授予或撤销其他用户的权限。</li><li><strong>References_priv</strong>: 是否允许用户创建外键。</li><li><strong>Index_priv</strong>: 是否允许用户创建或删除索引。</li><li><strong>Alter_priv</strong>: 是否允许用户修改表结构。</li><li><strong>Create_tmp_table_priv</strong>: 是否允许用户创建临时表。</li><li><strong>Lock_tables_priv</strong>: 是否允许用户锁定表。</li><li><strong>Create_view_priv</strong>: 是否允许用户创建视图。</li><li><strong>Show_view_priv</strong>: 是否允许用户查看视图定义。</li><li><strong>Create_routine_priv</strong>: 是否允许用户创建存储过程和函数。</li><li><strong>Alter_routine_priv</strong>: 是否允许用户修改存储过程和函数。</li><li><strong>Execute_priv</strong>: 是否允许用户执行存储过程和函数。</li></ul><p>这些字段中的权限可以单独设置,也可以通过 <code>GRANT</code> 和 <code>REVOKE</code> 语句来修改。<code>mysql.user</code> 表中的信息通常由 MySQL 的授权管理过程自动维护,不需要手动编辑。</p><p>管理员可以使用 <code>CREATE USER</code>、<code>GRANT</code>、<code>REVOKE</code>、<code>SET PASSWORD</code> 等语句来管理用户权限。例如,创建一个新用户并授予权限的语句可能如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">USER</span> <span class="string">&#x27;newuser&#x27;</span> <span class="string">&#x27;localhost&#x27;</span> IDENTIFIED <span class="keyword">BY</span> <span class="string">&#x27;password&#x27;</span>;</span><br><span class="line"><span class="keyword">GRANT</span> <span class="keyword">ALL</span> PRIVILEGES <span class="keyword">ON</span> database_name.<span class="operator">*</span> <span class="keyword">TO</span> <span class="string">&#x27;newuser&#x27;</span> <span class="string">&#x27;localhost&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将创建一个新用户 <code>newuser</code>,并授予他们对 <code>database_name</code> 数据库中所有表的所有权限。</p><p><code>mysql.user</code> 表是 MySQL 权限系统的核心,确保了数据库的安全性和适当的访问控制。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-25/img37.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/25/bd20fbdf/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL内置数据库】information_schema</title>
      <link>https://blog.eucalyptus.cc/2024/09/24/d6f9f2fc/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/24/d6f9f2fc/</guid>
      <pubDate>Tue, 24 Sep 2024 07:20:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;MySQL8.0.37&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3 id=&quot;统计&quot;&gt;&lt;a href=&quot;#统计&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><p><strong>MySQL8.0.37</strong></p></blockquote><h3 id="统计"><a href="#统计" class="headerlink" title="统计"></a>统计</h3><table><thead><tr><th>序号</th><th>表名</th></tr></thead><tbody><tr><td>1</td><td>ADMINISTRABLE_ROLE_AUTHORIZATIONS</td></tr><tr><td>2</td><td>APPLICABLE_ROLES</td></tr><tr><td>3</td><td>CHARACTER_SETS</td></tr><tr><td>4</td><td>CHECK_CONSTRAINTS</td></tr><tr><td>5</td><td>COLLATIONS</td></tr><tr><td>6</td><td>COLLATION_CHARACTER_SET_APPLICABILITY</td></tr><tr><td>7</td><td>COLUMNS</td></tr><tr><td>8</td><td>COLUMNS_EXTENSIONS</td></tr><tr><td>9</td><td>COLUMN_PRIVILEGES</td></tr><tr><td>10</td><td>COLUMN_STATISTICS</td></tr><tr><td>11</td><td>ENABLED_ROLES</td></tr><tr><td>12</td><td>ENGINES</td></tr><tr><td>13</td><td>EVENTS</td></tr><tr><td>14</td><td>FILES</td></tr><tr><td>15</td><td>INNODB_BUFFER_PAGE</td></tr><tr><td>16</td><td>INNODB_BUFFER_PAGE_LRU</td></tr><tr><td>17</td><td>INNODB_BUFFER_POOL_STATS</td></tr><tr><td>18</td><td>INNODB_CACHED_INDEXES</td></tr><tr><td>19</td><td>INNODB_CMP</td></tr><tr><td>20</td><td>INNODB_CMPMEM</td></tr><tr><td>21</td><td>INNODB_CMPMEM_RESET</td></tr><tr><td>22</td><td>INNODB_CMP_PER_INDEX</td></tr><tr><td>23</td><td>INNODB_CMP_PER_INDEX_RESET</td></tr><tr><td>24</td><td>INNODB_CMP_RESET</td></tr><tr><td>25</td><td>INNODB_COLUMNS</td></tr><tr><td>26</td><td>INNODB_DATAFILES</td></tr><tr><td>27</td><td>INNODB_FIELDS</td></tr><tr><td>28</td><td>INNODB_FOREIGN</td></tr><tr><td>29</td><td>INNODB_FOREIGN_COLS</td></tr><tr><td>30</td><td>INNODB_FT_BEING_DELETED</td></tr><tr><td>31</td><td>INNODB_FT_CONFIG</td></tr><tr><td>32</td><td>INNODB_FT_DEFAULT_STOPWORD</td></tr><tr><td>33</td><td>INNODB_FT_DELETED</td></tr><tr><td>34</td><td>INNODB_FT_INDEX_CACHE</td></tr><tr><td>35</td><td>INNODB_FT_INDEX_TABLE</td></tr><tr><td>36</td><td>INNODB_INDEXES</td></tr><tr><td>37</td><td>INNODB_METRICS</td></tr><tr><td>38</td><td>INNODB_SESSION_TEMP_TABLESPACES</td></tr><tr><td>39</td><td>INNODB_TABLES</td></tr><tr><td>40</td><td>INNODB_TABLESPACES</td></tr><tr><td>41</td><td>INNODB_TABLESPACES_BRIEF</td></tr><tr><td>42</td><td>INNODB_TABLESTATS</td></tr><tr><td>43</td><td>INNODB_TEMP_TABLE_INFO</td></tr><tr><td>44</td><td>INNODB_TRX</td></tr><tr><td>45</td><td>INNODB_VIRTUAL</td></tr><tr><td>46</td><td>KEYWORDS</td></tr><tr><td>47</td><td>KEY_COLUMN_USAGE</td></tr><tr><td>48</td><td>OPTIMIZER_TRACE</td></tr><tr><td>49</td><td>PARAMETERS</td></tr><tr><td>50</td><td>PARTITIONS</td></tr><tr><td>51</td><td>PLUGINS</td></tr><tr><td>52</td><td>PROCESSLIST</td></tr><tr><td>53</td><td>PROFILING</td></tr><tr><td>54</td><td>REFERENTIAL_CONSTRAINTS</td></tr><tr><td>55</td><td>RESOURCE_GROUPS</td></tr><tr><td>56</td><td>ROLE_COLUMN_GRANTS</td></tr><tr><td>57</td><td>ROLE_ROUTINE_GRANTS</td></tr><tr><td>58</td><td>ROLE_TABLE_GRANTS</td></tr><tr><td>59</td><td>ROUTINES</td></tr><tr><td>60</td><td>SCHEMATA</td></tr><tr><td>61</td><td>SCHEMATA_EXTENSIONS</td></tr><tr><td>62</td><td>SCHEMA_PRIVILEGES</td></tr><tr><td>63</td><td>STATISTICS</td></tr><tr><td>64</td><td>ST_GEOMETRY_COLUMNS</td></tr><tr><td>65</td><td>ST_SPATIAL_REFERENCE_SYSTEMS</td></tr><tr><td>66</td><td>ST_UNITS_OF_MEASURE</td></tr><tr><td>67</td><td>TABLES</td></tr><tr><td>68</td><td>TABLESPACES</td></tr><tr><td>69</td><td>TABLESPACES_EXTENSIONS</td></tr><tr><td>70</td><td>TABLES_EXTENSIONS</td></tr><tr><td>71</td><td>TABLE_CONSTRAINTS</td></tr><tr><td>72</td><td>TABLE_CONSTRAINTS_EXTENSIONS</td></tr><tr><td>73</td><td>TABLE_PRIVILEGES</td></tr></tbody></table><h3 id="ADMINISTRABLE-ROLE-AUTHORIZATIONS"><a href="#ADMINISTRABLE-ROLE-AUTHORIZATIONS" class="headerlink" title="ADMINISTRABLE_ROLE_AUTHORIZATIONS"></a>ADMINISTRABLE_ROLE_AUTHORIZATIONS</h3><p><code>ADMINISTRABLE_ROLE_AUTHORIZATIONS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关当前用户或角色可以授予给其他用户或角色的角色的信息。这个表在 MySQL 8.0.19 及以后的版本中可用。此表包含以下列:</p><ul><li><code>USER</code>: 当前用户账户的用户名部分。</li><li><code>HOST</code>: 当前用户账户的主机名部分。</li><li><code>GRANTEE</code>: 被授予角色的账户的用户名部分。</li><li><code>GRANTEE_HOST</code>: 被授予角色的账户的主机名部分。</li><li><code>ROLE_NAME</code>: 被授予角色的用户名部分。</li><li><code>ROLE_HOST</code>: 被授予角色的主机名部分。</li><li><code>IS_GRANTABLE</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示该角色是否可以授予给其他账户。</li><li><code>IS_DEFAULT</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示角色是否为默认角色。</li><li><code>IS_MANDATORY</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示角色是否是强制性的。</li></ul><p>这个表对于数据库管理员来说是有价值的,因为它可以帮助他们理解和管理数据库中的角色和权限。例如,管理员可以使用此表来确定哪些角色可以被特定用户授予,以及这些角色的授予权限情况。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img1.avif"></p><h3 id="APPLICABLE-ROLES"><a href="#APPLICABLE-ROLES" class="headerlink" title="APPLICABLE_ROLES"></a>APPLICABLE_ROLES</h3><p><code>APPLICABLE_ROLES</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关当前用户或启用的角色的所有适用角色的信息。这个表在 MySQL 8.0.19 及以后的版本中可用。此表包含以下列:</p><ul><li><code>USER</code>: 当前用户账户的用户名部分。</li><li><code>HOST</code>: 当前用户账户的主机名部分。</li><li><code>GRANTEE</code>: 角色被授予的账户的用户名部分。</li><li><code>GRANTEE_HOST</code>: 授予角色的账户的主机名部分。</li><li><code>ROLE_NAME</code>: 授予角色的用户名部分。</li><li><code>ROLE_HOST</code>: 授予角色的主机名部分。</li><li><code>IS_GRANTABLE</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示该角色是否可以授予给其他账户。</li><li><code>IS_DEFAULT</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示角色是否为默认角色。</li><li><code>IS_MANDATORY</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,表示角色是否是强制性的。</li></ul><p>这个表对于数据库管理员来说是有价值的,因为它可以帮助他们理解和管理数据库中的角色和权限。例如,管理员可以使用此表来确定哪些角色适用于当前用户,以及这些角色的授予权限情况。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img2.avif"></p><h3 id="CHARACTER-SETS"><a href="#CHARACTER-SETS" class="headerlink" title="CHARACTER_SETS"></a>CHARACTER_SETS</h3><p><code>CHARACTER_SETS</code> 表是 MySQL 的 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 MySQL 服务器支持的字符集的信息。以下是 <code>CHARACTER_SETS</code> 表中的一些关键列及其描述:</p><ul><li><code>CHARACTER_SET_NAME</code>: 字符集的名称。</li><li><code>DEFAULT_COLLATE_NAME</code>: 字符集的默认排序规则 collation 。</li><li><code>DESCRIPTION</code>: 字符集的描述性文字。</li><li><code>MAXLEN</code>: 存储一个字符所需的最大字节数。</li></ul><p>该表列出了 MySQL 服务器支持的所有字符集及其相关信息。例如,<code>utf8mb4</code> 是一种常用的字符集,支持存储任意 Unicode 字符,而 <code>latin1</code> 是一种西欧语言的字符集。通过查询这个表,可以了解服务器上可用的不同字符集及其属性。</p><p>要查看 MySQL 中的字符集信息,除了查询 <code>CHARACTER_SETS</code> 表外,还可以使用 <code>SHOW CHARACTER SET</code> 语句。这些方法提供了一个关于服务器支持的字符集的概览,这对于处理国际化应用程序和数据迁移非常重要。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img3.avif"></p><h3 id="CHECK-CONSTRAINTS"><a href="#CHECK-CONSTRAINTS" class="headerlink" title="CHECK_CONSTRAINTS"></a>CHECK_CONSTRAINTS</h3><p><code>CHECK_CONSTRAINTS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关表或列上的 <code>CHECK</code> 约束的信息。从 MySQL 8.0.16 版本开始,<code>CREATE TABLE</code> 语句允许使用 <code>CHECK</code> 约束,这些约束用于确保表中的数据满足一定的条件。<code>CHECK_CONSTRAINTS</code> 表包含了这些约束的详细信息,具体列如下:</p><ul><li><code>CONSTRAINT_CATALOG</code>: 约束所属目录的名称,对于 MySQL,这个值通常是 <code>def</code>。</li><li><code>CONSTRAINT_SCHEMA</code>: 约束所属的数据库 模式 的名称。</li><li><code>CONSTRAINT_NAME</code>: 约束的名称。</li><li><code>CHECK_CLAUSE</code>: 定义约束条件的表达式。</li></ul><p>这个表可以用来查询数据库中所有 <code>CHECK</code> 约束的详细信息,包括约束名称、所属表、以及约束的具体条件。这对于数据库管理员在进行数据完整性管理时非常有用。</p><p>例如,如果你想查看某个特定表的所有 <code>CHECK</code> 约束,你可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONSTRAINT_NAME, CHECK_CLAUSE</span><br><span class="line"><span class="keyword">FROM</span> information_schema.CHECK_CONSTRAINTS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回指定表的所有 <code>CHECK</code> 约束及其条件表达式。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img4.avif"></p><h3 id="COLLATIONS"><a href="#COLLATIONS" class="headerlink" title="COLLATIONS"></a>COLLATIONS</h3><p><code>COLLATIONS</code> 表是 MySQL 的 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关每个字符集的排序规则 collation 的信息。以下是 <code>COLLATIONS</code> 表中的一些关键列及其描述:</p><ul><li><code>COLLATION_NAME</code>: 排序规则的名称。</li><li><code>CHARACTER_SET_NAME</code>: 与排序规则关联的字符集名称。</li><li><code>ID</code>: 排序规则的唯一标识符 ID 。</li><li><code>IS_DEFAULT</code>: 表示这个排序规则是否是其字符集的默认排序规则,<code>YES</code> 或 <code>NO</code>。</li><li><code>IS_COMPILED</code>: 表示这个排序规则是否被编译到 MySQL 服务器中,<code>YES</code> 或 <code>NO</code>。</li><li><code>SORTLEN</code>: 与排序操作相关的内存长度要求。</li></ul><p>排序规则定义了字符数据如何比较和排序。例如,某些排序规则可能是大小写敏感的,而其他排序规则可能是大小写不敏感的。排序规则通常与字符集一起使用,以确保数据的正确处理和显示。</p><p>要查询 <code>COLLATIONS</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> COLLATION_NAME, CHARACTER_SET_NAME, IS_DEFAULT, IS_COMPILED, SORTLEN</span><br><span class="line"><span class="keyword">FROM</span> information_schema.COLLATIONS;</span><br></pre></td></tr></table></figure><p>这个查询将返回服务器上所有可用排序规则的列表,以及每个规则所属的字符集和一些属性。</p><p>排序规则的信息也可以通过 <code>SHOW COLLATION</code> 语句获得。例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> <span class="keyword">COLLATION</span> <span class="keyword">WHERE</span> Charset <span class="string">&#x27;utf8mb4&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示所有 <code>utf8mb4</code> 字符集的排序规则。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img5.avif"></p><h3 id="COLLATION-CHARACTER-SET-APPLICABILITY"><a href="#COLLATION-CHARACTER-SET-APPLICABILITY" class="headerlink" title="COLLATION_CHARACTER_SET_APPLICABILITY"></a>COLLATION_CHARACTER_SET_APPLICABILITY</h3><p><code>COLLATION_CHARACTER_SET_APPLICABILITY</code> 表是 MySQL 的 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它指示了哪个字符集适用于哪个排序规则 collation 。这个表在 MySQL 8.0.11 及以后的版本中可用。此表包含以下列:</p><ul><li><code>COLLATION_NAME</code>: 排序规则的名称。</li><li><code>CHARACTER_SET_NAME</code>: 与排序规则关联的字符集名称。</li></ul><p>这个表可以用来查询数据库中所有可用的排序规则及其对应的字符集。这对于数据库管理员在进行数据排序和国际化处理时非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img6.avif"></p><h3 id="COLUMNS"><a href="#COLUMNS" class="headerlink" title="COLUMNS"></a>COLUMNS</h3><p><code>COLUMNS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于数据库中所有表的列的信息。这个表对于查询和管理数据库结构非常有用,可以帮助您了解每个表中的列定义、数据类型、约束等细节。</p><p>以下是 <code>COLUMNS</code> 表的一些主要列及其含义:</p><ul><li><code>TABLE_CATALOG</code>: 包含列的表所属的目录的名称,通常为 <code>def</code>。</li><li><code>TABLE_SCHEMA</code>: 包含列的表所属的数据库 模式 的名称。</li><li><code>TABLE_NAME</code>: 包含列的表的名称。</li><li><code>COLUMN_NAME</code>: 列的名称。</li><li><code>ORDINAL_POSITION</code>: 列在表中的顺序位置,从1开始。</li><li><code>COLUMN_DEFAULT</code>: 列的默认值。</li><li><code>IS_NULLABLE</code>: 是否允许NULL值,可以是 <code>YES</code> 或 <code>NO</code>。</li><li><code>DATA_TYPE</code>: 列的数据类型,如 <code>int</code>, <code>varchar</code>, <code>datetime</code> 等。</li><li><code>CHARACTER_MAXIMUM_LENGTH</code>: 对于字符类型,此列的最大长度。</li><li><code>CHARACTER_OCTET_LENGTH</code>: 对于字符类型,此列的最大字节长度。</li><li><code>NUMERIC_PRECISION</code>: 对于数值类型,精度 总位数 。</li><li><code>NUMERIC_SCALE</code>: 对于数值类型,小数位数。</li><li><code>DATETIME_PRECISION</code>: 对于日期和时间类型,精度 小数点后的位数 。</li><li><code>CHARACTER_SET_NAME</code>: 字符集名称。</li><li><code>COLLATION_NAME</code>: 排序规则名称。</li><li><code>COLUMN_TYPE</code>: 列的完整类型定义,包括类型和约束。</li><li><code>COLUMN_KEY</code>: 列的键类型,可以是 <code>PRI</code> 主键 、<code>MUL</code> 多值索引 等。</li><li><code>EXTRA</code>: 列的附加信息,如 <code>AUTO_INCREMENT</code>, <code>ON UPDATE CURRENT_TIMESTAMP</code> 等。</li><li><code>PRIVILEGES</code>: 列的权限,如 <code>SELECT</code>, <code>INSERT</code>, <code>UPDATE</code>, <code>REFERENCES</code> 等。</li><li><code>COLUMN_COMMENT</code>: 列的注释。</li></ul><p>通过查询 <code>COLUMNS</code> 表,您可以获取特定数据库或表的列信息。例如,要获取特定数据库中的所有表和列信息,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> TABLE_NAME, COLUMN_NAME, DATA_TYPE, CHARACTER_MAXIMUM_LENGTH</span><br><span class="line"><span class="keyword">FROM</span> information_schema.COLUMNS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>要获取特定表的所有列信息,可以使用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">FROM</span> information_schema.COLUMNS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这些查询将返回表的列信息,包括列名、数据类型、是否允许为空、默认值等。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img7.avif"></p><h3 id="COLUMNS-EXTENSIONS"><a href="#COLUMNS-EXTENSIONS" class="headerlink" title="COLUMNS_EXTENSIONS"></a>COLUMNS_EXTENSIONS</h3><p><code>COLUMNS_EXTENSIONS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,从 MySQL 8.0.21 版本开始提供。它提供有关数据库表列的扩展属性信息,这些属性是为主存储引擎和辅助存储引擎定义的。</p><p>以下是 <code>COLUMNS_EXTENSIONS</code> 表的列及其描述:</p><ul><li><code>TABLE_CATALOG</code>: 表所属目录的名称,此值始终为 <code>def</code> 。</li><li><code>TABLE_SCHEMA</code>: 表所属的数据库 模式 的名称。</li><li><code>TABLE_NAME</code>: 表的名称。</li><li><code>COLUMN_NAME</code>: 列的名称。</li><li><code>ENGINE_ATTRIBUTE</code>: 为主存储引擎定义的列属性。这个属性是保留以供将来使用的 。</li><li><code>SECONDARY_ENGINE_ATTRIBUTE</code>: 为辅助存储引擎定义的列属性。这个属性也是保留以供将来使用的 。</li></ul><p>这个表目前主要保留供将来使用,当前版本中这些列属性可能不包含实际的数据,但是它们为MySQL未来版本的存储引擎扩展提供了基础架构。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img8.avif"></p><h3 id="COLUMN-PRIVILEGES"><a href="#COLUMN-PRIVILEGES" class="headerlink" title="COLUMN_PRIVILEGES"></a>COLUMN_PRIVILEGES</h3><p><code>COLUMN_PRIVILEGES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关列权限的信息。这些信息是从 <code>mysql.columns_priv</code> 系统表中获取的。以下是 <code>COLUMN_PRIVILEGES</code> 表中的一些关键列及其描述:</p><ul><li><code>GRANTEE</code>: 授予权限的账户的名称,格式为 <code>&#39;user_name&#39; &#39;host_name&#39;</code>。</li><li><code>TABLE_CATALOG</code>: 包含该列的表所属目录的名称,此值总是 <code>def</code>。</li><li><code>TABLE_SCHEMA</code>: 包含该列的表所属的数据库 模式 的名称。</li><li><code>TABLE_NAME</code>: 包含该列的表的名称。</li><li><code>COLUMN_NAME</code>: 列的名称。</li><li><code>PRIVILEGE_TYPE</code>: 授予的权限类型,可以是 <code>SELECT</code>、<code>INSERT</code>、<code>UPDATE</code>、<code>REFERENCES</code> 等。</li><li><code>IS_GRANTABLE</code>: 如果用户具有 <code>GRANT OPTION</code> 权限,则为 <code>YES</code>,否则为 <code>NO</code>。</li></ul><p>这个表可以用来查询数据库中特定列的权限信息,包括哪些用户或角色拥有对这些列的特定权限。例如,如果你想查看某个特定表的所有列权限,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">FROM</span> information_schema.COLUMN_PRIVILEGES</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个查询将返回指定表的所有列权限信息,包括哪些用户有权限访问这些列,以及他们拥有哪些类型的权限。</p><p>需要注意的是,<code>COLUMN_PRIVILEGES</code> 表是一个非标准的 <code>INFORMATION_SCHEMA</code> 表,因此在使用时需要特别注意,例如 <code>SELECT ... FROM INFORMATION_SCHEMA.COLUMN_PRIVILEGES</code> 与 <code>SHOW GRANTS ...</code> 语句的输出并不等效 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img9.avif"></p><h3 id="COLUMN-STATISTICS"><a href="#COLUMN-STATISTICS" class="headerlink" title="COLUMN_STATISTICS"></a>COLUMN_STATISTICS</h3><p>在 MySQL 中,<code>information_schema.COLUMN_STATISTICS</code> 表包含了数据库中每个表的列的统计信息,这些信息通常以直方图的形式存在。直方图是一种统计工具,它提供了关于数据分布的概览,可以帮助数据库优化器更有效地生成查询计划。</p><p>当你执行以下查询时:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> COLUMN_STATISTICS;</span><br></pre></td></tr></table></figure><p>你将看到以下几列:</p><ul><li><strong>SCHEMA_NAME</strong>: 数据库的名称。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>COLUMN_NAME</strong>: 列的名称。</li><li><strong>HISTOGRAM</strong>: 以 JSON 格式存储的直方图数据。</li></ul><p>例如,返回的结果可能如下所示:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"> ------------- ------------ ------------- -----------</span><br><span class="line">| SCHEMA_NAME | TABLE_NAME |</span><br><span class="line">| --- | --- |</span><br><span class="line">| COLUMN_NAME | HISTOGRAM |</span><br><span class="line">| mydatabase | mytable |</span><br><span class="line">| --- | --- |</span><br><span class="line">| mycolumn | &#123;...&#125; |</span><br></pre></td></tr></table></figure><p>其中 <code>HISTOGRAM</code> 列将包含关于 <code>mycolumn</code> 列值分布的统计信息,这些信息以 JSON 对象的形式存储。例如:</p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">buckets <span class="punctuation">:</span> <span class="punctuation">[</span></span><br><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">low_value <span class="punctuation">:</span> <span class="number">10</span> <span class="punctuation">,</span></span><br><span class="line">high_value <span class="punctuation">:</span> <span class="number">20</span> <span class="punctuation">,</span></span><br><span class="line">repeat_count <span class="punctuation">:</span> <span class="number">100</span><span class="punctuation">,</span></span><br><span class="line">null_count <span class="punctuation">:</span> <span class="number">0</span></span><br><span class="line"><span class="punctuation">&#125;</span><span class="punctuation">,</span></span><br><span class="line">...</span><br><span class="line"><span class="punctuation">]</span><span class="punctuation">,</span></span><br><span class="line">null_count <span class="punctuation">:</span> <span class="number">0</span><span class="punctuation">,</span></span><br><span class="line">totalRowCount <span class="punctuation">:</span> <span class="number">1000</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p>在这个 JSON 示例中:</p><ul><li><code>buckets</code>: 包含了一系列的区间 buckets ,每个区间定义了列值的范围 <code>low_value</code> 到 <code>high_value</code> ,以及这个范围内值出现的频率 <code>repeat_count</code> 。</li><li><code>null_count</code>: 列中 NULL 值的数量。</li><li><code>totalRowCount</code>: 表中行的总数。</li></ul><p>直方图数据可以帮助优化器估计查询条件的匹配行数,从而选择最佳的查询执行计划。例如,如果一个查询条件是 <code>mycolumn BETWEEN 10 AND 20</code>,优化器可以使用直方图数据来估计大约有 100 行数据满足这个条件。</p><p>要查看具体的直方图数据,你可以选择特定的列,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> SCHEMA_NAME, TABLE_NAME, COLUMN_NAME, HISTOGRAM</span><br><span class="line"><span class="keyword">FROM</span> information_schema.COLUMN_STATISTICS</span><br><span class="line"><span class="keyword">WHERE</span> SCHEMA_NAME <span class="string">&#x27;mydatabase&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;mytable&#x27;</span> <span class="keyword">AND</span> COLUMN_NAME <span class="string">&#x27;mycolumn&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回 <code>mydatabase</code> 数据库中 <code>mytable</code> 表的 <code>mycolumn</code> 列的统计信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img10.avif"></p><h3 id="ENABLED-ROLES"><a href="#ENABLED-ROLES" class="headerlink" title="ENABLED_ROLES"></a>ENABLED_ROLES</h3><p><code>ENABLED_ROLES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,从 MySQL 8.0.19 版本开始引入。此表提供关于当前会话中启用的角色的信息。每个角色可以包含一组权限,并且可以在用户的当前会话中被激活。</p><p>以下是 <code>ENABLED_ROLES</code> 表的列及其描述:</p><ul><li><code>ROLE_NAME</code>: 授予角色的用户名部分。</li><li><code>ROLE_HOST</code>: 授予角色的主机名部分。</li><li><code>IS_DEFAULT</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,指示角色是否为默认角色。</li><li><code>IS_MANDATORY</code>: 一个 <code>YES</code> 或 <code>NO</code> 值,指示角色是否为强制性角色。</li></ul><p>要查看当前会话中启用的角色,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> ROLE_NAME, ROLE_HOST, IS_DEFAULT, IS_MANDATORY</span><br><span class="line"><span class="keyword">FROM</span> information_schema.ENABLED_ROLES;</span><br></pre></td></tr></table></figure><p>这个查询将返回当前会话中启用的角色的列表,以及每个角色是否是默认角色或强制性角色的信息。默认角色是会话自动激活的角色,而强制性角色是服务器配置为所有用户会话必须激活的角色。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img11.avif"></p><h3 id="ENGINES"><a href="#ENGINES" class="headerlink" title="ENGINES"></a>ENGINES</h3><p><code>ENGINES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了有关 MySQL 服务器支持的存储引擎的信息。这个表对于检查是否支持特定的存储引擎或查看默认引擎是什么特别有用。</p><p>以下是 <code>ENGINES</code> 表中的一些关键列及其描述:</p><ul><li><code>ENGINE</code>: 存储引擎的名称。</li><li><code>SUPPORT</code>: 服务器对存储引擎的支持程度。可能的值包括 <code>YES</code> 引擎受支持并处于活动状态 、<code>DEFAULT</code> 除了 <code>YES</code>,还表示这是默认引擎 、<code>NO</code> 引擎不受支持 、<code>DISABLED</code> 引擎受支持但已被禁用 。</li><li><code>COMMENT</code>: 对存储引擎的简要描述。</li><li><code>TRANSACTIONS</code>: 存储引擎是否支持事务。</li><li><code>XA</code>: 存储引擎是否支持 XA 事务。</li><li><code>SAVEPOINTS</code>: 存储引擎是否支持保存点。</li></ul><p>存储引擎是 MySQL 中用于数据存储和检索的底层软件组件。不同的存储引擎针对不同的应用场景进行了优化,例如 <code>InnoDB</code> 存储引擎支持事务、行级锁定和外键,而 <code>MyISAM</code> 存储引擎则提供了高速读取操作但不支持事务。<code>MEMORY</code> 存储引擎将所有数据保存在内存中,适合用于临时表或快速访问的小型数据集。</p><p>要查看 MySQL 中所有可用存储引擎的信息,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.ENGINES;</span><br></pre></td></tr></table></figure><p>这个查询将返回服务器上所有可用存储引擎的列表,以及它们各自的支持级别、描述、事务支持情况等信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img12.avif"></p><h3 id="EVENTS"><a href="#EVENTS" class="headerlink" title="EVENTS"></a>EVENTS</h3><p><code>EVENTS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 MySQL 事件调度器事件的信息。这些事件可以是按照一定频率自动执行的 SQL 语句或存储过程。以下是 <code>EVENTS</code> 表中的一些关键列及其描述:</p><ul><li><code>EVENT_CATALOG</code>: 事件所属目录的名称,此值总是 <code>def</code>。</li><li><code>EVENT_SCHEMA</code>: 事件所属的数据库 模式 的名称。</li><li><code>EVENT_NAME</code>: 事件的名称。</li><li><code>DEFINER</code>: 创建事件的用户,格式为 <code>&#39;user_name&#39; &#39;host_name&#39;</code>。</li><li><code>TIME_ZONE</code>: 事件执行的时区,默认为 <code>SYSTEM</code>,即操作系统使用的时区。</li><li><code>EVENT_BODY</code>: 事件 <code>DO</code> 子句中使用的语言,总是 <code>SQL</code>。</li><li><code>EVENT_DEFINITION</code>: 事件的 <code>DO</code> 子句的文本,即事件执行的 SQL 语句。</li><li><code>EVENT_TYPE</code>: 事件的重复类型,可以是 <code>ONE TIME</code> 一次性 或 <code>RECURRING</code> 重复执行 。</li><li><code>EXECUTE_AT</code>: 对于一次性事件,这是在创建事件的语句中指定的 <code>DATETIME</code> 值。</li><li><code>INTERVAL_VALUE</code>: 如果事件是重复执行的,则为两次执行的时间间隔。</li><li><code>INTERVAL_FIELD</code>: 两次事件执行之间的时间单位。</li><li><code>STARTS</code>: 重复性事件的开始时间。</li><li><code>ENDS</code>: 重复性事件的结束时间。</li><li><code>STATUS</code>: 事件的状态,可以是 <code>ENABLED</code>、<code>DISABLED</code> 或 <code>SLAVESIDE_DISABLED</code>。</li><li><code>ON_COMPLETION</code>: 事件完成后的行为,可以是 <code>PRESERVE</code> 或 <code>NOT PRESERVE</code>。</li><li><code>CREATED</code>: 事件的创建时间。</li><li><code>LAST_ALTERED</code>: 最后一次修改事件的时间。</li><li><code>LAST_EXECUTED</code>: 事件最后一次执行的时间。</li></ul><p>要查看数据库中的事件及其相关信息,可以使用以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> EVENT_NAME, EVENT_DEFINITION, STATUS, LAST_EXECUTED</span><br><span class="line"><span class="keyword">FROM</span> information_schema.EVENTS</span><br><span class="line"><span class="keyword">WHERE</span> EVENT_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个查询将返回指定数据库中所有事件的名称、定义、状态和最后一次执行的时间。通过查询 <code>EVENTS</code> 表,您可以管理和诊断数据库中的定时任务事件。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img13.avif"></p><h3 id="FILES"><a href="#FILES" class="headerlink" title="FILES"></a>FILES</h3><p><code>FILES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了有关存储 MySQL 表空间数据的文件的信息。这个表对于 InnoDB 存储引擎是特别有用的,因为它提供 InnoDB 数据文件的信息。在 NDB Cluster 中,此表还提供有关存储 NDB Cluster 磁盘数据表的文件的信息。</p><p>以下是 <code>FILES</code> 表中的一些关键列及其描述:</p><ul><li><code>FILE_ID</code>: 表空间的 ID。</li><li><code>FILE_NAME</code>: 数据文件的名称。例如,<code>.ibd</code> 文件扩展名用于 file-per-table 和 general 表空间,<code>undo</code> 前缀用于撤消表空间,<code>ibdata</code> 前缀用于系统表空间,<code>ibtmp</code> 前缀用于临时表空间。</li><li><code>FILE_TYPE</code>: 文件的类型,可以是 <code>TABLESPACE</code>、<code>TEMPORARY</code> 或 <code>UNDO LOG</code>。</li><li><code>TABLESPACE_NAME</code>: 表空间的 SQL 名称。</li><li><code>ENGINE</code>: 存储引擎的名称,例如 <code>InnoDB</code> 或 <code>ndbcluster</code>。</li><li><code>FREE_EXTENTS</code>: 当前文件中完全空闲的段的个数。</li><li><code>TOTAL_EXTENTS</code>: 当前文件完全使用的段的个数。</li><li><code>EXTENT_SIZE</code>: 数据文件段的大小。</li><li><code>INITIAL_SIZE</code>: 文件的初始大小。</li><li><code>MAXIMUM_SIZE</code>: 数据文件的最大大小。</li><li><code>AUTOEXTEND_SIZE</code>: 数据文件的自动扩展大小。</li><li><code>DATA_FREE</code>: 整个表空间的剩余大小。</li><li><code>STATUS</code>: 文件的状态,通常为 <code>NORMAL</code>。</li></ul><p>要查询 <code>FILES</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> FILE_NAME, FILE_TYPE, TABLESPACE_NAME, EXTENT_SIZE, INITIAL_SIZE, MAXIMUM_SIZE, AUTOEXTEND_SIZE, DATA_FREE</span><br><span class="line"><span class="keyword">FROM</span> information_schema.FILES</span><br><span class="line"><span class="keyword">WHERE</span> ENGINE <span class="string">&#x27;InnoDB&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 存储引擎的文件信息,包括文件名、类型、表空间名称、段大小、初始大小、最大大小、自动扩展大小和剩余空间。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img14.avif"></p><h3 id="INNODB-BUFFER-PAGE"><a href="#INNODB-BUFFER-PAGE" class="headerlink" title="INNODB_BUFFER_PAGE"></a>INNODB_BUFFER_PAGE</h3><p><code>INNODB_BUFFER_PAGE</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 缓冲池中每个页面的信息。此表对于监控和诊断 InnoDB 缓冲池性能非常有用。以下是该表的一些关键列及其描述:</p><ul><li><code>POOL_ID</code>: 缓冲池的 ID,用于区分多个缓冲池实例。</li><li><code>BLOCK_ID</code>: 缓冲池块的 ID。</li><li><code>SPACE</code>: 表空间 ID,与 <code>INNODB_TABLES.SPACE</code> 相同。</li><li><code>PAGE_NUMBER</code>: 页面编号。</li><li><code>PAGE_TYPE</code>: 页面类型,可能的值包括 <code>INDEX</code>、<code>DATA</code>、<code>SYSTEM</code> 等。</li><li><code>FLUSH_TYPE</code>: 冲洗类型。</li><li><code>FIX_COUNT</code>: 缓冲池中使用该块的线程数。</li><li><code>IS_HASHED</code>: 页面是否建立了哈希索引。</li><li><code>NEWEST_MODIFICATION</code>: 最新的修改的日志序列号。</li><li><code>OLDEST_MODIFICATION</code>: 最早的修改的日志序列号。</li><li><code>ACCESS_TIME</code>: 页面的访问时间。</li><li><code>TABLE_NAME</code>: 页所属表的名称。</li><li><code>INDEX_NAME</code>: 页面所属索引的名称。</li><li><code>NUMBER_RECORDS</code>: 页内的记录数。</li><li><code>DATA_SIZE</code>: 记录大小的总和。</li><li><code>COMPRESSED_SIZE</code>: 压缩页面的大小。</li><li><code>PAGE_STATE</code>: 页面状态,如 <code>FILE_PAGE</code>。</li><li><code>IO_FIX</code>: 页面是否有任何 I&#x2F;O 挂起。</li><li><code>IS_OLD</code>: 该块是否在 LRU 列表中旧块的子列表中。</li><li><code>FREE_PAGE_CLOCK</code>: 当块最后被放置在 LRU 列表的头部时计数器的值。</li><li><code>IS_STALE</code>: 页面是否过时 在 MySQL 8.0.24 中添加 。</li></ul><p>查询此表需要具有 <code>PROCESS</code> 权限。此表主要用于专家级性能监控,或在为 MySQL 开发与性能相关的扩展时使用。当表、表行、分区或索引被删除时,关联的页面将保留在缓冲池中,直到其他数据需要空间为止。该 <code>INNODB_BUFFER_PAGE</code> 表报告有关这些页面的信息,直到它们被从缓冲池中逐出。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img15.avif"></p><h3 id="INNODB-BUFFER-PAGE-LRU"><a href="#INNODB-BUFFER-PAGE-LRU" class="headerlink" title="INNODB_BUFFER_PAGE_LRU"></a>INNODB_BUFFER_PAGE_LRU</h3><p><code>INNODB_BUFFER_PAGE_LRU</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 缓冲池中页面的信息,特别是这些页面在最近最少使用 LRU 列表中的排序方式。这个排序决定了当缓冲池空间不足时,哪些页面应该被逐出缓冲池。</p><p>以下是 <code>INNODB_BUFFER_PAGE_LRU</code> 表中的一些关键列及其描述:</p><ul><li><code>POOL_ID</code>: 缓冲池的 ID,用于区分多个缓冲池实例。</li><li><code>LRU_POSITION</code>: 页面在 LRU 列表中的位置。</li><li><code>SPACE</code>: 表空间 ID,与 <code>INNODB_TABLES.SPACE</code> 相同。</li><li><code>PAGE_NUMBER</code>: 页面编号。</li><li><code>PAGE_TYPE</code>: 页面类型,可能的值包括 <code>INDEX</code>、<code>DATA</code>、<code>SYSTEM</code> 等。</li><li><code>FLUSH_TYPE</code>: 页面的刷新类型。</li><li><code>FIX_COUNT</code>: 固定该页面的线程数量。当此值为零时,该页面有资格被逐出。</li><li><code>IS_HASHED</code>: 页面是否已经建立哈希索引。</li><li><code>NEWEST_MODIFICATION</code>: 页面的最新修改时间。</li><li><code>OLDEST_MODIFICATION</code>: 页面的最旧修改时间。</li><li><code>ACCESS_TIME</code>: 页面的访问时间。</li><li><code>TABLE_NAME</code>: 页面所属的表的名称。</li><li><code>INDEX_NAME</code>: 页面所属的索引的名称。</li><li><code>NUMBER_RECORDS</code>: 页面中的记录数。</li><li><code>DATA_SIZE</code>: 页面中数据的大小。</li><li><code>COMPRESSED_SIZE</code>: 压缩页面的大小。</li><li><code>COMPRESSED</code>: 页面是否被压缩。</li><li><code>IO_FIX</code>: 页面是否有任何挂起的 I&#x2F;O 操作。</li><li><code>IS_OLD</code>: 页面是否在 LRU 列表中的旧页面子列表中。</li><li><code>FREE_PAGE_CLOCK</code>: 页面最后被放置在 LRU 列表头部时的 <code>free_page_clock</code> 计数器的值。</li></ul><p>查询此表通常需要具有 <code>PROCESS</code> 权限,并且可能会对性能产生影响,因此不建议在生产环境中频繁查询此表。如果您需要监控或诊断缓冲池性能,应谨慎使用此表,并在测试环境中重现问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img16.avif"></p><h3 id="INNODB-BUFFER-POOL-STATS"><a href="#INNODB-BUFFER-POOL-STATS" class="headerlink" title="INNODB_BUFFER_POOL_STATS"></a>INNODB_BUFFER_POOL_STATS</h3><p><code>INNODB_BUFFER_POOL_STATS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 缓冲池的统计信息,这些信息与 <code>SHOW ENGINE INNODB STATUS</code> 命令的输出类似。此表包含许多关于 InnoDB 缓冲池的列,可以用于监控和性能调优。</p><p>以下是 <code>INNODB_BUFFER_POOL_STATS</code> 表中的一些关键列及其描述:</p><ul><li><code>POOL_ID</code>: 缓冲池的 ID,用于区分多个缓冲池实例 。</li><li><code>POOL_SIZE</code>: InnoDB 缓冲池的大小,以页为单位 。</li><li><code>FREE_BUFFERS</code>: InnoDB 缓冲池中的空闲页数 。</li><li><code>DATABASE_PAGES</code>: InnoDB 缓冲池中包含数据的页数,包括脏页和干净页 。</li><li><code>OLD_DATABASE_PAGES</code>: 旧缓冲池子列表中的页数 。</li><li><code>MODIFIED_DATABASE_PAGES</code>: 已修改 脏 的数据库页数 。</li><li><code>PENDING_DECOMPRESS</code>: 等待解压的页数 。</li><li><code>PENDING_READS</code>: 等待读取的页数 。</li><li><code>PENDING_FLUSH_LRU</code>: LRU 列表中等待刷新的页数 。</li><li><code>PENDING_FLUSH_LIST</code>: 刷新列表中等待刷新的页数 。</li><li><code>PAGES_MADE_YOUNG</code>: 标记为“年轻”的页数 。</li><li><code>PAGES_NOT_MADE_YOUNG</code>: 未标记为“年轻”的页数 。</li><li><code>PAGES_MADE_YOUNG_RATE</code>: 每秒标记为“年轻”的页数 。</li><li><code>PAGES_MADE_NOT_YOUNG_RATE</code>: 每秒未标记为“年轻”的页数 。</li><li><code>NUMBER_PAGES_READ</code>: 读取的页数 。</li><li><code>NUMBER_PAGES_CREATED</code>: 创建的页数 。</li><li><code>NUMBER_PAGES_WRITTEN</code>: 写入的页数 。</li><li><code>PAGES_READ_RATE</code>: 每秒读取的页数 。</li><li><code>PAGES_CREATE_RATE</code>: 每秒创建的页数 。</li><li><code>PAGES_WRITTEN_RATE</code>: 每秒写入的页数 。</li><li><code>NUMBER_PAGES_GET</code>: 逻辑读取请求的数量 。</li><li><code>HIT_RATE</code>: 缓冲池命中率 。</li><li><code>YOUNG_MAKE_PER_THOUSAND_GETS</code>: 每千个获取请求中标记为“年轻”的页数 。</li><li><code>NOT_YOUNG_MAKE_PER_THOUSAND_GETS</code>: 每千个获取请求中未标记为“年轻”的页数 。</li><li><code>NUMBER_PAGES_READ_AHEAD</code>: 预读的页数 。</li><li><code>NUMBER_READ_AHEAD_EVICTED</code>: 由预读后台线程读入 InnoDB 缓冲池但未被查询访问即被驱逐的页数 。</li><li><code>READ_AHEAD_RATE</code>: 每秒预读的页数 。</li><li><code>READ_AHEAD_EVICTED_RATE</code>: 每秒驱逐的预读页数 。</li></ul><p>要查询 <code>INNODB_BUFFER_POOL_STATS</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_BUFFER_POOL_STATS;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 缓冲池的统计信息,包括页数、读取率、命中率等。这些信息对于监控缓冲池性能和调整缓冲池大小非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img17.avif"></p><h3 id="INNODB-CACHED-INDEXES"><a href="#INNODB-CACHED-INDEXES" class="headerlink" title="INNODB_CACHED_INDEXES"></a>INNODB_CACHED_INDEXES</h3><p><code>INNODB_CACHED_INDEXES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,从 MySQL 8.0 开始引入。它提供了有关 InnoDB 缓冲池中缓存的索引页面的信息。</p><p>以下是 <code>INNODB_CACHED_INDEXES</code> 表中的一些关键列及其描述:</p><ul><li><code>SPACE_ID</code>: 表空间的 ID。</li><li><code>INDEX_ID</code>: 索引的唯一标识符。这个标识符在实例中是唯一的。</li><li><code>N_CACHED_PAGES</code>: InnoDB 缓冲池中缓存的索引页面数。</li></ul><p>这个表可以用来查看哪些索引被缓存在缓冲池中以及缓存的页面数。这对于性能调优和监控索引使用情况非常有用。例如,如果您想要查看特定索引在缓冲池中的缓存页面数,可以使用以下查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CACHED_INDEXES <span class="keyword">WHERE</span> INDEX_ID 你的索引ID;</span><br></pre></td></tr></table></figure><p>此外,如果您想获取表名和索引名,可以将 <code>INNODB_CACHED_INDEXES</code> 与其他表如 <code>INNODB_INDEXES</code> 和 <code>INNODB_TABLES</code> 联查:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span></span><br><span class="line">tables.NAME <span class="keyword">AS</span> table_name,</span><br><span class="line">indexes.NAME <span class="keyword">AS</span> index_name,</span><br><span class="line">cached.N_CACHED_PAGES <span class="keyword">AS</span> n_cached_pages</span><br><span class="line"><span class="keyword">FROM</span></span><br><span class="line">INFORMATION_SCHEMA.INNODB_CACHED_INDEXES <span class="keyword">AS</span> cached,</span><br><span class="line">INFORMATION_SCHEMA.INNODB_INDEXES <span class="keyword">AS</span> indexes,</span><br><span class="line">INFORMATION_SCHEMA.INNODB_TABLES <span class="keyword">AS</span> tables</span><br><span class="line"><span class="keyword">WHERE</span></span><br><span class="line">cached.INDEX_ID indexes.INDEX_ID</span><br><span class="line"><span class="keyword">AND</span> indexes.TABLE_ID tables.TABLE_ID;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img18.avif"></p><p>要查询此表,您需要具有 <code>PROCESS</code> 权限。这个表对于数据库管理员在监控和优化数据库性能时非常有用,尤其是在处理大量索引和表空间的情况下 。</p><h3 id="INNODB-CMP"><a href="#INNODB-CMP" class="headerlink" title="INNODB_CMP"></a>INNODB_CMP</h3><p><code>INNODB_CMP</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎的压缩操作的信息。这个表主要用于存储 InnoDB 引擎的压缩字典的比较信息,包括压缩前后的页数量和大小的统计,有助于评估和监控 InnoDB 表和索引使用压缩功能的效果。</p><p>以下是 <code>INNODB_CMP</code> 表中的一些关键列及其描述:</p><ul><li><code>PAGE_SIZE</code>: 表示压缩评估中涉及的页面大小。</li><li><code>COMPRESS_OPS</code>: 自上次重置以来,压缩操作的总数。</li><li><code>COMPRESS_OPS_OK</code>: 自上次重置以来,成功完成的压缩操作数。</li><li><code>COMPRESS_TIME</code>: 执行所有压缩操作所花费的时间 微秒 。</li><li><code>UNCOMPRESS_OPS</code>: 自上次重置以来,解压缩操作的总数。</li><li><code>UNCOMPRESS_TIME</code>: 执行所有解压缩操作所花费的时间 微秒 。</li></ul><p>通过查询这个表,数据库管理员或开发者可以了解压缩如何影响存储空间的使用和数据库的整体性能。例如,如果发现压缩操作耗时较长,但节省的空间不多,可能需要重新考虑是否继续使用压缩或者调整压缩级别。</p><p>要查询 <code>INNODB_CMP</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMP;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 压缩操作的统计信息,包括页面大小、压缩操作次数、成功压缩操作次数、压缩操作耗时、解压缩操作次数和解压缩操作耗时。这些信息对于监控压缩性能和优化数据库配置非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img19.avif"></p><h3 id="INNODB-CMPMEM"><a href="#INNODB-CMPMEM" class="headerlink" title="INNODB_CMPMEM"></a>INNODB_CMPMEM</h3><p><code>INNODB_CMPMEM</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 缓冲池中压缩页面使用情况的详细信息。此表对于监控和管理 InnoDB 缓冲池中压缩页面的内存使用情况非常有用。</p><p>以下是 <code>INNODB_CMPMEM</code> 表中的一些关键列及其描述:</p><ul><li><code>PAGE_SIZE</code>: 表示压缩的页有效块大小 以字节为单位 。</li><li><code>BUFFER_POOL_INSTANCE</code>: 缓冲池实例的唯一标识符。</li><li><code>PAGES_USED</code>: 表示对应每行记录中的 <code>PAGE_SIZE</code> 块大小的块数 页数 。</li><li><code>PAGES_FREE</code>: 表示每行记录对应的 <code>PAGE_SIZE</code> 块大小的当前可分配的块数。此列显示内存池中的外部碎片。理想情况下,该列值不应该超过1。</li><li><code>RELOCATION_OPS</code>: 表示 <code>PAGE_SIZE</code> 列值对应的块大小的块被重新设置的次数。</li><li><code>RELOCATION_TIME</code>: 表示用于重新定位 <code>PAGE_SIZE</code> 列值大小的块的总时间 以微秒为单位 。</li></ul><p>通过查询这个表,您可以了解不同块大小的页面在缓冲池中的使用情况,以及这些页面的重定位操作次数和时间。这有助于评估压缩对性能的影响和缓冲池的内存使用效率。</p><p>要查询 <code>INNODB_CMPMEM</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMPMEM;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 缓冲池中压缩页面的统计信息,包括块大小、使用的页数、空闲页数、重定位操作次数和重定位时间。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img20.avif"></p><h3 id="INNODB-CMPMEM-RESET"><a href="#INNODB-CMPMEM-RESET" class="headerlink" title="INNODB_CMPMEM_RESET"></a>INNODB_CMPMEM_RESET</h3><p><code>INNODB_CMPMEM_RESET</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎缓冲池中压缩页面内存使用情况的统计信息。该表的统计信息可以帮助你了解压缩页面在缓冲池中的分布和使用情况。</p><p>以下是 <code>INNODB_CMPMEM_RESET</code> 表中的一些关键列及其描述:</p><ul><li><code>PAGE_SIZE</code>: 表示压缩页的大小 以字节为单位 。</li><li><code>BUFFER_POOL_INSTANCE</code>: 缓冲池实例的唯一标识符。</li><li><code>PAGES_USED</code>: 表示当前正在使用的指定 <code>PAGE_SIZE</code> 的页数。</li><li><code>PAGES_FREE</code>: 表示当前可用于分配的指定 <code>PAGE_SIZE</code> 的空闲页数。这个值表示缓冲池的碎片情况,理想情况下,这些数字最多应为 1。</li><li><code>RELOCATION_OPS</code>: 表示大小为 <code>PAGE_SIZE</code> 的页面已被重定位的次数。当伙伴系统试图形成更大的释放块时,可以重新分配释放块的分配的“伙伴邻居”。</li><li><code>RELOCATION_TIME</code>: 表示用于重新定位大小为 <code>PAGE_SIZE</code> 的页面的总时间 以微秒为单位 。当从 <code>INNODB_CMPMEM_RESET</code> 表中读取时,此计数会被重置。</li></ul><p>这些统计信息可以用来衡量 InnoDB 表压缩的有效性。例如,你可以创建多个版本的表 每个候选值一个 ,在它们上运行实际的工作负载,然后使用这些表来查看不同页面大小下的操作如何执行。</p><p>要查询 <code>INNODB_CMPMEM_RESET</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMPMEM_RESET;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 缓冲池中压缩页面的统计信息,包括块大小、使用的页数、空闲页数、重定位操作次数和重定位时间。这些信息对于监控压缩性能和优化数据库配置非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img21.avif"></p><h3 id="INNODB-CMP-PER-INDEX"><a href="#INNODB-CMP-PER-INDEX" class="headerlink" title="INNODB_CMP_PER_INDEX"></a>INNODB_CMP_PER_INDEX</h3><p><code>INNODB_CMP_PER_INDEX</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它为 InnoDB 存储引擎的压缩表和索引提供操作状态信息。此表为数据库、表和索引的每个组合提供单独的统计信息,帮助评估特定表的压缩性能和有用性。对于压缩的 InnoDB 表,表数据和所有二级索引都会被压缩。此表中的统计信息可以用于衡量 InnoDB 表压缩对特定表、索引或两者的有效性 。</p><p>以下是 <code>INNODB_CMP_PER_INDEX</code> 表中的一些关键列及其描述:</p><ul><li><code>DATABASE_NAME</code>: 包含适用表的架构 数据库 。</li><li><code>TABLE_NAME</code>: 要监视压缩统计信息的表。</li><li><code>INDEX_NAME</code>: 要监视压缩统计信息的索引。</li><li><code>COMPRESS_OPS</code>: 尝试的压缩操作数。每当创建空白页或未压缩的修改日志空间用完时,页面会被压缩。</li><li><code>COMPRESS_OPS_OK</code>: 成功的压缩操作数。从 <code>COMPRESS_OPS</code> 值中减去此数值可得到压缩失败的次数。</li><li><code>COMPRESS_TIME</code>: 用于压缩此索引中的数据的总时间 以秒为单位 。</li><li><code>UNCOMPRESS_OPS</code>: 执行的解压缩操作数。每当压缩失败或第一次在缓冲池中访问压缩页面且未压缩页面不存在时,压缩的 InnoDB 页面会被解压缩。</li><li><code>UNCOMPRESS_TIME</code>: 用于解压缩此索引中的数据的总时间 以秒为单位 。</li></ul><p>要查询此表,您需要具有 <code>PROCESS</code> 权限。此外,因为收集每个索引的单独测量值会带来很大的性能开销,所以 <code>INNODB_CMP_PER_INDEX</code> 统计信息默认情况下不会收集,您必须在执行要监控的压缩表操作之前启用 <code>innodb_cmp_per_index_enabled</code> 系统变量 。</p><p>查询示例:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMP_PER_INDEX;</span><br></pre></td></tr></table></figure><p>这个查询将返回特定表的压缩操作统计信息,包括数据库名、表名、索引名、压缩操作次数、成功压缩操作次数、压缩操作耗时、解压缩操作次数和解压缩操作耗时。这些信息对于监控压缩性能和优化数据库配置非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img22.avif"></p><h3 id="INNODB-CMP-PER-INDEX-RESET"><a href="#INNODB-CMP-PER-INDEX-RESET" class="headerlink" title="INNODB_CMP_PER_INDEX_RESET"></a>INNODB_CMP_PER_INDEX_RESET</h3><p><code>INNODB_CMP_PER_INDEX_RESET</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎的压缩表和索引的操作状态信息。这个表为数据库、表和索引的每个组合提供单独的统计信息,帮助评估特定表的压缩性能和有用性。对于压缩的 InnoDB 表,表数据和所有二级索引都被压缩。此表中的统计信息可以用于衡量压缩对性能的影响和缓冲池的内存使用效率。</p><p>以下是 <code>INNODB_CMP_PER_INDEX_RESET</code> 表中的一些关键列及其描述:</p><ul><li><code>DATABASE_NAME</code>: 包含适用表的架构 数据库 。</li><li><code>TABLE_NAME</code>: 要监视压缩统计信息的表。</li><li><code>INDEX_NAME</code>: 要监视压缩统计信息的索引。</li><li><code>COMPRESS_OPS</code>: 尝试的压缩操作数。每当创建空白页或未压缩的修改日志空间用完时,页面会被压缩。</li><li><code>COMPRESS_OPS_OK</code>: 成功的压缩操作数。从 <code>COMPRESS_OPS</code> 值中减去此数值可得到压缩失败的次数。</li><li><code>COMPRESS_TIME</code>: 执行所有压缩操作所花费的时间 以秒为单位 。</li><li><code>UNCOMPRESS_OPS</code>: 自上次重置以来,解压缩操作的总数。</li><li><code>UNCOMPRESS_TIME</code>: 执行所有解压缩操作所花费的时间 以秒为单位 。</li></ul><p>通过查询这个表,数据库管理员或开发者可以了解压缩如何影响存储空间的使用和数据库的整体性能。例如,如果发现压缩操作耗时较长,但节省的空间不多,可能需要重新考虑是否继续使用压缩或者调整压缩级别。</p><p>要查询 <code>INNODB_CMP_PER_INDEX_RESET</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMP_PER_INDEX_RESET;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 缓冲池中压缩页面的统计信息,包括数据库名、表名、索引名、压缩操作次数、成功压缩操作次数、压缩操作耗时、解压缩操作次数和解压缩操作耗时。这些信息对于监控压缩性能和优化数据库配置非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img23.avif"></p><h3 id="INNODB-CMP-RESET"><a href="#INNODB-CMP-RESET" class="headerlink" title="INNODB_CMP_RESET"></a>INNODB_CMP_RESET</h3><p><code>INNODB_CMP_RESET</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎的压缩表操作的状态信息。该表与 <code>INNODB_CMP</code> 表具有相同的内容,但读取 <code>INNODB_CMP_RESET</code> 会重置统计信息,因此可以用来监控压缩和解压缩操作的统计数据。</p><p>以下是 <code>INNODB_CMP_RESET</code> 表中的一些关键列及其描述:</p><ul><li><code>PAGE_SIZE</code>: 表示压缩页面的大小 以字节为单位 。</li><li><code>COMPRESS_OPS</code>: 自上次重置以来,尝试压缩操作的总数。</li><li><code>COMPRESS_OPS_OK</code>: 自上次重置以来,成功完成的压缩操作数。</li><li><code>COMPRESS_TIME</code>: 执行所有压缩操作所花费的时间 以秒为单位 。</li><li><code>UNCOMPRESS_OPS</code>: 自上次重置以来,解压缩操作的总数。</li><li><code>UNCOMPRESS_TIME</code>: 执行所有解压缩操作所花费的时间 以秒为单位 。</li></ul><p>通过查询这个表,您可以了解压缩操作的频率、成功率以及它们对性能的影响。例如,如果发现压缩操作耗时较长,但节省的空间不多,可能需要重新考虑是否继续使用压缩或者调整压缩级别。</p><p>要查询 <code>INNODB_CMP_RESET</code> 表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_CMP_RESET;</span><br></pre></td></tr></table></figure><p>这个查询将返回自上次重置以来的压缩操作统计信息,包括页面大小、压缩操作次数、成功压缩操作次数、压缩操作耗时、解压缩操作次数和解压缩操作耗时。这些信息对于监控压缩性能和优化数据库配置非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img24.avif"></p><h3 id="INNODB-COLUMNS"><a href="#INNODB-COLUMNS" class="headerlink" title="INNODB_COLUMNS"></a>INNODB_COLUMNS</h3><p><code>INNODB_COLUMNS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 表列的元数据。这些信息通常与 InnoDB 内部数据字典中的 <code>SYS_COLUMNS</code> 表中的数据相对应。以下是 <code>INNODB_COLUMNS</code> 表中的一些关键列及其描述:</p><ul><li><code>TABLE_ID</code>: 一个标识符,代表与列关联的表;与 <code>INNODB_TABLES.TABLE_ID</code> 的值相同 。</li><li><code>NAME</code>: 列的名称。这些名称可以是大写或小写,具体取决于 <code>lower_case_table_names</code> 设置。列没有特殊的系统保留名称 。</li><li><code>POS</code>: 表中列的序号位置,从 0 开始依次递增。当删除一列时,剩余的列将重新排序,以便序列没有间隙 。</li><li><code>MTYPE</code>: 代表“主要类型”。列类型的数字标识符,例如:1 表示 <code>VARCHAR</code>,2 表示 <code>CHAR</code> 等 。</li><li><code>PRTYPE</code>: InnoDB“精确类型”,一个二进制值,其中的位表示 MySQL 数据类型、字符集代码和可空性 。</li><li><code>LEN</code>: 列长度,例如 4 表示 <code>INT</code>,8 表示 <code>BIGINT</code>。对于多字节字符集中的字符列,此长度值是表示定义 如 <code>VARCHAR(N)</code> 所需的最大字节长度 。</li></ul><p>要查询此表,您需要具有 <code>PROCESS</code> 权限。使用 <code>INFORMATION_SCHEMA.COLUMNS</code> 表或 <code>SHOW COLUMNS</code> 语句查看有关此表的列的其他信息,包括数据类型和默认值 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img25.avif"></p><h3 id="INNODB-DATAFILES"><a href="#INNODB-DATAFILES" class="headerlink" title="INNODB_DATAFILES"></a>INNODB_DATAFILES</h3><p><code>INNODB_DATAFILES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它为 InnoDB 的 file-per-table 和通用表空间提供数据文件路径信息。这个表对于监控和管理 InnoDB 数据文件非常有用。</p><p>以下是 <code>INNODB_DATAFILES</code> 表中的一些关键列及其描述:</p><ul><li><code>SPACE</code>: 表空间的 ID。</li><li><code>PATH</code>: 表空间数据文件的路径。如果 file-per-table 表空间是在 MySQL 数据目录之外的位置创建的,则路径值是绝对路径。否则,路径是相对于数据目录的。</li></ul><p>要查询此表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> SPACE, PATH <span class="keyword">FROM</span> information_schema.INNODB_DATAFILES;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 数据文件的列表,包括文件的路径和表空间 ID。这些信息对于了解数据文件的存储位置和进行数据库维护非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img26.avif"></p><h3 id="INNODB-FIELDS"><a href="#INNODB-FIELDS" class="headerlink" title="INNODB_FIELDS"></a>INNODB_FIELDS</h3><p><code>INNODB_FIELDS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 索引的键列 字段 的元数据。此表对于查看和管理 InnoDB 索引的列信息非常有用。</p><p>以下是 <code>INNODB_FIELDS</code> 表中的一些关键列及其描述:</p><ul><li><code>INDEX_ID</code>: 与此键字段关联的索引的标识符;与 <code>INNODB_INDEXES.INDEX_ID</code> 的值相同。</li><li><code>NAME</code>: 表中原始列的名称;与 <code>INNODB_COLUMNS.NAME</code> 的值相同。</li><li><code>POS</code>: 索引中关键字段的序号位置,从 0 开始并按顺序递增。当列被删除时,剩余的列将重新排序,以使序列没有间隙。</li></ul><p>要查询此表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_FIELDS <span class="keyword">WHERE</span> INDEX_ID [指定索引ID];</span><br></pre></td></tr></table></figure><p>这个查询将返回指定索引ID的字段元数据,包括字段名称和位置。这些信息对于了解索引结构和优化索引非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img27.avif"></p><h3 id="INNODB-FOREIGN"><a href="#INNODB-FOREIGN" class="headerlink" title="INNODB_FOREIGN"></a>INNODB_FOREIGN</h3><p><code>INNODB_FOREIGN</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎中定义的外键的元数据。这个表对于查看和管理 InnoDB 外键约束非常有用。</p><p>以下是 <code>INNODB_FOREIGN</code> 表中的一些关键列及其描述:</p><ul><li><code>ID</code>: 外键索引的名称 不是数字值 。例如,<code>test/fk1</code>。</li><li><code>FOR_NAME</code>: 外键关系中子表的名称。例如,<code>test/child</code>。</li><li><code>REF_NAME</code>: 外键关系中父表的名称。例如,<code>test/parent</code>。</li><li><code>N_COLS</code>: 外键索引中的列数。</li><li><code>TYPE</code>: 包含有关外键列的信息的位标志集合,或者是组合在一起的 OR 操作。例如,<code>1</code> 表示 <code>ON DELETE CASCADE</code> 。</li></ul><p>要查询此表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_FOREIGN;</span><br></pre></td></tr></table></figure><p>这个查询将返回数据库中所有 InnoDB 外键的列表,包括外键名称、子表和父表的名称、列数以及外键类型。这些信息对于了解和维护数据库的外键约束非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img28.avif"></p><h3 id="INNODB-FOREIGN-COLS"><a href="#INNODB-FOREIGN-COLS" class="headerlink" title="INNODB_FOREIGN_COLS"></a>INNODB_FOREIGN_COLS</h3><p><code>INNODB_FOREIGN_COLS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎中外键约束中涉及的列的详细信息。这个表对于查看和管理 InnoDB 外键列非常有用。</p><p>以下是 <code>INNODB_FOREIGN_COLS</code> 表中的一些关键列及其描述:</p><ul><li><code>ID</code>: 与外键约束关联的索引的标识符,与 <code>INNODB_FOREIGN</code> 表中的 <code>ID</code> 列相同。</li><li><code>FOR_COL_NAME</code>: 子表 即外键所在的表 中参与外键关系的列的名称。</li><li><code>REF_COL_NAME</code>: 父表 即外键引用的主表 中被外键关系引用的列的名称。</li><li><code>POS</code>: 外键索引中的列的位置,从 0 开始计数。</li></ul><p>要查询此表,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_FOREIGN_COLS;</span><br></pre></td></tr></table></figure><p>这个查询将返回数据库中所有 InnoDB 外键的列信息,包括外键约束的索引 ID、子表列名称、父表列名称以及列的位置。这些信息对于了解和维护数据库的外键约束非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img29.avif"></p><h3 id="INNODB-FT-BEING-DELETED"><a href="#INNODB-FT-BEING-DELETED" class="headerlink" title="INNODB_FT_BEING_DELETED"></a>INNODB_FT_BEING_DELETED</h3><p><code>INNODB_FT_BEING_DELETED</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它在 <code>OPTIMIZE TABLE</code> 维护操作期间作为 <code>INNODB_FT_DELETED</code> 表的快照使用。当执行 <code>OPTIMIZE TABLE</code> 语句时,<code>INNODB_FT_BEING_DELETED</code> 表会被清空,并且 <code>DOC_ID</code> 值会从 <code>INNODB_FT_DELETED</code> 表中移除。这个表通常具有较短的生命周期,因此对于监控或调试的实用性有限 。</p><p>该表通常在最初是空的,在查询之前,需要设置 <code>innodb_ft_aux_table</code> 系统变量的值为包含 <code>FULLTEXT</code> 索引的表的名称 包括数据库名称 。例如,如果表名为 <code>test/articles</code>,则需要执行以下命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> innodb_ft_aux_table <span class="string">&#x27;test/articles&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这样,<code>INNODB_FT_BEING_DELETED</code> 表将显示正在被删除的行的文档 ID,这些 ID 用于在物理删除 <code>FULLTEXT</code> 索引中的行之前跳过 <code>INNODB_FT_INDEX_TABLE</code> 表中的行 。</p><p><code>INNODB_FT_BEING_DELETED</code> 表结构简单,通常只包含一个列 <code>DOC_ID</code>,表示正在删除的行的文档 ID。这个 ID 可能反映了基础表中定义的 ID 列的值,或者是 InnoDB 生成的序列值 。</p><p>由于 <code>INNODB_FT_BEING_DELETED</code> 表是在 <code>OPTIMIZE TABLE</code> 操作期间使用的临时表,因此其内容会随着操作的完成而被清空,这也是为什么它对于日常监控和调试的实用性有限的原因 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img30.avif"></p><h3 id="INNODB-FT-CONFIG"><a href="#INNODB-FT-CONFIG" class="headerlink" title="INNODB_FT_CONFIG"></a>INNODB_FT_CONFIG</h3><p><code>INNODB_FT_CONFIG</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 表的全文索引及其相关处理的元数据信息。这个表最初是空的,在查询之前,需要将 <code>innodb_ft_aux_table</code> 系统变量的值设置为包含全文索引的表的名称 包括数据库名称 ,例如 <code>test/articles</code>。</p><p><code>INNODB_FT_CONFIG</code> 表包含以下几列:</p><ul><li><p><code>KEY</code>: 指定包含全文索引的 InnoDB 表的元数据项的名称。可能的键包括:</p></li><li><p><code>optimize_checkpoint_limit</code>: <code>OPTIMIZE TABLE</code> 运行停止的秒数。</p></li><li><p><code>synced_doc_id</code>: 下一个要发放的 <code>DOC_ID</code>。</p></li><li><p><code>stopword_table_name</code>: 用户定义的停用词表的数据库&#x2F;表名称。如果没有用户定义的停用词表,则该列为空。</p></li><li><p><code>use_stopword</code>: 表示是否使用停用词表,在创建全文索引时定义。</p></li><li><p><code>VALUE</code>: 与相应的 <code>KEY</code> 列关联的值,反映 <code>InnoDB</code> 表的 <code>FULLTEXT</code> 索引的某个方面的一些限制或当前值。</p></li></ul><p>例如,查询 <code>INNODB_FT_CONFIG</code> 表可以提供如下信息:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_FT_CONFIG;</span><br><span class="line"><span class="comment">--------------------------- -------------------</span></span><br><span class="line"><span class="operator">|</span> KEY <span class="operator">|</span> <span class="keyword">VALUE</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- -------------------</span></span><br><span class="line"><span class="operator">|</span> optimize_checkpoint_limit <span class="operator">|</span> <span class="number">180</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> synced_doc_id <span class="operator">|</span> <span class="number">0</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> stopword_table_name <span class="operator">|</span> test<span class="operator">/</span>my_stopwords <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> use_stopword <span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">--------------------------- ------------------- </span></span><br></pre></td></tr></table></figure><p>这些信息对于性能调优和调试 InnoDB 全文索引处理非常有用 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img31.avif"></p><h3 id="INNODB-FT-DEFAULT-STOPWORD"><a href="#INNODB-FT-DEFAULT-STOPWORD" class="headerlink" title="INNODB_FT_DEFAULT_STOPWORD"></a>INNODB_FT_DEFAULT_STOPWORD</h3><p><code>INNODB_FT_DEFAULT_STOPWORD</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它存储了 InnoDB 存储引擎在创建 FULLTEXT 索引时默认使用的停用词列表。这些停用词是在全文搜索中通常被忽略的常见词汇,因为它们对于搜索通常不具有区分度。</p><p>以下是 <code>INNODB_FT_DEFAULT_STOPWORD</code> 表中的列及其描述:</p><ul><li><code>value</code>: 这是一个字符串列,包含了默认的停用词。例如, a , about , an , are , as , at , be , by , com , de , en , for , from , how , i , in , is , it , la , of , on , or , that , the , this , to , was , what , when , where , who , will , with , und , the , www 等 。</li></ul><p>要查看默认的停用词列表,可以执行以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.INNODB_FT_DEFAULT_STOPWORD;</span><br></pre></td></tr></table></figure><p>这个查询将返回 InnoDB 默认的停用词列表。这些信息对于了解和调整全文索引的搜索效果非常有用。如果您需要为特定的 FULLTEXT 索引设置不同的停用词列表,可以通过创建自己的停用词表并使用 <code>innodb_ft_user_stopword_table</code> 系统变量来指定 。</p><p>请注意,查询 <code>INNODB_FT_DEFAULT_STOPWORD</code> 表需要有 PROCESS 权限,并且这个表是 MEMORY 引擎的临时表 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img32.avif"></p><h3 id="INNODB-FT-DELETED"><a href="#INNODB-FT-DELETED" class="headerlink" title="INNODB_FT_DELETED"></a>INNODB_FT_DELETED</h3><p><code>INNODB_FT_DELETED</code> 是 MySQL 中的一个特殊表,它位于 <code>INFORMATION_SCHEMA</code> 数据库中。这个表的目的是为了存储那些已经被删除的行的文档 ID DOC_ID ,这些行原本存在于一个 InnoDB 表的 FULLTEXT 索引中。这样做的目的是为了优化性能,避免在进行删除操作 DML 时对 FULLTEXT 索引进行昂贵的重组。</p><p>当一个带有 FULLTEXT 索引的 InnoDB 表中的行被删除时,相关的信息 而不是实际的行数据 会被存储在 <code>INNODB_FT_DELETED</code> 表中。在执行文本搜索时,这些被删除的行的信息会被过滤掉,以确保搜索结果不包含这些已经不存在的数据。只有当执行了 <code>OPTIMIZE TABLE</code> 语句后,这些被删除的行的信息才会从主搜索索引中物理删除。</p><p><code>INNODB_FT_DELETED</code> 表通常在初始化时是空的。在查询这个表之前,需要设置系统变量 <code>innodb_ft_aux_table</code> 的值为包含 FULLTEXT 索引的表的名称 包括数据库名称 。例如,如果表名为 <code>test/articles</code>,则需要执行以下命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> innodb_ft_aux_table <span class="string">&#x27;test/articles&#x27;</span>;</span><br></pre></td></tr></table></figure><p><code>INNODB_FT_DELETED</code> 表只包含一个列 <code>DOC_ID</code>,它表示新删除行的文档 ID。这个值可能是基础表定义的 ID 列的值,或者是当表不包含合适的列时由 InnoDB 生成的序列值。</p><p>在进行文本搜索时,<code>DOC_ID</code> 用于跳过 <code>INNODB_FT_INDEX_TABLE</code> 表中的行,直到通过 <code>OPTIMIZE TABLE</code> 语句从 FULLTEXT 索引中物理删除删除行的数据。</p><p>需要注意的是,查询 <code>INNODB_FT_DELETED</code> 表需要有 <code>PROCESS</code> 权限。此外,可以通过 <code>INFORMATION_SCHEMA.COLUMNS</code> 表或 <code>SHOW COLUMNS</code> 语句来查看这个表的列的更多信息,包括数据类型和默认值。</p><p>在某些情况下,即使执行了删除操作,<code>INNODB_FT_DELETED</code> 表中的记录也不会立即减少,因为这些记录只有在执行 <code>OPTIMIZE TABLE</code> 后才会被清除。如果需要立即清除这些记录,可以通过设置 <code>innodb_optimize_fulltext_only</code> 系统变量为 1,然后执行 <code>OPTIMIZE TABLE</code> 来实现。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img33.avif"></p><h3 id="INNODB-FT-INDEX-CACHE"><a href="#INNODB-FT-INDEX-CACHE" class="headerlink" title="INNODB_FT_INDEX_CACHE"></a>INNODB_FT_INDEX_CACHE</h3><p><code>INNODB_FT_INDEX_CACHE</code> 是 MySQL 中 <code>INFORMATION_SCHEMA</code> 数据库的一个表,它提供了关于 <code>FULLTEXT</code> 索引中新插入行的标记信息。为了避免在 DML 操作期间昂贵的索引重组,新索引的词的信息被单独存储,并仅在执行 <code>OPTIMIZE TABLE</code>、服务器关闭或当缓存大小超过 <code>innodb_ft_cache_size</code> 或 <code>innodb_ft_total_cache_size</code> 系统变量定义的限制时,才与主搜索索引合并。</p><p>这个表最初是空的。在查询它之前,需要设置 <code>innodb_ft_aux_table</code> 系统变量的值为包含 <code>FULLTEXT</code> 索引的表的名称 包括数据库名称 。例如,如果表名为 <code>test/articles</code>,则需要执行以下命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> innodb_ft_aux_table <span class="string">&#x27;test/articles&#x27;</span>;</span><br></pre></td></tr></table></figure><p><code>INNODB_FT_INDEX_CACHE</code> 表包含以下字段:</p><ul><li><code>WORD</code>:从新插入行的文本中提取的单词。</li><li><code>FIRST_DOC_ID</code>:这个词首次出现的文档 ID。</li><li><code>LAST_DOC_ID</code>:这个词最后出现的文档 ID。</li><li><code>DOC_COUNT</code>:这个词在 <code>FULLTEXT</code> 索引中出现的行数。同一个词可以在缓存表中出现多次,每次对应不同的 <code>DOC_ID</code> 和 <code>POSITION</code> 值组合。</li><li><code>DOC_ID</code>:新插入行的文档 ID。这个值可能反映了你为底层表定义的 ID 列的值,或者当表不包含合适的列时,它可以是 InnoDB 生成的序列值。</li><li><code>POSITION</code>:这个词在由 <code>DOC_ID</code> 值标识的相关文档中的特定实例的位置。该值不代表绝对位置;它是添加到前面那个词的 <code>POSITION</code> 的偏移量。</li></ul><p>这个表是 InnoDB 全文索引的调试和性能优化的重要工具,它可以帮助开发者了解文档被标记化后如何被添加到索引中,并且可以监控索引的插入和缓存行为。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img34.avif"></p><h3 id="INNODB-FT-INDEX-TABLE"><a href="#INNODB-FT-INDEX-TABLE" class="headerlink" title="INNODB_FT_INDEX_TABLE"></a>INNODB_FT_INDEX_TABLE</h3><p><code>INNODB_FT_INDEX_TABLE</code> 是 MySQL 中 <code>INFORMATION_SCHEMA</code> 数据库的一个表,它提供了关于 InnoDB 表中 <code>FULLTEXT</code> 索引的倒排索引的信息。这个表最初是空的,需要通过设置 <code>innodb_ft_aux_table</code> 系统变量为包含 <code>FULLTEXT</code> 索引的表的名称 包括数据库名 后,才会显示相关信息。</p><p>该表包含以下列:</p><ul><li><code>WORD</code>: 从 <code>FULLTEXT</code> 索引的列文本中提取的单词。</li><li><code>FIRST_DOC_ID</code>: 该词在 <code>FULLTEXT</code> 索引中出现的的第一个文档 ID。</li><li><code>LAST_DOC_ID</code>: 该词在 <code>FULLTEXT</code> 索引中出现的最后一个文档 ID。</li><li><code>DOC_COUNT</code>: 该词在 <code>FULLTEXT</code> 索引中出现的行数。同一个词可以在表中出现多次,每个 <code>DOC_ID</code> 和 <code>POSITION</code> 值组合出现一次。</li><li><code>DOC_ID</code>: 包含该词的行的文档 ID。这个值可能是你为基础表定义的 ID 列的值,或者当表不包含合适的列时,它可以是 InnoDB 生成的序列值。</li><li><code>POSITION</code>: 单词的这个特定实例在由 <code>DOC_ID</code> 值标识的相关文档中的位置。</li></ul><p>在查询 <code>INNODB_FT_INDEX_TABLE</code> 之前,需要设置 <code>innodb_ft_aux_table</code> 系统变量,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> <span class="keyword">GLOBAL</span> innodb_ft_aux_table <span class="string">&#x27;test/articles&#x27;</span>;</span><br></pre></td></tr></table></figure><p>然后可以查询 <code>INNODB_FT_INDEX_TABLE</code> 来获取倒排索引的信息。例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> WORD, DOC_COUNT, DOC_ID, POSITION <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_FT_INDEX_TABLE LIMIT <span class="number">5</span>;</span><br></pre></td></tr></table></figure><p>这个表对于监视和调试全文索引非常有用,尤其是在优化全文索引的时候。需要注意的是,查询这个表需要有 <code>PROCESS</code> 权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img35.avif"></p><h3 id="INNODB-INDEXES"><a href="#INNODB-INDEXES" class="headerlink" title="INNODB_INDEXES"></a>INNODB_INDEXES</h3><p><code>INNODB_INDEXES</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于 InnoDB 存储引擎索引的详细信息和元数据。这个表对于数据库管理员和开发者在进行数据库性能优化和索引管理时非常有用。</p><p>以下是 <code>INNODB_INDEXES</code> 表中包含的一些关键列:</p><ul><li><p><strong>INDEX_ID</strong>: 索引的唯一标识符,在所有数据库中唯一。</p></li><li><p><strong>NAME</strong>: 索引的名称。大多数由 InnoDB 隐式创建的索引具有一致的名称,但请注意,索引名称不一定是唯一的。</p></li><li><p><strong>TABLE_ID</strong>: 索引所属表的标识符,与 <code>INNODB_TABLES.TABLE_ID</code> 相同。</p></li><li><p><strong>TYPE</strong>: 表示索引类型的数值,例如:</p></li><li><p>0 非唯一二级索引</p></li><li><p>1 自动生成聚集索引 (<code>GEN_CLUST_INDEX</code>)</p></li><li><p>2 唯一非聚集索引</p></li><li><p>3 聚簇索引</p></li><li><p>32 全文索引</p></li><li><p>64 空间索引</p></li><li><p>128 虚拟生成列上的二级索引</p></li><li><p><strong>N_FIELDS</strong>: 索引键中的列数。对于 <code>GEN_CLUST_INDEX</code> 索引,此值为 0,因为它使用的是人工值而不是真实的表列创建的。</p></li><li><p><strong>PAGE_NO</strong>: 索引 B 树的根页码。对于全文索引,这个字段未使用并设置为 -1,因为全文索引布局在多个 B 树中。</p></li><li><p><strong>SPACE</strong>: 索引所在的表空间的标识符。0 表示 InnoDB 系统表空间,其他数字表示每个表文件模式下使用单独 <code>.ibd</code> 文件创建的表。</p></li><li><p><strong>MERGE_THRESHOLD</strong>: 索引页的合并阈值。如果删除行或通过更新操作缩短行时索引页中的数据量低于该值,则 InnoDB 尝试将索引页与相邻索引页合并。</p></li></ul><p>要查询 <code>INNODB_INDEXES</code> 表,你通常需要具备 <code>PROCESS</code> 权限。这个表的信息可以帮助你了解索引的物理结构和特性,从而进行更有效的索引策略规划和优化。</p><p>例如,要查看某个表的所有索引信息,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_INDEXES <span class="keyword">WHERE</span> TABLE_ID [特定的TABLE_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的TABLE_ID]</code> 替换为你想要查询的表的 <code>TABLE_ID</code>。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img36.avif"></p><h3 id="INNODB-METRICS"><a href="#INNODB-METRICS" class="headerlink" title="INNODB_METRICS"></a>INNODB_METRICS</h3><p><code>INNODB_METRICS</code> 是 MySQL 的 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于 InnoDB 存储引擎性能和资源相关的计数器信息。这个表在 MySQL 5.6 版本中引入,用以补充 Performance Schema 表中对 InnoDB 的监控。</p><p>这个表包含许多列,每个列代表一个特定的性能指标或计数器,例如:</p><ul><li><code>NAME</code>: 计数器的唯一名称。</li><li><code>SUBSYSTEM</code>: 指标适用的 InnoDB 方面。</li><li><code>COUNT</code>: 自启用计数器以来的值。</li><li><code>MAX_COUNT</code>: 自启用计数器以来的最大值。</li><li><code>MIN_COUNT</code>: 自启用计数器以来的最小值。</li><li><code>AVG_COUNT</code>: 自启用计数器以来的平均值。</li><li><code>COUNT_RESET</code>: 自上次重置以来的计数器值。</li><li><code>MAX_COUNT_RESET</code>: 自上次重置以来的最大计数器值。</li><li><code>MIN_COUNT_RESET</code>: 自上次重置以来的最小计数器值。</li><li><code>AVG_COUNT_RESET</code>: 自上次重置以来的平均计数器值。</li><li><code>TIME_ENABLED</code>: 最后一次启动的时间戳。</li><li><code>TIME_DISABLED</code>: 最后一次停用的时间戳。</li><li><code>TIME_ELAPSED</code>: 自计数器启动以来经过的秒数。</li><li><code>TIME_RESET</code>: 上次重置的时间戳。</li><li><code>STATUS</code>: 计数器是否仍在运行 <code>enabled</code> 或已停止 <code>disabled</code> 。</li><li><code>TYPE</code>: 该项目是累积计数器,还是测量某些资源的当前值。</li><li><code>COMMENT</code>: 计数器的描述。</li></ul><p>通过查询 <code>INNODB_METRICS</code> 表,数据库管理员可以监控 InnoDB 的性能状况,诊断问题如性能瓶颈、资源短缺和应用程序问题。每个监控器代表 InnoDB 源代码中的一个点,用于收集计数器信息。每个计数器都可以启动、停止和重置,也可以使用它们的公共模块名称对一组计数器执行这些操作。</p><p>默认情况下,不会收集太多的数据,但是可以通过设置系统变量 <code>innodb_monitor_enable</code>、<code>innodb_monitor_disable</code>、<code>innodb_monitor_reset</code> 或 <code>innodb_monitor_reset_all</code> 来控制计数器的状态。需要注意的是,每个计数器都会增加一定程度的运行时开销,因此在生产服务器上应谨慎使用计数器,以诊断特定问题或监视特定功能。建议在测试或开发服务器上更广泛地使用计数器。</p><p>要查询 <code>INNODB_METRICS</code> 表,你需要有 <code>PROCESS</code> 权限。通过查看该表,可以了解 InnoDB 的内部运行状况,比如插入、更新、删除等 DML 操作的次数,以及其他如锁等待、索引查找等操作的统计信息。这些信息对于数据库的性能优化和故障排查非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img37.avif"></p><h3 id="INNODB-SESSION-TEMP-TABLESPACES"><a href="#INNODB-SESSION-TEMP-TABLESPACES" class="headerlink" title="INNODB_SESSION_TEMP_TABLESPACES"></a>INNODB_SESSION_TEMP_TABLESPACES</h3><p><code>INNODB_SESSION_TEMP_TABLESPACES</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关会话临时表空间的元数据,这些临时表空间用于存储用户创建的临时表和优化器创建的内部临时表。这个表是在 MySQL 8.0.13 版本中引入的。</p><p>以下是 <code>INNODB_SESSION_TEMP_TABLESPACES</code> 表中的一些关键列:</p><ul><li><strong>ID</strong>: 进程或会话 ID。</li><li><strong>SPACE</strong>: 表空间 ID。为会话临时表空间保留了一个空间 ID 范围。</li><li><strong>PATH</strong>: 表空间数据文件的路径。会话临时表空间的文件有 <code>.ibt</code> 扩展名。</li><li><strong>SIZE</strong>: 表空间的大小,单位是字节。</li><li><strong>STATE</strong>: 表空间的状态,<code>ACTIVE</code> 表示当前正被会话使用,<code>INACTIVE</code> 表示该表空间位于可用会话临时表空间池中。</li><li><strong>PURPOSE</strong>: 表空间的用途。<code>INTRINSIC</code> 表示用于优化器使用的内部临时表,<code>USER</code> 表示用于用户创建的临时表,<code>NONE</code> 表示表空间未被使用。</li></ul><p>会话临时表空间在服务器启动时创建,并在会话第一次请求创建磁盘临时表时分配给会话。一个会话最多可以分配两个表空间,一个用于用户创建的临时表,另一个用于优化器创建的内部临时表。当会话断开连接时,其临时表空间将被截断并释放回池中。</p><p>可以通过查询 <code>INNODB_SESSION_TEMP_TABLESPACES</code> 来监控会话临时表空间的使用情况,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_SESSION_TEMP_TABLESPACES;</span><br></pre></td></tr></table></figure><p>这个表对于数据库管理员在进行性能监控和优化时特别有用,因为它可以帮助他们了解临时表空间的使用模式和潜在的资源瓶颈。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img38.avif"></p><h3 id="INNODB-TABLES"><a href="#INNODB-TABLES" class="headerlink" title="INNODB_TABLES"></a>INNODB_TABLES</h3><p><code>INNODB_TABLES</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎管理的表的元数据。这个表包含了 InnoDB 表的各种信息,例如表的标识符、名称、列数、所在表空间的ID、行格式等。</p><p>以下是 <code>INNODB_TABLES</code> 表中的一些关键列:</p><ul><li><strong>TABLE_ID</strong>: 表的唯一标识符,在 InnoDB 实例中全局唯一。</li><li><strong>NAME</strong>: 表的名称,通常包括数据库名称作为前缀 例如 <code>test/t1</code> 。</li><li><strong>FLAG</strong>: 表示表的格式和存储特性的位掩码标志。</li><li><strong>N_COLS</strong>: 表中的列数,包括隐藏的 DB_ROW_ID、DB_TRX_ID 和 DB_ROLL_PTR 列。</li><li><strong>SPACE</strong>: 表所在的表空间的标识符。0 表示系统表空间,其他值表示单独的表空间。</li><li><strong>ROW_FORMAT</strong>: 表的行格式,如 <code>Compact</code>、<code>Redundant</code>、<code>Dynamic</code> 或 <code>Compressed</code>。</li><li><strong>ZIP_PAGE_SIZE</strong>: 对于行格式为 <code>Compressed</code> 的表,表示压缩页面的大小。</li><li><strong>SPACE_TYPE</strong>: 表所属的表空间类型,如 <code>System</code>、<code>General</code> 或 <code>Single</code>。</li></ul><p>这个表对于数据库管理员和开发者在进行数据库性能优化和表管理时非常有用。例如,可以通过查询 <code>INNODB_TABLES</code> 来获取表的物理存储信息,从而进行更有效的表空间规划和管理。</p><p>要查询 <code>INNODB_TABLES</code> 表,你可以使用如下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_TABLES <span class="keyword">WHERE</span> NAME <span class="string">&#x27;test/t1&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回名为 <code>test/t1</code> 的表的相关信息。需要注意的是,查询这个表通常需要有 <code>PROCESS</code> 权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img39.avif"></p><h3 id="INNODB-TABLESPACES"><a href="#INNODB-TABLESPACES" class="headerlink" title="INNODB_TABLESPACES"></a>INNODB_TABLESPACES</h3><p><code>INNODB_TABLESPACES</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 InnoDB 存储引擎管理的文件-per-table、通用 general 和 undo 表空间的元数据信息。</p><p>以下是 <code>INNODB_TABLESPACES</code> 表中的一些关键列:</p><ul><li><strong>SPACE</strong>: 表空间的ID。</li><li><strong>NAME</strong>: 表空间的名称,通常包括数据库名和表名。</li><li><strong>FLAG</strong>: 表示表空间格式和存储特征的位掩码值。</li><li><strong>ROW_FORMAT</strong>: 表空间的行格式,可能的值包括 <code>Compact</code>, <code>Redundant</code>, <code>Dynamic</code>, 或 <code>Compressed</code>。</li><li><strong>PAGE_SIZE</strong>: 表空间的页面大小。</li><li><strong>ZIP_PAGE_SIZE</strong>: 压缩表空间的页面大小。</li><li><strong>SPACE_TYPE</strong>: 表空间的类型,可能的值包括 <code>System</code>, <code>Single</code>, <code>General</code>, 或 <code>Undo</code>。</li><li><strong>FS_BLOCK_SIZE</strong>: 文件系统块大小,这是磁盘读写的最小单位。</li><li><strong>FILE_SIZE</strong>: 表空间文件的显示大小。</li><li><strong>ALLOCATED_SIZE</strong>: 分配给表空间的实际磁盘空间量。</li><li><strong>AUTOEXTEND_SIZE</strong>: 表空间的自动扩展大小。</li><li><strong>SERVER_VERSION</strong>: 创建表空间时的 MySQL 版本号。</li><li><strong>SPACE_VERSION</strong>: 表空间版本,用于跟踪表空间格式的变化。</li><li><strong>ENCRYPTION</strong>: 表空间是否加密。</li><li><strong>STATE</strong>: 表空间的状态,例如 <code>normal</code>, <code>discarded</code>, 或 <code>corrupted</code>。</li></ul><p>要查询 <code>INNODB_TABLESPACES</code> 表,你可以使用如下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_TABLESPACES <span class="keyword">WHERE</span> SPACE [特定的SPACE_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的SPACE_ID]</code> 替换为你想要查询的表空间的ID。需要注意的是,查询这个表通常需要有 <code>PROCESS</code> 权限。</p><p>这个表对于数据库管理员在进行数据库性能优化和表空间管理时特别有用,因为它可以帮助他们了解表空间的使用情况和配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img40.avif"></p><h3 id="INNODB-TABLESPACES-BRIEF"><a href="#INNODB-TABLESPACES-BRIEF" class="headerlink" title="INNODB_TABLESPACES_BRIEF"></a>INNODB_TABLESPACES_BRIEF</h3><p><code>INNODB_TABLESPACES_BRIEF</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了简洁的表空间元数据信息,包括空间 ID、名称、路径、标志和空间类型。这个表为 file-per-table、通用 general 、回滚 undo 和系统表空间提供了元数据。</p><p>以下是 <code>INNODB_TABLESPACES_BRIEF</code> 表中的一些关键列:</p><ul><li><strong>SPACE</strong>: 表空间的 ID。</li><li><strong>NAME</strong>: 表空间的名称。对于 file-per-table 表空间,名称通常以 <code>&lt;schema_name&gt;/&lt;table_name&gt;</code> 的形式出现。</li><li><strong>PATH</strong>: 表空间数据文件的路径。如果 file-per-table 表空间在 MySQL 数据目录之外的位置创建,则路径值是完整的目录路径。否则,路径是相对于数据目录的。</li><li><strong>FLAG</strong>: 一个数值,表示有关表空间格式和存储特征的位级信息。</li><li><strong>SPACE_TYPE</strong>: 表空间的类型。可能的值包括 <code>General</code> 通用表空间 、<code>Single</code> file-per-table 表空间 和 <code>System</code> 系统表空间 。</li></ul><p><code>INNODB_TABLESPACES_BRIEF</code> 表提供了比 <code>INNODB_TABLESPACES</code> 更快加载的元数据子集,因为它不包含如 <code>FS_BLOCK_SIZE</code>、<code>FILE_SIZE</code> 和 <code>ALLOCATED_SIZE</code> 等需要动态加载的其他元数据。空间和路径元数据也可以通过 <code>INNODB_DATAFILES</code> 表获得。</p><p>例如,要查询特定表空间的信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_TABLESPACES_BRIEF <span class="keyword">WHERE</span> SPACE [特定的SPACE_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的SPACE_ID]</code> 替换为你想要查询的表空间的 ID。这个表对于数据库管理员在进行表空间管理和监控时非常有用,因为它提供了快速访问表空间基本信息的方式 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img41.avif"></p><h3 id="INNODB-TABLESTATS"><a href="#INNODB-TABLESTATS" class="headerlink" title="INNODB_TABLESTATS"></a>INNODB_TABLESTATS</h3><p><code>INNODB_TABLESTATS</code> 提供了一个视图,展示了关于 InnoDB 表的低层次状态信息。这些数据被 MySQL 优化器用来计算查询 InnoDB 表时应该使用哪个索引。这些信息来源于内存中的数据结构,而不是存储在磁盘上的数据。如果表自从上次服务器重启后被打开过,并且没有从表缓存中老化出去,那么这个表就会在视图中表示出来。如果持久性统计信息可用,那么这些表也总是会在这个视图中表示出来。</p><p><code>INNODB_TABLESTATS</code> 表包含以下列:</p><ul><li><strong>TABLE_ID</strong>:表的标识符,与 <code>INNODB_TABLES.TABLE_ID</code> 的值相同。</li><li><strong>NAME</strong>:表的名称,与 <code>INNODB_TABLES.NAME</code> 的值相同。</li><li><strong>STATS_INITIALIZED</strong>:如果已经收集了统计信息,值为 <code>Initialized</code>;如果没有,则为 <code>Uninitialized</code>。</li><li><strong>NUM_ROWS</strong>:表中当前估计的行数。每次 DML 操作后更新。如果未提交的事务正在向表中插入或从表中删除数据,则这个值可能不精确。</li><li><strong>CLUST_INDEX_SIZE</strong>:存储聚集索引的磁盘上的页数,它以主键顺序保存 InnoDB 表数据。如果尚未为表收集统计信息,则此值可能为 null。</li><li><strong>OTHER_INDEX_SIZE</strong>:存储表的所有二级索引的磁盘上的页数。如果尚未为表收集统计信息,则此值可能为 null。</li><li><strong>MODIFIED_COUNTER</strong>:DML 操作修改的行数,例如 <code>INSERT</code>、<code>UPDATE</code>、<code>DELETE</code>,以及外键的级联操作。每次表统计信息被重新计算时,此列都会被重置。</li><li><strong>AUTOINC</strong>:下一次任何基于自动增量的操作将发出的数字。<code>AUTOINC</code> 值变化的速度取决于请求自动增量号码的次数以及每次请求授予的号码数量。</li><li><strong>REF_COUNT</strong>:当此计数器达到零时,表的元数据可以从表缓存中逐出。</li></ul><p>例如,要查看表的统计信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_TABLESTATS <span class="keyword">WHERE</span> TABLE_ID [特定的TABLE_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的TABLE_ID]</code> 替换为你想要查询的表的 <code>TABLE_ID</code>。需要注意的是,查询这个视图通常需要有 <code>PROCESS</code> 权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img42.avif"></p><h3 id="INNODB-TEMP-TABLE-INFO"><a href="#INNODB-TEMP-TABLE-INFO" class="headerlink" title="INNODB_TEMP_TABLE_INFO"></a>INNODB_TEMP_TABLE_INFO</h3><p><code>INNODB_TEMP_TABLE_INFO</code> 提供了关于 InnoDB 实例中活动的用户创建的临时表的信息。这个表不包括关于 InnoDB 优化器使用的内部临时表的信息。这个表在第一次被查询时创建,只存在于内存中,不会持久化到磁盘。</p><p>以下是 <code>INNODB_TEMP_TABLE_INFO</code> 表中的一些关键列:</p><ul><li><strong>TABLE_ID</strong>: 临时表的表 ID。</li><li><strong>NAME</strong>: 临时表的名称。系统为临时表生成的名称,该名称以 #sql 为前缀。</li><li><strong>N_COLS</strong>: 临时表中的列数。这个数字包括由 InnoDB 创建的三个隐藏列:<code>DB_ROW_ID</code>、<code>DB_TRX_ID</code> 和 <code>DB_ROLL_PTR</code>。</li><li><strong>SPACE</strong>: 临时表所在的临时表空间的 ID。在 MySQL 5.7 中,非压缩的 InnoDB 临时表驻留在共享临时表空间中。共享临时表空间的数据文件由 <code>innodb_temp_data_file_path</code> 系统变量定义。压缩的临时表驻留在单独的文件表空间中,这些表空间位于由 <code>tmpdir</code> 定义的临时目录中。</li><li><strong>PER_TABLE_TABLESPACE</strong>: 如果值为 <code>TRUE</code> 表示临时表驻留在单独的 file-per-table 表空间中。如果值为 <code>FALSE</code> 表示临时表驻留在共享临时表空间中。</li><li><strong>IS_COMPRESSED</strong>: 如果值为 <code>TRUE</code> 表示临时表已压缩。</li></ul><p>这个表对于专家级别的监控非常有用,需要 <code>PROCESS</code> 权限才能查询此表。重启 MySQL 后,查询 <code>INNODB_TEMP_TABLE_INFO</code> 会返回空集,因为数据不会持久保存到磁盘 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img43.avif"></p><h3 id="INNODB-TRX"><a href="#INNODB-TRX" class="headerlink" title="INNODB_TRX"></a>INNODB_TRX</h3><p><code>INNODB_TRX</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了当前在 InnoDB 存储引擎中执行的每个事务的详细信息。这些信息包括事务是否正在等待锁、事务何时开始以及事务正在执行的 SQL 语句 如果有的话 。</p><p>以下是 <code>INNODB_TRX</code> 表中的一些关键列:</p><ul><li><strong>TRX_ID</strong>: InnoDB 内部生成的事务唯一 ID 号。</li><li><strong>TRX_WEIGHT</strong>: 事务的权重,反映 但不一定是确切的计数 更改的行数和事务锁定的行数。InnoDB 在解决死锁时会选择权重最小的事务作为“受害者”进行回滚。</li><li><strong>TRX_STATE</strong>: 事务的执行状态,可能的值包括 <code>RUNNING</code>、<code>LOCK WAIT</code>、<code>ROLLING BACK</code> 和 <code>COMMITTING</code>。</li><li><strong>TRX_STARTED</strong>: 事务开始的时间戳。</li><li><strong>TRX_REQUESTED_LOCK_ID</strong>: 如果事务处于 <code>LOCK WAIT</code> 状态,此字段标识它正在等待的锁的 ID。</li><li><strong>TRX_WAIT_STARTED</strong>: 如果事务在等待锁,记录等待开始的时间。</li><li><strong>TRX_MYSQL_THREAD_ID</strong>: MySQL 线程 ID,与执行事务的客户端线程相关联。</li><li><strong>TRX_QUERY</strong>: 正在执行的事务中的 SQL 语句文本。</li><li><strong>TRX_TABLES_IN_USE</strong>: 当前事务中涉及的表数量。</li><li><strong>TRX_TABLES_LOCKED</strong>: 被事务锁定的表数量。</li><li><strong>TRX_LOCK_STRUCTS</strong>: 事务保留的锁数量。</li><li><strong>TRX_LOCK_MEMORY_BYTES</strong>: 此事务的锁结构在内存中占用的总大小。</li><li><strong>TRX_ROWS_LOCKED</strong>: 此事务锁定的大概行数。</li><li><strong>TRX_ROWS_MODIFIED</strong>: 此事务中修改和插入的行数。</li><li><strong>TRX_CONCURRENCY_TICKETS</strong>: 一个值,表示当前事务在被换出之前可以做多少工作,由 <code>innodb_concurrency_tickets</code> 系统变量指定。</li><li><strong>TRX_ISOLATION_LEVEL</strong>: 当前事务的隔离级别。</li><li><strong>TRX_UNIQUE_CHECKS</strong>: 是否为当前事务打开或关闭唯一检查。</li><li><strong>TRX_FOREIGN_KEY_CHECKS</strong>: 是否为当前事务打开或关闭外键检查。</li><li><strong>TRX_LAST_FOREIGN_KEY_ERROR</strong>: 最后一次的外键错误信息,如果有的话;否则 <code>NULL</code>。</li><li><strong>TRX_ADAPTIVE_HASH_LATCHED</strong>: 自适应哈希索引是否被当前事务锁定。</li><li><strong>TRX_ADAPTIVE_HASH_TIMEOUT</strong>: 是否为了自适应哈希索引立即放弃查询锁,或者通过调用 MySQL 函数保留它。</li><li><strong>TRX_IS_READ_ONLY</strong>: 值为 1 表示事务是只读的。</li><li><strong>TRX_AUTOCOMMIT_NON_LOCKING</strong>: 值为 1 表示该事务是一个 <code>SELECT</code> 语句,该语句没有使用 <code>FOR UPDATE</code> 或 <code>LOCK IN SHARED MODE</code> 子句,并且执行开启了 <code>autocommit</code>,因此该事务只包含这一条语句。</li></ul><p>这个表对于监控和诊断数据库中的事务活动、识别长期运行的事务、检测死锁以及分析性能问题非常有帮助。查询这个表需要有 <code>PROCESS</code> 权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img44.avif"></p><h3 id="INNODB-VIRTUAL"><a href="#INNODB-VIRTUAL" class="headerlink" title="INNODB_VIRTUAL"></a>INNODB_VIRTUAL</h3><p><code>INNODB_VIRTUAL</code> 是 MySQL 中的一个系统表,它包含了 InnoDB 存储引擎中所有虚拟生成列的信息。虚拟生成列是一种特殊类型的列,它在查询时动态生成值,而不是存储在表中。这些列的值通常基于表中的其他列计算得出。</p><p>在 InnoDB 的数据字典中,<code>INNODB_VIRTUAL</code> 表扮演着重要的角色,它存储了虚拟列的元数据,包括列的名字、类型、表达式等信息。这些信息对于 InnoDB 存储引擎在查询时动态计算虚拟列的值至关重要。</p><p>虚拟生成列可以在创建表时定义,也可以在后续通过 <code>ALTER TABLE</code> 语句添加。它们的值是由用户定义的表达式计算得出的,表达式可以包含表中的其他列。</p><p>例如,如果有一个包含 <code>name</code> 和 <code>lastname</code> 列的表,可以定义一个虚拟列 <code>full_name</code> 来存储全名:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> my_table</span><br><span class="line"><span class="keyword">ADD</span> full_name <span class="keyword">AS</span> (name <span class="operator">||</span> lastname) VIRTUAL;</span><br></pre></td></tr></table></figure><p>在这个例子中,<code>full_name</code> 就是一个虚拟生成列,它的值是通过连接 <code>name</code> 和 <code>lastname</code> 列的值来计算的。</p><p><code>INNODB_VIRTUAL</code> 表是 InnoDB 存储引擎内部使用的,通常不需要用户直接查询或修改。它作为数据字典的一部分,由 MySQL 服务器在启动时自动填充和管理。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img45.avif"></p><p>查询结果显示了 <code>INNODB_VIRTUAL</code> 表中的一些行。这个表通常包含以下字段:</p><ul><li><code>TABLE_ID</code>: 表的唯一标识符。</li><li><code>POS</code>: 虚拟列在表中的位置上的偏移量。</li><li><code>BASE_POS</code>: 基柱 base column 的位置,虚拟列的值通常依赖于这个基柱。</li></ul><h3 id="KEYWORDS"><a href="#KEYWORDS" class="headerlink" title="KEYWORDS"></a>KEYWORDS</h3><p>在MySQL中,<code>information_schema</code> 是一个特殊的数据库,它包含了所有其他数据库的元数据,比如表结构、权限、字符集等信息。<code>information_schema</code> 中的 <code>KEYWORDS</code> 表列出了MySQL中所有的保留关键字及其状态。</p><p>从你提供的查询结果来看,<code>KEYWORDS</code> 表包含两列:</p><ul><li><p><code>WORD</code>:这是MySQL中的保留关键字。</p></li><li><p><code>RESERVED</code>:这个列显示了关键字的状态,其中:</p></li><li><p><code>1</code> 表示该关键字是保留的,不能用作任何标识符 除非使用反引号 。</p></li><li><p><code>0</code> 表示该关键字不是保留的,可以作为标识符使用。</p></li></ul><p>这个表对于开发者来说很有用,因为它可以帮助他们避免在创建数据库对象时使用保留关键字作为标识符,从而避免语法错误。</p><p>如果你想查看所有保留关键字,可以使用以下命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> WORD <span class="keyword">FROM</span> information_schema.KEYWORDS <span class="keyword">WHERE</span> RESERVED <span class="number">1</span>;</span><br></pre></td></tr></table></figure><p>这将列出所有保留关键字。如果你需要查看所有非保留关键字,可以使用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> WORD <span class="keyword">FROM</span> information_schema.KEYWORDS <span class="keyword">WHERE</span> RESERVED <span class="number">0</span>;</span><br></pre></td></tr></table></figure><p>希望这能帮助你更好地理解 <code>information_schema.KEYWORDS</code> 表。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img46.avif"></p><h3 id="KEY-COLUMN-USAGE"><a href="#KEY-COLUMN-USAGE" class="headerlink" title="KEY_COLUMN_USAGE"></a>KEY_COLUMN_USAGE</h3><p><code>KEY_COLUMN_USAGE</code> 是 <code>information_schema</code> 数据库中的一个表,它描述了哪些键列具有约束。这个表包含了关于表中列的键约束信息,包括主键、唯一键以及外键的详细信息。以下是 <code>KEY_COLUMN_USAGE</code> 表的主要字段及其含义:</p><ul><li><code>CONSTRAINT_CATALOG</code>: 约束所属目录的名称,通常为 <code>def</code>。</li><li><code>CONSTRAINT_SCHEMA</code>: 约束所属的数据库名称。</li><li><code>CONSTRAINT_NAME</code>: 约束的名称。</li><li><code>TABLE_CATALOG</code>: 表所属目录的名称,通常为 <code>def</code>。</li><li><code>TABLE_SCHEMA</code>: 表所属的数据库名称。</li><li><code>TABLE_NAME</code>: 具有约束的表的名称。</li><li><code>COLUMN_NAME</code>: 具有约束的列的名称。如果约束是外键,那么这是外键的列,而不是外键引用的列。</li><li><code>ORDINAL_POSITION</code>: 列在约束中的位置,列位置从 1 开始编号。</li><li><code>POSITION_IN_UNIQUE_CONSTRAINT</code>: 对于唯一和主键约束,此值为 <code>NULL</code>。对于外键约束,此列是被引用表的键中的序号位置。</li><li><code>REFERENCED_TABLE_SCHEMA</code>: 约束引用的模式 数据库 的名称。</li><li><code>REFERENCED_TABLE_NAME</code>: 约束引用的表的名称。</li><li><code>REFERENCED_COLUMN_NAME</code>: 约束引用的列的名称。</li></ul><p>这个表对于理解和管理数据库中的约束关系非常有用。例如,如果你想查看特定数据库中所有表的键列信息,可以使用以下查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> TABLE_NAME, COLUMN_NAME, CONSTRAINT_NAME</span><br><span class="line"><span class="keyword">FROM</span> information_schema.KEY_COLUMN_USAGE</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>替换 <code>&#39;your_database_name&#39;</code> 为你的数据库名称,这将列出该数据库中所有表的键列及其约束名称。</p><p>如果你想要获取特定表的所有键列信息,可以进一步指定表名:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> TABLE_NAME, COLUMN_NAME, CONSTRAINT_NAME</span><br><span class="line"><span class="keyword">FROM</span> information_schema.KEY_COLUMN_USAGE</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>替换 <code>&#39;your_database_name&#39;</code> 和 <code>&#39;your_table_name&#39;</code> 为你的数据库名称和表名称。</p><p>此外,如果你想获取特定表的外键信息,可以使用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> TABLE_NAME, COLUMN_NAME, CONSTRAINT_NAME, REFERENCED_TABLE_NAME, REFERENCED_COLUMN_NAME</span><br><span class="line"><span class="keyword">FROM</span> information_schema.KEY_COLUMN_USAGE</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span> <span class="keyword">AND</span> REFERENCED_TABLE_NAME <span class="keyword">IS</span> <span class="keyword">NOT NULL</span>;</span><br></pre></td></tr></table></figure><p>这将列出所有作为外键的列及其引用的表和列的信息。</p><p><code>information_schema</code> 是一个只读模式的数据库,不能对其进行修改,查询它通常不需要锁定表,因此性能影响较小。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img47.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img48.avif"></p><h3 id="OPTIMIZER-TRACE"><a href="#OPTIMIZER-TRACE" class="headerlink" title="OPTIMIZER_TRACE"></a>OPTIMIZER_TRACE</h3><p><code>OPTIMIZER_TRACE</code> 是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它存储了关于 SQL 语句优化过程的跟踪信息。这个表是从 MySQL 5.6 版本开始引入的,用于帮助开发者和数据库管理员理解 MySQL 优化器是如何工作的。</p><p>要使用 <code>OPTIMIZER_TRACE</code>,你首先需要通过设置 <code>optimizer_trace</code> 系统变量来启用跟踪功能。之后,当你执行一个 SQL 语句时,优化器的决策过程会被记录下来,并以 JSON 格式保存在 <code>OPTIMIZER_TRACE</code> 表的 <code>TRACE</code> 列中。</p><p>以下是 <code>OPTIMIZER_TRACE</code> 表中的一些关键列:</p><ul><li><strong>QUERY</strong>: 被跟踪的 SQL 语句文本。</li><li><strong>TRACE</strong>: 跟踪信息,以 JSON 格式表现。</li><li><strong>MISSING_BYTES_BEYOND_MAX_MEM_SIZE</strong>: 如果跟踪信息超过了 <code>optimizer_trace_max_mem_size</code> 指定的内存大小限制,则该列显示丢失的字节数。</li><li><strong>INSUFFICIENT_PRIVILEGES</strong>: 如果被跟踪的 SQL 使用了没有权限的视图或存储过程,则该列值为 1,表示没有足够的权限查看完整的跟踪信息。</li></ul><p>使用 <code>OPTIMIZER_TRACE</code> 可以帮助你分析和解决查询性能问题,理解为什么优化器选择了特定的执行计划,以及是否有更优的执行计划未被选择。通过分析 <code>TRACE</code> 列中的 JSON 数据,你可以获得关于优化器决策的深入信息,比如是否使用了索引、是否进行了表的合并、是否进行了子查询优化等。</p><p>例如,要启用优化器跟踪并执行一个查询,你可以按照以下步骤操作:</p><ul><li>启用优化器跟踪:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> SESSION OPTIMIZER_TRACE enabled <span class="keyword">on</span> ;</span><br></pre></td></tr></table></figure><ul><li>执行你的查询语句。</li><li>查看跟踪结果:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> information_schema.OPTIMIZER_TRACE;</span><br></pre></td></tr></table></figure><ul><li>可选 关闭优化器跟踪:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> SESSION OPTIMIZER_TRACE enabled off ;</span><br></pre></td></tr></table></figure><p>需要注意的是,<code>OPTIMIZER_TRACE</code> 表只会显示最近一次的跟踪结果,如果你需要跟踪多个语句,可以使用 <code>optimizer_trace_offset</code> 和 <code>optimizer_trace_limit</code> 来控制跟踪的条目数量和偏移量。</p><p>此外,如果跟踪信息过于复杂,为了提高可读性,你可以设置 <code>optimizer_trace_one_line</code> 为 <code>on</code>,这样跟踪信息会以单行的形式展示,但这可能会牺牲可读性。</p><p>更多详细信息,可以参考 MySQL 官方文档 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img49.avif"></p><p>例子:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br><span class="line">100</span><br><span class="line">101</span><br><span class="line">102</span><br><span class="line">103</span><br><span class="line">104</span><br><span class="line">105</span><br><span class="line">106</span><br></pre></td><td class="code"><pre><span class="line">MySQL (<span class="keyword">none</span>) (<span class="keyword">none</span>):information_schema<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> OPTIMIZER_TRACE\G</span><br><span class="line"><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span>[ <span class="number">1.</span> <span class="type">row</span> ]<span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span></span><br><span class="line">QUERY <span class="operator">|</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> demo1.t1</span><br><span class="line">TRACE <span class="operator">|</span> &#123;</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">join_preparation : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">expanded_query : <span class="comment">/* select#1 */</span> <span class="keyword">select</span> demo1 . t1 . a <span class="keyword">AS</span> a , demo1 . t1 . b <span class="keyword">AS</span> b , demo1 . t1 . c <span class="keyword">AS</span> c , demo1 . t1 . c11 <span class="keyword">AS</span> c11 <span class="keyword">from</span> demo1 . t1</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">join_optimization : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">&#123;</span><br><span class="line">table_dependencies : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : demo1 . t1 ,</span><br><span class="line">row_may_be_null : <span class="literal">false</span>,</span><br><span class="line">map_bit : <span class="number">0</span>,</span><br><span class="line">depends_on_map_bits : [</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">rows_estimation : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : demo1 . t1 ,</span><br><span class="line">table_scan : &#123;</span><br><span class="line"><span class="keyword">rows</span> : <span class="number">3</span>,</span><br><span class="line">cost : <span class="number">0.25</span></span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">considered_execution_plans : [</span><br><span class="line">&#123;</span><br><span class="line">plan_prefix : [</span><br><span class="line">],</span><br><span class="line"><span class="keyword">table</span> : demo1 . t1 ,</span><br><span class="line">best_access_path : &#123;</span><br><span class="line">considered_access_paths : [</span><br><span class="line">&#123;</span><br><span class="line">rows_to_scan : <span class="number">3</span>,</span><br><span class="line">access_type : scan ,</span><br><span class="line">resulting_rows : <span class="number">3</span>,</span><br><span class="line">cost : <span class="number">0.55</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">condition_filtering_pct : <span class="number">100</span>,</span><br><span class="line">rows_for_plan : <span class="number">3</span>,</span><br><span class="line">cost_for_plan : <span class="number">0.55</span>,</span><br><span class="line">chosen : <span class="literal">true</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">attaching_conditions_to_tables : &#123;</span><br><span class="line">original_condition : <span class="keyword">null</span>,</span><br><span class="line">attached_conditions_computation : [</span><br><span class="line">],</span><br><span class="line">attached_conditions_summary : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : demo1 . t1 ,</span><br><span class="line">attached : <span class="keyword">null</span></span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">finalizing_table_conditions : [</span><br><span class="line">]</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">refine_plan : [</span><br><span class="line">&#123;</span><br><span class="line"><span class="keyword">table</span> : demo1 . t1</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;,</span><br><span class="line">&#123;</span><br><span class="line">join_execution : &#123;</span><br><span class="line"><span class="keyword">select</span># : <span class="number">1</span>,</span><br><span class="line">steps : [</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">]</span><br><span class="line">&#125;</span><br><span class="line">MISSING_BYTES_BEYOND_MAX_MEM_SIZE <span class="operator">|</span> <span class="number">0</span></span><br><span class="line">INSUFFICIENT_PRIVILEGES <span class="operator">|</span> <span class="number">0</span></span><br><span class="line"></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span></span><br><span class="line"><span class="type">Time</span>: <span class="number">0.002</span>s</span><br></pre></td></tr></table></figure><h3 id="PARAMETERS"><a href="#PARAMETERS" class="headerlink" title="PARAMETERS"></a>PARAMETERS</h3><p>在 MySQL 中,<code>PARAMETERS</code> 表属于 <code>INFORMATION_SCHEMA</code> 数据库,它提供了关于存储过程、函数、触发器、事件等数据库对象的参数的详细信息。这个表通常用于查看这些数据库对象的参数定义,包括参数名称、类型、方向 如输入、输出或两者兼有 等。</p><p>根据你提供的查询结果,<code>PARAMETERS</code> 表显示了某个特定数据库对象 在这个例子中是一个函数 的参数信息。以下是你提供的结果中的列的解释:</p><ul><li><strong>SPECIFIC_CATALOG</strong>: 包含数据库对象的数据库名称。</li><li><strong>SPECIFIC_SCHEMA</strong>: 包含数据库对象的数据库的默认模式或数据库。</li><li><strong>SPECIFIC_NAME</strong>: 数据库对象的名称。</li><li><strong>ORDINAL_POSITION</strong>: 参数在对象定义中的位置 从 1 开始 。</li><li><strong>PARAMETER_MODE</strong>: 参数的方向 如 IN、OUT、INOUT 。对于存储过程和函数的参数,这个值可能是 NULL,因为这些对象通常只使用 IN 类型的参数。</li><li><strong>PARAMETER_NAME</strong>: 参数的名称。在这个例子中,该列为 NULL,可能是因为这是一个函数,而函数可能不需要参数。</li><li><strong>DATA_TYPE</strong>: 参数的数据类型。</li><li><strong>CHARACTER_MAXIMUM_LENGTH</strong>: 如果参数是字符类型,这是最大长度。</li><li><strong>CHARACTER_OCTET_LENGTH</strong>: 如果参数是字符类型,这是最大字节长度。</li><li><strong>NUMERIC_PRECISION</strong>: 如果参数是数字类型,这是精度。</li><li><strong>NUMERIC_SCALE</strong>: 如果参数是数字类型,这是小数点后的位数。</li><li><strong>DATETIME_PRECISION</strong>: 如果参数是日期或时间类型,这是精度。</li><li><strong>CHARACTER_SET_NAME</strong>: 参数使用的字符集名称。</li><li><strong>COLLATION_NAME</strong>: 参数使用的排序规则名称。</li><li><strong>DTD_IDENTIFIER</strong>: 参数的数据类型标识符,通常与 DATA_TYPE 列相同。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img50.avif"></p><h3 id="PARTITIONS"><a href="#PARTITIONS" class="headerlink" title="PARTITIONS"></a>PARTITIONS</h3><p>在 MySQL 中,<code>PARTITIONS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库的一部分,它提供了关于分区表的分区信息。分区是一种数据库优化技术,它允许你将一个大表分割成多个更小的、更易于管理的部分,每个部分称为一个分区。分区可以提高查询性能,优化数据维护任务,如备份和恢复。</p><p>以下是 <code>INFORMATION_SCHEMA.PARTITIONS</code> 表中可能包含的一些关键列:</p><ul><li><strong>TABLE_CATALOG</strong>: 表所在的数据库名称。</li><li><strong>TABLE_SCHEMA</strong>: 表的模式 通常称为数据库 。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>PARTITION_EXPRESSION</strong>: 定义分区的表达式。</li><li><strong>PARTITION_DESCRIPTION</strong>: 分区的描述。</li><li><strong>TABLE_ROWS</strong>: 表中估计的行数。</li><li><strong>AVG_ROW_LENGTH</strong>: 表中行的平均长度。</li><li><strong>DATA_LENGTH</strong>: 分区中数据的长度。</li><li><strong>MAX_DATA_LENGTH</strong>: 分区中数据的最大长度。</li><li><strong>INDEX_LENGTH</strong>: 分区索引的长度。</li><li><strong>DATA_FREE</strong>: 分区中的空闲空间。</li><li><strong>CREATE_TIME</strong>: 分区创建的时间。</li><li><strong>UPDATE_TIME</strong>: 分区上次更新的时间。</li><li><strong>CHECK_TIME</strong>: 分区上次检查的时间。</li><li><strong>CHECKSUM</strong>: 分区的校验和。</li><li><strong>PARTITION_COMMENT</strong>: 分区的注释。</li><li><strong>NODEGROUP</strong>: 分区所属的节点组。</li><li><strong>TABLESPACE_NAME</strong>: 分区使用的表空间名称。</li></ul><p>要查询 <code>PARTITIONS</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PARTITIONS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 和 <code>your_table_name</code> 替换为你要查询的数据库和表的名称。这将返回指定表的所有分区信息。</p><p>例如,如果你想查看 <code>employees</code> 表的所有分区信息,你可以执行:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PARTITIONS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;employees&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回 <code>employees</code> 表的分区方案的详细信息,包括每个分区的行数、大小、索引长度等。</p><p>请注意,<code>PARTITIONS</code> 表可能不包含所有 MySQL 版本中的所有列。某些列可能在特定版本中不可用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img51.avif"></p><h3 id="PLUGINS"><a href="#PLUGINS" class="headerlink" title="PLUGINS"></a>PLUGINS</h3><p><code>PLUGINS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于 MySQL 服务器上可用插件的信息。插件通常是动态加载的库,它们为 MySQL 服务器提供额外的功能,比如身份验证插件、存储引擎插件、审计插件等。</p><p>以下是 <code>INFORMATION_SCHEMA.PLUGINS</code> 表中可能包含的一些关键列:</p><ul><li><strong>PLUGIN_NAME</strong>: 插件的名称。</li><li><strong>PLUGIN_VERSION</strong>: 插件的版本。</li><li><strong>PLUGIN_STATUS</strong>: 插件的状态 例如 <code>ACTIVE</code>、<code>INACTIVE</code>、<code>DISABLED</code> 。</li><li><strong>PLUGIN_TYPE</strong>: 插件的类型 例如 <code>AUTHENTICATION</code>、<code>STORAGE ENGINE</code>、<code>SERVICE</code> 。</li><li><strong>PLUGIN_TYPE_VERSION</strong>: 插件类型的版本。</li><li><strong>PLUGIN_LIBRARY</strong>: 插件使用的库文件的名称。</li><li><strong>PLUGIN_LIBRARY_VERSION</strong>: 库文件的版本。</li><li><strong>PLUGIN_SOURCE</strong>: 插件的来源 例如 <code>FILE</code>、<code>FUNCTION</code>、<code>KEYRING</code> 。</li><li><strong>PLUGIN_AUTHOR</strong>: 插件的作者。</li><li><strong>PLUGIN_DESCRIPTION</strong>: 插件的描述。</li></ul><p>要查询 <code>PLUGINS</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PLUGINS;</span><br></pre></td></tr></table></figure><p>这将返回服务器上所有插件的列表及其相关信息。这对于了解服务器上安装了哪些插件以及它们的当前状态非常有用。</p><p>例如,如果你想查看所有激活的存储引擎插件,你可以执行:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> PLUGIN_NAME, PLUGIN_STATUS <span class="keyword">FROM</span> INFORMATION_SCHEMA.PLUGINS</span><br><span class="line"><span class="keyword">WHERE</span> PLUGIN_TYPE <span class="string">&#x27;STORAGE ENGINE&#x27;</span> <span class="keyword">AND</span> PLUGIN_STATUS <span class="string">&#x27;ACTIVE&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回所有当前激活的存储引擎插件的名称和状态。</p><p><code>PLUGINS</code> 表是管理和维护 MySQL 服务器时的一个有用资源,特别是在处理存储引擎或身份验证机制时。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img52.avif"></p><h3 id="PROCESSLIST"><a href="#PROCESSLIST" class="headerlink" title="PROCESSLIST"></a>PROCESSLIST</h3><p>在 MySQL 中,<code>PROCESSLIST</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了当前 MySQL 服务器上所有活动线程的列表。这个表对于监控和诊断数据库性能问题、锁定问题和其他并发问题非常有用。</p><p>以下是 <code>INFORMATION_SCHEMA.PROCESSLIST</code> 表中可能包含的一些关键列:</p><ul><li><strong>ID</strong>: 线程的唯一标识符。</li><li><strong>USER</strong>: 执行线程的 MySQL 用户名。</li><li><strong>HOST</strong>: 用户连接的主机名和端口号。</li><li><strong>DB</strong>: 当前线程正在操作的数据库名称。如果线程没有操作数据库,则此列为 <code>NULL</code>。</li><li><strong>COMMAND</strong>: 线程正在执行的命令类型 例如 <code>Query</code>、<code>Sleeping</code>、<code>Connect</code> 等 。</li><li><strong>TIME</strong>: 线程执行当前命令的时间长度 秒 。对于 <code>Sleeping</code> 线程,这是它等待的时长。</li><li><strong>STATE</strong>: 线程的状态,例如 <code>Sleeping</code>、<code>Locked</code>、<code>Query</code> 等。</li><li><strong>INFO</strong>: 线程正在执行的 SQL 语句的前 100 个字符。对于非查询命令,此列可能包含额外的状态信息。</li></ul><p>要查询 <code>PROCESSLIST</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PROCESSLIST;</span><br></pre></td></tr></table></figure><p>这将返回服务器上所有当前活动的线程的列表。</p><p>例如,如果你想查看特定用户的活动线程,你可以执行:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PROCESSLIST <span class="keyword">WHERE</span> <span class="keyword">USER</span> <span class="string">&#x27;your_username&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_username</code> 替换为你要查询的用户名。</p><p><code>PROCESSLIST</code> 表通常用于以下情况:</p><ul><li><strong>性能监控</strong>:查看哪些查询正在执行以及它们的执行时长。</li><li><strong>锁定诊断</strong>:识别可能导致锁定问题的长时间运行的查询。</li><li><strong>资源使用</strong>:了解哪些线程正在使用数据库资源。</li></ul><p>请注意,<code>PROCESSLIST</code> 表中显示的信息可能会随着 MySQL 版本的不同而有所变化。此外,为了保护用户隐私,某些列 如 <code>INFO</code> 可能会截断显示的查询文本。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img53.avif"></p><h3 id="PROFILING"><a href="#PROFILING" class="headerlink" title="PROFILING"></a>PROFILING</h3><p><code>PROFILING</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于执行过的 SQL 语句的分析信息。这些信息可以帮助数据库管理员和开发者了解 SQL 语句执行过程中的资源消耗情况,例如 CPU 使用时间、I&#x2F;O 操作、上下文切换、页面错误等。</p><p>要使用 <code>PROFILING</code> 表,你需要先启用 MySQL 的分析功能,可以通过设置 <code>profiling</code> 系统变量为 1 来启用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> profiling <span class="number">1</span>;</span><br></pre></td></tr></table></figure><p>启用后,执行的 SQL 语句将被记录在 <code>PROFILING</code> 表中。这个表包含以下列:</p><ul><li><strong>QUERY_ID</strong>: 一个数字标识符,唯一地标识执行的 SQL 语句。</li><li><strong>SEQ</strong>: 一个序列号,指示具有相同 <code>QUERY_ID</code> 值的行的显示顺序。</li><li><strong>STATE</strong>: 行测量适用的分析状态,例如 Sending data 、 Creating sort index 等。</li><li><strong>DURATION</strong>: 语句执行在给定状态下保持多长时间,以秒为单位。</li><li><strong>CPU_USER</strong>, <strong>CPU_SYSTEM</strong>: 用户和系统 CPU 使用情况,以秒为单位。</li><li><strong>CONTEXT_VOLUNTARY</strong>, <strong>CONTEXT_INVOLUNTARY</strong>: 自愿和非自愿上下文切换的次数。</li><li><strong>BLOCK_OPS_IN</strong>, <strong>BLOCK_OPS_OUT</strong>: 块输入和输出操作的数量。</li><li><strong>MESSAGES_SENT</strong>, <strong>MESSAGES_RECEIVED</strong>: 发送和接收的通信消息数。</li><li><strong>PAGE_FAULTS_MAJOR</strong>, <strong>PAGE_FAULTS_MINOR</strong>: 主要和次要页面错误的数量。</li><li><strong>SWAPS</strong>: 发生了多少次交换。</li><li><strong>SOURCE_FUNCTION</strong>, <strong>SOURCE_FILE</strong>, <strong>SOURCE_LINE</strong>: 指示分析状态在源代码中执行位置的信息。</li></ul><p>你可以通过以下 SQL 语句查询 <code>PROFILING</code> 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.PROFILING <span class="keyword">WHERE</span> QUERY_ID [特定的QUERY_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的QUERY_ID]</code> 替换为你想要查询的 SQL 语句的 <code>QUERY_ID</code>。这将返回指定 SQL 语句的分析信息。</p><p><code>PROFILING</code> 表是分析和优化 SQL 性能的有力工具,它可以帮助识别性能瓶颈和资源消耗的热点。不过,需要注意的是,频繁地使用 <code>PROFILING</code> 可能会对数据库性能产生一定影响,因此建议在分析问题时开启,在不需要时关闭该功能 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img54.avif"></p><h3 id="REFERENTIAL-CONSTRAINTS"><a href="#REFERENTIAL-CONSTRAINTS" class="headerlink" title="REFERENTIAL_CONSTRAINTS"></a>REFERENTIAL_CONSTRAINTS</h3><p><code>REFERENTIAL_CONSTRAINTS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了数据库中所有外键约束的详细信息。外键约束用于维护两个表之间的关系,确保引用完整性,即子表中的外键值必须在父表中有对应的值。</p><p>以下是 <code>INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS</code> 表中的一些关键列:</p><ul><li><strong>CONSTRAINT_CATALOG</strong>: 约束所属目录的名称,对于 MySQL,这个值通常是 <code>def</code>。</li><li><strong>CONSTRAINT_SCHEMA</strong>: 约束所属的数据库 模式 名称。</li><li><strong>CONSTRAINT_NAME</strong>: 外键约束的名称。</li><li><strong>UNIQUE_CONSTRAINT_CATALOG</strong>: 引用的唯一约束所在的目录名称,对于 MySQL,这个值通常是 <code>def</code>。</li><li><strong>UNIQUE_CONSTRAINT_SCHEMA</strong>: 引用的唯一约束所在的数据库 模式 名称。</li><li><strong>UNIQUE_CONSTRAINT_NAME</strong>: 被引用的唯一约束的名称。</li><li><strong>MATCH_OPTION</strong>: 匹配选项,通常是 <code>NONE</code>,表示没有特殊的匹配规则。</li><li><strong>UPDATE_RULE</strong>: <code>ON UPDATE</code> 动作的规则,可能的值包括 <code>CASCADE</code>、<code>SET NULL</code>、<code>SET DEFAULT</code>、<code>RESTRICT</code>、<code>NO ACTION</code>。</li><li><strong>DELETE_RULE</strong>: <code>ON DELETE</code> 动作的规则,可能的值与 <code>UPDATE_RULE</code> 相同。</li><li><strong>TABLE_NAME</strong>: 包含外键的表的名称。</li><li><strong>REFERENCED_TABLE_NAME</strong>: 被引用的表的名称。</li></ul><p>通过查询 <code>REFERENTIAL_CONSTRAINTS</code> 表,可以查看数据库中外键约束的详细信息,例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> CONSTRAINT_NAME, UPDATE_RULE, DELETE_RULE, TABLE_NAME, REFERENCED_TABLE_NAME</span><br><span class="line"><span class="keyword">FROM</span> INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS</span><br><span class="line"><span class="keyword">WHERE</span> CONSTRAINT_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 替换为你要查询的数据库名称。这将返回指定数据库中所有外键约束的更新和删除规则,以及它们所在的表和被引用的表的名称。</p><p>这个表对于理解和管理数据库的外键约束非常有用,尤其是在进行数据完整性和数据关系管理时。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img55.avif"></p><h3 id="RESOURCE-GROUPS"><a href="#RESOURCE-GROUPS" class="headerlink" title="RESOURCE_GROUPS"></a>RESOURCE_GROUPS</h3><p><code>RESOURCE_GROUPS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于服务器上定义的资源组的信息。资源组是 MySQL 8.0 引入的功能,它允许数据库管理员对服务器上的资源进行更细粒度的控制,特别是 CPU 资源。</p><p>资源组可以是 <code>USER</code> 类型或 <code>SYSTEM</code> 类型,分别对应于用户线程和系统线程。通过资源组,管理员可以控制这些线程可以使用的 CPU 称为 vCPU 或虚拟 CPU ,以及线程的优先级。</p><p>以下是 <code>INFORMATION_SCHEMA.RESOURCE_GROUPS</code> 表中的一些关键列:</p><ul><li><strong>RESOURCE_GROUP_NAME</strong>: 资源组的名称。</li><li><strong>RESOURCE_GROUP_TYPE</strong>: 资源组的类型,可以是 <code>USER</code> 或 <code>SYSTEM</code>。</li><li><strong>RESOURCE_GROUP_ENABLED</strong>: 表示资源组是否启用,1 表示启用,0 表示禁用。</li><li><strong>VCPU_IDS</strong>: 资源组可以使用的虚拟 CPU 编号或范围。</li><li><strong>THREAD_PRIORITY</strong>: 资源组中线程的优先级,范围从 -20 最高 到 19 最低 。<code>SYSTEM</code> 类型的资源组优先级范围是 -20 到 0,而 <code>USER</code> 类型的资源组优先级范围是 0 到 19。</li></ul><p>默认情况下,MySQL 8.0 会创建两个资源组 <code>USR_default</code> 和 <code>SYS_default</code>。管理员可以根据需要创建额外的资源组,并分配特定的 CPU 资源和优先级。例如,可以创建一个资源组来管理不需要高优先级执行的批处理作业。</p><p>要查看资源组的信息,可以执行以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.RESOURCE_GROUPS;</span><br></pre></td></tr></table></figure><p>这将返回当前服务器上所有资源组的详细信息。管理员可以使用这些信息来监控和调整资源组的配置,以优化服务器的性能和资源利用率。</p><p>创建资源组的例子:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> RESOURCE <span class="keyword">GROUP</span> my_resource_group</span><br><span class="line">TYPE <span class="keyword">USER</span></span><br><span class="line">VCPU <span class="number">2</span><span class="number">-3</span></span><br><span class="line">THREAD_PRIORITY <span class="number">10</span>;</span><br></pre></td></tr></table></figure><p>查询特定资源组的信息:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.RESOURCE_GROUPS</span><br><span class="line"><span class="keyword">WHERE</span> RESOURCE_GROUP_NAME <span class="string">&#x27;my_resource_group&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这将返回名为 <code>my_resource_group</code> 的资源组的详细信息。</p><p>资源组管理是本地化的,不会复制到其他服务器。此外,某些平台或 MySQL 服务器配置可能限制了资源组的功能。例如,在 macOS 上,资源组不可用,因为 macOS 不提供用于将 CPU 绑定到线程的 API。在 Linux 上,除非设置了 <code>CAP_SYS_NICE</code> 功能,否则会忽略资源组线程优先级 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img56.avif"></p><h3 id="ROLE-COLUMN-GRANTS"><a href="#ROLE-COLUMN-GRANTS" class="headerlink" title="ROLE_COLUMN_GRANTS"></a>ROLE_COLUMN_GRANTS</h3><p><code>ROLE_COLUMN_GRANTS</code> 是 <code>INFORMATION_SCHEMA</code> 下的一个视图,它提供了关于数据库角色的列级权限的详细信息。此视图显示了授予者或被授予者是当前启用的角色的列上授予的所有权限。这可以帮助数据库管理员了解和维护数据库角色的权限设置。</p><p>以下是 <code>INFORMATION_SCHEMA.ROLE_COLUMN_GRANTS</code> 视图中的一些关键列:</p><ul><li><strong>GRANTOR</strong>: 授予权限的角色的名称。</li><li><strong>GRANTEE</strong>: 被授予权限的角色的名称。</li><li><strong>TABLE_CATALOG</strong>: 包含该列的表的数据库名称。</li><li><strong>TABLE_SCHEMA</strong>: 包含该列的表的模式 Schema 名称。</li><li><strong>TABLE_NAME</strong>: 包含该列的表的名称。</li><li><strong>COLUMN_NAME</strong>: 列的名称。</li><li><strong>PRIVILEGE_TYPE</strong>: 权限的类型,如 <code>SELECT</code>、<code>INSERT</code>、<code>UPDATE</code> 或 <code>REFERENCES</code>。</li><li><strong>IS_GRANTABLE</strong>: 如果权限可授予,显示为 <code>YES</code>,否则为 <code>NO</code>。</li></ul><p>要查询 <code>ROLE_COLUMN_GRANTS</code> 视图,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ROLE_COLUMN_GRANTS;</span><br></pre></td></tr></table></figure><p>这将返回当前数据库中所有角色的列级权限的详细信息。通过分析这些信息,管理员可以确保角色具有适当的权限,以执行其职责范围内的操作。</p><p>需要注意的是,<code>ROLE_COLUMN_GRANTS</code> 视图仅显示与当前用户相关的角色权限。如果你需要查看所有角色的权限,可以使用 <code>COLUMN_PRIVILEGES</code> 视图,它不限制于当前用户的角色 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img57.avif"></p><h3 id="ROLE-ROUTINE-GRANTS"><a href="#ROLE-ROUTINE-GRANTS" class="headerlink" title="ROLE_ROUTINE_GRANTS"></a>ROLE_ROUTINE_GRANTS</h3><p><code>ROLE_ROUTINE_GRANTS</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关当前启用的角色可用的或授予的角色例程权限的信息。这个表在 MySQL 8.0.19 版本中引入,用于显示当前用户或角色的存储过程和函数权限。</p><p>以下是 <code>INFORMATION_SCHEMA.ROLE_ROUTINE_GRANTS</code> 表中的一些关键列:</p><ul><li><strong>GRANTOR</strong>: 授予角色的账户用户名部分。</li><li><strong>GRANTOR_HOST</strong>: 授予角色的账户主机名部分。</li><li><strong>GRANTEE</strong>: 被授予角色的账户用户名部分。</li><li><strong>GRANTEE_HOST</strong>: 被授予角色的账户主机名部分。</li><li><strong>SPECIFIC_CATALOG</strong>: 例程所属的目录名称,对于 MySQL,这个值总是 <code>def</code>。</li><li><strong>SPECIFIC_SCHEMA</strong>: 例程所属的模式 数据库 名称。</li><li><strong>SPECIFIC_NAME</strong>: 例程的名称。</li><li><strong>ROUTINE_CATALOG</strong>: 例程所属的目录名称,对于 MySQL,这个值总是 <code>def</code>。</li><li><strong>ROUTINE_SCHEMA</strong>: 例程所属的模式 数据库 名称。</li><li><strong>ROUTINE_NAME</strong>: 例程的名称。</li><li><strong>PRIVILEGE_TYPE</strong>: 授予的权限类型,可以是 <code>EXECUTE</code> 等。</li><li><strong>IS_GRANTABLE</strong>: 表示权限是否可授予其他用户,值为 <code>YES</code> 或 <code>NO</code>。</li></ul><p>要查看角色的例程权限,可以执行以下 SQL 查询:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ROLE_ROUTINE_GRANTS;</span><br></pre></td></tr></table></figure><p>这将返回当前用户或角色的所有例程权限信息。此视图有助于数据库管理员审查和维护角色的存储过程和函数权限。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img58.avif"></p><h3 id="ROLE-TABLE-GRANTS"><a href="#ROLE-TABLE-GRANTS" class="headerlink" title="ROLE_TABLE_GRANTS"></a>ROLE_TABLE_GRANTS</h3><p><code>ROLE_TABLE_GRANTS</code> 视图是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个组成部分,它提供当前启用的角色可用的或授予的表权限信息。这个视图在 MySQL 8.0.19 版本中引入,用于显示当前用户或角色的表级权限。</p><p>以下是 <code>INFORMATION_SCHEMA.ROLE_TABLE_GRANTS</code> 视图中的一些关键列:</p><ul><li><strong>GRANTOR</strong>: 授予角色的账户用户名部分。</li><li><strong>GRANTOR_HOST</strong>: 授予角色的账户主机名部分。</li><li><strong>GRANTEE</strong>: 被授予角色的账户用户名部分。</li><li><strong>GRANTEE_HOST</strong>: 被授予角色的账户主机名部分。</li><li><strong>TABLE_CATALOG</strong>: 应用角色的目录名称,此值始终为 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: 应用角色的模式 数据库 名称。</li><li><strong>TABLE_NAME</strong>: 应用角色的表名称。</li><li><strong>PRIVILEGE_TYPE</strong>: 授予的权限类型,可以是表级权限,如 <code>SELECT</code>、<code>INSERT</code>、<code>UPDATE</code>、<code>DELETE</code> 等。</li><li><strong>IS_GRANTABLE</strong>: 表示角色是否可以将权限授予其他账户,值为 <code>YES</code> 或 <code>NO</code>。</li></ul><p>要查询 <code>ROLE_TABLE_GRANTS</code> 视图,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ROLE_TABLE_GRANTS;</span><br></pre></td></tr></table></figure><p>这将返回当前用户或角色的所有表级权限信息。此视图有助于数据库管理员审查和维护角色的表权限。</p><p>需要注意的是,<code>ROLE_TABLE_GRANTS</code> 视图仅显示与当前用户相关的角色权限。如果你需要查看所有角色的权限,可以使用 <code>TABLE_PRIVILEGES</code> 视图,它不限制于当前用户的角色 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img59.avif"></p><h3 id="ROUTINES"><a href="#ROUTINES" class="headerlink" title="ROUTINES"></a>ROUTINES</h3><p><code>ROUTINES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于存储例程 存储过程和存储函数 的信息。这个表不包括内置 本机 函数或可加载函数。</p><p>以下是 <code>INFORMATION_SCHEMA.ROUTINES</code> 表中的一些关键列:</p><ul><li><strong>SPECIFIC_NAME</strong>: 例程的名称。</li><li><strong>ROUTINE_CATALOG</strong>: 例程所属目录的名称。对于 MySQL,这个值总是 <code>def</code>。</li><li><strong>ROUTINE_SCHEMA</strong>: 例程所属的模式 数据库 的名称。</li><li><strong>ROUTINE_NAME</strong>: 例程的名称。</li><li><strong>ROUTINE_TYPE</strong>: <code>PROCEDURE</code> 表示存储过程,<code>FUNCTION</code> 表示存储函数。</li><li><strong>DATA_TYPE</strong>: 如果例程是存储函数,这是返回值的数据类型。如果是存储过程,则此值为空。</li><li><strong>CHARACTER_MAXIMUM_LENGTH</strong>: 对于存储的函数字符串返回值,这是最大字符长度。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>CHARACTER_OCTET_LENGTH</strong>: 对于存储的函数字符串返回值,这是以字节为单位的最大长度。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>NUMERIC_PRECISION</strong>: 对于存储函数数字返回值,这是数字精度。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>NUMERIC_SCALE</strong>: 对于存储的函数数字返回值,这是数字比例。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>DATETIME_PRECISION</strong>: 对于存储函数时间返回值,这是小数秒精度。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>CHARACTER_SET_NAME</strong>: 对于存储的函数字符串返回值,这是字符集名称。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>COLLATION_NAME</strong>: 对于存储的函数字符串返回值,这是排序规则名称。如果是存储过程,则此值为 <code>NULL</code>。</li><li><strong>DTD_IDENTIFIER</strong>: 如果例程是存储函数,这是返回值数据类型。如果是存储过程,则此值为空。</li></ul><p>要查询 <code>ROUTINES</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ROUTINES</span><br><span class="line"><span class="keyword">WHERE</span> ROUTINE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 替换为你要查询的数据库名称。这将返回指定数据库中所有存储过程和函数的详细信息。</p><p>这个表对于管理和维护数据库的存储例程非常有用,尤其是在进行代码审查、性能优化和安全审计时。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img60.avif"></p><h3 id="SCHEMATA"><a href="#SCHEMATA" class="headerlink" title="SCHEMATA"></a>SCHEMATA</h3><p><code>SCHEMATA</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于 MySQL 服务器上所有数据库 在 MySQL 中被称为模式 的信息。这个表包含了数据库的名称、默认字符集、默认排序规则等信息。</p><p>以下是 <code>INFORMATION_SCHEMA.SCHEMATA</code> 表中的一些关键列:</p><ul><li><strong>CATALOG_NAME</strong>: 数据库所属目录的名称。在 MySQL 中,这个值通常是 <code>def</code>。</li><li><strong>SCHEMA_NAME</strong>: 数据库 模式 的名称。</li><li><strong>DEFAULT_CHARACTER_SET_NAME</strong>: 数据库的默认字符集名称。</li><li><strong>DEFAULT_COLLATION_NAME</strong>: 数据库的默认排序规则名称。</li><li><strong>SQL_PATH</strong>: 这个值始终为 <code>NULL</code>。</li><li><strong>DEFAULT_ENCRYPTION</strong>: 数据库的默认加密选项 在 MySQL 8.0.16 及以后版本中添加 。</li></ul><p>要查询 <code>SCHEMATA</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> SCHEMA_NAME <span class="keyword">FROM</span> INFORMATION_SCHEMA.SCHEMATA;</span><br></pre></td></tr></table></figure><p>这将返回 MySQL 服务器上所有数据库的名称列表。这个查询等同于使用 <code>SHOW DATABASES</code> 命令,但通过查询 <code>INFORMATION_SCHEMA</code> 表来实现。</p><p><code>SCHEMATA</code> 表对于管理和维护数据库的元数据非常有用,尤其是在进行数据库结构分析、权限管理或性能优化时。通过这个表,你可以了解数据库的默认字符集和排序规则,这对于确保数据的一致性和性能至关重要。</p><p>请注意,你只能看到那些你拥有某种权限的数据库,除非你拥有全局 <code>SHOW DATABASES</code> 特权。这是因为 MySQL 的权限系统限制了对元数据的访问,以保护数据库的安全性 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img61.avif"></p><h3 id="SCHEMATA-EXTENSIONS"><a href="#SCHEMATA-EXTENSIONS" class="headerlink" title="SCHEMATA_EXTENSIONS"></a>SCHEMATA_EXTENSIONS</h3><p><code>SCHEMATA_EXTENSIONS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它在 MySQL 8.0.22 版本中引入,用于提供有关模式 数据库 选项的额外信息。这个表通常用于查看和管理数据库的只读状态。</p><p>以下是 <code>INFORMATION_SCHEMA.SCHEMATA_EXTENSIONS</code> 表中的一些关键列:</p><ul><li><strong>CATALOG_NAME</strong>: 模式所属目录的名称。这个值始终为 <code>def</code>。</li><li><strong>SCHEMA_NAME</strong>: 模式 数据库 的名称。</li><li><strong>OPTIONS</strong>: 模式的选项。如果模式是只读的,则该值包含 <code>READ ONLY 1</code>。如果模式不是只读的,则没有 <code>READ ONLY</code> 选项。</li></ul><p>例如,如果你将一个数据库设置为只读,可以使用以下命令:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER</span> SCHEMA mydb READ <span class="keyword">ONLY</span> <span class="number">1</span>;</span><br></pre></td></tr></table></figure><p>然后,通过查询 <code>SCHEMATA_EXTENSIONS</code> 表,你可以看到数据库的只读选项:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.SCHEMATA_EXTENSIONS <span class="keyword">WHERE</span> SCHEMA_NAME <span class="string">&#x27;mydb&#x27;</span>;</span><br></pre></td></tr></table></figure><p>如果数据库被设置为只读,上述查询将返回包含 <code>READ ONLY 1</code> 的 <code>OPTIONS</code> 列。如果数据库不是只读的,则 <code>OPTIONS</code> 列可能为空。</p><p>这个表是非标准的 <code>INFORMATION_SCHEMA</code> 表,意味着它可能不遵循其他数据库管理系统的 <code>INFORMATION_SCHEMA</code> 标准 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img62.avif"></p><h3 id="SCHEMA-PRIVILEGES"><a href="#SCHEMA-PRIVILEGES" class="headerlink" title="SCHEMA_PRIVILEGES"></a>SCHEMA_PRIVILEGES</h3><p><code>SCHEMA_PRIVILEGES</code> 表是 MySQL <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关数据库 schema 权限的信息。这个表从 <code>mysql.db</code> 系统表中获取其值,主要用于管理和审查数据库权限。</p><p>以下是 <code>SCHEMA_PRIVILEGES</code> 表中的一些关键列:</p><ul><li><strong>GRANTEE</strong>: 授予权限的账户名称,格式为 <code>&#39;user_name&#39; &#39;host_name&#39;</code>。</li><li><strong>TABLE_CATALOG</strong>: schema 所属目录的名称,该值始终为 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: schema 的名称。</li><li><strong>PRIVILEGE_TYPE</strong>: 授予的特权,可以是任何在 schema 级别授予的权限,例如 <code>SELECT</code>、<code>INSERT</code>、<code>UPDATE</code> 等。</li><li><strong>IS_GRANTABLE</strong>: 如果用户具有 <code>GRANT OPTION</code> 权限,则为 <code>YES</code>,否则为 <code>NO</code>。输出不会将 <code>GRANT OPTION</code> 列为具有 <code>PRIVILEGE_TYPE &#39;GRANT OPTION&#39;</code> 的单独行。</li></ul><p>每行列出一个权限,因此被授权者拥有的每个 schema 权限对应一行。这使得数据库管理员可以清晰地了解每个用户或角色的权限设置。</p><p><code>SCHEMA_PRIVILEGES</code> 表是一个非标准的 <code>INFORMATION_SCHEMA</code> 表,因此与其他数据库管理系统的实现可能有所不同。通过查询这个表,管理员可以有效地管理和审查数据库的访问权限,确保数据的安全性和完整性。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img63.avif"></p><h3 id="STATISTICS"><a href="#STATISTICS" class="headerlink" title="STATISTICS"></a>STATISTICS</h3><p><code>STATISTICS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关表索引的信息。这个表中的列保存了缓存值,这些值在默认情况下会在 24 小时后过期。如果没有缓存统计信息或统计信息已过期,则在查询表统计信息列时会从存储引擎中检索统计信息。</p><p>以下是 <code>STATISTICS</code> 表中的一些关键列:</p><ul><li><strong>TABLE_CATALOG</strong>: 包含索引的表所属目录的名称,该值始终为 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: 包含索引的表所属的模式 数据库 的名称。</li><li><strong>TABLE_NAME</strong>: 包含索引的表的名称。</li><li><strong>NON_UNIQUE</strong>: 如果索引不能包含重复项,则为 0,如果可以,则为 1。</li><li><strong>INDEX_SCHEMA</strong>: 索引所属的模式 数据库 的名称。</li><li><strong>INDEX_NAME</strong>: 索引的名称。如果索引是主键,则名称始终是 <code>PRIMARY</code>。</li><li><strong>SEQ_IN_INDEX</strong>: 索引中的列序号,从 1 开始。</li><li><strong>COLUMN_NAME</strong>: 列名称。</li><li><strong>COLLATION</strong>: 列在索引中的排序方式,可以是 <code>A</code> 升序 、<code>D</code> 降序 或 <code>NULL</code> 未排序 。</li><li><strong>CARDINALITY</strong>: 索引中唯一值数量的估计。要更新此数字,请运行 <code>ANALYZE TABLE</code>。</li><li><strong>SUB_PART</strong>: 如果列仅被部分索引,则为索引前缀的字符数;如果整个列被索引,则为 <code>NULL</code>。</li><li><strong>PACKED</strong>: 指示密钥的打包方式,如果不是,则为 <code>NULL</code>。</li><li><strong>NULLABLE</strong>: 如果列可能包含 <code>NULL</code> 值,则为 <code>YES</code>,否则为空。</li><li><strong>INDEX_TYPE</strong>: 索引类型,如 <code>BTREE</code>、<code>FULLTEXT</code>、<code>HASH</code>、<code>RTREE</code>。</li><li><strong>COMMENT</strong>: 有关未在其自己的列中描述的索引的信息,例如在禁用索引时禁用。</li><li><strong>INDEX_COMMENT</strong>: 创建索引时提供的任何注释。</li></ul><p>要查询索引信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.STATISTICS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span></span><br><span class="line"><span class="keyword">AND</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_table_name</code> 和 <code>your_database_name</code> 替换为你要查询的表名和数据库名。这将返回指定表的索引信息。</p><p><code>STATISTICS</code> 表对于数据库管理员和优化器来说非常重要,因为它们提供了索引的统计信息,有助于优化查询性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img64.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img65.avif"></p><h3 id="ST-GEOMETRY-COLUMNS"><a href="#ST-GEOMETRY-COLUMNS" class="headerlink" title="ST_GEOMETRY_COLUMNS"></a>ST_GEOMETRY_COLUMNS</h3><p><code>ST_GEOMETRY_COLUMNS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,提供有关存储空间数据的表列的信息。此表基于 SQL&#x2F;MM (ISO&#x2F;IEC 13249-3) 标准,并带有注释的扩展。MySQL 实现 <code>ST_GEOMETRY_COLUMNS</code> 作为 <code>INFORMATION_SCHEMA.COLUMNS</code> 表的视图。</p><p>以下是 <code>ST_GEOMETRY_COLUMNS</code> 表中的一些关键列:</p><ul><li><strong>TABLE_CATALOG</strong>: 包含该列的表所属目录的名称。该值始终为 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: 包含该列的表所属的模式 数据库 的名称。</li><li><strong>TABLE_NAME</strong>: 包含该列的表的名称。</li><li><strong>COLUMN_NAME</strong>: 列的名称。</li><li><strong>SRS_NAME</strong>: 空间参照系 (SRS) 名称。</li><li><strong>SRS_ID</strong>: 空间参考系统 ID (SRID)。</li><li><strong>GEOMETRY_TYPE_NAME</strong>: 列数据类型。允许的值为:<code>geometry</code>, <code>point</code>, <code>linestring</code>, <code>polygon</code>, <code>multipoint</code>, <code>multilinestring</code>, <code>multipolygon</code>, <code>geometrycollection</code>。这一列是 MySQL 对标准的扩展 。</li></ul><p>这个表对于管理和使用空间数据类型 如 <code>GEOMETRY</code> 非常有用,尤其是在进行空间数据查询和操作时。通过这个表,用户可以了解哪些列是空间数据类型,它们的空间参考系统是什么,以及它们的几何类型是什么。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img66.avif"></p><h3 id="ST-SPATIAL-REFERENCE-SYSTEMS"><a href="#ST-SPATIAL-REFERENCE-SYSTEMS" class="headerlink" title="ST_SPATIAL_REFERENCE_SYSTEMS"></a>ST_SPATIAL_REFERENCE_SYSTEMS</h3><p><code>ST_SPATIAL_REFERENCE_SYSTEMS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关空间数据的空间参考系统 SRS 的信息。此表基于 SQL&#x2F;MM (ISO&#x2F;IEC 13249-3) 标准,并且以 European Petroleum Survey Group (EPSG) 数据集为基础,除了 SRID 0 之外,它代表 MySQL 中使用的一个特殊 SRS,表示一个无限的平面笛卡尔平面,没有分配单位给它的轴。</p><p>以下是 <code>ST_SPATIAL_REFERENCE_SYSTEMS</code> 表中的一些关键列:</p><ul><li><strong>SRS_NAME</strong>: 空间参考系统名称,此值是唯一的。</li><li><strong>SRS_ID</strong>: 空间参考系统数字 ID,此值是唯一的。<code>SRS_ID</code> 值与几何值的 SRID 或作为 SRID 参数传递给空间函数的值相同。</li><li><strong>ORGANIZATION</strong>: 定义坐标系统 空间参考系统基于此坐标系统 的组织的名称。</li><li><strong>ORGANIZATION_COORDSYS_ID</strong>: 由定义它的组织提供的 SRS 的数字 ID。</li><li><strong>DEFINITION</strong>: 空间参考系统定义。<code>DEFINITION</code> 值是 WKT 值,按照 Open Geospatial Consortium 文档 OGC 12-063r5 中的规定表示。</li><li><strong>DESCRIPTION</strong>: 空间参考系统描述。</li></ul><p>例如,GPS 系统使用的 SRS 有一个名称 SRS_NAME WGS 84 和一个 ID SRS_ID 4326,这是由 EPSG 使用的 ID。<code>DEFINITION</code> 列中的 SRS 定义是 WKT 值,如 所述。</p><p>要查询空间参考系统的信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ST_SPATIAL_REFERENCE_SYSTEMS</span><br><span class="line"><span class="keyword">WHERE</span> SRS_ID <span class="number">4326</span>;</span><br></pre></td></tr></table></figure><p>这将返回与 SRS ID 4326 相关的空间参考系统信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img67.avif"></p><h3 id="ST-UNITS-OF-MEASURE"><a href="#ST-UNITS-OF-MEASURE" class="headerlink" title="ST_UNITS_OF_MEASURE"></a>ST_UNITS_OF_MEASURE</h3><p><code>ST_UNITS_OF_MEASURE</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关 <code>ST_Distance()</code> 函数可接受的单位的信息。这个表在 MySQL 8.0.14 版本中引入,包含了空间数据距离测量单位的相关信息。</p><p>以下是 <code>ST_UNITS_OF_MEASURE</code> 表中的一些关键列:</p><ul><li><strong>UNIT_NAME</strong>: 单位的名称。</li><li><strong>UNIT_TYPE</strong>: 单位类型 例如 <code>LINEAR</code> 。</li><li><strong>CONVERSION_FACTOR</strong>: 用于内部计算的转换因子。</li><li><strong>DESCRIPTION</strong>: 单位的描述。</li></ul><p>这个表用于支持 <code>ST_Distance()</code> 函数,该函数可以计算两个几何对象之间的距离,并允许指定返回值的长度单位。如果指定了一个单位但 MySQL 不支持,将会发生 <code>ER_UNIT_NOT_FOUND</code> 错误。如果指定了支持的线性单位且 SRID 为 0,将会发生 <code>ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT</code> 错误。如果未指定单位,则结果采用几何 SRS 的单位,无论是笛卡尔还是地理。</p><p>例如,如果你想查询所有可用的测量单位及其相关信息,可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.ST_UNITS_OF_MEASURE;</span><br></pre></td></tr></table></figure><p>这将返回所有已定义的测量单位的列表,包括它们的名称、类型、转换因子和描述。这个表对于确保空间数据计算的准确性和理解不同测量单位之间的转换非常有用。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img68.avif"></p><h3 id="TABLES"><a href="#TABLES" class="headerlink" title="TABLES"></a>TABLES</h3><p><code>TABLES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供了关于数据库中表的详细信息,包括视图和基础表。这个表包含了数据库中每个表的元数据,如表的名称、类型、使用的存储引擎、行格式、创建时间等信息。</p><p>以下是 <code>INFORMATION_SCHEMA.TABLES</code> 表中的一些关键列及其含义:</p><ul><li><strong>TABLE_CATALOG</strong>: 表所属目录的名称,对于 MySQL,这个值通常是 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: 表所属的数据库 模式 的名称。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>TABLE_TYPE</strong>: 表的类型,例如 <code>BASE TABLE</code> 基础表 或 <code>VIEW</code> 视图 。</li><li><strong>ENGINE</strong>: 表使用的存储引擎,如 <code>InnoDB</code>、<code>MyISAM</code> 等。</li><li><strong>VERSION</strong>: 存储引擎的版本号。</li><li><strong>ROW_FORMAT</strong>: 行的存储格式,例如 <code>Dynamic</code>、<code>Fixed</code>、<code>Compressed</code> 等。</li><li><strong>TABLE_ROWS</strong>: 表中估计的行数。</li><li><strong>AVG_ROW_LENGTH</strong>: 表中行的平均长度。</li><li><strong>DATA_LENGTH</strong>: 表的数据占用的字节数。</li><li><strong>MAX_DATA_LENGTH</strong>: 表数据的最大长度。</li><li><strong>INDEX_LENGTH</strong>: 表索引占用的字节数。</li><li><strong>DATA_FREE</strong>: 表中的空闲空间。</li><li><strong>AUTO_INCREMENT</strong>: 自增字段的当前值。</li><li><strong>CREATE_TIME</strong>: 表的创建时间。</li><li><strong>UPDATE_TIME</strong>: 表的最后更新时间。</li><li><strong>CHECK_TIME</strong>: 表的最后检查时间。</li><li><strong>TABLE_COLLATION</strong>: 表的默认字符集排序规则。</li><li><strong>CHECKSUM</strong>: 表的校验和,用于验证数据的完整性。</li><li><strong>CREATE_OPTIONS</strong>: 创建表时使用的选项。</li><li><strong>TABLE_COMMENT</strong>: 表的注释或描述。</li></ul><p>要查询 <code>TABLES</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.TABLES</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 替换为你要查询的数据库名称。这将返回指定数据库中所有表的详细信息。</p><p><code>TABLES</code> 表对于数据库管理员和开发者在进行数据库设计、优化和管理时非常有用。通过这个表,可以快速了解数据库中表的存储和性能特性,以及表的创建和更新时间等信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img69.avif"></p><h3 id="TABLESPACES"><a href="#TABLESPACES" class="headerlink" title="TABLESPACES"></a>TABLESPACES</h3><p><code>TABLESPACES</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,提供关于 InnoDB 存储引擎管理的文件-per-table、通用 general 和 undo 表空间的元数据信息。</p><p>以下是 <code>INFORMATION_SCHEMA.TABLESPACES</code> 表中的一些关键列:</p><ul><li><strong>SPACE</strong>: 表空间的 ID。</li><li><strong>NAME</strong>: 表空间的名称。对于 file-per-table 表空间,名称通常以 <code>&lt;schema_name&gt;/&lt;table_name&gt;</code> 的形式出现。</li><li><strong>FLAG</strong>: 表示表空间格式和存储特征的位掩码值。</li><li><strong>FILE_FORMAT</strong>: 表空间的文件格式,例如 <code>Antelope</code>、<code>Barracuda</code> 或 <code>Any</code> 通用表空间支持任何行格式 。</li><li><strong>ROW_FORMAT</strong>: 表空间的行格式,如 <code>Compact</code>、<code>Redundant</code>、<code>Dynamic</code> 或 <code>Compressed</code>。</li><li><strong>PAGE_SIZE</strong>: 表空间的页面大小。</li><li><strong>ZIP_PAGE_SIZE</strong>: 表空间的压缩页面大小。</li><li><strong>SPACE_TYPE</strong>: 表空间的类型,可能的值包括 <code>System</code>、<code>Single</code> 或 <code>General</code>。</li><li><strong>FS_BLOCK_SIZE</strong>: 文件系统块大小,这是磁盘读写的最小单位。</li><li><strong>FILE_SIZE</strong>: 表空间文件的显示大小。</li><li><strong>ALLOCATED_SIZE</strong>: 分配给表空间的实际磁盘空间量。</li><li><strong>AUTOEXTEND_SIZE</strong>: 表空间的自动扩展大小。</li><li><strong>SERVER_VERSION</strong>: 创建表空间时的 MySQL 版本号。</li><li><strong>SPACE_VERSION</strong>: 表空间版本,用于跟踪表空间格式的变化。</li><li><strong>ENCRYPTION</strong>: 表空间是否加密。</li><li><strong>STATE</strong>: 表空间的状态,例如 <code>normal</code>、<code>discarded</code> 或 <code>corrupted</code>。</li></ul><p>要查询 <code>TABLESPACES</code> 表,可以使用类似以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.TABLESPACES <span class="keyword">WHERE</span> SPACE [特定的SPACE_ID];</span><br></pre></td></tr></table></figure><p>将 <code>[特定的SPACE_ID]</code> 替换为你想要查询的表空间的ID。这个表对于数据库管理员在进行数据库性能优化和表空间管理时特别有用,因为它可以帮助他们了解表空间的使用情况和配置。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img70.avif"></p><h3 id="TABLESPACES-EXTENSIONS"><a href="#TABLESPACES-EXTENSIONS" class="headerlink" title="TABLESPACES_EXTENSIONS"></a>TABLESPACES_EXTENSIONS</h3><p><code>TABLESPACES_EXTENSIONS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它提供有关存储引擎定义的表空间属性的信息。这个表在 MySQL 8.0.21 版本中引入,包含了表空间的扩展属性。</p><p>以下是 <code>TABLESPACES_EXTENSIONS</code> 表中的一些关键列:</p><ul><li><strong>TABLESPACE_NAME</strong>: 表空间的名称。</li><li><strong>ENGINE_ATTRIBUTE</strong>: 存储引擎定义的表空间属性。</li></ul><p>需要注意的是,<code>TABLESPACES_EXTENSIONS</code> 表保留供将来使用,当前版本中可能不包含实际的数据。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img71.avif"></p><h3 id="TABLES-EXTENSIONS"><a href="#TABLES-EXTENSIONS" class="headerlink" title="TABLES_EXTENSIONS"></a>TABLES_EXTENSIONS</h3><p><code>TABLES_EXTENSIONS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,从 MySQL 8.0.21 版本开始可用。这个表提供了有关为主存储引擎和辅助存储引擎定义的表属性的信息。</p><p>以下是 <code>TABLES_EXTENSIONS</code> 表中的一些关键列:</p><ul><li><strong>TABLE_CATALOG</strong>: 表所属目录的名称。此值始终为 <code>def</code>。</li><li><strong>TABLE_SCHEMA</strong>: 表所属的模式 数据库 的名称。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>ENGINE_ATTRIBUTE</strong>: 为主存储引擎定义的表属性。保留以供将来使用。</li><li><strong>SECONDARY_ENGINE_ATTRIBUTE</strong>: 为辅助存储引擎定义的表属性。保留以供将来使用。</li></ul><p>此表目前保留供将来使用,意味着这些列可能在将来的版本中填充实际的数据。当前版本中,这些属性可能不包含实际的表属性信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img72.avif"></p><h3 id="TABLE-CONSTRAINTS"><a href="#TABLE-CONSTRAINTS" class="headerlink" title="TABLE_CONSTRAINTS"></a>TABLE_CONSTRAINTS</h3><p><code>TABLE_CONSTRAINTS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,它描述了哪些表具有约束。这个表包含了关于表的约束信息,如约束类型、约束名称、所属数据库和表名等。</p><p>以下是 <code>TABLE_CONSTRAINTS</code> 表中的一些关键列:</p><ul><li><strong>CONSTRAINT_CATALOG</strong>: 约束所属目录的名称。在 MySQL 中,这个值总是 <code>def</code> 。</li><li><strong>CONSTRAINT_SCHEMA</strong>: 约束所属的模式 数据库 的名称。</li><li><strong>TABLE_SCHEMA</strong>: 表所属的模式 数据库 的名称。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>CONSTRAINT_NAME</strong>: 约束的名称。</li><li><strong>CONSTRAINT_TYPE</strong>: 约束的类型。可能的值包括 <code>UNIQUE</code>、<code>PRIMARY KEY</code>、<code>FOREIGN KEY</code>,以及从 MySQL 8.0.16 开始支持的 <code>CHECK</code> 。</li><li><strong>ENFORCED</strong>: 对于 <code>CHECK</code> 约束,值为 <code>YES</code> 或 <code>NO</code> 以指示是否强制执行约束。对于其他约束,该值始终为 <code>YES</code> 。</li></ul><p>要查询 <code>TABLE_CONSTRAINTS</code> 表,你可以使用以下 SQL 语句:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.TABLE_CONSTRAINTS</span><br><span class="line"><span class="keyword">WHERE</span> TABLE_SCHEMA <span class="string">&#x27;your_database_name&#x27;</span> <span class="keyword">AND</span> TABLE_NAME <span class="string">&#x27;your_table_name&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将 <code>your_database_name</code> 和 <code>your_table_name</code> 替换为你要查询的数据库和表的名称。这将返回指定表的约束信息。</p><p><code>TABLE_CONSTRAINTS</code> 表对于数据库管理员和开发者在进行数据库设计、优化和管理时非常有用。通过这个表,可以快速了解数据库中表的约束情况,包括约束类型和约束名称等信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img73.avif"></p><h3 id="TABLE-CONSTRAINTS-EXTENSIONS"><a href="#TABLE-CONSTRAINTS-EXTENSIONS" class="headerlink" title="TABLE_CONSTRAINTS_EXTENSIONS"></a>TABLE_CONSTRAINTS_EXTENSIONS</h3><p><code>TABLE_CONSTRAINTS_EXTENSIONS</code> 表是 <code>INFORMATION_SCHEMA</code> 数据库中的一个表,从 MySQL 8.0.21 版本开始引入。这个表提供有关主要和辅助存储引擎定义的表约束属性的信息。</p><p>以下是 <code>TABLE_CONSTRAINTS_EXTENSIONS</code> 表中的一些关键列:</p><ul><li><strong>CONSTRAINT_CATALOG</strong>: 表所属目录的名称。</li><li><strong>CONSTRAINT_SCHEMA</strong>: 表所属的模式 数据库 的名称。</li><li><strong>CONSTRAINT_NAME</strong>: 约束的名称。</li><li><strong>TABLE_NAME</strong>: 表的名称。</li><li><strong>ENGINE_ATTRIBUTE</strong>: 为主存储引擎定义的约束属性。保留以供将来使用。</li><li><strong>SECONDARY_ENGINE_ATTRIBUTE</strong>: 为辅助存储引擎定义的约束属性。保留以供将来使用。</li></ul><p>需要注意的是,这个表目前保留供将来使用,意味着这些列可能在将来的版本中填充实际的数据。当前版本中,这些属性可能不包含实际的表约束信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-24/img74.avif"></p><h3 id="TABLE-PRIVILEGES"><a href="#TABLE-PRIVILEGES" class="headerlink" title="TABLE_PRIVILEGES"></a>TABLE_PRIVILEGES</h3><p>以下是 <code>TABLE_PRIVILEGES</code> 表中的一些关键列:</p><ul><li><strong>GRANTEE</strong>: 授予权限的账户的名称,格式为 <code>&#39;user_name&#39; &#39;host_name&#39;</code>。<br><strong>TABLE_CATALOG</strong>: 表所属目录的名称。在 MySQL</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/24/d6f9f2fc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0.13-函数索引</title>
      <link>https://blog.eucalyptus.cc/2024/09/14/f1232e27/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/14/f1232e27/</guid>
      <pubDate>Sat, 14 Sep 2024 09:21:40 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是函数索引&quot;&gt;&lt;a href=&quot;#什么是函数索引&quot; class=&quot;headerlink&quot; title=&quot;什么是函数索引&quot;&gt;&lt;/a&gt;什么是函数索引&lt;/h2&gt;&lt;p&gt;本篇主要介绍 MySQL 的函数索引 也叫表达式索引</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是函数索引"><a href="#什么是函数索引" class="headerlink" title="什么是函数索引"></a>什么是函数索引</h2><p>本篇主要介绍 MySQL 的函数索引 也叫表达式索引 。</p><p>通常来讲,索引都是基于字段本身或者字段前缀,而函数索引是基于字段本身加上函数、操作符、表达式等计算而来。如果将表达式或者操作符也看做函数的话,简单来说,这样的索引就可以统称函数索引。</p><p>MySQL 的函数索引内部是基于虚拟列 generated columns 实现,不同于直接定义虚拟列,函数索引自动创建的虚拟列本身实时计算结果,并不存储数据,只把函数索引本身存在磁盘上。</p><p>MySQL 8.0.13 之前不支持函数索引,所以老版本包括现在主流的 MySQL 5.7 也不支持函数索引,需要手工模拟创建或者改 SQL。</p><h2 id="语法"><a href="#语法" class="headerlink" title="语法"></a>语法</h2><p>创建函数索引的基本语法如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX index_name <span class="keyword">ON</span> table_name (expression);</span><br></pre></td></tr></table></figure><p>或者,如果正在修改表并添加新的索引,可以使用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> table_name <span class="keyword">ADD</span> INDEX index_name (expression);</span><br></pre></td></tr></table></figure><p>这里的 <code>expression</code> 可以是列名、列名的函数 如 <code>LOWER(column_name)</code> 、列名的计算 如 <code>column_name * 2</code> 或其他有效的 SQL 表达式。</p><p>以下是一些创建函数索引的例子:</p><ul><li><strong>对字符串列的特定转换进行索引</strong>:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX idx_lastname_lowercase <span class="keyword">ON</span> customers (<span class="built_in">LOWER</span>(last_name));</span><br></pre></td></tr></table></figure><ul><li><strong>对日期列的特定格式进行索引</strong>:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX idx_birthdate <span class="keyword">ON</span> users (<span class="type">DATE</span>(birthdate));</span><br></pre></td></tr></table></figure><ul><li><strong>对数值列的计算结果进行索引</strong>:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX idx_price_times_two <span class="keyword">ON</span> products (price <span class="operator">*</span> <span class="number">2</span>);</span><br></pre></td></tr></table></figure><ul><li><strong>对 JSON 列的路径表达式进行索引</strong>:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX idx_json_column <span class="keyword">ON</span> <span class="built_in">json_table</span> (JSON_EXTRACT(json_column, <span class="string">&#x27;$.path.to.value&#x27;</span>));</span><br></pre></td></tr></table></figure><p>请注意,不是所有的函数都适合用于函数索引。函数必须是确定性的,这意味着对于相同的输入,函数总是返回相同的结果。此外,函数索引的使用也受到存储引擎的限制,例如,InnoDB 支持函数索引,而 MyISAM 不支持。</p><h2 id="函数索引测试"><a href="#函数索引测试" class="headerlink" title="函数索引测试"></a>函数索引测试</h2><h3 id="创建表结构"><a href="#创建表结构" class="headerlink" title="创建表结构"></a>创建表结构</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> idx_test (</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">col1 <span class="type">INT</span>,</span><br><span class="line">col2 <span class="type">INT</span>,</span><br><span class="line">col3 <span class="type">VARCHAR</span>(<span class="number">30</span>),</span><br><span class="line">create_time DATETIME <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci;</span><br></pre></td></tr></table></figure><h3 id="插入数据"><a href="#插入数据" class="headerlink" title="插入数据"></a>插入数据</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> idx_test <span class="keyword">values</span> (<span class="number">1</span>,<span class="number">10</span>,<span class="number">10</span>,<span class="string">&#x27;helloworld&#x27;</span>,<span class="string">&#x27;2021-01-01 00:00:00&#x27;</span>),</span><br><span class="line">(<span class="number">2</span>,<span class="number">20</span>,<span class="number">20</span>,<span class="string">&#x27;hellochina&#x27;</span>,<span class="string">&#x27;2021-02-02 00:00:00&#x27;</span>),</span><br><span class="line">(<span class="number">3</span>,<span class="number">30</span>,<span class="number">30</span>,<span class="string">&#x27;hellojap&#x27;</span>,<span class="string">&#x27;2021-03-03 00:00:00&#x27;</span>),</span><br><span class="line">(<span class="number">4</span>,<span class="number">40</span>,<span class="number">40</span>,<span class="string">&#x27;hellorus&#x27;</span>,<span class="string">&#x27;2021-04-04 00:00:00&#x27;</span>),</span><br><span class="line">(<span class="number">5</span>,<span class="number">50</span>,<span class="number">50</span>,<span class="string">&#x27;helloita&#x27;</span>,<span class="string">&#x27;2021-05-05 00:00:00&#x27;</span>);</span><br></pre></td></tr></table></figure><h3 id="创建普通索引"><a href="#创建普通索引" class="headerlink" title="创建普通索引"></a>创建普通索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> idx_test <span class="keyword">add</span> index idx_create_time(create_time);</span><br></pre></td></tr></table></figure><h4 id="查看执行计划"><a href="#查看执行计划" class="headerlink" title="查看执行计划"></a>查看执行计划</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">explain <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> idx_test <span class="keyword">where</span> <span class="type">date</span>(create_time) <span class="string">&#x27;2021-01-01&#x27;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-14/img1.avif"></p><h3 id="创建函数索引"><a href="#创建函数索引" class="headerlink" title="创建函数索引"></a>创建函数索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> idx_test <span class="keyword">add</span> index fun_create_time((<span class="type">date</span>(create_time)));</span><br></pre></td></tr></table></figure><h4 id="查看执行计划-1"><a href="#查看执行计划-1" class="headerlink" title="查看执行计划"></a>查看执行计划</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> idx_test <span class="keyword">add</span> index fun_create_time((<span class="type">date</span>(create_time)));</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-14/img2.avif"></p><h3 id="查看索引信息"><a href="#查看索引信息" class="headerlink" title="查看索引信息"></a>查看索引信息</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> index <span class="keyword">from</span> idx_test ;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-14/img3.avif"></p><h2 id="函数索引效率"><a href="#函数索引效率" class="headerlink" title="函数索引效率"></a>函数索引效率</h2><p>如果两条 sql 一个用到普通索引,一个用到函数索引,结果集一致,那哪个 sql 的开销会大点?</p><h3 id="普通索引"><a href="#普通索引" class="headerlink" title="普通索引"></a>普通索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#普通索引:</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> idx_test <span class="keyword">where</span> create_time <span class="operator">&gt;</span> <span class="string">&#x27;2021-02-02 00:00:00&#x27;</span> <span class="keyword">and</span> create_time <span class="operator">&lt;</span> <span class="string">&#x27;2021-03-03 00:00:00&#x27;</span>;</span><br></pre></td></tr></table></figure><p>查看详细执行计划</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">explain format json <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> idx_test <span class="keyword">where</span> create_time <span class="operator">&gt;</span> <span class="string">&#x27;2021-02-02 00:00:00&#x27;</span> <span class="keyword">and</span> create_time <span class="operator">&lt;</span> <span class="string">&#x27;2021-03-03 00:00:00&#x27;</span>\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-14/img4.avif"></p><h3 id="函数索引"><a href="#函数索引" class="headerlink" title="函数索引"></a>函数索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#用到函数索引:</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> idx_test <span class="keyword">where</span> <span class="type">date</span>(create_time) <span class="string">&#x27;2021-03-03&#x27;</span>;</span><br></pre></td></tr></table></figure><p>查看详细执行计划</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">explain format json <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> idx_test <span class="keyword">where</span> <span class="type">date</span>(create_time) <span class="string">&#x27;2021-03-03&#x27;</span>\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-14/img5.avif"></p><h3 id="分析"><a href="#分析" class="headerlink" title="分析"></a>分析</h3><p>普通索引的开销会大点,也比较符合预期,本来建立函数索引就是为了查询更为高效。总的来看,函数索引在特定场景还是很有用处的,只要严格遵守函数索引的定义去编写 sql,那就能大大减少不必要的开销。</p><h2 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h2><ul><li><strong>表达式括号</strong>:在创建函数索引时,需要将表达式放入括号中,以区分于普通列索引或前缀索引。例如,创建一个基于 <code>DATE()</code> 函数的索引应该这样写:<code>ALTER TABLE table_name ADD INDEX index_name((DATE(column_name)));</code></li><li><strong>函数限制</strong>:函数索引中的表达式不能使用列的前缀,也不能包含非确定性的函数,如 <code>NOW()</code>、<code>RAND()</code> 等。此外,不能使用子查询、参数、变量、存储函数以及自定义函数。只有确定性的函数才能用于创建函数索引。</li><li><strong>索引类型</strong>:虽然普通索引支持前缀索引,但函数索引不支持字段的前缀索引。如果需要对字段的前缀进行索引,可以使用 <code>SUBSTRING()</code> 或 <code>CAST()</code> 函数作为替代方案。</li><li><strong>性能考虑</strong>:函数索引在查询时动态计算其值,这可能会影响性能,尤其是在数据量大或表达式复杂的情况下。因此,在创建函数索引之前,应该进行性能测试,确保它确实能够提高查询效率。</li><li><strong>存储引擎限制</strong>:函数索引仅在某些存储引擎中受支持,如 InnoDB。在使用函数索引之前,确保它与你的存储引擎兼容。</li><li><strong>索引维护</strong>:创建函数索引时,MySQL 会在内部创建一个隐藏的虚拟列,并在该虚拟列上创建索引。这意味着函数索引的维护与普通索引类似,但需要注意虚拟列的存在。</li><li><strong>查询优化</strong>:在使用函数索引时,查询条件必须与索引定义的表达式完全一致,才能确保查询优化器使用该索引。例如,如果函数索引是基于 <code>UPPER(column_name)</code> 创建的,那么查询条件也应该是 <code>UPPER(column_name) &#39;SOMEVALUE&#39;</code>。</li><li><strong>特殊数据类型</strong>:对于 JSON 数据类型,函数索引可以用于优化 JSON 列的查询,但需要注意 <code>JSON_UNQUOTE()</code> 函数和 <code>CAST()</code> 函数在索引和查询中的使用,因为它们可能影响索引的可见性和查询性能。</li><li><strong>索引数量</strong>:虽然函数索引可以提高查询性能,但过多的索引会增加数据库的维护成本,因此应该根据实际需求合理创建索引。</li><li><strong>版本限制</strong>:函数索引是在 MySQL 8.0.13 版本中引入的,因此需要确保你的 MySQL 版本支持此特性。</li></ul><h2 id="老版本如何实现函数索引"><a href="#老版本如何实现函数索引" class="headerlink" title="老版本如何实现函数索引"></a><strong>老版本如何实现函数索引</strong></h2><p>函数索引是 MySQL 8.0.13 才有的。那在老的版本如何实现呢?</p><p>MySQL 5.7 自持虚拟列,只需要在虚拟列上创建一个普通索引就行。</p><p>MySQL 5.6 以及 MySQL 5.5 等,则需要自己定义一个冗余列,然后定期更新这列内容。当然最核心的是如何规划好定期更新内容这块。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/14/f1232e27/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL5.7-虚拟列</title>
      <link>https://blog.eucalyptus.cc/2024/09/14/8922d87b/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/14/8922d87b/</guid>
      <pubDate>Sat, 14 Sep 2024 08:50:53 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;虚拟列的定义和作用&quot;&gt;&lt;a href=&quot;#虚拟列的定义和作用&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="虚拟列的定义和作用"><a href="#虚拟列的定义和作用" class="headerlink" title="虚拟列的定义和作用"></a>虚拟列的定义和作用</h2><p>MySQL虚拟列是一种特殊的列,是mysql-5.7版本引入的一个新特性,它并不存储数据,而是在查询时动态生成数据。这种列的值通常是由其他列的值通过某种表达式计算得出的。虚拟列的主要作用是提高查询效率和数据处理的便利性。它可以使我们在不增加实际存储开销的情况下,对数据进行更高效的查询和管理。</p><h2 id="虚拟列和普通列的区别"><a href="#虚拟列和普通列的区别" class="headerlink" title="虚拟列和普通列的区别"></a>虚拟列和普通列的区别</h2><p>虚拟列与普通列在使用上有几个主要的区别:</p><ul><li>存储方式:普通列的值在插入或更新时会被实际存储在数据库中,而虚拟列的值并不会被存储,而是在查询时动态计算生成。</li><li>更新方式:普通列的值可以直接通过UPDATE语句进行修改,而虚拟列的值则不能直接修改,它的值是由定义它的表达式决定的。</li><li>索引应用:虚拟列可以被索引,这使得它在某些情况下可以提高查询性能。虽然虚拟列的值在查询时才生成,但是如果对虚拟列创建了索引,那么索引的值会被存储,从而提高查询效率。</li></ul><h2 id="虚拟列的类型"><a href="#虚拟列的类型" class="headerlink" title="虚拟列的类型"></a>虚拟列的类型</h2><p>在MySQL中,虚拟列主要分为两种类型:生成列和存储列。</p><blockquote><ul><li><strong>STORED</strong>:实际存储的列 (占用物理空间),在 保存&#x2F;修改 的时候,根据 表达式 及时生成数据,能提升性能。</li><li><strong>VIRTUAL</strong>:真正虚拟的列 (不占用物理空间),在查询时,根据 表达式 实时生成,占用性能。</li></ul></blockquote><h3 id="生成列"><a href="#生成列" class="headerlink" title="生成列"></a>生成列</h3><p>生成列是一种特殊的虚拟列,它的值是由其他列的值通过一个表达式生成的。生成列的值不会被实际存储,而是在查询时动态计算生成。生成列可以是基于一个或多个列的任何MySQL合法的表达式</p><h4 id="语法"><a href="#语法" class="headerlink" title="语法"></a>语法</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> users</span><br><span class="line"><span class="keyword">ADD</span> <span class="keyword">COLUMN</span> full_name <span class="type">VARCHAR</span>(<span class="number">255</span>) <span class="keyword">AS</span> (CONCAT(first_name, <span class="string">&#x27; &#x27;</span>, last_name)) VIRTUAL;</span><br></pre></td></tr></table></figure><h3 id="存储列"><a href="#存储列" class="headerlink" title="存储列"></a>存储列</h3><p>存储列是生成列的一种特殊形式。与生成列不同,存储列的值在插入或更新数据时会被计算并实际存储在数据库中。这意味着存储列的值不需要在查询时动态计算。</p><p>虽然存储列需要占用额外的存储空间,但是它可以提高查询速度,因为它的值在查询时已经被计算并存储好了。存储列特别适用于那些计算成本高,但查询频繁的场景。</p><p>需要注意的是,虽然存储列的值被存储在数据库中,但是它的值不能直接被修改,它的值仍然是由定义它的表达式决定的。</p><h4 id="语法-1"><a href="#语法-1" class="headerlink" title="语法"></a>语法</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> users</span><br><span class="line"><span class="keyword">ADD</span> <span class="keyword">COLUMN</span> full_name <span class="type">VARCHAR</span>(<span class="number">255</span>) <span class="keyword">AS</span> (CONCAT(first_name, <span class="string">&#x27; &#x27;</span>, last_name)) STORED;</span><br></pre></td></tr></table></figure><h3 id="实战-使用MySQL虚拟列解决实际问题"><a href="#实战-使用MySQL虚拟列解决实际问题" class="headerlink" title="实战:使用MySQL虚拟列解决实际问题"></a>实战:使用MySQL虚拟列解决实际问题</h3><h4 id="场景描述"><a href="#场景描述" class="headerlink" title="场景描述"></a>场景描述</h4><p>假设你是一家电子商务公司的数据库管理员,公司有一个 <code>orders</code> 表,记录了客户的订单信息。表结构如下:</p><ul><li><code>order_id</code>:订单的唯一标识。</li><li><code>product_id</code>:产品的唯一标识。</li><li><code>quantity</code>:购买的产品数量。</li><li><code>unit_price</code>:产品的单价。</li><li><code>order_date</code>:订单日期。</li></ul><p>现在,公司需要快速生成每个订单的总金额报告,这是一个经常需要执行的查询。为了提高查询效率,你决定使用虚拟列来存储每个订单的总金额。</p><h4 id="表结构"><a href="#表结构" class="headerlink" title="表结构"></a>表结构</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> orders (</span><br><span class="line">order_id <span class="type">INT</span> AUTO_INCREMENT <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">product_id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">quantity <span class="type">INT</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">unit_price <span class="type">DECIMAL</span>(<span class="number">10</span>, <span class="number">2</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">order_date <span class="type">DATE</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">total_amount <span class="type">DECIMAL</span>(<span class="number">10</span>, <span class="number">2</span>) GENERATED ALWAYS <span class="keyword">AS</span> (quantity <span class="operator">*</span> unit_price) VIRTUAL</span><br><span class="line">) ENGINE InnoDB;</span><br></pre></td></tr></table></figure><p>在这个表结构中,<code>total_amount</code> 是一个虚拟列,它的值是 <code>quantity</code> 和 <code>unit_price</code> 相乘的结果。</p><h4 id="插入数据"><a href="#插入数据" class="headerlink" title="插入数据"></a>插入数据</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> orders (product_id, quantity, unit_price, order_date)</span><br><span class="line"><span class="keyword">VALUES</span></span><br><span class="line">(<span class="number">101</span>, <span class="number">2</span>, <span class="number">29.99</span>, <span class="string">&#x27;2024-01-01&#x27;</span>),</span><br><span class="line">(<span class="number">102</span>, <span class="number">1</span>, <span class="number">49.99</span>, <span class="string">&#x27;2024-01-02&#x27;</span>),</span><br><span class="line">(<span class="number">103</span>, <span class="number">3</span>, <span class="number">19.99</span>, <span class="string">&#x27;2024-01-03&#x27;</span>);</span><br></pre></td></tr></table></figure><h4 id="查询订单总金额"><a href="#查询订单总金额" class="headerlink" title="查询订单总金额"></a>查询订单总金额</h4><p>在没有虚拟列的情况下,你需要执行一个包含计算的查询来获取每个订单的总金额:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> order_id, quantity, unit_price, quantity <span class="operator">*</span> unit_price <span class="keyword">AS</span> total_amount</span><br><span class="line"><span class="keyword">FROM</span> orders;</span><br></pre></td></tr></table></figure><p>但是,通过使用虚拟列,你可以简化查询,并可能提高性能:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> order_id, total_amount</span><br><span class="line"><span class="keyword">FROM</span> orders;</span><br></pre></td></tr></table></figure><h4 id="性能优化"><a href="#性能优化" class="headerlink" title="性能优化"></a>性能优化</h4><p>由于 <code>total_amount</code> 是一个虚拟列,MySQL 会在查询时动态计算其值。如果你发现这个计算成为了性能瓶颈,你可以将虚拟列改为存储列 必须先删除后创建 :</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> orders <span class="keyword">DROP</span> <span class="keyword">COLUMN</span> total_amount;</span><br><span class="line"><span class="keyword">ALTER TABLE</span> orders <span class="keyword">ADD</span> <span class="keyword">COLUMN</span> total_amount <span class="type">DECIMAL</span>(<span class="number">10</span>, <span class="number">2</span>) GENERATED ALWAYS <span class="keyword">AS</span> (quantity <span class="operator">*</span> unit_price) STORED;</span><br></pre></td></tr></table></figure><p>这样,MySQL 会在插入或更新行时计算 <code>total_amount</code> 并将其存储在表中。由于值已经预先计算并存储,查询时可以直接读取,而不需要每次都进行计算。</p><h2 id="虚拟列使用限制"><a href="#虚拟列使用限制" class="headerlink" title="虚拟列使用限制"></a>虚拟列使用限制</h2><p>虚拟列在查询时动态计算,不占用磁盘空间,因此不会增加存储负担。以下是虚拟列的一些限制和注意事项:</p><ul><li><strong>只读属性</strong>:虚拟列是只读的,你不能直接插入或更新虚拟列的值。如果需要修改虚拟列的值,必须修改其依赖的基础列的值 。</li><li><strong>表达式限制</strong>:虚拟列的表达式必须使用确定性的函数和操作符。不能使用非确定性的函数,如 <code>NOW()</code>、<code>RAND()</code> 等,也不能使用子查询或存储过程 。</li><li><strong>索引限制</strong>:在 MySQL 5.7 及更早版本中,虚拟列不能被索引。但从 MySQL 8.0 开始,你可以在虚拟列上创建索引,这有助于提高查询性能 。</li><li><strong>存储引擎限制</strong>:虚拟列仅在某些存储引擎中受支持。例如,在 MySQL 5.7 中,只有 InnoDB、MyISAM 和 MEMORY 存储引擎支持虚拟列 。</li><li><strong>修改限制</strong>:虚拟列的定义可以修改,但是虚拟列和存储列之间不能相互转换。如果需要更改列的存储方式,必须先删除列,然后重新添加 。</li><li><strong>性能考虑</strong>:虽然虚拟列不占用存储空间,但每次查询时都需要计算其值,这可能会影响性能。特别是当表达式复杂或数据量大时,这种影响更为明显 。</li><li><strong>数据类型兼容性</strong>:虚拟列的数据类型必须与表达式的结果兼容。例如,如果你将两个整数相加,虚拟列的数据类型应该是整数类型 。</li><li><strong>复制和二进制日志</strong>:在使用复制或二进制日志时,对虚拟列的更改 通过修改其依赖的基础列 也会被记录并复制到其他服务器上 。</li><li><strong>备份和恢复</strong>:在备份和恢复数据库时,需要确保备份工具能够正确处理虚拟列 。</li><li><strong>升级考虑</strong>:如果你的数据库是从较旧的 MySQL 版本升级而来的,需要确保升级过程正确处理了虚拟列 。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/14/8922d87b/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0新特性解读</title>
      <link>https://blog.eucalyptus.cc/2024/09/13/acdd628e/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/13/acdd628e/</guid>
      <pubDate>Fri, 13 Sep 2024 08:58:48 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;一、功能增强&quot;&gt;&lt;a href=&quot;#一、功能增强&quot; class=&quot;headerlink&quot; title=&quot;一、功能增强&quot;&gt;&lt;/a&gt;一、功能增强&lt;/h3&gt;&lt;h4 id=&quot;1-1-所有系统表更换为InnoDB引擎&quot;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="一、功能增强"><a href="#一、功能增强" class="headerlink" title="一、功能增强"></a>一、功能增强</h3><h4 id="1-1-所有系统表更换为InnoDB引擎"><a href="#1-1-所有系统表更换为InnoDB引擎" class="headerlink" title="1.1-所有系统表更换为InnoDB引擎"></a>1.1-所有系统表更换为InnoDB引擎</h4><p>系统表全部换成事务型的innodb表,默认的MySQL实例将不包含任何MyISAM表,除非手动创建MyISAM表。</p><h4 id="1-2-DDL原子化"><a href="#1-2-DDL原子化" class="headerlink" title="1.2-DDL原子化"></a>1.2-DDL原子化</h4><p>InnoDB表的DDL支持事务完整性,要么成功要么回滚,将DDL操作回滚日志写入到data dictionary 数据字典表 mysql.innodb_ddl_log 中用于回滚操作,该表是隐藏的表,通过show tables无法看到。通过设置参数,可将ddl操作日志打印输出到mysql错误日志中。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">set</span> <span class="keyword">global</span> log_error_verbosity <span class="number">3</span>;</span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">set</span> <span class="keyword">global</span> innodb_print_ddl_logs <span class="number">1</span>;</span><br></pre></td></tr></table></figure><h4 id="1-3-DDL秒加列"><a href="#1-3-DDL秒加列" class="headerlink" title="1.3-DDL秒加列"></a>1.3-DDL秒加列</h4><p>只有在 MySQL 8.0.12 以上的版本才支持</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">show</span> <span class="keyword">create table</span> sbtest1;</span><br><span class="line"><span class="keyword">CREATE TABLE</span> sbtest1 (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span> AUTO_INCREMENT,</span><br><span class="line">k <span class="type">int</span> <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="string">&#x27;0&#x27;</span>,</span><br><span class="line">c <span class="type">char</span>(<span class="number">120</span>) <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="string">&#x27;&#x27;</span>,</span><br><span class="line">pad <span class="type">char</span>(<span class="number">60</span>) <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="string">&#x27;&#x27;</span>,</span><br><span class="line">d <span class="type">int</span> <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="string">&#x27;0&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id ),</span><br><span class="line">KEY k_1 ( k )</span><br><span class="line">) ENGINE InnoDB AUTO_INCREMENT <span class="number">1000001</span> <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci</span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">alter table</span> sbtest1 <span class="keyword">drop</span> <span class="keyword">column</span> d ;</span><br><span class="line">Query OK, <span class="number">0</span> <span class="keyword">rows</span> affected (<span class="number">0.05</span> sec)</span><br><span class="line">Records: <span class="number">0</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line">mysql<span class="operator">&gt;</span></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">insert into</span> sbtest1(k,c,pad) <span class="keyword">select</span> k,c,pad <span class="keyword">from</span> sbtest1;</span><br><span class="line">Query OK, <span class="number">1000000</span> <span class="keyword">rows</span> affected (<span class="number">19.61</span> sec)</span><br><span class="line">Records: <span class="number">1000000</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">insert into</span> sbtest1(k,c,pad) <span class="keyword">select</span> k,c,pad <span class="keyword">from</span> sbtest1;</span><br><span class="line">Query OK, <span class="number">2000000</span> <span class="keyword">rows</span> affected (<span class="number">38.25</span> sec)</span><br><span class="line">Records: <span class="number">2000000</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">insert into</span> sbtest1(k,c,pad) <span class="keyword">select</span> k,c,pad <span class="keyword">from</span> sbtest1;</span><br><span class="line">Query OK, <span class="number">4000000</span> <span class="keyword">rows</span> affected (<span class="number">1</span> min <span class="number">14.51</span> sec)</span><br><span class="line">Records: <span class="number">4000000</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="built_in">count</span>(<span class="operator">*</span>) <span class="keyword">from</span> sbtest1;</span><br><span class="line"><span class="comment">----------</span></span><br><span class="line"><span class="operator">|</span> <span class="built_in">count</span>(<span class="operator">*</span>) <span class="operator">|</span></span><br><span class="line"><span class="comment">----------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">8000000</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">----------</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.31</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">alter table</span> sbtest1 <span class="keyword">add</span> <span class="keyword">column</span> d <span class="type">int</span> <span class="keyword">not null</span> <span class="keyword">default</span> <span class="number">0</span>;</span><br><span class="line">Query OK, <span class="number">0</span> <span class="keyword">rows</span> affected (<span class="number">1.22</span> sec)</span><br><span class="line">Records: <span class="number">0</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">alter table</span> sbtest1 <span class="keyword">add</span> <span class="keyword">column</span> e <span class="type">int</span> <span class="keyword">not null</span> <span class="keyword">default</span> <span class="number">0</span>;</span><br><span class="line">Query OK, <span class="number">0</span> <span class="keyword">rows</span> affected (<span class="number">0.03</span> sec)</span><br><span class="line">Records: <span class="number">0</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br></pre></td></tr></table></figure><h4 id="1-4-公用表表达式-CTE-Common-Table-Expression"><a href="#1-4-公用表表达式-CTE-Common-Table-Expression" class="headerlink" title="1.4-公用表表达式 CTE:Common Table Expression"></a>1.4-公用表表达式 CTE:Common Table Expression</h4><p>CTE(Common Table Expression)可以认为是派生表(derived table)的替代,在一定程度上,CTE简化了复杂的join查询和子查询,另外CTE可以很方便地实现递归查询,提高了SQL的可读性和执行性能。CTE是ANSI SQL 99标准的一部分,在MySQL 8.0.1版本被引入。</p><h5 id="1-4-1-CTE优势"><a href="#1-4-1-CTE优势" class="headerlink" title="1.4.1-CTE优势"></a>1.4.1-CTE优势</h5><ul><li>查询语句的可读性更好</li><li>在一个查询中,可以被引用多次</li><li>能够链接多个CTE</li><li>能够创建递归查询</li><li>能够提高SQL执行性能</li><li>能够有效地替代视图</li></ul><h4 id="1-5-默认字符集由latin1变为utf8mb4"><a href="#1-5-默认字符集由latin1变为utf8mb4" class="headerlink" title="1.5-默认字符集由latin1变为utf8mb4"></a>1.5-默认字符集由latin1变为utf8mb4</h4><p>在8.0版本之前,默认字符集为latin1,utf8指向的是utf8mb3,8.0版本默认字符集为utf8mb4,utf8默认指向的也是utf8mb4。</p><h4 id="1-6-Clone插件"><a href="#1-6-Clone插件" class="headerlink" title="1.6-Clone插件"></a>1.6-Clone插件</h4><p>MySQL 8.0 clone插件提供从一个实例克隆出另外一个实例的功能,克隆功能提供了更有效的方式来快速创建MySQL实例,搭建主从复制和组复制。</p><h4 id="1-7-资源组"><a href="#1-7-资源组" class="headerlink" title="1.7-资源组"></a>1.7-资源组</h4><p>MySQL 8.0新增了一个资源组功能,用于调控线程优先级以及绑定CPU核。MySQL用户需要有 RESOURCE_GROUP_ADMIN权限才能创建、修改、删除资源组。在Linux环境下,MySQL进程需要有 CAP_SYS_NICE 权限才能使用资源组完整功能。</p><h4 id="1-8-角色管理"><a href="#1-8-角色管理" class="headerlink" title="1.8-角色管理"></a>1.8-角色管理</h4><p>角色可以认为是一些权限的集合,为用户赋予统一的角色,权限的修改直接通过角色来进行,无需为每个用户单独授权。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br></pre></td><td class="code"><pre><span class="line"># 创建角色</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">create</span> role role_test;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.03</span>sec)</span><br><span class="line"></span><br><span class="line"># 给角色授予权限</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">grant</span> <span class="keyword">select</span> <span class="keyword">on</span> db.<span class="operator">*</span><span class="keyword">to</span> <span class="string">&#x27;role_test&#x27;</span>;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.10</span>sec)</span><br><span class="line"></span><br><span class="line"># 创建用户</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;read_user&#x27;</span> <span class="string">&#x27;%&#x27;</span>identified <span class="keyword">by</span> <span class="string">&#x27;123456&#x27;</span>;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.09</span>sec)</span><br><span class="line"></span><br><span class="line"># 给用户赋予角色</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">grant</span> <span class="string">&#x27;role_test&#x27;</span><span class="keyword">to</span> <span class="string">&#x27;read_user&#x27;</span> <span class="string">&#x27;%&#x27;</span>;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.02</span>sec)</span><br><span class="line"></span><br><span class="line"># 给角色role_test增加<span class="keyword">insert</span>权限</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">grant</span> <span class="keyword">insert</span> <span class="keyword">on</span> db.<span class="operator">*</span><span class="keyword">to</span> <span class="string">&#x27;role_test&#x27;</span>;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.08</span>sec)</span><br><span class="line"></span><br><span class="line"># 给角色role_test删除<span class="keyword">insert</span>权限</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">revoke</span> <span class="keyword">insert</span> <span class="keyword">on</span> db.<span class="operator">*</span><span class="keyword">from</span> <span class="string">&#x27;role_test&#x27;</span>;</span><br><span class="line">QueryOK, <span class="number">0</span><span class="keyword">rows</span> affected (<span class="number">0.10</span>sec)</span><br><span class="line"></span><br><span class="line"># 查看默认角色信息</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> mysql.default_roles;</span><br><span class="line"></span><br><span class="line"># 查看角色与用户关系</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> mysql.role_edges;</span><br><span class="line"></span><br><span class="line"># 删除角色</span><br><span class="line">mysql<span class="operator">&gt;</span><span class="keyword">drop</span> role role_test;</span><br></pre></td></tr></table></figure><h4 id="1-9-多值索引"><a href="#1-9-多值索引" class="headerlink" title="1.9-多值索引"></a>1.9-多值索引</h4><p>从 MySQL 8.0.17 开始,InnoDB 支持创建多值索引,这是在存储值数组的 JSON 列上定义的二级索引,单个数据记录可以有多个索引记录。这样的索引使用关键部分定义,例如 CAST(data-&gt;’$.zipcode’ AS UNSIGNED ARRAY)。 MySQL 优化器自动使用多值索引来进行合适的查询,可以在 EXPLAIN 的输出中查看。</p><h4 id="1-10-函数索引"><a href="#1-10-函数索引" class="headerlink" title="1.10-函数索引"></a>1.10-函数索引</h4><p>MySQL 8.0.13 以及更高版本支持函数索引 functional key parts ,也就是将表达式的值作为索引的内容,而不是列值或列值前缀。 将函数作为索引键可以用于索引那些没有在表中直接存储的内容。</p><p>其实MySQL5.7中推出了虚拟列的功能,而MySQL8.0的函数索引也是依据虚拟列来实现的。</p><ul><li>只有那些能够用于计算列的函数才能够用于创建函数索引。</li><li>函数索引中不允许使用子查询、参数、变量、存储函数以及自定义函数。</li><li>SPATIAL 索引和 FULLTEXT 索引不支持函数索引。</li></ul><h4 id="1-11-不可见索引"><a href="#1-11-不可见索引" class="headerlink" title="1.11-不可见索引"></a>1.11-不可见索引</h4><p>在MySQL 5.7版本及之前,只能通过显式的方式删除索引。此时,如果发现删除索引后出现错误,又只能通过显式创建索引的方式将删除的索引创建回来。如果数据表中的数据量非常大,或者数据表本身比较大,这种操作就会消耗系统过多的资源,操作成本非常高。</p><p>从MySQL 8.x开始支持隐藏索引 invisible indexes ,只需要将待删除的索引设置为隐藏索引,使查询优化器不再使用这个索引 即使使用force index 强制使用索引 ,优化器也不会使用该索引 , 确认将索引设置为隐藏索引后系统不受任何响应,就可以彻底删除索引。 这种通过先将索引设置为隐藏索引,再删除索引的方式就是软删除 。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">show</span> <span class="keyword">create table</span> t1\G</span><br><span class="line"><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span></span><br><span class="line"><span class="keyword">Table</span>: t1</span><br><span class="line"><span class="keyword">Create Table</span>: <span class="keyword">CREATE TABLE</span> t1 (</span><br><span class="line">c1 <span class="type">int</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">c2 <span class="type">int</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">create_time <span class="type">timestamp</span> <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">KEY idx_c1 ( c1 ) <span class="comment">/*!80000 INVISIBLE */</span></span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci</span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line"># 不可见的情况下是不会走索引的,key <span class="keyword">null</span></span><br><span class="line">mysql<span class="operator">&gt;</span> explain <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> t1 <span class="keyword">where</span> c1 <span class="number">3</span>;</span><br><span class="line"><span class="comment">---- ------------- ------- ------------ ------ --------------- ------ --------- ------ ------ ---------- -------------</span></span><br><span class="line"><span class="operator">|</span> id <span class="operator">|</span> select_type <span class="operator">|</span> <span class="keyword">table</span> <span class="operator">|</span> partitions <span class="operator">|</span> type <span class="operator">|</span> possible_keys <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> SIMPLE <span class="operator">|</span> t1 <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">ALL</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="number">5</span> <span class="operator">|</span> <span class="number">20.00</span> <span class="operator">|</span> <span class="keyword">Using</span> <span class="keyword">where</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="number">5</span> <span class="operator">|</span> <span class="number">20.00</span> <span class="operator">|</span> <span class="keyword">Using</span> <span class="keyword">where</span> <span class="operator">|</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span>, <span class="number">1</span> warning (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line"># 设置为索引可见,</span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">alter table</span> t1 <span class="keyword">alter</span> index idx_c1 visible;</span><br><span class="line">Query OK, <span class="number">0</span> <span class="keyword">rows</span> affected (<span class="number">0.01</span> sec)</span><br><span class="line">Records: <span class="number">0</span> Duplicates: <span class="number">0</span> Warnings: <span class="number">0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">show</span> <span class="keyword">create table</span> t1\G</span><br><span class="line"><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span></span><br><span class="line"><span class="keyword">Table</span>: t1</span><br><span class="line"><span class="keyword">Create Table</span>: <span class="keyword">CREATE TABLE</span> t1 (</span><br><span class="line">c1 <span class="type">int</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">c2 <span class="type">int</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">create_time <span class="type">timestamp</span> <span class="keyword">NOT NULL</span> <span class="keyword">DEFAULT</span> <span class="built_in">CURRENT_TIMESTAMP</span>,</span><br><span class="line">KEY idx_c1 ( c1 )</span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci</span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line"></span><br><span class="line"># 可以走索引,key idx_c1</span><br><span class="line">mysql<span class="operator">&gt;</span> explain <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> t1 <span class="keyword">where</span> c1 <span class="number">3</span>;</span><br><span class="line"><span class="comment">---- ------------- ------- ------------ ------ --------------- -------- --------- ------- ------ ---------- -------</span></span><br><span class="line"><span class="operator">|</span> id <span class="operator">|</span> select_type <span class="operator">|</span> <span class="keyword">table</span> <span class="operator">|</span> partitions <span class="operator">|</span> type <span class="operator">|</span> possible_keys <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> SIMPLE <span class="operator">|</span> t1 <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> idx_c1 <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> idx_c1 <span class="operator">|</span> <span class="number">5</span> <span class="operator">|</span> const <span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">100.00</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> idx_c1 <span class="operator">|</span> <span class="number">5</span> <span class="operator">|</span> const <span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">100.00</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span>, <span class="number">1</span> warning (<span class="number">0.00</span> sec)</span><br></pre></td></tr></table></figure><h4 id="1-12-新增降序索引"><a href="#1-12-新增降序索引" class="headerlink" title="1.12-新增降序索引"></a>1.12-新增降序索引</h4><p>MySQL在语法上很早就已经支持降序索引,但实际上创建的仍然是升序索引。从8.0开始,实际创建的为降序索引。</p><h4 id="1-13-SET-VAR-语法"><a href="#1-13-SET-VAR-语法" class="headerlink" title="1.13-SET_VAR 语法"></a>1.13-SET_VAR 语法</h4><p>在sql语法中增加SET_VAR语法,动态调整部分参数,有利于提升语句性能。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="comment">/* SET_VAR(sort_buffer_size 16M) */</span> id <span class="keyword">from</span> test <span class="keyword">order</span> id ;</span><br><span class="line"><span class="keyword">insert</span> <span class="comment">/* SET_VAR(foreign_key_checks OFF) */</span> <span class="keyword">into</span> test(name) <span class="keyword">values</span>(<span class="number">1</span>);</span><br></pre></td></tr></table></figure><h4 id="1-14-参数修改持久化"><a href="#1-14-参数修改持久化" class="headerlink" title="1.14-参数修改持久化"></a>1.14-参数修改持久化</h4><p>MySQL 8.0版本支持在线修改全局参数并持久化,通过加上PERSIST关键字,可以将修改的参数持久化到新的配置文件 mysqld-auto.cnf 中,重启MySQL时,可以从该配置文件获取到最新的配置参数。</p><p>例如执行:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">set</span> PERSIST expire_logs_days <span class="number">10</span> ;</span><br></pre></td></tr></table></figure><p>系统会在数据目录下生成一个包含json格式的 mysqld-auto.cnf 的文件,格式化后如下所示,当 my.cnf 和 mysqld-auto.cnf 同时存在时,后者具有更高优先级。</p><h4 id="1-15-innodb-select-for-update跳过锁等待"><a href="#1-15-innodb-select-for-update跳过锁等待" class="headerlink" title="1.15-innodb select for update跳过锁等待"></a>1.15-innodb select for update跳过锁等待</h4><p>select … for update,select … for share(8.0新增语法) 添加 NOWAIT、SKIP LOCKED语法,跳过锁等待,或者跳过锁定。</p><p>在5.7及之前的版本,select…for update,如果获取不到锁,会一直等待,直到innodb_lock_wait_timeout超时。</p><p>在8.0版本,通过添加nowait,skip locked语法,能够立即返回。如果查询的行已经加锁,那么nowait会立即报错返回,而skip locked也会立即返回,只是返回的结果中不包含被锁定的行。</p><h4 id="1-16-group-by-不再隐式排序"><a href="#1-16-group-by-不再隐式排序" class="headerlink" title="1.16-group by 不再隐式排序"></a>1.16-group by 不再隐式排序</h4><p>目的是为了兼容sql的标准语法,方便迁移</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br></pre></td><td class="code"><pre><span class="line">mysql <span class="number">5.7</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="built_in">count</span>(<span class="operator">*</span>),age <span class="keyword">from</span> t5 <span class="keyword">group</span> <span class="keyword">by</span> age;</span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="operator">|</span> <span class="built_in">count</span>(<span class="operator">*</span>) <span class="operator">|</span> age <span class="operator">|</span></span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">25</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">29</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">32</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">33</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">35</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="number">5</span> <span class="keyword">rows</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br><span class="line">mysql <span class="number">8.0</span></span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> <span class="built_in">count</span>(<span class="operator">*</span>),age <span class="keyword">from</span> t5 <span class="keyword">group</span> <span class="keyword">by</span> age;</span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="operator">|</span> <span class="built_in">count</span>(<span class="operator">*</span>) <span class="operator">|</span> age <span class="operator">|</span></span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">25</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">32</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">35</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">29</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> <span class="number">33</span> <span class="operator">|</span></span><br><span class="line"><span class="comment">---------- ------</span></span><br><span class="line"><span class="number">5</span> <span class="keyword">rows</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.00</span> sec)</span><br></pre></td></tr></table></figure><p>可以看到,MySQL5.7 在group by中对分组字段进行了隐式排序,而MySQL8.0取消了隐式排序。如果要添加排序的话,需要显示增加,比如 select count(*),age from t5 group by age order by age;</p><h4 id="1-17-自增变量持久化"><a href="#1-17-自增变量持久化" class="headerlink" title="1.17-自增变量持久化"></a>1.17-自增变量持久化</h4><p>在8.0之前的版本,自增值是保存在内存中,自增主键AUTO_INCREMENT的值如果大于max(primary key) 1,在MySQL重启后,会重置AUTO_INCREMENT max(primary key) 1。这种现象在某些情况下会导致业务主键冲突或者其他难以发现的问题。自增主键重启重置的问题很早就被发现([<a href="https://bugs.mysql.com/bug.php?id">https://bugs.mysql.com/bug.php?id</a> 199](<a href="https://link.segmentfault.com/?enc">https://link.segmentfault.com/?enc</a> gUfXo0yPZKw1mc7el4KnTQ%3D%3D.6Fbh8hhQOxnhZAxh%2BzdLZPHHcr1Vzam%2B6SQpd5Ak0iGwFTyLyReG2IBRz7EA0Ob4)),一直到8.0才被解决。8.0版本将会对AUTO_INCREMENT值进行持久化,MySQL重启后,该值将不会改变。</p><p>8.0开始,当前最大的自增计数器每当发生变化,值会被写入redo log中,并在每个检查点时候保存到private system table中。这一变化,对AUTO_INCREMENT值进行持久化,MySQL重启后,该值将不会改变。</p><ul><li>MySQL server重启后不再取消AUTO_INCREMENT N表选项的效果。如果将自增计数器初始化为特定值,或者将自动递增计数器值更改为更大的值,新的值被持久化,即使服务器重启。</li><li>在回滚操作之后立即重启服务器将不再导致重新使用分配给回滚事务的自动递增值。</li><li>如果将AUTO_INCREMEN列值修改为大于当前最大自增值(例如,在更新操作中)的值,则新值将被持久化,随后的插入操作将从新的、更大的值开始分配自动增量值。</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">-- 确认下自己的版本</span></span><br><span class="line"><span class="keyword">select</span> VERSION()</span><br><span class="line"><span class="comment">/*</span></span><br><span class="line"><span class="comment">VERSION() |</span></span><br><span class="line"><span class="comment">----------</span></span><br><span class="line"><span class="comment">5.7.26-log|</span></span><br><span class="line"><span class="comment">*/</span></span><br><span class="line"></span><br><span class="line"><span class="comment">-- 创建表</span></span><br><span class="line"><span class="keyword">create table</span> testincr(</span><br><span class="line">id <span class="type">int</span> auto_increment <span class="keyword">primary key</span>,</span><br><span class="line">name <span class="type">varchar</span>(<span class="number">50</span>)</span><br><span class="line">)</span><br><span class="line"></span><br><span class="line"><span class="comment">-- 插入数据</span></span><br><span class="line"><span class="keyword">insert into</span> testincr(name) <span class="keyword">values</span></span><br><span class="line">(<span class="string">&#x27;刘备&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;关羽&#x27;</span>),</span><br><span class="line">(<span class="string">&#x27;张飞&#x27;</span>);</span><br><span class="line"></span><br><span class="line"><span class="comment">-- 查看当前的自增量</span></span><br><span class="line"><span class="keyword">select</span> t. AUTO_INCREMENT <span class="keyword">from</span> information_schema.TABLES t <span class="keyword">where</span> TABLE_NAME <span class="string">&#x27;testincr&#x27;</span></span><br><span class="line"><span class="comment">/*</span></span><br><span class="line"><span class="comment">AUTO_INCREMENT|</span></span><br><span class="line"><span class="comment">--------------</span></span><br><span class="line"><span class="comment">4|</span></span><br><span class="line"><span class="comment">*/</span></span><br><span class="line"><span class="comment">-- 更改列值</span></span><br><span class="line"><span class="keyword">update</span> testincr <span class="keyword">set</span> id <span class="number">4</span> <span class="keyword">where</span> id <span class="number">3</span></span><br><span class="line"></span><br><span class="line"><span class="comment">-- 查看现在的表值</span></span><br><span class="line"><span class="comment">/*</span></span><br><span class="line"><span class="comment">id|name|</span></span><br><span class="line"><span class="comment">-- ----</span></span><br><span class="line"><span class="comment">1|刘备 |</span></span><br><span class="line"><span class="comment">2|关羽 |</span></span><br><span class="line"><span class="comment">4|张飞 |</span></span><br><span class="line"><span class="comment">*/</span></span><br><span class="line"><span class="comment">-- 插入新值 问题出现</span></span><br><span class="line"><span class="keyword">insert into</span> testincr(name) <span class="keyword">values</span>(<span class="string">&#x27;赵云&#x27;</span>);</span><br><span class="line"><span class="comment">/*</span></span><br><span class="line"><span class="comment">SQL 错误 [1062] [23000]: Duplicate entry &#x27;4&#x27; for key &#x27;PRIMARY&#x27;</span></span><br><span class="line"><span class="comment">*/</span></span><br><span class="line"></span><br><span class="line"><span class="comment">-- 如果我们再次插入,它就是正常的,因为id到5了。。。</span></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">insert into</span> testincr(name) <span class="keyword">values</span>(<span class="string">&#x27;赵云&#x27;</span>);</span><br><span class="line">Query OK, <span class="number">1</span> <span class="type">row</span> affected (<span class="number">0.01</span> sec)</span><br></pre></td></tr></table></figure><h4 id="1-18-binlog日志事务压缩"><a href="#1-18-binlog日志事务压缩" class="headerlink" title="1.18-binlog日志事务压缩"></a>1.18-binlog日志事务压缩</h4><p>MySQL 8.0.20 版本增加了binlog日志事务压缩功能,将事务信息使用zstd算法进行压缩,然后再写入binlog日志文件,这种被压缩后的事务信息,在binlog中对应为一个新的event类型,叫做Transaction_payload_event。</p><h4 id="1-19-分区表改进"><a href="#1-19-分区表改进" class="headerlink" title="1.19-分区表改进"></a>1.19-分区表改进</h4><p>MySQL 8.0 对于分区表功能进行了较大的修改,在 8.0 之前,分区表在Server层实现,支持多种存储引擎,从 8.0 版本开始,分区表功能移到引擎层实现,目前MySQL 8.0 版本只有InnoDB存储引擎支持分区表。</p><h4 id="1-20-自动参数设置"><a href="#1-20-自动参数设置" class="headerlink" title="1.20-自动参数设置"></a>1.20-自动参数设置</h4><p>将innodb_dedicated_server开启的时候,它可以自动的调整下面这四个参数的值:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">innodb_buffer_pool_size 总内存大小</span><br><span class="line">innodb_log_file_size redo文件大小</span><br><span class="line">innodb_log_files_in_group redo文件数量</span><br><span class="line">innodb_flush_method 数据刷新方法</span><br></pre></td></tr></table></figure><p>只需将innodb_dedicated_server ON 设置好,上面四个参数会自动调整,解决非专业人员安装数据库后默认初始化数据库参数默认值偏低的问题,让MySQL自适应的调整上面四个参数,前提是服务器是专用来给MySQL数据库的,如果还有其他软件或者资源或者多实例MySQL使用,不建议开启该参数,本文以MySQL8.0.19为例。</p><p>那么按照什么规则调整呢?MySQL官方给出了相关参数调整规则如下:</p><p><strong>1. innodb_buffer_pool_size自动调整规则:</strong></p><table><thead><tr><th>专用服务器内存大小</th><th>buffer_pool_size大小</th></tr></thead><tbody><tr><td>小于1G</td><td>128MB (MySQL缺省值)</td></tr><tr><td>1G to 4G</td><td>OS内存*0.5</td></tr><tr><td>大于4G</td><td>OS内存*0.75</td></tr></tbody></table><p><strong>2. innodb_log_file_size自动调整规则:</strong></p><p><strong>3. innodb_log_files_in_group自动调整规则:</strong><br>innodb_log_files_in_group值就是log file的数量</p><table><thead><tr><th>buffer_pool_size大小</th><th>log file数量</th></tr></thead><tbody><tr><td>小于8G</td><td>ROUND(buffer pool size)</td></tr><tr><td>8G to 128G</td><td>ROUND(buffer pool size * 0.75)</td></tr><tr><td>大于128G</td><td>64</td></tr><tr><td>说明:如果ROUND(buffer pool size)值小于2GB,那么innodb_log_files_in_group会强制设置为2。</td><td></td></tr></tbody></table><p><strong>4. innodb_flush_method自动调整规则:</strong></p><p>该参数调整规则直接引用官方文档的解释:The flush method is set to O_DIRECT_NO_FSYNC when innodb_dedicated_server is enabled. If the O_DIRECT_NO_FSYNC setting is not available, the default innodb_flush_method setting is used.<br>如果系统允许设置为O_DIRECT_NO_FSYNC;如果系统不允许,则设置为InnoDB默认的Flush method。</p><h5 id="1-20-1-自适应参数的好处"><a href="#1-20-1-自适应参数的好处" class="headerlink" title="1.20.1-自适应参数的好处:"></a>1.20.1-自适应参数的好处:</h5><ul><li>自动调整,简单方便,让DBA更省心</li><li>自带优化光环:没有该参数前,innodb_buffer_pool_size和log_file_size默认安装初始化后只有128M和48M,这对于一个生产环境来说是远远不够的,通常DBA都会手工根据服务器的硬件配置来调整优化,该参数出现后基本上可以解决入门人员安装MySQL后的性能问题。</li><li>云厂商,虚拟化等动态资源扩容或者缩容后,不必再操心MySQL参数配置问题。</li></ul><h5 id="1-20-2-自适应参数的限制"><a href="#1-20-2-自适应参数的限制" class="headerlink" title="1.20.2-自适应参数的限制:"></a>1.20.2-自适应参数的限制:</h5><ul><li>专门给MySQL独立使用的服务器</li><li>单机多实例的情况不适用</li><li>服务器上还跑着其他软件或应用的情况不适用</li></ul><h4 id="1-21-窗口函数"><a href="#1-21-窗口函数" class="headerlink" title="1.21-窗口函数"></a>1.21-窗口函数</h4><p>从 MySQL 8.0 开始,新增了一个叫窗口函数的概念。</p><p>什么叫窗口?</p><p>它可以理解为记录集合,窗口函数也就是在满足某种条件的记录集合上执行的特殊函数。对于每条记录都要在此窗口内执行函数,有的函数随着记录不同,窗口大小都是固定的,这种属于静态窗口;有的函数则相反,不同的记录对应着不同的窗口,这种动态变化的窗口叫滑动窗口。</p><p>它可以用来实现若干新的查询方式。窗口函数与 SUM()、COUNT() 这种聚合函数类似,但它不会将多行查询结果合并为一行,而是将结果放回多行当中。即窗口函数不需要 GROUP BY。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-13/img1.avif"></p><p>窗口函数内容太多,后期我会专门写一篇文章介绍窗口函数</p><h4 id="1-22-索引损坏标记"><a href="#1-22-索引损坏标记" class="headerlink" title="1.22-索引损坏标记"></a>1.22-索引损坏标记</h4><p>当遇到索引树损坏时,InnoDB会在redo日志中写入一个损坏标志,这会使损坏标志安全崩溃。InnoDB还将内存损坏标志数据写入每个检查点的私有系统表中。</p><p>在恢复的过程中,InnoDB会从这两个位置读取损坏标志,并合并结果,然后将内存中的表和索引对象标记为损坏。</p><h4 id="1-23-InnoDB-memcached插件"><a href="#1-23-InnoDB-memcached插件" class="headerlink" title="1.23-InnoDB memcached插件"></a>1.23-InnoDB memcached插件</h4><p>InnoDB memcached插件支持批量get操作 在一个memcached查询中获取多个键值对 和范围查询。减少客户端和服务器之间的通信流量,在单个memcached查询中获取多个键、值对的功能可以提高读取性能。</p><h4 id="1-24-Online-DDL"><a href="#1-24-Online-DDL" class="headerlink" title="1.24-Online DDL"></a>1.24-Online DDL</h4><p>从 MySQL 8.0.12 开始 仅仅指InnoDB引擎 ,以下 ALTER TABLE 操作支持 ALGORITHM INSTANT:</p><ul><li>添加列。此功能也称为“即时添加列”。限制适用。</li><li>添加或删除虚拟列。</li><li>添加或删除列默认值。</li><li>修改 ENUM 或 SET 列的定义。</li><li>更改索引类型。</li><li>重命名表。</li></ul><p>Online DDL的好处:</p><p>支持 ALGORITHM INSTANT 的操作只修改数据字典中的元数据。表上没有元数据锁,表数据不受影响,操作是即时的,并不会造成业务抖动。这在一些服务级别要求比较高 7*24 的系统中,是非常方便的。该特性是由腾讯游戏DBA团队贡献的。</p><p>如果未明确指定,则支持它的操作默认使用 ALGORITHM INSTANT。如果指定了 ALGORITHM INSTANT 但不受支持,则操作会立即失败并出现错误。需要注意的是,在 MySQL 8.0.29 之前,一列只能作为表的最后一列添加。不支持将列添加到其他列中的任何其他位置。从 MySQL 8.0.29 开始,可以将即时添加的列添加到表中的任何位置。</p><h4 id="1-25-EXPLAIN-ANALYZE"><a href="#1-25-EXPLAIN-ANALYZE" class="headerlink" title="1.25-EXPLAIN ANALYZE"></a>1.25-EXPLAIN ANALYZE</h4><p>Explain 是我们常用的查询分析工具,可以对查询语句的执行方式进行评估,给出很多有用的线索。但他仅仅是评估,不是实际的执行情况,比如结果中的 rows,可能和实际结果相差甚大。</p><p>Explain Analyze 是 MySQL 8 中提供的新工具,可贵之处在于可以给出实际执行情况。Explain Analyze 是一个查询性能分析工具,可以详细的显示出 查询语句执行过程中,都在哪儿花费了多少时间。Explain Analyze 会做出查询计划,并且会实际执行,以测量出查询计划中各个关键点的实际指标,例如耗时、条数,最后详细的打印出来。</p><p>这项新功能建立在常规的EXPLAIN基础之上,可以看作是MySQL 8.0之前添加的EXPLAIN FORMAT TREE的扩展。EXPLAIN除了输出查询计划和估计成本之外,EXPLAIN ANALYZE还会输出执行计划中各个迭代器的实际成本。</p><h4 id="1-26-ReplicaSet"><a href="#1-26-ReplicaSet" class="headerlink" title="1.26-ReplicaSet"></a>1.26-ReplicaSet</h4><p>InnoDB ReplicaSet 由一个主节点和多个从节点构成. 可以使用MySQL Shell的ReplicaSet对象和AdminAPI操作管理复制集, 例如检查InnoDB复制集的状态, 并在发生故障时手动故障转移到新的主服务器.</p><p>ReplicaSet 所有的节点必须基于GTID,并且数据复制采用异步的方式。使用复制集还可以接管既有的主从复制,但是需要注意,一旦被接管,只能通过AdminAPI对其进行管理。</p><h4 id="1-27-备份锁"><a href="#1-27-备份锁" class="headerlink" title="1.27-备份锁"></a>1.27-备份锁</h4><p>在MySQL 8.0中,引入了一个轻量级的备份锁,这个锁可以保证备份一致性,而且阻塞的操作相对比较少,是一个非常重要的新特性。</p><p>在MySQL 8.0中,为了解决备份FTWRL的问题,引入了轻量级的备份锁;可以通过LOCK INSTANCE FOR BACKUP和UNLOCK INSTANCE,以获取和释放备份锁,执行该语句需要BACKUP_ADMIN权限。</p><p>backup lock不会阻塞读写操作。不过,backup lock会阻塞大部分DDL操作,包括创建&#x2F;删除表、加&#x2F;减字段、增&#x2F;删索引、optimize&#x2F;analyze&#x2F;repair table等。</p><p>总的来说,备份锁还是非常实用的,毕竟其不会影响业务的正常读写;至于备份锁和DDL操作的冲突,还是有很多方法可以避免,比如错开备份和变更的时间、通过pt-online-schema-change&#x2F;gh-ost避免长时间阻塞等等。随着备份锁的引入,Oracle官方备份工具MEB 8.0和Percona开源备份工具XtraBackup 8.0,也是更新了对backup lock的支持。</p><h4 id="1-28-Binlog增强"><a href="#1-28-Binlog增强" class="headerlink" title="1.28-Binlog增强"></a>1.28-Binlog增强</h4><p>MySQL 8.0.20 版本增加了binlog日志事务压缩功能,将事务信息使用zstd算法进行压缩,然后再写入binlog日志文件,这种被压缩后的事务信息,在binlog中对应为一个新的event类型,叫做Transaction_payload_event。</p><h3 id="二、性能提升"><a href="#二、性能提升" class="headerlink" title="二、性能提升"></a>二、性能提升</h3><h4 id="2-1-基于竞争感知的事务调度"><a href="#2-1-基于竞争感知的事务调度" class="headerlink" title="2.1-基于竞争感知的事务调度"></a>2.1-基于竞争感知的事务调度</h4><p>MySQL 在 8.0.3 版本引入了新的事务调度算法,基于竞争感知的事务调度,Contention-Aware Transaction Scheduling,简称CATS。在CATS算法之前,MySQL使用FIFO算法,先到的事务先获得锁,如果发生锁等待,则按照FIFO算法进行排队。CATS相比FIFO更加复杂,也更加聪明,在高负载、高争用的场景下,性能提升显著。</p><h4 id="2-2-基于WriteSet的并行复制"><a href="#2-2-基于WriteSet的并行复制" class="headerlink" title="2.2-基于WriteSet的并行复制"></a>2.2-基于WriteSet的并行复制</h4><p>总的来说MySQL关于并行复制到目前为止经历过三个比较关键的时间结点“库间并发”,“组提交”,“写集合”;真可谓是江山代有人才出,前浪死在沙滩上;总的来说就后面的比前面的不知道高到哪里去了</p><p>MySQL 8.0 版本引入了一个新的机制 WriteSet,来追踪事务之间的依赖性,这个特性被用于优化从库应用binlog的速度,在主库并发较低的场景下,能够显著提高从库回放binlog的速度,基于WriteSet 的并行复制方案,彻底解决了MySQL复制延迟问题。只需要设置这2个参数即可</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">binlog_transaction_dependency_tracking WRITESET # COMMIT_ORDER</span><br><span class="line">transaction_write_set_extraction XXHASH64</span><br></pre></td></tr></table></figure><h4 id="2-3-JSON特性增强"><a href="#2-3-JSON特性增强" class="headerlink" title="2.3-JSON特性增强"></a>2.3-JSON特性增强</h4><p>MySQL 8 大幅改进了对 JSON 的支持,添加了基于路径查询参数从 JSON 字段中抽取数据的 JSON_EXTRACT() 函数,以及用于将数据分别组合到 JSON 数组和对象中的 JSON_ARRAYAGG() 和 JSON_OBJECTAGG() 聚合函数。</p><p>在主从复制中,新增参数 binlog_row_value_options,控制JSON数据的传输方式,允许对于Json类型部分修改,在binlog中只记录修改的部分,减少json大数据在只有少量修改的情况下,对资源的占用。</p><h4 id="2-4-空间数据类型增强"><a href="#2-4-空间数据类型增强" class="headerlink" title="2.4-空间数据类型增强"></a>2.4-空间数据类型增强</h4><p>MySQL 8 大幅改进了空间数据类型和函数,支持更多的空间分析函数和空间类型对象,空间分析功能和性能得到大幅提升。</p><h4 id="2-5-doublewrite改进"><a href="#2-5-doublewrite改进" class="headerlink" title="2.5-doublewrite改进"></a>2.5-doublewrite改进</h4><p>在MySQL 8.0.20 版本之前,doublewrite 存储区位于系统表空间,从 8.0.20 版本开始,doublewrite 有自己独立的表空间文件,这种变更,能够降低doublewrite的写入延迟,增加吞吐量,为设置doublewrite文件的存放位置提供了更高的灵活性。</p><h4 id="2-6-hash-join"><a href="#2-6-hash-join" class="headerlink" title="2.6-hash join"></a>2.6-hash join</h4><p>MySQL 8.0.18 版本引入 hash join 功能,对于没有走索引的等值 join 连接可以使用 hash join 进行优化。8.0.20 版本对 hash join 进行了加强,即使 join 连接没有使用等值条件也可以使用 hash join 优化,原来使用 BNL 算法的 join 连接将全部由 hash join 代替。</p><h5 id="2-6-1-NestLoopJoin算法"><a href="#2-6-1-NestLoopJoin算法" class="headerlink" title="2.6.1-NestLoopJoin算法"></a>2.6.1-NestLoopJoin算法</h5><p>简单来说,就是双重循环,遍历外表(驱动表),对于外表的每一行记录,然后遍历内表,然后判断join条件是否符合,进而确定是否将记录吐出给上一个执行节点。</p><p>从算法角度来说,这是一个M*N的复杂度。</p><h5 id="2-6-2-Hash-Join"><a href="#2-6-2-Hash-Join" class="headerlink" title="2.6.2-Hash Join"></a>2.6.2-Hash Join</h5><p>是针对equal-join场景的优化,基本思想是,将外表数据load到内存,并建立hash表,这样只需要遍历一遍内表,就可以完成join操作,输出匹配的记录。</p><p>如果数据能全部load到内存当然好,逻辑也简单,一般称这种join为CHJ(Classic Hash Join),之前MariaDB就已经实现了这种HashJoin算法。</p><p>如果数据不能全部load到内存,就需要分批load进内存,然后分批join,下面具体介绍这几种join算法的实现。</p><h4 id="2-7-anti-join-反连接"><a href="#2-7-anti-join-反连接" class="headerlink" title="2.7-anti join 反连接"></a>2.7-anti join 反连接</h4><p>MySQL 8.0.17版本引入了一个anti join的优化,这个优化能够将where条件中的not in(subquery), not exists(subquery),in(subquery) is not true,exists(subquery) is not true,在内部转化成一个anti join,以便移除里面的子查询subquery,这个优化在某些场景下,能够将性能提升20%左右。</p><p>anti join适用的场景案例通常如下:</p><ul><li>找出在集合A且不在集合B中的数据</li><li>找出在当前季度里没有购买商品的客户</li><li>找出今年没有通过考试的学生</li><li>找出过去3年,某个医生的病人中没有进行医学检查的部分</li></ul><h4 id="2-8-redo优化"><a href="#2-8-redo优化" class="headerlink" title="2.8-redo优化"></a>2.8-redo优化</h4><p>mysql8.0一个新特性就是redo log提交的无锁化。在8.0以前,各个用户线程都是通过互斥量竞争,串行的写log buffer,因此能保证lsn的顺序无间隔增长。</p><p>mysql8.0通过redo log无锁化,解决了用户线程写redo log时竞争锁带来的性能影响。同时将redo log写文件、redo log刷盘从用户线程中剥离出来,抽成单独的线程,用户线程只负责将redo log写入到log buffer,不再关心redo log的落盘细节,只需等待log_writer线程或log_flusher线程的通知。</p><h4 id="2-9-直方图-统计信息"><a href="#2-9-直方图-统计信息" class="headerlink" title="2.9-直方图 统计信息"></a>2.9-直方图 统计信息</h4><p>优化器会利用column_statistics的数据,判断字段的值的分布,得到更准确的执行计划。</p><p>可以通过ANALYZE TABLE table_name [UPDATE HISTOGRAM on colume_name with N BUCKETS |DROP HISTOGRAM ON clo_name] 来收集或者删除直方图信息。</p><p>直方图统计了表中某些字段的数据分布情况,为优化选择高效的执行计划提供参考,直方图与索引有着本质的区别,维护一个索引有代价。每一次的insert、update、delete都需要更新索引,会对性能有一定的影响。而直方图一次创建永不更新,除非明确去更新它,因此不会影响insert、update、delete的性能。</p><h4 id="2-10-关闭QC-Query-Cache"><a href="#2-10-关闭QC-Query-Cache" class="headerlink" title="2.10-关闭QC Query Cache"></a>2.10-关闭QC <strong>Query Cache</strong></h4><p>从 MySQL 8.0开始,不再使用查询缓存 Query Cache 。</p><p>随着技术的进步,经过时间的考验,MySQL的工程团队发现启用缓存的好处并不多。</p><p>首先,查询缓存的效果取决于缓存的命中率,只有命中缓存的查询效果才能有改善,因此无法预测其性能。</p><p>其次,查询缓存的另一个大问题是它受到单个互斥锁的保护。在具有多个内核的服务器上,大量查询会导致大量的互斥锁争用。</p><p>MySQL8.0取消查询缓存的另外一个原因是,研究表明,缓存越靠近客户端,获得的好处越大。MySQL8.0新增加了一些其他对性能干预的工具来支持。另外,还有像ProxySQL这样的第三方工具,也可以充当中间缓存。</p><h3 id="三、安全性增强"><a href="#三、安全性增强" class="headerlink" title="三、安全性增强"></a>三、安全性增强</h3><h4 id="3-1-死锁检测"><a href="#3-1-死锁检测" class="headerlink" title="3.1-死锁检测"></a>3.1-死锁检测</h4><p>可以使用一个新的动态变量 innodb_deadlock_detect 来禁用死锁检测。在高并发系统上,当多个线程等待同一个锁时,死锁检测会导致速度变慢。有时,禁用死锁检测并在发生死锁时依靠 innodb_lock_wait_timeout 设置进行事务回滚可能更有效。</p><h4 id="3-2-默认密码认证插件"><a href="#3-2-默认密码认证插件" class="headerlink" title="3.2-默认密码认证插件"></a>3.2-默认密码认证插件</h4><p>MySQL 8.0.4 版本修改了默认的身份认证插件,从老的mysql_native_password插件变为新的caching_sha2_password,并将其作为默认的身份认证机制,同时客户端对应的libmysqlclient也默认使用新的认证插件。</p><h4 id="3-3-升级密码过期-历史密码使用规则"><a href="#3-3-升级密码过期-历史密码使用规则" class="headerlink" title="3.3-升级密码过期,历史密码使用规则"></a>3.3-升级密码过期,历史密码使用规则</h4><p>设置历史密码检测规则,防止反复重用旧密码。</p><ul><li>password_history</li><li>password_reuse_interval</li></ul><p>双密码机制,修改密码时,创建新的密码,同时旧的密码也可以使用,保留一定的缓冲时间进行检查确认。</p><p>当修改一个账户密码时,需要去验证当前的密码,通过参数password_require_current来控制,默认关闭,当打开该选项时,如果要修改账户密码,必须要提供当前的密码才允许修改。</p><h4 id="3-4-认值加密插件"><a href="#3-4-认值加密插件" class="headerlink" title="3.4-认值加密插件"></a>3.4-认值加密插件</h4><p>老版本:认证方式为sha256_password</p><p>8.0 版本:在老版本的基础上,新增caching_sha2_password,可以使用缓存解决连接时的延时问题。</p><p>需要注意的问题是:如果客户端与服务端配置不同,无法进行连接,两者的加密认证方式需要一样。</p><h4 id="3-5-用户密码增强"><a href="#3-5-用户密码增强" class="headerlink" title="3.5-用户密码增强"></a>3.5-用户密码增强</h4><p>** 1 密码的重复使用策略**</p><p>历史密码重复次数检测:新密码不能与最近最新的5个密码相同。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">password_history 5 ; </span><br></pre></td></tr></table></figure><p>时间间隔:新密码不能和过去90天内的密码相同。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">password_reuse_interval 90 ; </span><br></pre></td></tr></table></figure><p>** 2 修改密码必要的验证策略**</p><p>修改密码,要输入当前的密码。增加了用户的安全性。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">## 默认为off;为on 时 修改密码需要用户提供当前密码 (开启后修改密码需要验证旧密码,root 用户不需要)</span><br><span class="line">password_require_current on ;</span><br></pre></td></tr></table></figure><p>** 3 双密码**</p><p>相比于一个用户只有一个密码最大优点就是:修改密码不会导致应用不可用。那么应用就可以自动使用副密码 副密码和当前密码保持一致 连接数据库库。确保了业务的不中断。修改密码不会导致应用不可用;应用就可以自动使用副密码连接数据库。</p><h4 id="3-6-角色功能"><a href="#3-6-角色功能" class="headerlink" title="3.6-角色功能"></a>3.6-角色功能</h4><p>MySQL角色是指定权限集合。像用户账户一样,角色可以拥有授予和撤销的权限。</p><p>可以授予用户账户角色,授予该账户与每个角色相关的权限。</p><p>方便了用户权限管理和维护。很好地解决了多个用户使用相同的权限集。权限–》角色–》用户。</p><h4 id="3-7-redo-undo-日志加密"><a href="#3-7-redo-undo-日志加密" class="headerlink" title="3.7-redo &amp; undo 日志加密"></a>3.7-redo &amp; undo 日志加密</h4><p>增加以下两个参数,用于控制redo、undo日志的加密。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">innodb_redo_log_encrypt</span><br><span class="line">innodb_undo_log_encrypt</span><br></pre></td></tr></table></figure><h3 id="四、优化器增强"><a href="#四、优化器增强" class="headerlink" title="四、优化器增强"></a>四、优化器增强</h3><h4 id="4-1-Cost-Model改进"><a href="#4-1-Cost-Model改进" class="headerlink" title="4.1-Cost Model改进"></a>4.1-Cost Model改进</h4><p>优化器能够感知到页是否存在缓冲池中。5.7其实已经开放接口,但是不对内存中的页进行统计,返回都是1.0.</p><h4 id="4-2-可伸缩的读写负载-Scaling-Read-Write-Workloads"><a href="#4-2-可伸缩的读写负载-Scaling-Read-Write-Workloads" class="headerlink" title="4.2-可伸缩的读写负载 Scaling Read&#x2F;Write Workloads"></a>4.2-可伸缩的读写负载 Scaling Read&#x2F;Write Workloads</h4><p>8.0版本对于读写皆有和高写负载的拿捏恰到好处。在集中的读写均有的负载情况下,我们观测到在4个用户并发的情况下,对于高负载,和5.7版本相比有着两倍性能的提高。在5.7上我们显著了提高了只读情况下的性能,8.0则显著提高了读写负载的可扩展性。为MySQL提升了硬件性能的利用率,其改进是基于重新设计了InnoDB写入Redo日志的方法。对比之前用户线程之前互相争抢着写入其数据变更,在新的Redo日志解决方案中,现在Redo日志由于其写入和刷缓存的操作都有专用的线程来处理。用户线程之间不在持有Redo写入相关的锁,整个Redo处理过程都是时间驱动。</p><p>8.0版本允许马力全开的使用存储设备,比如使用英特尔奥腾闪存盘的时候,我们可以在IO敏感的负载情况下获得1百万的采样 QPS 这里说的IO敏感是指不在IBP中,且必须从二级存储设备中获取 。这个改观是由于我们摆脱了 <code>file_system_mutex</code>全局锁的争用。</p><h4 id="4-3-在高争用-热点数据-负载情况下的更优性能"><a href="#4-3-在高争用-热点数据-负载情况下的更优性能" class="headerlink" title="4.3-在高争用 热点数据 负载情况下的更优性能"></a>4.3-在高争用 热点数据 负载情况下的更优性能</h4><p>Better Performance upon High Contention Loads (“hot rows”)</p><p>8.0版本显著地提升了高争用负载下的性能。高争用负载通常发生在许多事务争用同一行数据的锁,导致了事务等待队列的产生。在实际情景中,负载并不是平稳的,负载可能在特定的时间内爆发 80&#x2F;20法则 。8.0版本针对短时间的爆发负载无论在每秒处理的事务数 换句话,延迟 还是95%延迟上都处理的更好。对于终端用户来说体现在更好的硬件资源利用率 效率 上。因为系统需要尽量使用榨尽硬件性能,才可以提供更高的平均负载。</p><h3 id="五、其他增强"><a href="#五、其他增强" class="headerlink" title="五、其他增强"></a>五、其他增强</h3><h4 id="5-1-支持在线修改全局参数并持久化"><a href="#5-1-支持在线修改全局参数并持久化" class="headerlink" title="5.1-支持在线修改全局参数并持久化"></a>5.1-支持在线修改全局参数并持久化</h4><p>通过加上PERSIST关键字,可以将修改的参数持久化到新的配置文件 mysqld-auto.cnf 中,重启MySQL时,可以从该配置文件获取到最新的配置参数。</p><p>系统会在数据目录下生成mysqld-auto.cnf 文件,该文件内容是以json格式存储的。当my.cnf 和mysqld-auto.cnf 同时存在时,后者优先级更高。</p><p>例如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> PERSIST max_connections <span class="number">1000</span>;</span><br><span class="line"><span class="keyword">SET</span> PERSIST.max_connections <span class="number">1000</span>;</span><br></pre></td></tr></table></figure><p>此 SET 语法使您能够在运行时进行配置更改,这些更改也会在服务器重新启动后持续存在。与 SET GLOBAL 一样,SET PERSIST 设置全局变量运行时值,但也将变量设置写入 mysqld-auto.cnf 文件 如果存在则替换任何现有变量设置 。</p><h4 id="5-2-binlog日志过期时间精确到秒"><a href="#5-2-binlog日志过期时间精确到秒" class="headerlink" title="5.2-binlog日志过期时间精确到秒"></a>5.2-binlog日志过期时间精确到秒</h4><p>之前是天,并且参数名称发生变化. 在8.0版本之前,binlog日志过期时间设置都是设置<code>expire_logs_days</code>参数,而在8.0版本中,MySQL默认使用binlog_expire_logs_seconds参数。</p><h4 id="5-3-undo空间自动回收"><a href="#5-3-undo空间自动回收" class="headerlink" title="5.3-undo空间自动回收"></a>5.3-undo空间自动回收</h4><p>innodb_undo_log_truncate参数在8.0.2版本默认值由OFF变为ON,默认开启undo日志表空间自动回收。</p><p>innodb_undo_tablespaces参数在8.0.2版本默认为2,当一个undo表空间被回收时,还有另外一个提供正常服务。</p><p>innodb_max_undo_log_size参数定义了undo表空间回收的最大值,当undo表空间超过这个值,该表空间被标记为可回收。</p><h4 id="5-4-地理信息系统-GIS"><a href="#5-4-地理信息系统-GIS" class="headerlink" title="5.4-地理信息系统 GIS"></a>5.4-地理信息系统 GIS</h4><p>8.0 版本提供对地形的支持,其中包括了对空间参照系的数据源信息的支持,SRS aware spatial数据类型,空间索引,空间函数。总而言之,8.0版本可以理解地球表面的经纬度信息,而且可以在任意受支持的5000个空间参照系中计算地球上任意两点之间的距离.</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">注意:升级前,一定要验证jdbc驱动是否匹配,是否需要随着升级。</span><br></pre></td></tr></table></figure><h4 id="5-5-参数开关表"><a href="#5-5-参数开关表" class="headerlink" title="5.5-参数开关表"></a>5.5-参数开关表</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> optimizer_switch \G</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> optimizer_switch \G</span><br><span class="line"><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span></span><br><span class="line">optimizer_switch: index_merge <span class="keyword">on</span>,index_merge_union <span class="keyword">on</span>,index_merge_sort_union <span class="keyword">on</span>,index_merge_intersection <span class="keyword">on</span>,engine_condition_pushdown <span class="keyword">on</span>,index_condition_pushdown <span class="keyword">on</span>,mrr <span class="keyword">on</span>,mrr_cost_based <span class="keyword">on</span>,block_nested_loop <span class="keyword">on</span>,batched_key_access off,materialization <span class="keyword">on</span>,semijoin <span class="keyword">on</span>,loosescan <span class="keyword">on</span>,firstmatch <span class="keyword">on</span>,duplicateweedout <span class="keyword">on</span>,subquery_materialization_cost_based <span class="keyword">on</span>,use_index_extensions <span class="keyword">on</span>,condition_fanout_filter <span class="keyword">on</span>,derived_merge <span class="keyword">on</span>,use_invisible_indexes off,skip_scan <span class="keyword">on</span>,hash_join <span class="keyword">on</span>,subquery_to_derived off,prefer_ordering_index <span class="keyword">on</span>,hypergraph_optimizer off,derived_condition_pushdown <span class="keyword">on</span></span><br><span class="line"></span><br><span class="line">session 开关</span><br><span class="line"><span class="keyword">set</span> session optimizer_switch use_invisible_indexes off ;</span><br><span class="line"><span class="keyword">set</span> session optimizer_switch use_invisible_indexes <span class="keyword">on</span> ;</span><br><span class="line"></span><br><span class="line"><span class="keyword">global</span> 开关</span><br><span class="line"><span class="keyword">set</span> <span class="keyword">global</span> optimizer_switch use_invisible_indexes off ;</span><br><span class="line"><span class="keyword">set</span> <span class="keyword">global</span> optimizer_switch use_invisible_indexes <span class="keyword">on</span> ; </span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/13/acdd628e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>深入解析：MySQL半同步复制的配置指南与实践技巧</title>
      <link>https://blog.eucalyptus.cc/2024/09/10/e6cdb30b/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/10/e6cdb30b/</guid>
      <pubDate>Tue, 10 Sep 2024 09:11:05 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;本次配置是在已搭建好主从复制的架构中进行配置&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;配置环境&quot;&gt;&lt;a href=&quot;#配置环境&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>本次配置是在已搭建好主从复制的架构中进行配置</strong></p><h2 id="配置环境"><a href="#配置环境" class="headerlink" title="配置环境"></a>配置环境</h2><table><thead><tr><th>操作系统</th><th>master节点</th><th>slave节点</th></tr></thead><tbody><tr><td>centos7</td><td>8.0.37</td><td>8.0.37</td></tr></tbody></table><h2 id="配置半同步复制"><a href="#配置半同步复制" class="headerlink" title="配置半同步复制"></a>配置半同步复制</h2><h3 id="配置master"><a href="#配置master" class="headerlink" title="配置master"></a>配置master</h3><p>安装master半同步复制插件</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">INSTALL PLUGIN rpl_semi_sync_source SONAME <span class="string">&#x27;semisync_source.so&#x27;</span>;</span><br></pre></td></tr></table></figure><p>在MySQL的配置文件中添加配置</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">rpl_semi_sync_source_enabled <span class="keyword">ON</span></span><br><span class="line">rpl_semi_sync_source_timeout <span class="number">60000</span></span><br><span class="line">rpl_semi_sync_source_trace_level <span class="number">32</span></span><br><span class="line">rpl_semi_sync_source_wait_for_replica_count <span class="number">1</span></span><br><span class="line">rpl_semi_sync_source_wait_no_replica <span class="keyword">ON</span></span><br><span class="line">rpl_semi_sync_source_wait_point AFTER_COMMIT</span><br></pre></td></tr></table></figure><p><strong>重启MySQL服务</strong></p><h3 id="配置slave"><a href="#配置slave" class="headerlink" title="配置slave"></a>配置slave</h3><p>安装slave半同步复制插件</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">INSTALL PLUGIN rpl_semi_sync_replica SONAME <span class="string">&#x27;semisync_replica.so&#x27;</span>;</span><br></pre></td></tr></table></figure><p>在MySQL的配置文件中添加配置</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">rpl_semi_sync_replica_enabled <span class="keyword">ON</span></span><br><span class="line">rpl_semi_sync_replica_trace_level <span class="number">32</span></span><br></pre></td></tr></table></figure><p><strong>重启MySQL服务</strong></p><h2 id="测试验证"><a href="#测试验证" class="headerlink" title="测试验证"></a>测试验证</h2><p>首先在slave上停止MySQL的复制关系</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img1.avif"></p><p>此时在master上执行一条inster语句</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img2.avif"></p><p>新打开个master窗口进行分析,可以看到master上的sql正在等待来自副本的半同步ACK,并且等master上面的sql执行完成后半同步复制会退化为异步复制</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img6.avif"></p><p>最后等master上面的sql执行完成,可以看到这条sql执行60s,与我们设置的超时时间相同</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img3.avif"></p><p>这时去slave上面启动复制关系</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img4.avif"></p><p>最后在新打开的master窗口上可以看到异步复制已经恢复为半同步复制</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img7.avif"></p><p>并且在MySQL的错误日志中也会记录这些信息</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-09-10/img5.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/10/e6cdb30b/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker网络模式详解与应用</title>
      <link>https://blog.eucalyptus.cc/2024/09/06/08fb2af6/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/06/08fb2af6/</guid>
      <pubDate>Fri, 06 Sep 2024 09:34:01 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>Docker作为一个革命性的技术平台，极大地简化了应用程序的部署、管理和扩展过程，其中容器网络是其核心组件之一，对于充分挖掘Docker潜力至关重要。虽然不少开发者和IT专业人员可能已经接触或应用过Docker，但深入理解其网络机制仍然是提升容器化技能的关键步骤。本文旨在提供一个全面而深入的指南，帮助您不仅了解Docker网络的基础，还能掌握其高级特性和最佳实践。</p><h2 id="Docker内置网络"><a href="#Docker内置网络" class="headerlink" title="Docker内置网络"></a>Docker内置网络</h2><p>当我们完成docker engine的安装以后，docker会在每一个engine上面生成一个3种网络，他们是：<code>bridge</code>, <code>none</code>还有<code>host</code>。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img1.avif" alt="img1"></p><h3 id="bridge"><a href="#bridge" class="headerlink" title="bridge"></a>bridge</h3><h4 id="基本概念"><a href="#基本概念" class="headerlink" title="基本概念"></a>基本概念</h4><p>当Docker进程启动时，会在主机上创建一个名为docker0的虚拟网桥，此主机上启动的Docker容器会连接到这个虚拟网桥上。虚拟网桥的工作方式和物理交换机类似，这样主机上的所有容器就通过交换机连在了一个二层网络中。</p><p>如下图所示，当Docker1需要访问外网时，请求先到达Docker0虚拟网卡，然后在到达物理网卡，请求就发送出去了。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img2.avif" alt="img2"></p><h4 id="案例"><a href="#案例" class="headerlink" title="案例"></a>案例</h4><p>（1）客户端执行”docker run”命令创建并启动容器。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img3.avif" alt="img3"></p><p>查看容器信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker inspect nginx</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img4.avif" alt="img4"></p><p>（2）Docker引擎创建一对虚拟接口veth pair;并把它们分别放到宿主机和新容器的网络命名空间中。</p><p>（3）Docker引擎将宿主机上的veth接口连接到宿主机的docker0网桥上，并且给它分配一个以”veth”开头的名字，如veth8ead84e@if117。</p><p>（4）Docker引擎将容器上的veth接口改名为”eth0”，并且该接口只有在容器内网络命名空间中是可见的。</p><p>（5）Docker引擎从宿主机的docker0网桥上分配一个空闲的ip地址给容器内的eth0，例如：172.17.0.2。并将容器内eth0的路由网关设置为docker0的内部IP地址，例如：172.17.0.1。完成以上的这些步骤后，容器就可以使用其内部的虚拟接口”eth0”来连接到其他的容器和访问外部的网络了。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img5.avif" alt="img5"></p><p>由于上面启动nginx容器的时候使用的是默认的bridge网络，并且也没有添加端口映射，所以iptables不会做DNAT规则</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img6.avif" alt="img6"></p><p>如果启动容器的时候做了端口映射，则iptables会做DNAT规则，实现端口转发功能，可以使用iptables -t nat -nL查看</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img7.avif" alt="img7"></p><h4 id="工作原理"><a href="#工作原理" class="headerlink" title="工作原理"></a>工作原理</h4><p>在 Docker 中启动容器时，如果没有指定网络模式，它默认连接到 Docker 主机上的一个桥接网络。这个桥接网络起初是空的，当容器连接到它时，Docker 会为每个容器分配一个 IP 地址和一个网络接口，并将这个接口连接到虚拟桥接上。</p><p>Docker 的桥接网络通常使用 NAT（网络地址转换）来连接到物理网络，使得容器能够通过宿主机的 IP 地址访问外部网络。</p><h4 id="使用场景"><a href="#使用场景" class="headerlink" title="使用场景"></a>使用场景</h4><ul><li><strong>隔离容器网络环境</strong>：当你希望运行的每个容器都有独立的网络堆栈时，Bridge网络非常有用。每个使用Bridge网络的容器都会获得自己的IP地址，并且容器之间的网络通信需要通过端口映射来进行，这提供了基本的网络隔离。</li><li><strong>快速部署和测试</strong>：在开发和测试环境中，Bridge网络可以让开发者快速搭建一个与外部网络隔离的环境来部署和测试应用，而不会影响到主机或其他网络环境。</li><li><strong>服务发现</strong>：虽然基础的Bridge网络不直接支持服务发现，但通过结合DNS解析（如使用docker-compose或Kubernetes中的服务发现机制）可以在一定程度上实现容器间的服务发现和通信。</li><li><strong>端口映射</strong>：当需要从宿主机或其他网络访问容器内的服务时，可以使用Bridge网络并通过端口映射功能将容器的内部端口映射到宿主机的一个端口上，便于外部访问。</li><li><strong>多主机通信需求不高场景</strong>：对于一些简单的多容器应用，如果不需要跨主机的容器网络通信，或者可以通过其他手段（如使用外部负载均衡器）来实现跨主机通信，使用Bridge网络就足够了。</li><li><strong>轻量级解决方案</strong>：相比于更复杂的网络解决方案如overlay网络（用于跨多个Docker主机的容器通信）或macvlan网络，Bridge网络更简单、轻量，适合对网络需求不复杂的场景。</li></ul><h3 id="host"><a href="#host" class="headerlink" title="host"></a>host</h3><h4 id="基本概念-1"><a href="#基本概念-1" class="headerlink" title="基本概念"></a>基本概念</h4><p>host 模式：使用 –net&#x3D;host 指定</p><p>相当于VMware 中的桥接模式，与宿主机在同一个网络中，但是没有独立IP地址</p><p>Docker 使用了Linux 的Namespace 技术来进行资源隔离，如PID Namespace隔离进程，Mount Namespace隔离文件系统，Network Namespace 隔离网络等。一个Network Namespace 提供了一份独立的网络环境，包括网卡，路由，iptable 规则等都与其他Network Namespace 隔离。一个Docker 容器一般会分配一个独立的Network Namespace</p><p>但是如果启动容器的时候使用host 模式，那么这个容器将不会获得一个独立的Network Namespace，而是和宿主机共用一个Network Namespace。容器将不会虚拟出自己的网卡，配置自己的IP等，而是使用宿主机的IP和端口范围。此时容器不再拥有隔离的、独立的网络栈。不拥有所有端口资源</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img8.avif" alt="img8"></p><h4 id="案例-1"><a href="#案例-1" class="headerlink" title="案例"></a>案例</h4><p>我们拉起一个host网络的centos容器，查看容器信息，如下图所示，并没有发现IP信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --net=host --name centos7 eeb6ee3f44bd</span><br><span class="line"></span><br><span class="line">docker inspect centos7</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img9.avif" alt="img9"></p><p>我们可以进入容器内部去查看下网络信息，通过下图发现，host网络模式下的容器的IP和宿主机IP一致</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 进入容器</span></span><br><span class="line">docker <span class="built_in">exec</span> -it centos7 bash</span><br><span class="line"></span><br><span class="line"><span class="comment"># 安装网络工具</span></span><br><span class="line">yum install net-tools -y</span><br><span class="line"></span><br><span class="line"><span class="comment"># 查看IP</span></span><br><span class="line">ifconfig</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img10.avif" alt="img10"></p><h4 id="工作原理-1"><a href="#工作原理-1" class="headerlink" title="工作原理"></a>工作原理</h4><p>主机网络模式下，容器将不会获得独立的 IP 地址。容器的网络堆栈将直接映射到宿主机上，容器内的网络服务可以直接绑定到宿主机的 IP 地址和端口上。这种模式通常用于需要进行大量网络操作或需要提供高性能网络服务的场景。</p><h4 id="使用场景-1"><a href="#使用场景-1" class="headerlink" title="使用场景"></a>使用场景</h4><ul><li><strong>性能敏感型应用</strong>：当容器化应用需要最大化网络性能时，使用主机网络是一个好选择。因为它消除了网络虚拟化带来的额外开销。</li><li><strong>端口冲突</strong>：在主机网络模式下，容器可以直接使用宿主机的端口，避免了端口映射可能带来的端口冲突问题。</li><li><strong>网络监控和管理</strong>：对于需要进行网络监控和管理的工具，主机网络模式能够提供更广泛的网络可视性和控制能力。</li></ul><h3 id="none"><a href="#none" class="headerlink" title="none"></a>none</h3><h4 id="基本概念-2"><a href="#基本概念-2" class="headerlink" title="基本概念"></a>基本概念</h4><p>使用none模式，Docker容器拥有自己的Network Namespace，但是，并不为Docker容器进行任何网络配置。也就是说，这个Docker容器没有网卡、IP、路由等信息。需要我们自己为Docker容器添加网卡、配置IP等。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img11.avif" alt="img11"></p><h4 id="案例-2"><a href="#案例-2" class="headerlink" title="案例"></a>案例</h4><p>启动一个none网络的centos7的容器，查容器信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --name centos7 --net=none eeb6ee3f44bd</span><br><span class="line"></span><br><span class="line">docker inspect centos7</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img12.avif" alt="img12"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img13.avif" alt="img13"></p><p>进入容器查看网络信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 进入容器</span></span><br><span class="line">docker <span class="built_in">exec</span> -it centos7 bash</span><br><span class="line"></span><br><span class="line"><span class="comment"># 安装网络工具</span></span><br><span class="line">yum install net-tools -y</span><br><span class="line"></span><br><span class="line"><span class="comment"># 查看IP</span></span><br><span class="line">ifconfig</span><br></pre></td></tr></table></figure><h4 id="！！！大佬救命"><a href="#！！！大佬救命" class="headerlink" title="！！！大佬救命"></a>！！！大佬救命</h4><p>这里可能处于none网络的原因，导致上面安装网络工具的时候失败</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 安装网络工具</span></span><br><span class="line">yum install net-tools -y</span><br></pre></td></tr></table></figure><p>执行日志：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br></pre></td><td class="code"><pre><span class="line">Loaded plugins: fastestmirror, ovl</span><br><span class="line">Loading mirror speeds from cached hostfile</span><br><span class="line">http://mirrors.cloud.aliyuncs.com/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - &quot;Could not resolve host: mirrors.cloud.aliyuncs.com; Unknown error&quot;</span><br><span class="line">Trying other mirror.</span><br><span class="line">One of the configured repositories failed (CentOS-7),</span><br><span class="line">and yum doesn&#x27;t have enough cached data to continue. At this point the only</span><br><span class="line">safe thing yum can do is fail. There are a few ways to work &quot;fix&quot; this:</span><br><span class="line"></span><br><span class="line">1. Contact the upstream for the repository and get them to fix the problem.</span><br><span class="line"></span><br><span class="line">2. Reconfigure the baseurl/etc. for the repository, to point to a working</span><br><span class="line">upstream. This is most often useful if you are using a newer</span><br><span class="line">distribution release than is supported by the repository (and</span><br><span class="line">the packages for the previous distribution release still work).</span><br><span class="line"></span><br><span class="line">3. Run the command with the repository temporarily disabled</span><br><span class="line">yum --disablerepo=base ...</span><br><span class="line"></span><br><span class="line">4. Disable the repository permanently, so yum won&#x27;t use it by default. Yum</span><br><span class="line">will then just ignore the repository until you permanently enable it</span><br><span class="line">again or use --enablerepo for temporary usage:</span><br><span class="line">yum-config-manager --disable base</span><br><span class="line">or</span><br><span class="line">subscription-manager repos --disable=base</span><br><span class="line"></span><br><span class="line">5. Configure the failing repository to be skipped, if it is unavailable.</span><br><span class="line">Note that yum will try to contact the repo. when it runs most commands,</span><br><span class="line">so will have to try and fail each time (and thus. yum will be be much</span><br><span class="line">slower). If it is a very temporary problem though, this is often a nice</span><br><span class="line">compromise:</span><br><span class="line">yum-config-manager --save --setopt=base.skip_if_unavailable=true</span><br><span class="line"></span><br><span class="line">failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.</span><br><span class="line">http://mirrors.cloud.aliyuncs.com/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - &quot;Could not resolve host: mirrors.cloud.aliyuncs.com; Unknown error&quot;</span><br></pre></td></tr></table></figure><h3 id="container"><a href="#container" class="headerlink" title="container"></a>container</h3><h4 id="基本概念-3"><a href="#基本概念-3" class="headerlink" title="基本概念"></a>基本概念</h4><p>这个模式指定新创建的容器和已经存在的一个容器共享一个 Network Namespace，而不是和宿主机共享。新创建的容器不会创建自己的网卡，配置自己的 IP，而是和一个指定的容器共享 IP、端口范围等。同样，两个容器除了网络方面，其他的如文件系统、进程列表等还是隔离的。因此，在这种模式下，容器之间可以通过 localhost 或者 127.0.0.1 进行相互间的访问，从而提高了传输的效率。</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img14.avif" alt="img14"></p><h4 id="案例-3"><a href="#案例-3" class="headerlink" title="案例"></a>案例</h4><p>（1）首先创建个基础容器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --name centos7.A eeb6ee3f44bd</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img15.avif" alt="img15"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img16.avif" alt="img16"></p><p>（2）然后基于刚才的容器创建新的容器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --net=container:04dcd560b6ce --name centos7.B eeb6ee3f44bd</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img17.avif" alt="img17"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img18.avif" alt="img18"></p><p>（3）对比上面创建的两个容器centos7.A和centos7.B发现使用了相同的网络命名空间，这是因为在创建容器B时使用了container模式，使得容器B不再创建自己的网络命名空间，而直接使用容器A的网络命名空间。</p><h2 id="自定义网络"><a href="#自定义网络" class="headerlink" title="自定义网络"></a>自定义网络</h2><p>上面介绍的3种自带的网络模式有各自的局限性，因此，docker推荐大家自定义网络。通过自定义网络，我们可以实现”服务发现”与”DNS解析”。</p><p>docker 允许我们创建3种类型的自定义网络，<code>bridge</code>，<code>overlay</code>，<code>MACVLAN</code></p><ol><li><code>bridge</code>：Bridge模式是Docker默认的网络模式，当Docker进程启动时，会在主机上创建一个名为docker0的虚拟网桥，用来连接宿主机和容器，此主机上的Docker容器都会连接到这个虚拟网桥上</li><li><code>overlay</code>：当有多个docker主机时，跨主机的container通信</li><li><code>macvlan</code>：每个container都有一个虚拟的MAC地址</li></ol><h3 id="bridge-1"><a href="#bridge-1" class="headerlink" title="bridge"></a>bridge</h3><h4 id="基本概念-4"><a href="#基本概念-4" class="headerlink" title="基本概念"></a>基本概念</h4><p>虽然Docker提供的默认bridge网络能满足很多基本需求，但在某些场景下，你可能需要创建自定义的bridge网络以实现更灵活的网络配置，比如指定子网、IP范围、网桥名称等。</p><p>自定义bridge网络为Docker容器提供了更灵活和可控的网络配置方式，它不仅能够帮助用户更好地组织和隔离容器网络，还支持更复杂的网络架构设计，满足不同应用场景的需求。通过精细的网络配置，可以有效地提升容器化应用的部署效率和管理便利性。</p><h4 id="案例-4"><a href="#案例-4" class="headerlink" title="案例"></a>案例</h4><p>首先创建一个网络（这里创建的时候没有指定子网网段）</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network create -d bridge test_bridge</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img19.avif" alt="img19"></p><p>看下内置网络bridge和我们创建的test_bridge网络有什么区别</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">docker inspect test_bridge</span><br><span class="line"></span><br><span class="line">docker inspect bridge</span><br></pre></td></tr></table></figure><p>自定义test_bridge网络</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img20.avif" alt="img20"></p><p>内置网络bridge</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img21.avif" alt="内置网络bridge"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img22.avif" alt="内置网络bridge2"></p><p>基于自定义网络test_bridge创建一个容器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --name centos7.test --net=test_bridge eeb6ee3f44bd</span><br></pre></td></tr></table></figure><p>进入容器查看网络信息，会发现分配的ip在172.18.0.0&#x2F;16网段中</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img23.avif" alt="容器网络信息"></p><h4 id="Docker网络允许您将容器附加到任意数量的网络"><a href="#Docker网络允许您将容器附加到任意数量的网络" class="headerlink" title="Docker网络允许您将容器附加到任意数量的网络"></a>Docker网络允许您将容器附加到任意数量的网络</h4><p>将我们之前创建的centos7.A容器加入到test_bridge网络中，先看下centos7.A容器最初的网络信息</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img24.avif" alt="centos7.A初始网络"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network connect test_bridge centos7.A</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img25.avif" alt="连接后网络"></p><p>断开centos7.A容器和test_bridge网络的连接</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network disconnect test_bridge centos7.A</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-06/img26.avif" alt="断开连接后"></p><h4 id="使用方法"><a href="#使用方法" class="headerlink" title="使用方法"></a>使用方法</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">docker network create --driver bridge --subnet=172.18.0.0/16 my-bridge-network</span><br><span class="line"></span><br><span class="line"><span class="comment"># --driver bridge 指定了网络类型为bridge。</span></span><br><span class="line"><span class="comment"># --subnet=172.18.0.0/16 指定了网络的子网和CIDR，你可以根据需要选择合适的子网。</span></span><br><span class="line"><span class="comment"># my-bridge-network 是自定义网络的名称。</span></span><br></pre></td></tr></table></figure><hr><h3 id="overlay"><a href="#overlay" class="headerlink" title="overlay"></a>overlay</h3><h4 id="基本概念-5"><a href="#基本概念-5" class="headerlink" title="基本概念"></a>基本概念</h4><p>覆盖网络（Overlay Network）是 Docker 的一个高级网络类型，主要用于 Docker Swarm 集群环境中。它允许不同 Docker 主机上的容器相互通信，无论它们的物理位置如何。覆盖网络通过在宿主机之间创建一个虚拟网络层，来连接分布在不同节点上的容器。</p><h4 id="工作原理-2"><a href="#工作原理-2" class="headerlink" title="工作原理"></a>工作原理</h4><p>覆盖网络使用网络驱动（如 VXLAN）在宿主机之间建立一个虚拟网络。这个网络工作在现有的物理网络之上，容器之间的通信会被封装并通过这个虚拟网络传输。当数据包到达目的地后，它会被解封装并传递给目标容器。这种方式使得容器间能够透明地通信，就像它们在同一个网络中一样。</p><h4 id="使用场景-2"><a href="#使用场景-2" class="headerlink" title="使用场景"></a>使用场景</h4><ul><li><strong>多主机容器部署</strong>：当你需要在多个 Docker 主机上部署容器，并且这些容器需要相互通信时，覆盖网络是理想的选择。</li><li><strong>Docker Swarm 集群</strong>：在 Docker Swarm 环境中，覆盖网络允许不同节点上的服务实例之间进行通信，非常适合微服务架构。</li><li><strong>跨主机负载均衡</strong>：覆盖网络支持跨多个宿主机的负载均衡，使得服务可以更加灵活地扩展和管理。</li></ul><h4 id="使用方法-1"><a href="#使用方法-1" class="headerlink" title="使用方法"></a>使用方法</h4><p>要在 Docker Swarm 环境中创建一个覆盖网络，首先确保你的 Docker 环境已经初始化为 Swarm 模式，然后使用以下命令创建覆盖网络：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network create -d overlay my_overlay_network</span><br></pre></td></tr></table></figure><p>创建了覆盖网络后，你可以在部署服务时指定使用这个网络：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker service create --name my_service --network my_overlay_network my_image</span><br></pre></td></tr></table></figure><h4 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h4><ul><li><strong>网络性能</strong>：由于覆盖网络中存在数据封装和解封装的过程，可能会对网络性能造成一定影响。</li><li><strong>安全性</strong>：Docker 提供了网络加密选项来保护覆盖网络中的数据传输。</li><li><strong>网络管理</strong>：管理覆盖网络可能需要对 Docker Swarm 集群的管理和网络原理有一定的了解。</li></ul><hr><h3 id="macvlan"><a href="#macvlan" class="headerlink" title="macvlan"></a>macvlan</h3><h4 id="基本概念-6"><a href="#基本概念-6" class="headerlink" title="基本概念"></a>基本概念</h4><p>Macvlan 网络是 Docker 提供的另一种网络类型，允许容器直接连接到物理网络。每个使用 Macvlan 网络的容器都会被分配一个独立的 MAC 地址，使其在网络上表现得就像是一个物理设备一样。这种网络类型适用于需要容器直接参与物理网络的场景，例如，当容器需要有自己的 IP 地址、或需要绕过 Docker 网络堆栈的复杂性时。</p><h4 id="工作原理-3"><a href="#工作原理-3" class="headerlink" title="工作原理"></a>工作原理</h4><p>Macvlan 网络通过创建一个或多个虚拟网络接口（Macvlan 接口）来工作，这些接口附加到宿主机的物理网络接口上。每个接口都有自己的 MAC 地址，容器通过这些虚拟接口与外部网络进行通信。这样，容器可以直接出现在物理网络上，而不是通过 Docker 主机的网络堆栈。</p><h4 id="使用场景-3"><a href="#使用场景-3" class="headerlink" title="使用场景"></a>使用场景</h4><ul><li><strong>需要直接网络访问</strong>：对于需要绕过 NAT、或需要与外部网络中的其他设备直接通信的容器，Macvlan 网络是一个理想的选择。</li><li><strong>遗留系统集成</strong>：在一些遗留系统或需要直接网络访问的环境中，Macvlan 网络可以帮助容器更好地集成进这些环境中。</li><li><strong>网络性能</strong>：由于容器直接连接到物理网络，Macvlan 可以提供更好的网络性能，减少虚拟化带来的开销。</li></ul><h4 id="使用方法-2"><a href="#使用方法-2" class="headerlink" title="使用方法"></a>使用方法</h4><p>创建 Macvlan 网络的基本步骤如下：</p><ul><li><strong>创建 Macvlan 网络</strong>：</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network create -d macvlan --subnet=192.168.1.0/24 --gateway=192.168.1.1 -o parent=eth0 my_macvlan_net</span><br></pre></td></tr></table></figure><p>这个命令会在宿主机的 <code>eth0</code> 网络接口上创建一个新的 Macvlan 网络，设置了子网和网关。</p><ul><li><strong>运行容器并连接到 Macvlan 网络</strong>：</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run --network my_macvlan_net --name my_container my_image</span><br></pre></td></tr></table></figure><p>这个命令启动一个容器，并将其连接到刚刚创建的 Macvlan 网络。</p><h4 id="注意事项-1"><a href="#注意事项-1" class="headerlink" title="注意事项"></a>注意事项</h4><ul><li><strong>网络隔离</strong>：使用 Macvlan 网络时，容器的网络隔离级别较低，容器直接暴露在物理网络上</li><li><strong>路由和防火墙配置</strong>：可能需要在网络设备或宿主机上进行额外的路由和防火墙配置，以确保网络通信的正确性和安全性。</li><li><strong>宿主机通信</strong>：默认情况下，使用 Macvlan 的容器可能无法与其宿主机进行直接通信。这可能需要额外的网络配置来解决。</li></ul><hr><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><p>Docker 网络是容器化技术中不可或缺的一部分，它不仅提供了容器之间以及容器与外部世界之间通信的能力，还支持了高度的网络隔离和安全性。通过不同的网络类型和配置，Docker 能够满足各种应用场景的需求，从简单的单机部署到复杂的多主机、跨主机的集群环境。</p><p>bridge网络作为默认的网络类型，适用于大多数标准部署场景，提供了容器与外部网络的连接以及容器之间的隔离。host网络模式提供了最高的网络性能，适用于性能敏感型应用。overlay网络支持跨主机的容器通信，是在 Docker Swarm 集群中运行分布式应用的理想选择。Macvlan 网络则允许容器直接连接到物理网络，适用于需要直接网络访问或遗留系统集成的场景。</p><p>每种网络类型都有其适用场景和注意事项。选择合适的网络类型和配置，可以帮助开发者和运维人员构建高效、安全且易于管理的容器化应用。同时，Docker 的网络配置和管理工具也提供了灵活性和便利性，使得网络管理变得更加简单。</p><p>Docker 网络提供了强大而灵活的网络功能，支持各种应用部署和运行模式。通过合理选择和配置网络类型，可以最大化地发挥 Docker 容器的潜力，构建出高性能、安全且易于管理的容器化应用。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/06/08fb2af6/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>解决MySQL容器启动后无法编辑文件的问题：实用指南</title>
      <link>https://blog.eucalyptus.cc/2024/09/04/43948a6a/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/04/43948a6a/</guid>
      <pubDate>Wed, 04 Sep 2024 08:45:47 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;前段时间拉取了个MySQL的容器节点，但是拉起之后发现居然编辑不了MySQL的配置文件，这是我的启动命令&lt;/p&gt;
&lt;figure class=&quot;highlight bash&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>前段时间拉取了个MySQL的容器节点，但是拉起之后发现居然编辑不了MySQL的配置文件，这是我的启动命令</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd -p 3310:3306 -e MYSQL_ROOT_PASSWORD=12345678 --name slave2 f5f171121fa3 bash</span><br></pre></td></tr></table></figure><p><strong>下面总结下解决方法：</strong></p><ol><li>编辑docker file直接从根本上解决问题（还没试过）</li><li>安装需要命令的rpm包（不推荐，依赖特别多）</li><li>将需要编辑的文件在宿主机上编辑，然后再传到容器中（不推荐，特麻烦）</li><li>直接宿主机的挂载目录中编辑对应的容器文件（还行，比较容易）</li><li>我还有个想法，俗话所一切皆文件，直接将需要命令的相关文件从宿主机copy到容器中即可（还没试过）</li></ol><p>当然上面的方法比较另辟迄今，当我们遇到没有一个命令时首先想到的应该是安装，但是有的小伙伴也可能又和我遇到了同样的问题，比如，一顿操作猛如虎….</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-04/img1.avif" alt="img1"></p><p>首先启动一个容器后看下启动容器的os信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> /etc/os-release</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-04/img2.avif" alt="img2"></p><p>可以看到这个MySQL是oracle封装的你使用其他os命令肯定不行，但是我们可能对oracle linux server的命令不是很熟悉，那么该怎么办呢，下面介绍一个比yum,dnf还要轻量级的软件包管理器—microdnf</p><p><code>microdnf</code> 是一个轻量级的包管理器，它是 DNF 的一个分支，专为使用在容器环境和嵌入式系统中而设计。由于容器和嵌入式系统通常有资源限制，包括有限的磁盘空间和内存，<code>microdnf</code> 被优化以减少其内存占用和执行速度。</p><p>以下是 <code>microdnf</code> 的一些关键特点：</p><ul><li><strong>轻量化</strong>：<code>microdnf</code> 旨在减少内存和磁盘的使用，使其适合在资源受限的环境中运行。</li><li><strong>兼容性</strong>：它与 DNF 高度兼容，支持大部分 DNF 命令和功能，但去掉了一些在容器中不必要的功能。</li><li><strong>简单性</strong>：<code>microdnf</code> 提供了一个简单的方法来安装、更新和删除软件包。</li><li><strong>依赖管理</strong>：尽管是轻量级，<code>microdnf</code> 仍然处理依赖关系，确保安装的软件包所依赖的包也得到安装。</li><li><strong>配置文件</strong>：<code>microdnf</code> 使用 <code>/etc/microdnf.conf</code> 或 <code>/etc/dnf/microdnf.conf</code> 作为其主要配置文件。</li><li><strong>仓库管理</strong>：它支持配置软件仓库（repositories），允许用户添加、移除或修改仓库的配置。</li><li><strong>包管理操作</strong>：<code>microdnf</code> 支持基本的包管理操作，如安装、更新、查询和删除软件包。</li><li><strong>静默操作</strong>：它支持静默模式，可以在不提示用户输入的情况下自动执行操作。</li><li><strong>安全性</strong>：<code>microdnf</code> 可以配置为自动更新安全相关的包，帮助维护容器的安全性。</li><li><strong>使用场景</strong>：它适用于容器化应用、嵌入式系统和任何需要轻量级包管理器的场景。</li><li><strong>与 DNF 的区别</strong>：<code>microdnf</code> 没有 DNF 的所有特性，比如管理插件、复杂的仓库元数据处理等。</li></ul><p><strong>命令示例</strong>：</p><ul><li>安装包：<code>microdnf install &lt;package_name&gt;</code></li><li>更新包：<code>microdnf update &lt;package_name&gt;</code></li><li>查询包：<code>microdnf info &lt;package_name&gt;</code></li><li>删除包：<code>microdnf remove &lt;package_name&gt;</code></li><li>列出已安装包：<code>microdnf list --installed</code></li></ul><p><code>microdnf</code> 是一个实用的工具，尤其适用于需要轻量级包管理的场合。然而，它可能不适合那些需要 DNF 所有高级功能的环境。在使用 <code>microdnf</code> 时，您应该根据您的具体需求和环境来评估其适用性。</p><p>用microdnf安装vim</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">microdnf -y install vim</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-04/img3.avif" alt="img3"></p><p><strong>学识浅薄，疏漏难免，祈望高贤不吝赐教。</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/04/43948a6a/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>搭建与配置私有Docker镜像仓库实战指南</title>
      <link>https://blog.eucalyptus.cc/2024/09/03/6ddf08fb/</link>
      <guid>https://blog.eucalyptus.cc/2024/09/03/6ddf08fb/</guid>
      <pubDate>Tue, 03 Sep 2024 08:14:03 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>在当今快速迭代的软件开发环境中，Docker已成为容器化应用部署的事实标准，极大地提升了应用的可移植性、一致性和开发效率。随着企业级应用对容器技术依赖的日益加深，私有Docker镜像仓库的重要性愈发凸显。它不仅关乎于镜像的安全存储与高效分发，更是实现团队间高效协作与持续集成&#x2F;持续部署（CI&#x2F;CD）流程的关键一环。</p><p>然而，对于许多开发者和IT管理人员而言，搭建并配置一个稳定、高效且安全的私有Docker镜像仓库仍是一项挑战。从环境准备到服务部署，从访问控制到镜像备份，每一步都需谨慎规划与实施，以确保满足企业的特定需求和合规要求。</p><p>《搭建与配置私有Docker镜像仓库实战指南》正是为解决这一需求而生。本文旨在通过详实的步骤说明与实战案例，引导读者从零开始，深入理解私有Docker镜像仓库的核心概念，掌握Harbor、Nexus等主流私有仓库软件的安装、配置与管理技巧。我们不仅会探讨基本的部署策略，还会涉及高级功能如镜像签名、复制策略、性能优化及安全实践，确保您的私有仓库能够稳健运行，为团队带来最大化的效益。</p><p>无论您是刚刚接触容器技术的新手，还是寻求提升现有基础设施效能的资深工程师，本指南都将为您提供宝贵的参考与启示。让我们一同开启构建高效、安全私有Docker镜像仓库的旅程，为您的DevOps实践增添强大动力。</p><p><strong>关于镜像加速器的配置在之前的文章中已经介绍过了</strong></p><p><a href="https://blog.csdn.net/weixin_72610956/article/details/131507884">https://blog.csdn.net/weixin_72610956/article/details/131507884</a></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-03/img1.avif" alt="img1"></p><p><strong>当然阿里云官方文档中的这个加速器好像没有什么diao用</strong> ，<a href="https://cr.console.aliyun.com/cn-hangzhou/instances/mirrors">容器镜像服务 (aliyun.com)</a></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-03/img2.avif" alt="img2"></p><p><strong>推荐配置：</strong></p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">   <span class="attr">&quot;registry-mirrors&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span></span><br><span class="line">  <span class="string">&quot;https://docker.m.daocloud.io&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://dockerproxy.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.mirrors.ustc.edu.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.nju.edu.cn&quot;</span></span><br><span class="line"> <span class="punctuation">]</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p><strong>最后记得重启容器哦</strong></p><h2 id="关于镜像仓库配置首先你要知道"><a href="#关于镜像仓库配置首先你要知道" class="headerlink" title="关于镜像仓库配置首先你要知道"></a>关于镜像仓库配置首先你要知道</h2><p>在Linux中安装Docker后，默认配置的镜像仓库是Docker Hub。Docker Hub是一个公开的注册服务器，其中包含了大量的官方镜像以及用户贡献的镜像。当你在Docker中运行如<code>docker pull ubuntu</code>这样的命令时，如果没有指定其他仓库地址，Docker会默认从Docker Hub下载镜像。</p><p><strong>其次如果你没有配置镜像仓库，那么如果需要去指定的镜像仓库拉去或推送镜像，则每次推送或拉取镜像时都需要认证，就像阿里云中的介绍，是比较麻烦，</strong> <a href="https://cr.console.aliyun.com/repository/cn-hangzhou/pikaqiu-hub/pikaqiu/details">https://cr.console.aliyun.com/repository/cn-hangzhou/pikaqiu-hub/pikaqiu/details</a></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-03/img3.avif" alt="img3"></p><p><strong>为了避免每次推送或拉取镜像时都需要认证，可以配置镜像仓库凭据</strong></p><p>首先介绍两个文件</p><h3 id="root-docker-config-json"><a href="#root-docker-config-json" class="headerlink" title="&#x2F;root&#x2F;.docker&#x2F;config.json"></a>&#x2F;root&#x2F;.docker&#x2F;config.json</h3><p><code>/root/.docker/config.json</code> 是一个位于Linux系统根用户目录<code>.docker</code>隐藏文件夹中的JSON格式配置文件。它主要用于存储Docker客户端的认证信息，比如 Docker Hub 或其他私有 registry 的用户名、密码（经过加密处理）以及访问令牌等认证凭据。此外，该文件还可以包含Docker CLI的默认配置，比如proxies设置。当用户通过Docker命令行与Docker daemon交互，进行镜像拉取、推送等操作时，Docker客户端会自动引用此文件中的认证信息，以实现权限验证和管理。</p><h3 id="etc-docker-daemon-json"><a href="#etc-docker-daemon-json" class="headerlink" title="&#x2F;etc&#x2F;docker&#x2F;daemon.json"></a>&#x2F;etc&#x2F;docker&#x2F;daemon.json</h3><p><code>daemon.json</code>是Docker守护进程的配置文件，它允许系统管理员自定义Docker守护程序的行为。此文件通常位于<code>/etc/docker/</code>目录下。通过修改<code>daemon.json</code>，可以调整Docker守护进程的多种设置，包括网络配置、日志记录、存储驱动等。</p><p><strong>下面是<code>daemon.json</code>文件的简单配置</strong></p><p><code>推荐文章：</code>Docker配置文件daemon.json介绍及优化-CSDN博客</p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">  <span class="attr">&quot;debug&quot;</span><span class="punctuation">:</span> <span class="literal"><span class="keyword">true</span></span><span class="punctuation">,</span> <span class="comment">// 启用 Docker 守护进程的调试日志</span></span><br><span class="line">  <span class="attr">&quot;registry-mirrors&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span> <span class="comment">// 设置 Docker 镜像仓库的镜像源，加速拉取镜像</span></span><br><span class="line">    <span class="string">&quot;https://your.mirror.address&quot;</span></span><br><span class="line"> <span class="punctuation">]</span><span class="punctuation">,</span></span><br><span class="line">  <span class="attr">&quot;live-restore&quot;</span><span class="punctuation">:</span> <span class="literal"><span class="keyword">true</span></span><span class="punctuation">,</span> <span class="comment">// 当 Docker 守护进程重启时，保持正在运行的容器不被停止</span></span><br><span class="line">  <span class="attr">&quot;insecure-registries&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span> <span class="comment">// 添加不受信任的私有 Docker 注册表</span></span><br><span class="line">    <span class="string">&quot;myinsecueregistry:5000&quot;</span></span><br><span class="line"> <span class="punctuation">]</span><span class="punctuation">,</span></span><br><span class="line">  <span class="attr">&quot;max-concurrent-downloads&quot;</span><span class="punctuation">:</span> <span class="number">5</span><span class="punctuation">,</span> <span class="comment">// 最大并发下载数量</span></span><br><span class="line">  <span class="attr">&quot;iptables&quot;</span><span class="punctuation">:</span> <span class="literal"><span class="keyword">false</span></span><span class="punctuation">,</span> <span class="comment">// 禁用 Docker 自动管理 iptables 规则</span></span><br><span class="line">  <span class="attr">&quot;log-driver&quot;</span><span class="punctuation">:</span> <span class="string">&quot;json-file&quot;</span><span class="punctuation">,</span> <span class="comment">// 设置日志驱动，默认为 json-file，也可以是 syslog、journald 等</span></span><br><span class="line">  <span class="attr">&quot;log-opts&quot;</span><span class="punctuation">:</span> <span class="punctuation">&#123;</span> <span class="comment">// 日志驱动的额外选项</span></span><br><span class="line">    <span class="attr">&quot;max-size&quot;</span><span class="punctuation">:</span> <span class="string">&quot;100m&quot;</span><span class="punctuation">,</span></span><br><span class="line">    <span class="attr">&quot;max-file&quot;</span><span class="punctuation">:</span> <span class="string">&quot;3&quot;</span></span><br><span class="line"> <span class="punctuation">&#125;</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p><strong>下面是&#x2F;root&#x2F;.docker&#x2F;config.json文件的简单（<code>镜像仓库</code>）配置</strong></p><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">        <span class="attr">&quot;auths&quot;</span><span class="punctuation">:</span> <span class="punctuation">&#123;</span></span><br><span class="line">                <span class="attr">&quot;registry.cn-hangzhou.aliyuncs.com&quot;</span><span class="punctuation">:</span> <span class="punctuation">&#123;</span></span><br><span class="line">                        <span class="attr">&quot;auth&quot;</span><span class="punctuation">:</span> <span class="string">&quot;加密后的密码&quot;</span></span><br><span class="line"> <span class="punctuation">&#125;</span></span><br><span class="line"> <span class="punctuation">&#125;</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-09-03/img4.avif" alt="img4"></p><p><strong>最后修改配置后记得重启容器</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl daemon-reload</span><br><span class="line"><span class="built_in">sudo</span> systemctl restart docker</span><br></pre></td></tr></table></figure><p><strong>学识浅薄，疏漏难免，祈望高贤不吝赐教。</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/09/03/6ddf08fb/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>WordPress纯代码实现圆角彩色背景标签云</title>
      <link>https://blog.eucalyptus.cc/2024/08/20/3cb43b93/</link>
      <guid>https://blog.eucalyptus.cc/2024/08/20/3cb43b93/</guid>
      <pubDate>Tue, 20 Aug 2024 14:17:35 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot; title=&quot;一、前言&quot;&gt;&lt;/a&gt;一、前言&lt;/h2&gt;&lt;p&gt;**标签云</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>**标签云 **对我们的文章画龙点睛，如果让我们的标签云随机产生彩色效果，更是增加了不是个性化，我们现在抛弃插件，自己动手从网上学习DIY自己的彩色标签云。</p><h2 id="二、代码部署"><a href="#二、代码部署" class="headerlink" title="二、代码部署"></a>二、代码部署</h2><p>代码需放入主题目录下的tag-color-cloud.php文件中</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br></pre></td><td class="code"><pre><span class="line">&lt;?php</span><br><span class="line">/**</span><br><span class="line"> * 彩色圆角标签云</span><br><span class="line"> */</span><br><span class="line"><span class="keyword">if</span> ( ! defined( <span class="string">&#x27;ABSPATH&#x27;</span> ) ) &#123; <span class="built_in">exit</span>; &#125;</span><br><span class="line"></span><br><span class="line"><span class="keyword">function</span> colorCloud( <span class="variable">$text</span> ) &#123;</span><br><span class="line">    <span class="built_in">return</span> preg_replace_callback(</span><br><span class="line">        <span class="string">&#x27;|&lt;a (.+?)&gt;|i&#x27;</span>,</span><br><span class="line">        <span class="keyword">function</span> ( <span class="variable">$m</span> ) &#123;</span><br><span class="line">            <span class="variable">$colors</span> = array( <span class="string">&#x27;F99&#x27;</span>, <span class="string">&#x27;C9C&#x27;</span>, <span class="string">&#x27;F96&#x27;</span>, <span class="string">&#x27;6CC&#x27;</span>, <span class="string">&#x27;6C9&#x27;</span>, <span class="string">&#x27;37A7FF&#x27;</span>, <span class="string">&#x27;B0D686&#x27;</span>, <span class="string">&#x27;E6CC6E&#x27;</span> );</span><br><span class="line">            <span class="variable">$color</span>  = <span class="variable">$colors</span>[ array_rand( <span class="variable">$colors</span> ) ];</span><br><span class="line"></span><br><span class="line">            // 去掉原有的 style 属性（若有）</span><br><span class="line">            <span class="variable">$attrs</span> = preg_replace( <span class="string">&#x27;/style=([&quot;\&#x27;</span>])(.*?)\1/i<span class="string">&#x27;, &#x27;</span><span class="string">&#x27;, $m[1] );</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">            // 追加新样式</span></span><br><span class="line"><span class="string">            $style  = &quot;display:inline-block;color:#fff;padding:1px 5px;margin:0 5px 5px 0;&quot;;</span></span><br><span class="line"><span class="string">            $style .= &quot;background-color:#&#123;$color&#125;;border-radius:3px;&quot;;</span></span><br><span class="line"><span class="string">            $style .= &quot;transition:background-color .4s linear;&quot;;</span></span><br><span class="line"><span class="string"></span></span><br><span class="line"><span class="string">            return &#x27;</span>&lt;a <span class="string">&#x27; . $attrs . &#x27;</span> style=<span class="string">&quot;&#x27; . <span class="variable">$style</span> . &#x27;&quot;</span>&gt;<span class="string">&#x27;;</span></span><br><span class="line"><span class="string">        &#125;,</span></span><br><span class="line"><span class="string">        $text</span></span><br><span class="line"><span class="string">    );</span></span><br><span class="line"><span class="string">&#125;</span></span><br><span class="line"><span class="string">add_filter( &#x27;</span>wp_tag_cloud<span class="string">&#x27;, &#x27;</span>colorCloud<span class="string">&#x27;, 10 );</span></span><br></pre></td></tr></table></figure><p>最后在functions.php中调用即可</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">/* 彩色圆角标签云 */</span><br><span class="line">require_once get_template_directory() . <span class="string">&#x27;/self-innovate/tag-color-cloud.php&#x27;</span>;</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/tags/">tags</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/08/20/3cb43b93/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>七牛云图床域名证书免费续费</title>
      <link>https://blog.eucalyptus.cc/2024/08/14/7f8a2b1c/</link>
      <guid>https://blog.eucalyptus.cc/2024/08/14/7f8a2b1c/</guid>
      <pubDate>Wed, 14 Aug 2024 02:09:33 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot; title=&quot;一、前言&quot;&gt;&lt;/a&gt;一、前言&lt;/h2&gt;&lt;p&gt;近期，我收到了一封紧急通知，提示我&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>近期，我收到了一封紧急通知，提示我<a href="https://www.qiniu.com/">七牛云</a>图床服务的域名证书即将过期。这让我想到，许多用户可能尚未充分认识到域名证书的重要性以及续费的必要步骤。因此，我撰写了这篇文章，旨在为您提供一份详尽的指南，教您如何轻松续订七牛云图床的域名证书，以保障您的网站或图床服务的安全性和可靠性。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/01.avif"></p><p>操作步骤：</p><ul><li>首先，您需要申请一张免费的证书。申请完成后，稍等片刻，您便能在SSL证书管理界面中看到新申请的证书。</li><li>接下来，您需要切换至新证书。在完成切换并点击确认后，您的图床服务将开始使用新的证书。</li><li>如果原有证书即将到期，您只需重复上述操作即可完成续费流程。</li><li>通过遵循这些简单步骤，您可以确保您的在线服务始终保持安全和可靠。</li></ul><h2 id="二、续费"><a href="#二、续费" class="headerlink" title="二、续费"></a>二、续费</h2><p>七牛云官方地址：<a href="https://www.qiniu.com/">七牛云 | 一站式中立音视频云 + AI</a></p><h3 id="2-1、申请免费证书"><a href="#2-1、申请免费证书" class="headerlink" title="2.1、申请免费证书"></a>2.1、申请免费证书</h3><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/02.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/03.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/04.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/05.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/06.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/07.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/08.avif"></p><h3 id="2-2、切换证书"><a href="#2-2、切换证书" class="headerlink" title="2.2、切换证书"></a>2.2、切换证书</h3><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/09.avif"></p><p>一旦您成功更换了证书，<a href="https://www.qiniu.com/">七牛云</a>将自动向您发送一条通知，告知证书续签操作已顺利完成。此后，当证书再次接近有效期时，您只需依照前述步骤进行操作，即可轻松完成续签流程。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2024-08-14/10.avif"></p><p>为了确保您的网站或服务的持续安全，定期检查证书的有效期并及时更新至关重要。通过遵循这一简单而高效的续签流程，您可以避免服务中断的风险，同时保障用户数据的安全。此外，及时更新证书还能增强用户对您网站的信任度，因为有效的证书是网站安全性的重要标志。</p><p>请记得将此操作纳入您的维护计划中，以免因疏忽导致证书过期，从而影响您的业务连续性和客户满意度。通过持续监控和适时更新证书，您可以确保服务的稳定性和可靠性，为您的用户带来无缝且安全的体验。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/%E5%9B%BE%E5%BA%8A/">图床</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E4%B8%83%E7%89%9B%E4%BA%91/">七牛云</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%9B%BE%E5%BA%8A/">图床</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/SSL/">SSL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/08/14/7f8a2b1c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的空间索引技术深度解析：利用Spatial Key优化地理空间数据查询</title>
      <link>https://blog.eucalyptus.cc/2024/08/06/6ae44fcc/</link>
      <guid>https://blog.eucalyptus.cc/2024/08/06/6ae44fcc/</guid>
      <pubDate>Tue, 06 Aug 2024 08:44:27 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;h2 id=&quot;简介&quot;&gt;&lt;a href=&quot;#简介&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><h2 id="简介"><a href="#简介" class="headerlink" title="简介"></a>简介</h2><p>MySQL中的空间索引是一种针对空间数据类型的特殊索引,主要用于优化地理空间数据的查询性能。这类索引主要应用于存储几何对象如点、线、面、多边形等数据类型的列上,比如<code>POINT</code>, <code>LINESTRING</code>, <code>POLYGON</code>, 和 <code>GEOMETRY</code>等。空间索引利用R-Tree或其变种等数据结构来组织空间数据,使得数据库能高效地执行包含空间运算的SQL语句,如查找某个区域内的所有点、计算两个几何对象之间的距离、判断一个对象是否包含在另一个对象中等空间查询操作。通过使用空间索引,MySQL能够大幅度减少在大数据集上进行复杂空间分析和位置相关查询所需的时间,特别适用于地理信息系统 GIS 、位置服务、地图应用等领域。</p><h2 id="空间数据类型"><a href="#空间数据类型" class="headerlink" title="空间数据类型"></a>空间数据类型</h2><h3 id="GEOMETRY-抽象基类"><a href="#GEOMETRY-抽象基类" class="headerlink" title="GEOMETRY 抽象基类"></a>GEOMETRY 抽象基类</h3><p>虽然我们不直接创建GEOMETRY类型的列作为空间索引,但它作为所有空间数据类型的基类,理解其概念是基础。比如,在设计数据库时,可以声明一个表的某一列为GEOMETRY类型,但实际上会具体到POINT、LINESTRING等子类型。</p><h3 id="POINT"><a href="#POINT" class="headerlink" title="POINT"></a><strong>POINT</strong></h3><p>POINT:用于存储点的坐标。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">POINT(15 20)</span><br></pre></td></tr></table></figure><h3 id="LINESTRING"><a href="#LINESTRING" class="headerlink" title="LINESTRING"></a>LINESTRING</h3><p>用于存储线段,可以由一个或多个点组成。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">LINESTRING(0 0, 10 10, 20 25, 50 60)</span><br></pre></td></tr></table></figure><h3 id="POLYGON"><a href="#POLYGON" class="headerlink" title="POLYGON"></a>POLYGON</h3><p>用于存储多边形,即闭合的线段,带一个外环, 一个内环。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">POLYGON((0 0,10 0,10 10,0 10,0 0),(5 5,7 5,7 7,5 7, 5 5))</span><br></pre></td></tr></table></figure><h3 id="MULTIPOINT"><a href="#MULTIPOINT" class="headerlink" title="MULTIPOINT"></a>MULTIPOINT</h3><p>用于存储多个点的集合。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">MULTIPOINT(0 0, 20 20, 60 60)</span><br></pre></td></tr></table></figure><h3 id="MULTILINESTRING"><a href="#MULTILINESTRING" class="headerlink" title="MULTILINESTRING"></a>MULTILINESTRING</h3><p>用于存储多条线段的集合,多个<code>LineString</code>值。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">MULTILINESTRING((10 10, 20 20), (15 15, 30 15))</span><br></pre></td></tr></table></figure><h3 id="MULTIPOLYGON"><a href="#MULTIPOLYGON" class="headerlink" title="MULTIPOLYGON"></a>MULTIPOLYGON</h3><p>用于存储多个多边形的集合,多个 <code>Polygon</code>值。</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">MULTIPOLYGON(((0 0,10 0,10 10,0 10,0 0)),((5 5,7 5,7 7,5 7, 5 5)))</span><br></pre></td></tr></table></figure><h3 id="GEOMETRYCOLLECTION"><a href="#GEOMETRYCOLLECTION" class="headerlink" title="GEOMETRYCOLLECTION"></a>GEOMETRYCOLLECTION</h3><p>用于存储多种类型的空间对象的集合,比如由两个组成 <code>Point</code>值和一个 <code>LineString</code></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">GEOMETRYCOLLECTION(POINT(10 10), POINT(30 30), LINESTRING(15 15, 20 20))</span><br></pre></td></tr></table></figure><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-08-06/img1.avif"></p><p>官方文档:</p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/gis-data-formats.html">MySQL :: MySQL 8.0 Reference Manual :: 13.4.3 Supported Spatial Data Formats</a></p><h2 id="函数"><a href="#函数" class="headerlink" title="函数"></a>函数</h2><h3 id="ST-GeomFromText"><a href="#ST-GeomFromText" class="headerlink" title="ST_GeomFromText()"></a><code>ST_GeomFromText()</code></h3><p><code>ST_GeomFromText()</code> 是一个在许多数据库系统中用于处理地理空间数据的功能函数,尤其是在PostGIS PostgreSQL的扩展 中广泛使用。这个函数的主要目的是将一个表示几何对象的Well-Known Text (WKT)格式的字符串转换为数据库内部的二进制几何类型,以便于进行空间分析和查询。</p><p>基本语法:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ST_GeomFromText(text WKT[, integer srid])</span><br></pre></td></tr></table></figure><h3 id="ST-X"><a href="#ST-X" class="headerlink" title="ST_X"></a><code>ST_X</code></h3><p>这个函数用于从一个点几何对象中提取经度坐标 x坐标 ,即点在水平方向的位置。在地理坐标系统中,这通常指的是经度值。</p><p>基本语法:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ST_X(point)</span><br></pre></td></tr></table></figure><h3 id="ST-Y"><a href="#ST-Y" class="headerlink" title="ST_Y"></a><code>ST_Y</code></h3><p>相对地,这个函数用于从同一个点几何对象中提取纬度坐标 y坐标 ,即点在垂直方向的位置。在地理坐标系统中,这对应于纬度值。</p><p>基本语法:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ST_Y(point)</span><br></pre></td></tr></table></figure><h3 id="ST-AsText"><a href="#ST-AsText" class="headerlink" title="ST_AsText"></a>ST_AsText</h3><p>将点转换为Well-Known Text (WKT)格式的字符串表示,这个函数在上面提到的几种数据类型中是通用的</p><p>基本语法:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ST_AsText(point)</span><br></pre></td></tr></table></figure><h3 id="空间函数"><a href="#空间函数" class="headerlink" title="空间函数"></a>空间函数</h3><ul><li>ST_Contains: 判断一个几何对象是否包含另一个几何对象。</li><li>ST_Distance: 计算两个几何对象之间的距离。</li><li>ST_Buffer: 根据给定的距离,在几何对象周围创建一个缓冲区。</li><li>ST_Intersection: 计算两个几何对象的交集。</li><li>ST_Union: 计算多个几何对象的并集。</li></ul><h3 id="总结-1"><a href="#总结-1" class="headerlink" title="总结"></a>总结</h3><p>上面介绍的函数是常用的,下面的这些函数 针对不同的数据类型 用到的比较少</p><ul><li><code>ST_StartPoint(line)</code>:返回线段的起始点。</li><li><code>ST_EndPoint(line)</code>:返回线段的终点。</li><li><code>ST_NumPoints(line)</code>:返回线段中的点数。</li><li><code>ST_PointN(line, n)</code>:返回线段中的第n个点。</li><li><code>ST_Area(poly)</code>:计算多边形的面积。</li><li><code>ST_Centroid(poly)</code>:计算多边形的质心。</li><li><code>ST_Perimeter(poly)</code>:计算多边形的周长。</li><li><code>ST_NumGeometries(multipoint)</code>:返回多点集合中的点数。</li><li><code>ST_GeometryN(multipoint, n)</code>:返回多点集合中的第n个几何对象。</li><li>类似于MULTIPOINT,使用<code>ST_NumGeometries()</code>、<code>ST_GeometryN()</code>等函数来访问和操作其中的线段。</li><li>同样使用<code>ST_NumGeometries()</code>、<code>ST_GeometryN()</code>等函数来操作多边形集合中的每个多边形。</li><li><code>ST_NumGeometries(collection)</code>:返回集合中的几何对象数量。</li><li><code>ST_GeometryN(collection, n)</code>:返回集合中的第n个几何对象。</li></ul><h2 id="坐标系"><a href="#坐标系" class="headerlink" title="坐标系"></a>坐标系</h2><h3 id="WGS-84坐标系-EPSG-4326-默认-常用"><a href="#WGS-84坐标系-EPSG-4326-默认-常用" class="headerlink" title="WGS 84坐标系 EPSG:4326 默认&#x2F;常用"></a>WGS 84坐标系 EPSG:4326 默认&#x2F;常用</h3><ul><li>**经度 Longitude **:从本初子午线 通过英国格林尼治的经线 向东或向西测量的角度,范围从-180°到 180°。</li><li>**纬度 Latitude **:从赤道测量到南北极点的角度,范围从-90° 南极 到 90° 北极 。</li></ul><p>官方文档:</p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/spatial-reference-systems.html">MySQL :: MySQL 8.0 Reference Manual :: 13.4.5 Spatial Reference System Support</a></p><h3 id="Web-Mercator-Projection-EPSG-3857"><a href="#Web-Mercator-Projection-EPSG-3857" class="headerlink" title="Web Mercator Projection (EPSG:3857)"></a><strong>Web Mercator Projection (EPSG:3857)</strong></h3><p>这是网络地图服务中广泛使用的一种投影方式,如Google Maps、OpenStreetMap等。它基于墨卡托投影,适用于快速显示和可视化,但高纬度地区会有较大形变。</p><h3 id="China-Geodetic-Coordinate-System-2000-CGCS2000-EPSG-4490"><a href="#China-Geodetic-Coordinate-System-2000-CGCS2000-EPSG-4490" class="headerlink" title="China Geodetic Coordinate System 2000 (CGCS2000) &#x2F; EPSG:4490"></a><strong>China Geodetic Coordinate System 2000 (CGCS2000) &#x2F; EPSG:4490</strong></h3><p>中国自有的大地坐标系统,类似于WGS 84,但有自己定义的参考框架,适用于中国地区的高精度测量和制图。</p><h3 id="UTM-Universal-Transverse-Mercator-系统"><a href="#UTM-Universal-Transverse-Mercator-系统" class="headerlink" title="UTM (Universal Transverse Mercator) 系统"></a><strong>UTM (Universal Transverse Mercator) 系统</strong></h3><p>UTM是一种全球分带的墨卡托投影坐标系统,将地球分为60个6度带,每个带都有自己的坐标系,常用于军事、航空、地形图等领域,便于局部地区的高精度测量和制图。EPSG代码根据具体的带号和北&#x2F;南半球有所不同。</p><h3 id="State-Plane-Coordinate-System-SPCS"><a href="#State-Plane-Coordinate-System-SPCS" class="headerlink" title="State Plane Coordinate System (SPCS)"></a><strong>State Plane Coordinate System (SPCS)</strong></h3><p>美国的一种坐标参考系统,分为多个区域,旨在提供美国境内更精确的测量和制图,包括两种投影类型:横轴墨卡托和兰伯特锥形。每个州或区域有特定的EPSG代码。</p><h3 id="British-National-Grid-BNG-EPSG-27700"><a href="#British-National-Grid-BNG-EPSG-27700" class="headerlink" title="British National Grid (BNG) &#x2F; EPSG:27700"></a><strong>British National Grid (BNG) &#x2F; EPSG:27700</strong></h3><p>英国使用的一种坐标系,基于Transverse Mercator投影,适用于英国及周边岛屿的测量和地图制作。</p><h3 id="European-Terrestrial-Reference-System-1989-ETRS89-EPSG-4258"><a href="#European-Terrestrial-Reference-System-1989-ETRS89-EPSG-4258" class="headerlink" title="European Terrestrial Reference System 1989 (ETRS89) &#x2F; EPSG:4258"></a><strong>European Terrestrial Reference System 1989 (ETRS89) &#x2F; EPSG:4258</strong></h3><p>为欧洲设计的一种地心坐标参考系统,与WGS 84非常接近但在欧洲大陆内部提供了更高的长期稳定性,适用于欧洲的地理信息系统和测量工作。</p><h3 id="Pulkovo-1942-EPSG-4284"><a href="#Pulkovo-1942-EPSG-4284" class="headerlink" title="Pulkovo 1942 &#x2F; EPSG:4284"></a><strong>Pulkovo 1942 &#x2F; EPSG:4284</strong></h3><p>旧苏联及一些东欧国家曾经使用的坐标系,基于普尔科沃天文台的地理位置。</p><h2 id="空间索引"><a href="#空间索引" class="headerlink" title="空间索引"></a>空间索引</h2><h3 id="创建一个有空间列的表"><a href="#创建一个有空间列的表" class="headerlink" title="创建一个有空间列的表"></a>创建一个有空间列的表</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> places (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span> AUTO_INCREMENT,</span><br><span class="line">name <span class="type">varchar</span>(<span class="number">255</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line">location geometry <span class="keyword">NOT NULL</span> SRID <span class="number">4326</span></span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB AUTO_INCREMENT <span class="number">8</span> <span class="keyword">DEFAULT</span> CHARSET utf8mb4 <span class="keyword">COLLATE</span> utf8mb4_0900_ai_ci ;</span><br></pre></td></tr></table></figure><h3 id="添加空间索引"><a href="#添加空间索引" class="headerlink" title="添加空间索引"></a>添加空间索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> places <span class="keyword">add</span> spatial spatial_index(location);</span><br></pre></td></tr></table></figure><p>看到这里可能有人会问了,为什么不在创建表的时候就创建号空间索引,要在后面单独添加那,这是因为<strong>空间索引不能和其他的索引在创建表的同时创建</strong>,因为使用的数据结构不一样</p><h3 id="给表中插入不同子数据类型的数据"><a href="#给表中插入不同子数据类型的数据" class="headerlink" title="给表中插入不同子数据类型的数据"></a>给表中插入不同子数据类型的数据</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> places (name, location) <span class="keyword">VALUES</span> (<span class="string">&#x27;Place A&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;POINT(1 1) &#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"><span class="keyword">INSERT INTO</span> places (name, location) <span class="keyword">VALUES</span> (<span class="string">&#x27;Place B&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;LINESTRING(1 1,2 2,3 3))&#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"><span class="keyword">INSERT INTO</span> places (name, location) <span class="keyword">VALUES</span> (<span class="string">&#x27;Place C&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;POLYGON((0 0,10 0,10 10,0 10,0 0),(5 5,7 5,7 7,5 7,5 5)) &#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"><span class="keyword">INSERT INTO</span> places (name, location) <span class="keyword">VALUES</span> (<span class="string">&#x27;Place D&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;MULTIPOINT((0 0),(20 20),(60 60)) &#x27;</span>, <span class="number">4326</span>));</span><br><span class="line"><span class="keyword">INSERT INTO</span> places (name, location) <span class="keyword">VALUES</span> (<span class="string">&#x27;Place E&#x27;</span>, ST_GeomFromText(<span class="string">&#x27;MULTILINESTRING((10 10,20 20),(15 15,30 15)) , 4326));</span></span><br><span class="line"><span class="string">INSERT INTO places (name, location) VALUES (&#x27;</span>Place F<span class="string">&#x27;, ST_GeomFromText(&#x27;</span>GEOMETRYCOLLECTION(POINT(<span class="number">10</span> <span class="number">10</span>),POINT(<span class="number">30</span> <span class="number">30</span>),LINESTRING(<span class="number">15</span> <span class="number">15</span>,<span class="number">20</span> <span class="number">20</span>))<span class="string">&#x27;, 4326));</span></span><br><span class="line"><span class="string">INSERT INTO places (name, location) VALUES (&#x27;</span>Beijing<span class="string">&#x27;, ST_GeomFromText(&#x27;</span>POINT(<span class="number">39.9042</span> <span class="number">116.4074</span>) <span class="string">&#x27;, 4326));</span></span><br></pre></td></tr></table></figure><h2 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h2><ul><li>空间列必须是NOT NULL</li><li>spatial key不可以和no spatial key一起创建 MySQL8.0以后可以同时创建</li><li>创建空间列的时候需要指定SRID,不然MySQL优化器不会使用索引, 官方文档:</li></ul><p><a href="https://dev.mysql.com/doc/refman/8.4/en/creating-spatial-indexes.html">MySQL :: MySQL 8.4 Reference Manual :: 13.4.10 Creating Spatial Indexes</a></p><ul><li>point数据类型是按 纬度,经度 存储的,和WGS 84 经度,纬度 相反</li><li>插入数据的时候指定的SRID必须和创建表的时候指定的SRID是一致的,官方文档:</li></ul><p><a href="https://dev.mysql.com/doc/refman/8.0/en/spatial-index-optimization.html">MySQL :: MySQL 8.0 Reference Manual :: 10.3.3 SPATIAL Index Optimization</a></p><p>开发板推荐：天空星STM32F407VET6开发板</p><p>超高性价比 STM32主控 | 超高主频 | 一板兼容百芯 | 比赛神器 | 沉金彩色丝印</p><p>点击查看</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/08/06/6ae44fcc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>在线迁移InnoDB表空间：运用DISCARD与IMPORT实现高效数据传输</title>
      <link>https://blog.eucalyptus.cc/2024/07/23/0a1b2edb/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/23/0a1b2edb/</guid>
      <pubDate>Tue, 23 Jul 2024 09:51:31 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;前言&quot;&gt;&lt;a href=&quot;#前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="前言"><a href="#前言" class="headerlink" title="前言"></a>前言</h2><p>在日益复杂和动态变化的数据库管理环境中,高效且安全地迁移大数据量的表空间成为了一个重要的议题。尤其是在处理高可用性需求和资源优化的场景下,如何在不影响业务连续性的前提下,快速完成数据库表空间的迁移,是每一位数据库管理员 DBA 面临的关键挑战。《在线迁移InnoDB表空间:运用DISCARD与IMPORT TABLESPACE实现高效数据传输》正是为了解决这一痛点而撰写。</p><p>本书章节深入浅出地介绍了利用MySQL中InnoDB引擎提供的<code>DISCARD TABLESPACE</code>和<code>IMPORT TABLESPACE</code>命令,实现在生产环境中在线迁移表空间的全过程。通过理论讲解与实践操作相结合的方式,不仅详细解析了命令背后的机制和原理,还提供了详尽的操作步骤与最佳实践指导,旨在帮助读者掌握一种灵活、可靠的数据库迁移策略。</p><p>书中内容覆盖了从前期准备、风险评估、操作流程到后期验证的每一个环节,特别强调了数据一致性与安全性的重要性,确保在迁移过程中数据的完整无损。此外,我们还将探讨如何结合其他MySQL管理工具和技巧,进一步提升迁移效率和成功率,满足不同规模数据库的迁移需求。</p><p>无论是对于经验丰富的DBA,还是初涉数据库管理领域的技术人员,《在线迁移InnoDB表空间:运用DISCARD与IMPORT TABLESPACE实现高效数据传输》都将是一本不可或缺的参考书籍,助力您在数据迁移的征途中更加从容不迫,游刃有余。</p><h2 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h2><p>创建test1、test2两个数据库</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> database test1</span><br><span class="line"><span class="keyword">create</span> database test2</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>切换到目标库test1创建一个测试表</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">use test1</span><br><span class="line"><span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>) ENGINE INNODB;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>在目标库test1中丢弃刚刚创建的t1表的表空间</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> t1 DISCARD TABLESPACE;</span><br></pre></td></tr></table></figure><p>切换到源库test2中,创建和目标库test1中相同结构的t1表</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">use test2</span><br><span class="line"><span class="keyword">CREATE TABLE</span> t1 (c1 <span class="type">INT</span>) ENGINE INNODB;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>退出MySQL来到MySQL的数据目录下,YUM安装的MySQL数据目录一般都在&#x2F;var&#x2F;lib&#x2F;mysql&#x2F;下面</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">\q</span><br><span class="line"><span class="built_in">cd</span> /var/lib/mysql/</span><br></pre></td></tr></table></figure><p>将源库test2下t1表的.ibd文件copy到目标库test1下t1表的下面,<strong>这里复制的时候一定要复制到权限否则在import的时候会报错****Tablespace is missing for table test1 . t1 .</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cp</span> -avR /var/lib/mysql/test2/t1.ibd /var/lib/mysql/test1/</span><br></pre></td></tr></table></figure><p>登陆MySQL,切换到目标库test1,并恢复刚才在目标库test1中丢弃t1表的表空间</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">use test1;</span><br><span class="line"><span class="keyword">ALTER TABLE</span> t1 IMPORT TABLESPACE;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><ul><li>上面是一个粗糙的演示,具体的细节问题和前提条件看<a href="https://dev.mysql.com/doc/refman/8.0/en/innodb-table-import.html">MySQL官方文档</a></li><li>本次示例中MySQL的版本是8.0.37</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/23/0a1b2edb/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>快速迁移网站</title>
      <link>https://blog.eucalyptus.cc/2024/07/22/8de618e0/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/22/8de618e0/</guid>
      <pubDate>Mon, 22 Jul 2024 12:34:22 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>从建站开始到现在也有一年了，也看着服务器马上就要到期了。现在有俩个选择可以解决这个问题，其一是在现有的服务器上选择续费，但是成本很高，由于笔者的网站在建站的这一年之内也没有什么收入，所以很难拿出这么一大笔的费用，那么只能选择其二了，那就是购买一台新的服务器，毕竟在有活动的时候够买，相对来说还是很便宜的，但是如果购买新的服务器的话，也会面临一定的问题比如如何将网站从旧的服务器迁移到新的服务器。</p><p>先总结一下迁移的思路吧：</p><ul><li>首先要给新的服务器安装上和旧服务器一样的宝塔环境，包括php版本、mysql版本，这样能避免网站数据出错。</li><li>网站数据一定要提前备份，防止出现其他问题可以方便恢复。</li><li>然后在发送数据服务器上安装一键迁移工具，填写接收数据服务器信息，包括秘钥，就可以开始自动迁移了。</li></ul><h2 id="二、安装迁移工具"><a href="#二、安装迁移工具" class="headerlink" title="二、安装迁移工具"></a>二、安装迁移工具</h2><p>直接在宝塔面板的软件商店搜索<code>一键迁移</code>，即可找到宝塔一键迁移API版本，点击安装即可。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/1.avif"></p><h2 id="三、配置API"><a href="#三、配置API" class="headerlink" title="三、配置API"></a>三、配置API</h2><p>接收数据服务器上，点击面板设置，开启API，获得接口秘钥，并将发送数据端IP加入接收数据服务器API的IP白名单，最后点击保存即可。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/2.avif"></p><h2 id="四、开启迁移"><a href="#四、开启迁移" class="headerlink" title="四、开启迁移"></a>四、开启迁移</h2><p>发送数据服务器上，找到我们刚刚下载的宝塔一键迁移API版本，填写面板地址和API秘钥。<br>注意：面板地址和API秘钥都是接收数据服务器、接收数据服务器、接收数据服务器上的，千万别填错了。<br>面板地址包含 协议 + 主机IP地址 + 面板端口<br>例如：<a href="http://192.168.0.1:8888/">http://192.168.0.1:8888</a></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2024-07-22/7.avif"></p><h2 id="五、解析测试"><a href="#五、解析测试" class="headerlink" title="五、解析测试"></a>五、解析测试</h2><p>迁移完成后，网站文件和数据库就都已经到新的网站了，这个时候域名再重新解析到新的网站就可以正常访问了。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E7%BD%91%E7%AB%99%E8%BF%81%E7%A7%BB/">网站迁移</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/22/8de618e0/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL锁】基础篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/10/107af072/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/10/107af072/</guid>
      <pubDate>Wed, 10 Jul 2024 08:47:15 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;1-什么是锁&quot;&gt;&lt;a href=&quot;#1-什么是锁&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="1-什么是锁"><a href="#1-什么是锁" class="headerlink" title="1.什么是锁"></a>1.什么是锁</h2><p>MySQL中为了保证数据访问的一致性与有效性等功能,实现了锁机制,MySQL中的锁是在服务器层或者存储引擎层实现的。</p><h2 id="2-锁用来解决什么问题"><a href="#2-锁用来解决什么问题" class="headerlink" title="2.锁用来解决什么问题"></a>2.锁用来解决什么问题</h2><p>锁是用来解决并发事务的访问问题,我们已经知道事务并发执行时可能带来的各种问题,最大的一个难点是:一方面要最大程度地利用数据库的并发访问,另外一方面还要确保每个用户能以一致的方式读取和修改数据,尤其是一个事务进行读取操作,另一个同时进行改动操作的情况下。</p><p>一个事务进行读取操作,另一个进行改动操作,我们前边说过,这种情况下可能发生脏读、不可重复读、幻读的问题。</p><h3 id="2-1-脏读-select"><a href="#2-1-脏读-select" class="headerlink" title="2.1.脏读 select"></a>2.1.脏读 select</h3><p><strong>如果一个事务读取到了另一个未提交事务修改过的数据,我们就称发生了脏读现象。</strong></p><p>假设现在有两个事务A、B:</p><ul><li>假设现在A的余额是100,事务A正在准备查询Jay的余额</li><li>事务B先扣减Jay的余额,扣了10,但是还没提交</li><li>最后A读到的余额是90,即扣减后的余额</li></ul><p>因为事务A读取到事务B<strong>未提交的数据</strong>,这就是脏读。</p><h3 id="2-2-不可重复读-update"><a href="#2-2-不可重复读-update" class="headerlink" title="2.2.不可重复读 update"></a>2.2.不可重复读 update</h3><p><strong>同一个事务内,前后多次读取,读取到的数据内容不一致</strong></p><p>假设现在有两个事务A和B:</p><ul><li>事务A先查询Jay的余额,查到结果是100</li><li>这时候事务B 对Jay的账户余额进行扣减,扣去10后,提交事务</li><li>事务A再去查询Jay的账户余额发现变成了90</li></ul><p>事务A被事务B干扰到了 在事务A范围内,两个相同的查询,读取同一条记录,却返回了不同的数据,这就是<strong>不可重复读</strong>。</p><h3 id="2-3-幻读-insert"><a href="#2-3-幻读-insert" class="headerlink" title="2.3.幻读 insert"></a>2.3.幻读 insert</h3><p><strong>如果一个事务先根据某些搜索条件查询出一些记录,在该事务未提交时,另一个事务写入了一些符合那些搜索条件的记录 如insert、delete、update ,就意味着发生了幻读。</strong></p><p>假设现在有两个事务A、B:</p><ul><li>事务A先查询id大于2的账户记录,得到记录id 2和id 3的两条记录</li><li>这时候,事务B开启,插入一条id 4的记录,并且提交了</li><li>事务A再去执行相同的查询,却得到了id 2,3,4的3条记录了。</li></ul><p>事务A查询一个范围的结果集,另一个并发事务B往这个范围中插入新的数据,并提交事务,然后事务A再次查询相同的范围,两次读取到的结果集却不一样了,这就是幻读。</p><h2 id="3-锁的分类"><a href="#3-锁的分类" class="headerlink" title="3.锁的分类"></a>3.锁的分类</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img1.avif"></p><h3 id="3-1-使用方法"><a href="#3-1-使用方法" class="headerlink" title="3.1.使用方法"></a>3.1.使用方法</h3><h4 id="3-1-1-共享锁"><a href="#3-1-1-共享锁" class="headerlink" title="3.1.1.共享锁"></a>3.1.1.共享锁</h4><p>共享锁,Share lock,也叫读锁。它是指当对象被锁定时,允许其它事务读取该对象,也允许其它事务从该对象上再次获取共享锁,但不能对该对象进行写入。</p><p>加锁方式:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"># 方式<span class="number">1</span></span><br><span class="line"><span class="keyword">select</span> ... lock <span class="keyword">in</span> share mode;</span><br><span class="line"># 方式<span class="number">2</span></span><br><span class="line"><span class="keyword">select</span> ... <span class="keyword">for</span> share;</span><br></pre></td></tr></table></figure><p>如果事务T1 在某对象持有共享(S)锁,则事务T2 需要再次获取该对象的锁时,会出现下面两种情况:</p><ul><li>如果T2 获取该对象的共享(S)锁,则可以立即获取锁;</li><li>如果T2 获取该对象的排他(X)锁,则无法获取锁;</li></ul><h4 id="3-1-2-排他锁"><a href="#3-1-2-排他锁" class="headerlink" title="3.1.2.排他锁"></a>3.1.2.排他锁</h4><p>排它锁,Exclusive Lock,也叫写锁或者独占锁,主要是防止其它事务和当前加锁事务锁定同一对象。同一对象主要有两层含义:</p><ul><li>当排他锁加在表上,则其它事务无法对该表进行insert,update,delete,alter,drop等更新操作;</li><li>当排他锁加在表的行上,则其它事务无法对该行进行insert,update,delete,alter,drop等更新操作;</li></ul><p>加锁方式:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> ... <span class="keyword">for</span> <span class="keyword">update</span>;</span><br></pre></td></tr></table></figure><h2 id="4-加锁范围"><a href="#4-加锁范围" class="headerlink" title="4.加锁范围"></a>4.加锁范围</h2><h3 id="4-1-全局锁"><a href="#4-1-全局锁" class="headerlink" title="4.1.全局锁"></a>4.1.全局锁</h3><p>全局锁,顾名思义,就是对整个数据库实例加锁。它是粒度最大的锁。</p><h4 id="4-1-1-加锁方式"><a href="#4-1-1-加锁方式" class="headerlink" title="4.1.1.加锁方式"></a>4.1.1.加锁方式</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">flush tables <span class="keyword">with</span> read lock</span><br></pre></td></tr></table></figure><p>指令执行完,整个数据库就处于只读状态了,其他线程执行以下操作,都会被阻塞:</p><ul><li>数据更新语句被阻塞,包括 insert, update, delete语句;</li><li>数据定义语句被阻塞,包括建表 create table,alter table、drop table 语句;</li><li>更新操作事务commit语句被阻塞;</li></ul><h4 id="4-1-2-释放锁"><a href="#4-1-2-释放锁" class="headerlink" title="4.1.2.释放锁"></a>4.1.2.释放锁</h4><p>在MySQL中释放锁有2种方式:</p><p>1.执行指令</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">unlock tables</span><br></pre></td></tr></table></figure><p>2.加锁的会话断开,全局锁也会被自动释放</p><h4 id="4-1-3-使用场景"><a href="#4-1-3-使用场景" class="headerlink" title="4.1.3.使用场景"></a>4.1.3.使用场景</h4><p>全局锁的典型使用场景是做全库逻辑备份,在备份过程中整个库完全处于只读状态。如下图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img2.avif"></p><ul><li>假如在主库上备份,备份期间,业务服务器不能对数据库执行更新操作,因此涉及到更新操作的业务就瘫痪了;</li><li>假如在从库上备份,备份期间,从库不能执行主库同步过来的 binlog,会导致主从延迟越来越大,如果做了读写分离,那么从库上获取数据就会出现延时,影响业务;</li></ul><p>从上述分析可以看出,使用全局锁进行数据备份,不管是在主库还是在从库上进行备份操作,对业务总是不太友好。那不加锁行不行?我们可以通过下面还钱转账的例子,看看不加锁会不会出现问题:</p><ul><li>备份前:账户A 有1000,账户B 有500</li><li>此时,发起逻辑备份</li><li>假如数据备份时不加锁,此时,客户端A 发起一个还钱转账的操作:账户A 往账户B 转200</li><li>当账户A 转出200完成,账户B 转入200 还未完成时,整个数据备份完成</li><li>如果用该备份数据做恢复,会发现账户A 转出了200,账户B 却没有对应的转入记录,这样就会产生纠纷:A 说我账户少了 200, B 说我没有收到,最后,A,B谁都不干。</li></ul><p>既然不加锁会产生错误,加全局锁又会影响业务,那么有没有两全其美的方式呢?</p><p>有,MySQL官方自带的逻辑备份工具 mysqldump,具体指令如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqldump –single<span class="operator">-</span>transaction</span><br></pre></td></tr></table></figure><p>执行该指令,在备份数据之前会先启动一个事务,来确保拿到一致性视图, 加上 MVCC 的支持,保证备份过程中数据是可以正常更新。但是,single-transaction方法只适用于库中所有表都使用了事务引擎,如果有表使用了不支持事务的引擎,备份就只能用 FTWRL 方法。</p><h3 id="4-2-表级锁"><a href="#4-2-表级锁" class="headerlink" title="4.2.表级锁"></a>4.2.表级锁</h3><p>表锁就是对整张表加锁,包含读锁和写锁,由MySQL Server实现,表锁需要显示加锁或释放锁,具体指令如下:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 给表加写锁</span></span><br><span class="line">lock tables tablename write;</span><br><span class="line"></span><br><span class="line"><span class="comment"># 给表加读锁</span></span><br><span class="line">lock tables tablename <span class="built_in">read</span>;</span><br><span class="line"></span><br><span class="line"><span class="comment"># 释放锁</span></span><br><span class="line">unlock tables;</span><br></pre></td></tr></table></figure><h4 id="4-2-1读锁"><a href="#4-2-1读锁" class="headerlink" title="4.2.1读锁"></a><strong>4.2.1读锁</strong></h4><p>代表当前表为只读状态,读锁是一种共享锁。需要注意的是,读锁除了会限制其它线程的操作外,也会限制加锁线程的行为,具体限制如下:</p><ul><li>加锁线程只能对当前表进行读操作,不能对当前表进行更新操作,不能对其它表进行所有操作;</li><li>其它线程只能对当前表进行读操作,不能对当前表进行更新操作,可以对其它表进行所有操作;</li></ul><h4 id="4-2-2-写锁"><a href="#4-2-2-写锁" class="headerlink" title="4.2.2.写锁"></a><strong>4.2.2.写锁</strong></h4><p>写锁是一种独占锁,需要注意的是,写锁除了会限制其它线程的操作外,也会限制加锁线程的行为,具体限制如下:</p><ul><li>加锁线程对当前表能进行所有操作,不能对其它表进行任何操作;</li><li>其它线程不能对当前表进行任何操作,可以对其它表进行任何操作;</li></ul><h4 id="4-2-3-MDL元数据锁"><a href="#4-2-3-MDL元数据锁" class="headerlink" title="4.2.3.MDL元数据锁"></a>4.2.3.MDL元数据锁</h4><p>DDL的写锁请求优先级高于DML</p><p>元数据锁:metadata lock,简称MDL,它是在MySQL 5.5版本引进的。元数据锁不用像表锁那样显式的加锁和释放锁,而是在访问表时被自动加上,以保证读写的正确性。</p><p>加锁和释放锁规则如下:</p><ul><li>MDL读锁之间不互斥,也就是说,允许多个线程同时对加了 MDL读锁的表进行CRUD(增删改查)操作;</li><li>MDL写锁,它和读锁、写锁都是互斥的,目的是用来保证变更表结构操作的安全性。也就是说,当对表结构进行变更时,会被默认加 MDL写锁,因此,如果有两个线程要同时给一个表加字段,其中一个要等另一个执行完才能开始执行。</li><li>MDL读写锁是在事务commit之后才会被释放;</li></ul><p>当一个事务开始执行SELECT或UPDATE语句时,MySQL会自动获取相关表的共享元数据锁;而当一个事务开始执行CREATE TABLE或DROP TABLE语句时,则会自动获取相应表的独占元数据锁。在事务提交或回滚后,相应的元数据锁也会自动释放。</p><h4 id="4-2-4-意向锁"><a href="#4-2-4-意向锁" class="headerlink" title="4.2.4.意向锁"></a>4.2.4.意向锁</h4><p>当事务A有行锁时,MySQL会自动为该表添加意向锁,事务B如果想申请整个表的写锁,那么不需要遍历每一行判断是否存在行锁,而直接判断是否存在意向锁,增强性能。</p><p>意向锁为什么是表锁而不是行锁?</p><p>意向锁时表锁的话在遍历的时候只需要遍历一遍就可以,但是若时行锁则会需要一行一行遍历</p><p>意向锁,Intention lock,它是一种表锁,用来标识事务打算在表中的行上获取什么类型的锁。 不同的事务可以在同一张表上获取不同种类的意向锁,但是第一个获取表上意向排他(<strong>IX</strong>) 锁的事务会阻止其它事务获取该表上的任何 S锁 或 X 锁。反之,第一个获得表上意向共享锁(<strong>IS</strong>) 的事务可防止其它事务获取该表上的任何 X 锁。</p><p>意向锁通常有两种类型:</p><ul><li>意向共享锁(<strong>IS</strong>),表示事务打算在表中的各个行上设置共享锁。</li><li>意向排他锁(<strong>IX</strong>),表示事务打算对表中的各个行设置排他锁。</li></ul><p>意向锁是InnoDB自动加上的,加锁时遵从下面两个协议:</p><ul><li>事务在获取表中行的共享锁之前,必须先获取表上的IS锁或更强的锁。</li><li>事务在获取表中行的排他锁之前,必须先获取表上的IX锁。</li></ul><h4 id="4-2-5-AUTO-INC锁"><a href="#4-2-5-AUTO-INC锁" class="headerlink" title="4.2.5.AUTO-INC锁"></a>4.2.5.AUTO-INC锁</h4><p>AUTO-INC锁是一种特殊的表级锁,当表中有AUTO_INCREMENT的列时,如果向这张表插入数据时,InnoDB会先获取这张表的AUTO-INC锁,等插入语句执行完成后,AUTO-INC锁会被释放。</p><p>AUTO-INC锁可以使用innodb_autoinc_lock_mode变量来配置自增锁的算法,</p><p>innodb_autoinc_lock_mode变量可以选择三种值如下表:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img3.avif"></p><h4 id="4-2-6-锁的兼容性"><a href="#4-2-6-锁的兼容性" class="headerlink" title="4.2.6.锁的兼容性"></a>4.2.6.锁的兼容性</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img4.avif"></p><h3 id="4-3-行锁"><a href="#4-3-行锁" class="headerlink" title="4.3.行锁"></a>4.3.行锁</h3><p>行锁只用在事务中才能使用,若是事务提交行锁也会自动解锁,<strong>行锁是加在索引上面的</strong></p><p>行锁是针对数据表中行记录的锁。MySQL 的行锁是在引擎层实现的,并不是所有的引擎都支持行锁,比如,InnoDB引擎支持行锁而 MyISAM引擎不支持。</p><p>InnoDB 引擎的行锁主要有三类:</p><ul><li>Record Lock: 记录锁,是在索引记录上加锁;</li><li>Gap Lock:间隙锁,锁定一个范围,但不包含记录;</li><li>Next-key Lock:Gap Lock Record Lock,锁定一个范围(Gap Lock实现),并且锁定记录本身(Record Lock实现)</li></ul><h4 id="4-3-1-记录锁-Record-Lock"><a href="#4-3-1-记录锁-Record-Lock" class="headerlink" title="4.3.1.记录锁 Record Lock"></a>4.3.1.记录锁 Record Lock</h4><p><strong>Record Lock:记录锁,是针对索引记录的锁,锁定的总是索引记录,而不是真正的数据记录</strong></p><p>例如,select id from user where id 1 for update; for update 就显式在索引id上加行锁(排他锁),防止其它任何事务 update或delete id 1 的行,但是对user表的insert、alter、drop操作还是可以正常执行。</p><h4 id="4-3-2-间隙锁-Gap-Lock"><a href="#4-3-2-间隙锁-Gap-Lock" class="headerlink" title="4.3.2.间隙锁 Gap Lock"></a>4.3.2.间隙锁 Gap Lock</h4><p><strong>锁住的是一个区间,而不仅仅是这个区间中的每一条数据</strong>,<strong>是在可重复读的隔离级别下 为了解决幻读引入的锁机制</strong></p><p>Gap Lock:间隙锁,锁住两个索引记录之间的间隙上,由InnoDB隐式添加。比如(1,3) 表示锁住记录1和记录3之间的间隙,这样记录2就无法插入,间隙可能跨越单个索引值、多个索引值,甚至是空。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img5.avif"></p><h4 id="4-3-3-临建锁-Next-Key-Lock"><a href="#4-3-3-临建锁-Next-Key-Lock" class="headerlink" title="4.3.3.临建锁 Next-Key Lock"></a>4.3.3.临建锁 Next-Key Lock</h4><p>可以解决幻读的问题</p><p><strong>注意:临建锁只与非唯一索引列有关,在唯一索引列上不存在临建锁</strong></p><p>Next-Key锁,称为临键锁,它是Record Lock Gap Lock的组合,用来锁定一个范围,并且锁定记录本身锁,它是一种左开右闭的范围,可以用符号表示为:(a,b]。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img6.avif"></p><h4 id="4-3-4-插入意向锁-Insert-Intention-Lock"><a href="#4-3-4-插入意向锁-Insert-Intention-Lock" class="headerlink" title="4.3.4.插入意向锁 Insert Intention Lock"></a>4.3.4.插入意向锁 Insert Intention Lock</h4><p>插入意向锁,它是一种特殊的间隙锁,特指插入操作产生的间隙锁。</p><h4 id="4-3-5-临键锁在什么情况下会降级"><a href="#4-3-5-临键锁在什么情况下会降级" class="headerlink" title="4.3.5.临键锁在什么情况下会降级"></a>4.3.5.临键锁在什么情况下会降级</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-10/img7.avif"></p><h5 id="4-3-5-1-唯一索引等值查询"><a href="#4-3-5-1-唯一索引等值查询" class="headerlink" title="4.3.5.1.唯一索引等值查询"></a>4.3.5.1.唯一索引等值查询</h5><ul><li>当查询的记录是存在的,next-key lock 会退化成【记录锁】</li><li>当查询的记录是不存在的,next-key lock 会退化成【间隙锁】</li></ul><h5 id="4-3-5-2-非唯一索引等值查询"><a href="#4-3-5-2-非唯一索引等值查询" class="headerlink" title="4.3.5.2.非唯一索引等值查询"></a>4.3.5.2.非唯一索引等值查询</h5><ul><li>当查询的记录存在时,除了会加 next-key lock 外,还额外加间隙锁,也就是会加两把锁。</li><li>当查询的记录不存在时,只会加 next-key lock,然后会退化为间隙锁,也就是只会加一把锁。</li></ul><h2 id="5-乐观锁-悲观锁"><a href="#5-乐观锁-悲观锁" class="headerlink" title="5.乐观锁&amp;悲观锁"></a>5.乐观锁&amp;悲观锁</h2><p>在MySQL中,无论是悲观锁还是乐观锁,都是人们对概念的一种思想抽象,它们本身还是利用 MySQL提供的锁机制来实现的。其实,除了在MySQL数据,像 Java语言里面也有乐观锁和悲观锁的概念。</p><ul><li>悲观锁,可以理解成:在对任意记录进行修改前,先尝试为该记录加上排他锁(exclusive locking),采用的是先获取锁再操作数据的策略,可能会产生死锁;</li><li>乐观锁,是相对悲观锁而言,一般不会利用数据库的锁机制,而是采用类似版本号比较之类的操作,因此乐观锁不会产生死锁的问题;</li></ul><h2 id="6-死锁-死锁检测"><a href="#6-死锁-死锁检测" class="headerlink" title="6.死锁&amp;死锁检测"></a>6.死锁&amp;死锁检测</h2><p>当并发系统中不同线程出现循环资源依赖,涉及的线程都在等待别的线程释放资源时,就会导致这几个线程都进入无限等待的状态,称为死锁。可以通过下面的指令查看死锁</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">show</span> engine innodb status\G</span><br></pre></td></tr></table></figure><p>当出现死锁以后,有两种策略:</p><ul><li>一种策略是,直接进入等待,直到超时。这个超时时间可以通过参数 innodb_lock_wait_timeout 来设置,InnoDB 中 innodb_lock_wait_timeout 的默认值是 50s。</li><li>另一种策略是,发起死锁检测,发现死锁后,主动回滚死锁链条中的某一个事务,让其它事务得以继续执行。将参数 innodb_deadlock_detect 设置为 on,表示开启死锁检测。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/10/107af072/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker基础命令速查指南：从入门到实践</title>
      <link>https://blog.eucalyptus.cc/2024/07/03/3b094401/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/03/3b094401/</guid>
      <pubDate>Wed, 03 Jul 2024 05:53:53 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;Docker是什么？&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;“Docker”一词指代了多个概念，包括开源社区项目、开源项目使用的工具、主导支持此类项目的公司 Docker</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>Docker是什么？</strong></p><p>“Docker”一词指代了多个概念，包括开源社区项目、开源项目使用的工具、主导支持此类项目的公司 Docker Inc.，以及该公司官方支持的工具。这些技术和公司的同名可能会造成混淆。</p><p>以下简要说明 Docker 以便区分：</p><ul><li>IT 软件”Docker”是支持创建和使用 Linux® 容器的容器化技术。</li><li>开源 Docker 社区致力于改进这类技术，并免费提供给所有用户，使之获益。</li><li>Docker Inc. 公司凭借 Docker 社区产品起家，主要负责提升社区版本的安全性，并将技术进步与广大技术社区分享。此外，它还专门对这些技术产品进行完善和安全固化，以服务于企业客户。</li><li>借助 Docker，您可将容器当做轻巧、模块化的虚拟机来使用。同时，您还将获得高度灵活性，实现对容器的高效创建、部署及复制，并在环境之间迁移它们，从而有助于您针对云来优化应用。</li></ul><h2 id="镜像管理"><a href="#镜像管理" class="headerlink" title="镜像管理"></a>镜像管理</h2><h3 id="搜索镜像"><a href="#搜索镜像" class="headerlink" title="搜索镜像"></a>搜索镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker search 镜像的名字</span><br></pre></td></tr></table></figure><h3 id="拉取镜像"><a href="#拉取镜像" class="headerlink" title="拉取镜像"></a>拉取镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker pull 镜像的名字</span><br></pre></td></tr></table></figure><h3 id="查看本地镜像"><a href="#查看本地镜像" class="headerlink" title="查看本地镜像"></a>查看本地镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">docker images</span><br><span class="line"></span><br><span class="line">docker image <span class="built_in">ls</span></span><br><span class="line"></span><br><span class="line">docker images -q 只列出镜像的<span class="built_in">id</span></span><br><span class="line"></span><br><span class="line">docker images --format <span class="string">&quot;&#123;&#123;.ID&#125;&#125;--&#123;&#123;.Repository&#125;&#125;&quot;</span> 格式化显示镜像</span><br><span class="line"></span><br><span class="line">docker images --format <span class="string">&quot; table &#123;&#123;.ID&#125;&#125;\t&#123;&#123;.Repository&#125;&#125;\t&#123;&#123;.Tag&#125;&#125;&quot;</span> 以表格形式显示</span><br></pre></td></tr></table></figure><h3 id="删除镜像"><a href="#删除镜像" class="headerlink" title="删除镜像"></a>删除镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">docker rmi 镜像<span class="built_in">id</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 批量删除镜像</span></span><br><span class="line">docker rmi `docker images -qa</span><br></pre></td></tr></table></figure><h3 id="导入镜像"><a href="#导入镜像" class="headerlink" title="导入镜像"></a>导入镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 导入打包后的镜像</span></span><br><span class="line">docker image load -i /opt/centos7.8.2003.tar</span><br><span class="line"></span><br><span class="line"><span class="comment"># 导入打包压缩后的镜像</span></span><br><span class="line">zstd -dc /opt/centos-stream9.tar.zst | docker image load</span><br></pre></td></tr></table></figure><h3 id="导出镜像"><a href="#导出镜像" class="headerlink" title="导出镜像"></a>导出镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 打包</span></span><br><span class="line">docker image save centos-stream9:cs9 &gt; /opt/centos-stream9.tar</span><br><span class="line"></span><br><span class="line"><span class="comment"># 打包并压缩</span></span><br><span class="line">docker image save centos-stream9:cs9 | zstd -o /opt/centos-stream9.tar.zst</span><br><span class="line"></span><br><span class="line"><span class="comment"># 注意：打包时会占用临时空间</span></span><br></pre></td></tr></table></figure><h3 id="查看镜像详细信息"><a href="#查看镜像详细信息" class="headerlink" title="查看镜像详细信息"></a>查看镜像详细信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker image inspect 镜像<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h2 id="容器管理"><a href="#容器管理" class="headerlink" title="容器管理"></a>容器管理</h2><h3 id="启动容器"><a href="#启动容器" class="headerlink" title="启动容器"></a>启动容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line">docker run -p 85:80 nginx  <span class="comment"># 容器的端口映射85是宿主机的端口，80是容器的端口</span></span><br><span class="line">docker run -P nginx  <span class="comment"># 随机端口映射</span></span><br><span class="line">docker run -it --<span class="built_in">rm</span> -d --name <span class="built_in">test</span> --ip 192.168.159.152 容器<span class="built_in">id</span>/名字 bash/sh</span><br><span class="line"></span><br><span class="line"><span class="comment"># -i 交互式命令操作</span></span><br><span class="line"><span class="comment"># -t 开启一个终端</span></span><br><span class="line"><span class="comment"># bash 在进入容器后执行的命令，相当于shell解释器</span></span><br><span class="line"><span class="comment"># --rm 容器挂了后自动删除容器记录</span></span><br><span class="line"><span class="comment"># -d 在后台运行</span></span><br><span class="line"><span class="comment"># --name test 给容器起一个名字叫test</span></span><br><span class="line"><span class="comment"># --restart=always 容器挂了后自动重启</span></span><br><span class="line"><span class="comment"># --net 网桥名字</span></span><br><span class="line"><span class="comment"># --ip 分配容器的ip</span></span><br><span class="line"><span class="comment"># --cpus=0.5 限制cpu的使用率</span></span><br><span class="line"><span class="comment"># --privileged=true 启用容器的超级权限，启用超级权限的时候需要以/usr/sbin/init命令启动不然超级权限不会生效</span></span><br></pre></td></tr></table></figure><p>注意事项：</p><ul><li>docker run 等于创建加启动，如果镜像不存在在本地则会去下载镜像</li><li>容器内的进程必须处于前台运行状态，否则容器会直接退出</li><li>如果容器内，什么事也不做，容器也会挂掉，容器内，必须有一个进程在前台运行，例如 <code>docker run nginx</code> 容器会直接挂掉</li></ul><h3 id="进入容器"><a href="#进入容器" class="headerlink" title="进入容器"></a>进入容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">exec</span> -it 容器<span class="built_in">id</span> bash  <span class="comment"># 进入正在运行的容器</span></span><br></pre></td></tr></table></figure><h3 id="查看运行的容器"><a href="#查看运行的容器" class="headerlink" title="查看运行的容器"></a>查看运行的容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker ps</span><br></pre></td></tr></table></figure><h3 id="查看停止的容器"><a href="#查看停止的容器" class="headerlink" title="查看停止的容器"></a>查看停止的容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker ps -a</span><br></pre></td></tr></table></figure><h3 id="容器的重启、停止、启动"><a href="#容器的重启、停止、启动" class="headerlink" title="容器的重启、停止、启动"></a>容器的重启、停止、启动</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker restart/stop/start 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="查看容器的详细信息"><a href="#查看容器的详细信息" class="headerlink" title="查看容器的详细信息"></a>查看容器的详细信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker container inspect 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="查看容器端口转发情况"><a href="#查看容器端口转发情况" class="headerlink" title="查看容器端口转发情况"></a>查看容器端口转发情况</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker port 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="查看容器内进程信息"><a href="#查看容器内进程信息" class="headerlink" title="查看容器内进程信息"></a>查看容器内进程信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker top 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="查看容器内资源"><a href="#查看容器内资源" class="headerlink" title="查看容器内资源"></a>查看容器内资源</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker stats 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="查看容器的具体信息"><a href="#查看容器的具体信息" class="headerlink" title="查看容器的具体信息"></a>查看容器的具体信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker inspect 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="传输本地文件到容器中"><a href="#传输本地文件到容器中" class="headerlink" title="传输本地文件到容器中"></a>传输本地文件到容器中</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">cp</span> 本地文件路径 容器ID:容器中的存储路径</span><br></pre></td></tr></table></figure><h3 id="传输容器中的文件到本地"><a href="#传输容器中的文件到本地" class="headerlink" title="传输容器中的文件到本地"></a>传输容器中的文件到本地</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">cp</span> 容器ID:容器中的路径 本地存储路径</span><br></pre></td></tr></table></figure><h3 id="退出容器"><a href="#退出容器" class="headerlink" title="退出容器"></a>退出容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">exit</span></span><br></pre></td></tr></table></figure><h3 id="只删除容器，volume保留"><a href="#只删除容器，volume保留" class="headerlink" title="只删除容器，volume保留"></a>只删除容器，volume保留</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">rm</span> 容器<span class="built_in">id</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 强制删除容器</span></span><br><span class="line">docker <span class="built_in">rm</span> -f 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h3 id="阻塞容器"><a href="#阻塞容器" class="headerlink" title="阻塞容器"></a>阻塞容器</h3><p>用于阻塞 docker 容器，并在容器退出时打印退出码，当容器不在运行的时候，直接输出 0；可以用来监控容器是否正常退出。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">wait</span> 容器ID/容器名字</span><br></pre></td></tr></table></figure><h3 id="删除容器，同时删除volume"><a href="#删除容器，同时删除volume" class="headerlink" title="删除容器，同时删除volume"></a>删除容器，同时删除volume</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">rm</span> -v 容器ID</span><br><span class="line"></span><br><span class="line">docker <span class="built_in">rm</span> --volumes 容器ID</span><br></pre></td></tr></table></figure><h3 id="查看容器资源使用情况"><a href="#查看容器资源使用情况" class="headerlink" title="查看容器资源使用情况"></a>查看容器资源使用情况</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker stats &lt;container_name_or_id&gt;</span><br></pre></td></tr></table></figure><h3 id="容器打包成镜像"><a href="#容器打包成镜像" class="headerlink" title="容器打包成镜像"></a>容器打包成镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">docker commit [OPTIONS] CONTAINER [REPOSITORY[:TAG]]</span><br><span class="line"></span><br><span class="line">docker commit -a <span class="string">&#x27;LML&#x27;</span> -m <span class="string">&#x27;This is a container image&#x27;</span> 容器ID 容器打包后的镜像名字:标签</span><br></pre></td></tr></table></figure><table><thead><tr><th>Option</th><th>功能</th></tr></thead><tbody><tr><td>-a</td><td>指定新镜像作者</td></tr><tr><td>-c</td><td>使用 Dockerfile 指令来创建镜像</td></tr><tr><td>-m</td><td>提交生成镜像的说明信息</td></tr><tr><td>-p</td><td>在 commit 时，将容器暂停</td></tr></tbody></table><h3 id="容器打包成tar包"><a href="#容器打包成tar包" class="headerlink" title="容器打包成tar包"></a>容器打包成tar包</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">docker save -o tar包名称.tar 待打包镜像名称:待打包镜像版本</span><br><span class="line"></span><br><span class="line"><span class="comment"># 演示：</span></span><br><span class="line">docker save -o mysql-lml-docker.tar mysql-lml-docker:v1.0</span><br></pre></td></tr></table></figure><h3 id="tar包载入镜像"><a href="#tar包载入镜像" class="headerlink" title="tar包载入镜像"></a>tar包载入镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">docker load [OPTIONS] tar包名称.tar</span><br><span class="line"></span><br><span class="line"><span class="comment"># 演示：</span></span><br><span class="line">docker load -i mysql-lml-docker.tar</span><br></pre></td></tr></table></figure><h2 id="日志管理"><a href="#日志管理" class="headerlink" title="日志管理"></a>日志管理</h2><h3 id="查看容器日志"><a href="#查看容器日志" class="headerlink" title="查看容器日志"></a>查看容器日志</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 所有日志</span></span><br><span class="line">docker logs 容器<span class="built_in">id</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 相当于tail -f，实时的刷新日志</span></span><br><span class="line">docker logs -f 容器<span class="built_in">id</span></span><br></pre></td></tr></table></figure><h2 id="网络管理"><a href="#网络管理" class="headerlink" title="网络管理"></a>网络管理</h2><h3 id="列出所有网桥"><a href="#列出所有网桥" class="headerlink" title="列出所有网桥"></a>列出所有网桥</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network <span class="built_in">ls</span></span><br></pre></td></tr></table></figure><h3 id="查看网络信息"><a href="#查看网络信息" class="headerlink" title="查看网络信息"></a>查看网络信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network inspect 网络类型</span><br></pre></td></tr></table></figure><h3 id="创建新的网桥"><a href="#创建新的网桥" class="headerlink" title="创建新的网桥"></a>创建新的网桥</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network create --subnet=192.168.159.0/24 NetTest</span><br></pre></td></tr></table></figure><h3 id="删除创建的网桥"><a href="#删除创建的网桥" class="headerlink" title="删除创建的网桥"></a>删除创建的网桥</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network <span class="built_in">rm</span> net_name</span><br></pre></td></tr></table></figure><h3 id="将容器加入自建网络中"><a href="#将容器加入自建网络中" class="headerlink" title="将容器加入自建网络中"></a>将容器加入自建网络中</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network connect 网络名称 容器名称</span><br></pre></td></tr></table></figure><h3 id="将容器退出自建网络中"><a href="#将容器退出自建网络中" class="headerlink" title="将容器退出自建网络中"></a>将容器退出自建网络中</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker network disconnect 网络名称 容器名称</span><br></pre></td></tr></table></figure><h2 id="命名卷管理"><a href="#命名卷管理" class="headerlink" title="命名卷管理"></a>命名卷管理</h2><h3 id="列出所有的volume"><a href="#列出所有的volume" class="headerlink" title="列出所有的volume"></a>列出所有的volume</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume <span class="built_in">ls</span></span><br></pre></td></tr></table></figure><h3 id="删除未使用的volume"><a href="#删除未使用的volume" class="headerlink" title="删除未使用的volume"></a>删除未使用的volume</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume prune</span><br></pre></td></tr></table></figure><h3 id="查看volume信息"><a href="#查看volume信息" class="headerlink" title="查看volume信息"></a>查看volume信息</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume inspect 命名卷名字</span><br></pre></td></tr></table></figure><h3 id="删除volume"><a href="#删除volume" class="headerlink" title="删除volume"></a>删除volume</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume <span class="built_in">rm</span> 命名卷的卷名</span><br></pre></td></tr></table></figure><h3 id="创建volume"><a href="#创建volume" class="headerlink" title="创建volume"></a>创建volume</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume create 命名卷名字</span><br></pre></td></tr></table></figure><h2 id="进阶命令"><a href="#进阶命令" class="headerlink" title="进阶命令"></a>进阶命令</h2><h3 id="查看所有的容器和镜像大小"><a href="#查看所有的容器和镜像大小" class="headerlink" title="查看所有的容器和镜像大小"></a>查看所有的容器和镜像大小</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker system <span class="built_in">df</span></span><br></pre></td></tr></table></figure><h3 id="回收悬空的镜像"><a href="#回收悬空的镜像" class="headerlink" title="回收悬空的镜像"></a>回收悬空的镜像</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker image prune -a</span><br></pre></td></tr></table></figure><h3 id="删除所有已停用的容器"><a href="#删除所有已停用的容器" class="headerlink" title="删除所有已停用的容器"></a>删除所有已停用的容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker container prune</span><br></pre></td></tr></table></figure><h3 id="回收孤儿卷（无容器使用）"><a href="#回收孤儿卷（无容器使用）" class="headerlink" title="回收孤儿卷（无容器使用）"></a>回收孤儿卷（无容器使用）</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker volume prune</span><br></pre></td></tr></table></figure><h3 id="批量删除（网络，数据卷，镜像…）"><a href="#批量删除（网络，数据卷，镜像…）" class="headerlink" title="批量删除（网络，数据卷，镜像…）"></a>批量删除（网络，数据卷，镜像…）</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">docker system prune  <span class="comment"># 仅中间层 + 停止容器</span></span><br><span class="line"></span><br><span class="line">docker system prune -a  <span class="comment"># 再加&quot;无用&quot;镜像</span></span><br><span class="line"></span><br><span class="line">docker system prune -a --volumes  <span class="comment"># 连无用卷一起</span></span><br></pre></td></tr></table></figure><h3 id="启停全部容器"><a href="#启停全部容器" class="headerlink" title="启停全部容器"></a>启停全部容器</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker stop/start $(docker ps -aq -f <span class="string">&quot;status=running/exited/created/paused&quot;</span>)</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/03/3b094401/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】Percona XtraBackup总结篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/02/cd549a55/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/02/cd549a55/</guid>
      <pubDate>Tue, 02 Jul 2024 09:56:44 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;h2 id=&quot;1-前言&quot;&gt;&lt;a href=&quot;#1-前言&quot; class=&quot;headerlink&quot; title=&quot;1.前言&quot;&gt;&lt;/a&gt;1.前言&lt;/h2&gt;&lt;p&gt;在历经了详尽的探索之旅,从【MySQL备份】Percona</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><h2 id="1-前言"><a href="#1-前言" class="headerlink" title="1.前言"></a>1.前言</h2><p>在历经了详尽的探索之旅,从【MySQL备份】Percona XtraBackup全量备份的基础构筑,到【MySQL备份】增量备份的灵活运用;从【MySQL备份】压缩备份的高效策略,再到【MySQL备份】加密备份的安全深潜,这一系列实战篇章不仅铺陈了Percona XtraBackup这一强大工具的全方位应用,更是在实践中逐步揭示了数据保护的艺术。如今,站在这一知识体系的交汇点,本文旨在整合与升华,回顾并总结前四篇精华,提炼关键洞察,解答疑惑,巩固您的MySQL备份与恢复技能。</p><p>我们将再度审视全量备份的基石作用,强调其在数据保护计划中的不可替代性;剖析增量备份的精妙之处,展示如何在数据量剧增时保持备份的高效与敏捷;深入讨论压缩备份的策略,揭秘如何在资源有限的环境下最大化存储效率;最后,聚焦于加密备份的核心价值,强调在数据隐私与合规性日益重要的当下,如何构建坚不可摧的数据安全网。</p><p>通过这一综合回顾,您不仅将获得一套完善且实战性强的MySQL备份解决方案,更能深刻理解在不同业务场景下,如何灵活运用Percona XtraBackup的各项特性,以应对复杂多变的数据保护挑战。让我们一同复盘学习历程,巩固所学,确保在未来的数据管理路上,每一步都走得稳健而自信。</p><h2 id="2-问题总结"><a href="#2-问题总结" class="headerlink" title="2.问题总结"></a>2.问题总结</h2><h3 id="2-1-为什么在恢复备份前需要准备备份"><a href="#2-1-为什么在恢复备份前需要准备备份" class="headerlink" title="2.1.为什么在恢复备份前需要准备备份"></a>2.1.为什么在恢复备份前需要准备备份</h3><h4 id="2-1-1-保证数据一致性"><a href="#2-1-1-保证数据一致性" class="headerlink" title="2.1.1. 保证数据一致性"></a>2.1.1. 保证数据一致性</h4><p>InnoDB存储引擎利用事务日志 Redo Log 来确保事务的ACID特性,即原子性 Atomicity 、一致性 Consistency 、隔离性 Isolation 、持久性 Durability 。在备份过程中,Xtrabackup捕获的是数据库某一时刻的静态数据快照以及在此期间所有未完成事务的Redo Log信息。准备备份阶段会应用这些Redo Log到数据文件上,确保所有活跃事务被正确地提交或回滚,从而保证恢复后的数据文件处于一个一致的状态,与备份时点的数据库状态完全相同。</p><h4 id="2-1-2-完成崩溃恢复过程"><a href="#2-1-2-完成崩溃恢复过程" class="headerlink" title="2.1.2. 完成崩溃恢复过程"></a>2.1.2. 完成崩溃恢复过程</h4><p>Xtrabackup的准备备份过程类似于数据库的崩溃恢复 Crash Recovery 过程。在备份期间,数据库可能还在接受新的写入操作。准备备份阶段通过应用备份时的Redo Log,相当于模拟了一次数据库的崩溃重启恢复,确保了备份数据的完整性和一致性,这样恢复后的数据库可以直接使用,无需再次经历崩溃恢复流程。</p><h4 id="2-1-3-解决非锁定备份的特殊需求"><a href="#2-1-3-解决非锁定备份的特殊需求" class="headerlink" title="2.1.3. 解决非锁定备份的特殊需求"></a>2.1.3. 解决非锁定备份的特殊需求</h4><p>当使用<code>--no-lock</code>或<code>--lock-ddl-per-table</code>选项执行非锁定备份时,Xtrabackup并不会锁住整个数据库,允许备份过程中数据库继续处理写操作。这种备份方式虽然减少了备份对在线服务的影响,但也意味着备份时点的数据并不完全静止。准备备份阶段通过应用备份期间的事务日志,解决了数据不一致的问题,使得备份数据在恢复后能够正确反映备份时的实际数据库状态。</p><h4 id="2-1-4-支持增量和差异备份"><a href="#2-1-4-支持增量和差异备份" class="headerlink" title="2.1.4. 支持增量和差异备份"></a>2.1.4. 支持增量和差异备份</h4><p>在增量或差异备份的场景中,每次备份仅记录自上次备份以来发生变化的部分。在恢复时,必须顺序恢复全量备份,然后依次恢复每个增量或差异备份,并在每个备份之间执行准备步骤,以确保所有变化按正确的顺序应用,最终形成一个完整的、一致的数据库状态。</p><h4 id="2-1-5-优化恢复性能"><a href="#2-1-5-优化恢复性能" class="headerlink" title="2.1.5. 优化恢复性能"></a>2.1.5. 优化恢复性能</h4><p>准备备份阶段还可以进行一些优化操作,例如整理数据页,减少碎片,提高恢复后的数据库性能。尽管这不是准备备份的主要目的,但在某些情况下,它也可以带来额外的好处。</p><p>总之,准备备份是Xtrabackup备份恢复流程中的核心步骤,它确保了备份数据在恢复到生产环境之前的一致性、完整性和适用性,是实现可靠数据恢复策略的关键环节。</p><h3 id="2-2-Percona-XtraBackup的工作原理"><a href="#2-2-Percona-XtraBackup的工作原理" class="headerlink" title="2.2.Percona XtraBackup的工作原理"></a>2.2.Percona XtraBackup的工作原理</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img1.avif"></p><p><strong>文字描述:</strong></p><ul><li><code>innobackupex</code> 在启动后,会先 fork 一个进程,启动 <code>xtrabackup</code>进程,然后就等待 <code>xtrabackup</code> 备份完 ibd 数据文件;</li><li><code>xtrabackup</code> 在备份 InnoDB 相关数据时,是有2种线程的,1种是 redo 拷贝线程,负责拷贝 redo 文件,1种是 ibd 拷贝线程,负责拷贝 ibd 文件;redo 拷贝线程只有一个,在 ibd 拷贝线程之前启动,在 ibd 线程结束后结束。<code>xtrabackup</code> 进程开始执行后,先启动 redo 拷贝线程,从最新的 checkpoint 点开始顺序拷贝 redo 日志;然后再启动 ibd 数据拷贝线程,在 <code>xtrabackup</code> 拷贝 ibd 过程中,<code>innobackupex</code> 进程一直处于等待状态 等待文件被创建 。</li><li><code>xtrabackup</code> 拷贝完成idb后,通知 <code>innobackupex</code> 通过创建文件 ,同时自己进入等待 redo 线程仍然继续拷贝 ;</li><li><code>innobackupex</code> 收到 <code>xtrabackup</code> 通知后,执行<code>FLUSH TABLES WITH READ LOCK</code> (FTWRL),取得一致性位点,然后开始备份非 InnoDB 文件 包括 frm、MYD、MYI、CSV、opt、par等 。拷贝非 InnoDB 文件过程中,因为数据库处于全局只读状态,如果在业务的主库备份的话,要特别小心,非 InnoDB 表 主要是MyISAM 比较多的话整库只读时间就会比较长,这个影响一定要评估到。</li><li>当 <code>innobackupex</code> 拷贝完所有非 InnoDB 表文件后,通知 <code>xtrabackup</code> 通过删文件 ,同时自己进入等待 等待另一个文件被创建 ;</li><li><code>xtrabackup</code> 收到 <code>innobackupex</code> 备份完非 InnoDB 通知后,就停止 redo 拷贝线程,然后通知 <code>innobackupex</code> redo log 拷贝完成 通过创建文件 ;</li><li><code>innobackupex</code> 收到 redo 备份完成通知后,就开始解锁,执行 <code>UNLOCK TABLES</code>;</li><li>最后 <code>innobackupex</code> 和 <code>xtrabackup</code> 进程各自完成收尾工作,如资源的释放、写备份元数据信息等,<code>innobackupex</code> 等待 <code>xtrabackup</code> 子进程结束后退出。</li></ul><p>具体细节看官方文档 :<a href="https://docs.percona.com/percona-xtrabackup/2.4/how_xtrabackup_works.html">Percona XtraBackup的工作原理</a></p><p>3.注意和补充</p><ul><li>在恢复备份前需要停止数据库</li><li>恢复数据时,一定要记得更改数据目录下的文件拥有者以及所属组权限,否则mysql无法启动</li><li>使用xtrabackup工具进行恢复数据时,需要提前删除MySQL数据目录下的数据</li><li>当然除了前面文章中提到的几种备份方式,还有<strong>部分备份</strong>、<strong>分区备份</strong>等,不同的备份方式就是利用不同的参数实现不同的功能</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/02/cd549a55/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】Percona XtraBackup加密备份实战篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/02/3b3504ce/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/02/3b3504ce/</guid>
      <pubDate>Tue, 02 Jul 2024 09:31:59 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;p&gt;** 实战演练:利用Percona XtraBackup执行MySQL加密备份操作详解 **&lt;/p&gt;
&lt;h2 id=&quot;1-前言&quot;&gt;&lt;a href=&quot;#1-前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><p>** 实战演练:利用Percona XtraBackup执行MySQL加密备份操作详解 **</p><h2 id="1-前言"><a href="#1-前言" class="headerlink" title="1.前言"></a>1.前言</h2><p>继探索了【MySQL备份】Percona XtraBackup压缩备份实战篇后,本文将进一步深入,揭开Percona XtraBackup加密备份的神秘面纱,解锁数据安全的高级实践策略。</p><p>在数据保护日益重要的今天,仅仅实现备份是不够的,确保备份数据的私密性和安全性成为新的挑战。Percona XtraBackup,这一MySQL备份领域的佼佼者,不仅以其快速、高效著称,还内置了强大的加密功能,为你的数据库备份穿上坚不可摧的防护盔甲。本篇文章将引领你步入加密备份的实战殿堂,细致剖析如何在Percona XtraBackup中实施加密备份,为敏感信息构建一道坚固的安全防线。</p><p>我们不仅会介绍如何启用加密选项,选用合适的加密算法 如AES128、AES192、AES256 来为备份过程加码,还会深入讨论密钥管理的策略与实践,确保加密密钥如同保险箱的钥匙,既强大又安全地守护着你的数据宝藏。同时,考虑到实际操作中的效率与安全性平衡,文中还将涵盖并行加密技术的应用,让你在享受加密带来的安全保障的同时,也能保持备份的高效性。</p><p>此外,文章还将指导你如何在需要时,正确且安全地利用之前加密的备份进行数据恢复,确保在任何紧急情况下,都能迅速且无缝地恢复数据,让业务连续性得到最强有力的保障。</p><p>总之,本文不仅是对Percona XtraBackup加密备份功能的一次全面梳理,更是一份实战手册,旨在帮助你掌握高级数据保护技能,无论面对何种威胁,都能确保数据的绝对安全。让我们一起深入探究,为你的数据库备份战略增添一份不容忽视的安全力量。</p><h2 id="2-准备工作"><a href="#2-准备工作" class="headerlink" title="2.准备工作"></a>2.准备工作</h2><h3 id="2-1-环境信息"><a href="#2-1-环境信息" class="headerlink" title="2.1.环境信息"></a>2.1.环境信息</h3><table><thead><tr><th>主机IP</th><th>操作系统</th><th>Mysql版本</th><th>XtraBackup版本</th></tr></thead><tbody><tr><td>172.17.0.2</td><td>CentOS Stream release 9</td><td>8.0.37</td><td>8.0.35</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr></tbody></table><h3 id="2-2-配置-etc-my-cnf文件"><a href="#2-2-配置-etc-my-cnf文件" class="headerlink" title="2.2.配置&#x2F;etc&#x2F;my.cnf文件"></a>2.2.配置&#x2F;etc&#x2F;my.cnf文件</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">[xtrabackup]</span><br><span class="line">host localhost</span><br><span class="line">port 3306</span><br><span class="line">user root</span><br><span class="line">password 123456</span><br><span class="line">socket /var/lib/mysql/mysql.sock</span><br></pre></td></tr></table></figure><h3 id="2-3-授予root用户BACKUP-ADMIN权限"><a href="#2-3-授予root用户BACKUP-ADMIN权限" class="headerlink" title="2.3.授予root用户BACKUP_ADMIN权限"></a>2.3.授予root用户BACKUP_ADMIN权限</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">grant</span> BACKUP_ADMIN <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;root&#x27;</span> <span class="string">&#x27;%&#x27;</span></span><br></pre></td></tr></table></figure><p> LOCK INSTANCE FOR BACKUP 是MySQL 8.0引入的一种新的备份相关SQL语句,主要用于在进行数据库备份时,以一种更为细粒度和高效的方式控制对数据库实例的访问,以保证备份的一致性。这个命令的工作原理及特点如下:</p><p><strong>目的</strong>:在执行备份操作时,此命令用于获取一个实例级别的锁,该锁允许在备份过程中继续执行DML 数据操作语言,如INSERT、UPDATE、DELETE 操作,同时防止那些可能导致数据快照不一致的DDL 数据定义语言,如CREATE、ALTER、DROP 操作和某些管理操作。这样可以在不影响数据库服务的情况下进行备份,特别适用于需要最小化服务中断的在线备份场景。</p><p><strong>权限需求</strong>:执行LOCK INSTANCE FOR BACKUP语句需要用户具备BACKUP_ADMIN权限。这是一个专门为了备份相关的高级操作而设计的权限级别。</p><p>**兼容性:**此特性是在MySQL 8.0及以上版本中引入的,早于8.0的MySQL版本并不支持这一语句,因此在使用旧版本时,可能需要依赖其他机制 如FLUSH TABLES WITH READ LOCK 来确保备份的一致性。</p><p>**解锁:**执行备份后,需要使用UNLOCK INSTANCE语句来释放之前由LOCK INSTANCE FOR BACKUP获得的锁,从而恢复正常操作。</p><p><strong>与传统备份命令的对比</strong>:相比于传统的备份方法,如使用FLUSH TABLES WITH READ LOCK,LOCK INSTANCE FOR BACKUP提供了更小的性能影响,因为它不会完全阻止写操作,只是限制了可能引起数据不一致的活动,更适合于高可用性和高性能要求的生产环境。</p><h3 id="2-4-生成加密密钥"><a href="#2-4-生成加密密钥" class="headerlink" title="2.4.生成加密密钥"></a>2.4.生成加密密钥</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">openssl rand -base64 24</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img1.avif"></p><h3 id="2-5-配置加密密钥文件"><a href="#2-5-配置加密密钥文件" class="headerlink" title="2.5.配置加密密钥文件"></a>2.5.配置加密密钥文件</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img2.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">echo</span> -n VCGgD7I04P/kBhwSzBUvK4fyT214H9XP &gt; /data/keyfile</span><br></pre></td></tr></table></figure><h2 id="3-加密备份"><a href="#3-加密备份" class="headerlink" title="3.加密备份"></a>3.加密备份</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img3.avif"></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --target-dir /data/backups --encrypt AES256 \</span><br><span class="line">--encrypt-key VCGgD7I04P/kBhwSzBUvK4fyT214H9XP</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>或者</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --target-dir /data/backups/ --encrypt AES256 \</span><br><span class="line">--encrypt-key-file /data/keyfile</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img5.avif"></p><h2 id="4-优化加密过程"><a href="#4-优化加密过程" class="headerlink" title="4.优化加密过程"></a>4.优化加密过程</h2><p> 加密备份中引入了两个选项,可用于 加快加密过程这些是 <code>xtrabackup --encrypt-threads</code>和 <code>xtrabackup --encrypt-chunk-size</code>.通过使用 <code>xtrabackup --encrypt-threads</code>选项 可以指定多个线程用于并行加密。选项<code>xtrabackup --encrypt-chunk-size</code>可用于指定大小 以 字节 默认值为 64K 。</p><h2 id="5-解密加密备份"><a href="#5-解密加密备份" class="headerlink" title="5.解密加密备份"></a>5.解密加密备份</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --decrypt AES256 --encrypt-key-file /data/keyfile \</span><br><span class="line">--target-dir /data/backups/</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img7.avif"></p><h2 id="6-准备加密备份"><a href="#6-准备加密备份" class="headerlink" title="6.准备加密备份"></a>6.准备加密备份</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --prepare --target-dir /data/backups/</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img9.avif"></p><h2 id="7-恢复加密备份"><a href="#7-恢复加密备份" class="headerlink" title="7.恢复加密备份"></a>7.恢复加密备份</h2><h3 id="7-1-使用rsync进行恢复"><a href="#7-1-使用rsync进行恢复" class="headerlink" title="7.1.使用rsync进行恢复"></a>7.1.使用rsync进行恢复</h3><p><strong>停止MySQL服务进行恢复数据</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br><span class="line">rsync <span class="operator">-</span>avrP <span class="operator">/</span>data<span class="operator">/</span>backups<span class="operator">/</span> <span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span></span><br></pre></td></tr></table></figure><p> **恢复数据时,一定要记得更改数据目录下的文件拥有者以及所属组权限,否则mysql无法启动  **</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">chown</span> -R mysql.mysql /var/lib/mysql</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>重启MySQL服务</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl <span class="keyword">start</span> mysqld</span><br></pre></td></tr></table></figure><h3 id="7-2-使用xtrabackup命令恢复"><a href="#7-2-使用xtrabackup命令恢复" class="headerlink" title="7.2.使用xtrabackup命令恢复"></a>7.2.使用xtrabackup命令恢复</h3><p><strong>使用xtrabackup命令恢复之前需要删除MySQL数据目录</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">rm</span> -rf /var/lib/mysql/*</span><br></pre></td></tr></table></figure><p><strong>停止MySQL服务</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br></pre></td></tr></table></figure><p><strong>xtrabackup有一个<code>xtrabackup --copy-back</code>选项,它执行 将备份恢复到服务器的datadir</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --copy-back --target-dir /data/backups/</span><br></pre></td></tr></table></figure><p> <strong>恢复数据时,一定要记得更改数据目录下的文件拥有者以及所属组权限,否则mysql无法启动</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">chown</span> -R mysql.mysql /var/lib/mysql</span><br></pre></td></tr></table></figure><p> <strong>重启MySQL服务</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl <span class="keyword">start</span> mysqld</span><br></pre></td></tr></table></figure><h2 id="8-总结"><a href="#8-总结" class="headerlink" title="8.总结"></a>8.总结</h2><p>本篇文章和前面的文章其实没有什么区别,都是利用不同的参数实现不同的需求。本篇文章还介绍到了使用xtrabackup命令恢复备份,这里有个缺点就是要清除MySQL的数据目录下面的数据,而之前使用的rsync则不需要这个过程。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/02/3b3504ce/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】Percona XtraBackup压缩备份实战篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/02/52768202/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/02/52768202/</guid>
      <pubDate>Tue, 02 Jul 2024 06:11:50 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;blockquote&gt;
&lt;p&gt;** 实战演练:利用Percona XtraBackup执行MySQL压缩备份操作详解 **&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;1-前言&quot;&gt;&lt;a href=&quot;#1-前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><blockquote><p>** 实战演练:利用Percona XtraBackup执行MySQL压缩备份操作详解 **</p></blockquote><h2 id="1-前言"><a href="#1-前言" class="headerlink" title="1.前言"></a>1.前言</h2><p>在延续上篇【MySQL备份】Percona XtraBackup增量备份实战篇的探讨之后,本文将深度挖掘Percona XtraBackup的另一重要维度——压缩备份的实战技巧。继成功导航增量备份的复杂水域后,我们现在转向优化存储空间的策略,探讨如何高效利用压缩技术,确保您的MySQL备份既紧凑又实用。</p><p>通过本篇章节,我们将超越基础备份实践,引领您步入一个更为精细的操作层面,展示如何在不牺牲数据完整性的前提下,运用巧妙的压缩策略减少备份存储占用。您将学习如何无缝集成压缩工具与Percona XtraBackup流程,从备份创建直至恢复的每一步,最大化资源效率,为您的数据保护计划增添灵活性与经济性。</p><p>无论您面临的是日益增长的数据存储压力,还是对提升灾难恢复速度的迫切需求,本文都将提供宝贵的实战指导,帮助您在数据备份的征途上,以更精简的脚印,迈开更坚实的步伐。让我们一同探索,如何在保障业务连续性的基础上,实现备份存储的最优化,开启MySQL备份策略的新篇章</p><h2 id="2-准备工作"><a href="#2-准备工作" class="headerlink" title="2.准备工作"></a>2.准备工作</h2><h3 id="2-1-环境信息"><a href="#2-1-环境信息" class="headerlink" title="2.1.环境信息"></a>2.1.环境信息</h3><table><thead><tr><th>主机IP</th><th>操作系统</th><th>Mysql版本</th><th>XtraBackup版本</th></tr></thead><tbody><tr><td>172.17.0.2</td><td>CentOS Stream release 9</td><td>8.0.37</td><td>8.0.35</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr></tbody></table><h3 id="2-2-配置-etc-my-cnf文件"><a href="#2-2-配置-etc-my-cnf文件" class="headerlink" title="2.2.配置&#x2F;etc&#x2F;my.cnf文件"></a>2.2.配置&#x2F;etc&#x2F;my.cnf文件</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">[xtrabackup]</span><br><span class="line">host localhost</span><br><span class="line">port 3306</span><br><span class="line">user root</span><br><span class="line">password 123456</span><br><span class="line">socket /var/lib/mysql/mysql.sock</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="2-3-授予root用户BACKUP-ADMIN权限"><a href="#2-3-授予root用户BACKUP-ADMIN权限" class="headerlink" title="2.3.授予root用户BACKUP_ADMIN权限"></a>2.3.授予root用户BACKUP_ADMIN权限</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">grant</span> BACKUP_ADMIN <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;root&#x27;</span> <span class="string">&#x27;%&#x27;</span></span><br></pre></td></tr></table></figure><blockquote><p>LOCK INSTANCE FOR BACKUP 是MySQL 8.0引入的一种新的备份相关SQL语句,主要用于在进行数据库备份时,以一种更为细粒度和高效的方式控制对数据库实例的访问,以保证备份的一致性。这个命令的工作原理及特点如下:</p><p>**目的:**在执行备份操作时,此命令用于获取一个实例级别的锁,该锁允许在备份过程中继续执行DML 数据操作语言,如INSERT、UPDATE、DELETE 操作,同时防止那些可能导致数据快照不一致的DDL 数据定义语言,如CREATE、ALTER、DROP 操作和某些管理操作。这样可以在不影响数据库服务的情况下进行备份,特别适用于需要最小化服务中断的在线备份场景。</p><p>**权限需求:**执行LOCK INSTANCE FOR BACKUP语句需要用户具备BACKUP_ADMIN权限。这是一个专门为了备份相关的高级操作而设计的权限级别。</p><p>**兼容性:**此特性是在MySQL 8.0及以上版本中引入的,早于8.0的MySQL版本并不支持这一语句,因此在使用旧版本时,可能需要依赖其他机制 如FLUSH TABLES WITH READ LOCK 来确保备份的一致性。</p><p>**解锁:**执行备份后,需要使用UNLOCK INSTANCE语句来释放之前由LOCK INSTANCE FOR BACKUP获得的锁,从而恢复正常操作。</p><p>与传统备份命令的对比:相比于传统的备份方法,如使用FLUSH TABLES WITH READ LOCK,LOCK INSTANCE FOR BACKUP提供了更小的性能影响,因为它不会完全阻止写操作,只是限制了可能引起数据不一致的活动,更适合于高可用性和高性能要求的生产环境。</p></blockquote><h3 id="2-4-安装qpress"><a href="#2-4-安装qpress" class="headerlink" title="2.4.安装qpress"></a>2.4.安装qpress</h3><p><code>xtrabackup --compress</code>使用<code>qpress</code>工具</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">yum install qpress -y</span><br></pre></td></tr></table></figure><h2 id="3-压缩备份"><a href="#3-压缩备份" class="headerlink" title="3. 压缩备份"></a>3. 压缩备份</h2><p>登陆数据库创建employees2 表,为后面测试做准备</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> employees2(</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT, <span class="comment">-- 自增的ID作为主键</span></span><br><span class="line">first_name <span class="type">VARCHAR</span>(<span class="number">50</span>) <span class="keyword">NOT NULL</span>, <span class="comment">-- 姓名,最大长度50,不能为空</span></span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">100</span>) <span class="keyword">UNIQUE</span>, <span class="comment">-- 电子邮件,最大长度100,必须唯一</span></span><br><span class="line">hire_date <span class="type">DATE</span>, <span class="comment">-- 入职日期</span></span><br><span class="line"><span class="keyword">PRIMARY KEY</span> (id) <span class="comment">-- 指定id列为表的主键</span></span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb4; <span class="comment">-- 使用InnoDB存储引擎,字符集为utf8mb4支持更多字符</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img1.avif"></p><h3 id="3-1-创建压缩备份"><a href="#3-1-创建压缩备份" class="headerlink" title="3.1.创建压缩备份"></a>3.1.创建压缩备份</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --compress --target-dir /data/compressed/</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img4.avif"></p><h3 id="3-2-创建全量备份"><a href="#3-2-创建全量备份" class="headerlink" title="3.2.创建全量备份"></a>3.2.创建全量备份</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --target-dir /data/backup_compressed/</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img6.avif"></p><h3 id="3-3-对比两个备份的大小"><a href="#3-3-对比两个备份的大小" class="headerlink" title="3.3.对比两个备份的大小"></a>3.3.对比两个备份的大小</h3><p>可以看到压缩的备份比没有压缩的备份要小很多</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img7.avif"></p><h2 id="4-解压备份"><a href="#4-解压备份" class="headerlink" title="4.解压备份"></a>4.解压备份</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --decompress --target-dir /data/compressed/</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img8.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img9.avif"></p><h2 id="5-准备备份"><a href="#5-准备备份" class="headerlink" title="5.准备备份"></a>5.准备备份</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --prepare --target-dir /data/compressed/</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img11.avif"></p><h2 id="6-备份恢复"><a href="#6-备份恢复" class="headerlink" title="6.备份恢复"></a>6.备份恢复</h2><p>登陆数据库 删除之前创建的表</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img12.avif"></p><p><strong>停止MySQL服务进行恢复数据</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br><span class="line">rsync <span class="operator">-</span>avrP <span class="operator">/</span>data<span class="operator">/</span>full_backup<span class="operator">/</span> <span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img13.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img14.avif"></p><p><strong>恢复数据时,一定要记得更改数据目录下的文件拥有者以及所属组权限,否则mysql无法启动</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">chown</span> -R mysql.mysql /var/lib/mysql</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img15.avif"></p><p><strong>重启数据库查看数据是否恢复,可以看到之前被删除的表居然没有恢复成功</strong></p><h2 id=""><a href="#" class="headerlink" title=""></a><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img16.avif"></h2><p>7.问题分析</p><p>按道理来说上面的操作应该没有什么问题的,为什么会没有恢复成功呐?刚开始的时候以为是备份的问题,然后将之前对比创建的全量备份进行恢复,但是恢复之后还是没有之前删除的那个表,本来这里准备创建个表然后弄个截图糊弄过去的,但是创建的时候居然报错了</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img17.avif"></p><p>报错这个表是存在的,那为什么看不到呐?既然库中看不到就去看数据目录</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-02/img18.avif"></p><p>查看数据目录的时候明显可以看到这个表是存在的,说明我们备份恢复成功了,但是在数据库中没有显示出来,这是为什么?</p><h2 id="8-总结"><a href="#8-总结" class="headerlink" title="8.总结"></a>8.总结</h2><p>可以看到这篇文章和之前的有一些区别,在使用xtrabackup命令的时候没有像前面一样在命令行中添加参数,这是因为我们将这些信息配置到了&#x2F;etc&#x2F;my.cnf文件【<strong>当您将相关参数 如MySQL的用户名称、密码、端口等 配置到<code>/etc/my.cnf</code>或相应的配置文件中时,Percona XtraBackup等MySQL备份工具在执行命令时就可以自动读取这些配置,因而无需在命令行中显式地添加这些参数。这是因为XtraBackup以及大多数MySQL客户端工具在启动时会按照特定的顺序查找并读取配置文件,包括但不限于<code>/etc/my.cnf</code>、<code>~/.my.cnf</code> 用户家目录下的配置文件 等。</strong> 】。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/02/52768202/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】Percona XtraBackup全量备份实战篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/01/87f98269/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/01/87f98269/</guid>
      <pubDate>Mon, 01 Jul 2024 10:25:55 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;p&gt; 实战演练:利用Percona XtraBackup执行MySQL全量备份操作详解 &lt;/p&gt;
&lt;h2 id=&quot;1-前言&quot;&gt;&lt;a href=&quot;#1-前言&quot; class=&quot;headerlink&quot; title=&quot;1. 前言&quot;&gt;&lt;/a&gt;1.</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><p> 实战演练:利用Percona XtraBackup执行MySQL全量备份操作详解 </p><h2 id="1-前言"><a href="#1-前言" class="headerlink" title="1. 前言"></a>1. 前言</h2><p>本文将继续上篇【MySQL备份】Percona XtraBackup基础篇中对Percona XtraBackup的探索,深化讨论其全量备份技术及详尽的恢复策略。本章节旨在构建一套完备的备份恢复指南,进一步巩固您的数据库安全防线,确保数据资产的万无一失。</p><p>在本篇内容中,我们将细致剖析Percona XtraBackup执行全量备份的高效实践,这一核心功能不仅能够实时捕捉数据库状态的完整映像,还依托其先进的日志处理机制,保证备份数据的绝对一致性和可靠性。您将学习到如何运用简洁明了的命令行指令,安全无碍地将数据库快照存置于指定位置,为数据保护筑起第一道坚固壁垒。</p><p>紧接着,文章将引领您步入数据恢复的精密艺术殿堂。从备份到恢复的无缝对接,是检验备份方案成色的真正试金石。我们将逐步拆解恢复流程的每一个关键环节:从安全停机、数据迁移与权限配置,到细腻的预处理步骤,直至数据库服务的顺利重启与健康状况的全面核查。每一步都精心设计,确保在面对不可预见的数据危机时,能够迅速恢复业务运营,维持数据连续性和服务稳定性。</p><p>通过本篇的深度解析,您不仅能掌握Percona XtraBackup全量备份的精髓,更能领略其在数据恢复领域的独到之处,为您的数据库管理技能树增添一份坚实保障。无论是对初学者的启蒙,还是对资深DBA的技能进阶,本篇章节均是不可或缺的知识宝典。</p><h2 id="2-准备工作"><a href="#2-准备工作" class="headerlink" title="2.准备工作"></a>2.准备工作</h2><h3 id="2-1-环境信息"><a href="#2-1-环境信息" class="headerlink" title="2.1.环境信息"></a>2.1.环境信息</h3><table><thead><tr><th>主机IP</th><th>操作系统</th><th>Mysql版本</th><th>XtraBackup版本</th></tr></thead><tbody><tr><td>172.17.0.2</td><td>CentOS Stream release 9</td><td>8.0.37</td><td>8.0.35</td></tr></tbody></table><h3 id="2-2-创建备份目录"><a href="#2-2-创建备份目录" class="headerlink" title="2.2.创建备份目录"></a>2.2.创建备份目录</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> -p /data/backup</span><br></pre></td></tr></table></figure><h3 id="2-3-配置-etc-my-cnf文件"><a href="#2-3-配置-etc-my-cnf文件" class="headerlink" title="2.3.配置&#x2F;etc&#x2F;my.cnf文件"></a>2.3.配置&#x2F;etc&#x2F;my.cnf文件</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">[xtrabackup]</span><br><span class="line">host localhost</span><br><span class="line">port 3306</span><br><span class="line">user root</span><br><span class="line">password 123456</span><br><span class="line">socket /var/lib/mysql/mysql.sock</span><br><span class="line">target_dir /data/backup</span><br></pre></td></tr></table></figure><h3 id="2-4-授予root用户BACKUP-ADMIN权限"><a href="#2-4-授予root用户BACKUP-ADMIN权限" class="headerlink" title="2.4.授予root用户BACKUP_ADMIN权限"></a>2.4.授予root用户BACKUP_ADMIN权限</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">grant</span> BACKUP_ADMIN <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;root&#x27;</span> <span class="string">&#x27;%&#x27;</span></span><br></pre></td></tr></table></figure><p>LOCK INSTANCE FOR BACKUP 是MySQL 8.0引入的一种新的备份相关SQL语句,主要用于在进行数据库备份时,以一种更为细粒度和高效的方式控制对数据库实例的访问,以保证备份的一致性。这个命令的工作原理及特点如下:</p><p><strong>目的</strong>:在执行备份操作时,此命令用于获取一个实例级别的锁,该锁允许在备份过程中继续执行DML 数据操作语言,如INSERT、UPDATE、DELETE 操作,同时防止那些可能导致数据快照不一致的DDL 数据定义语言,如CREATE、ALTER、DROP 操作和某些管理操作。这样可以在不影响数据库服务的情况下进行备份,特别适用于需要最小化服务中断的在线备份场景。</p><p><strong>权限需求</strong>:执行LOCK INSTANCE FOR BACKUP语句需要用户具备BACKUP_ADMIN权限。这是一个专门为了备份相关的高级操作而设计的权限级别。</p><p><strong>兼容性</strong>:此特性是在MySQL 8.0及以上版本中引入的,早于8.0的MySQL版本并不支持这一语句,因此在使用旧版本时,可能需要依赖其他机制 如FLUSH TABLES WITH READ LOCK 来确保备份的一致性。</p><p><strong>解锁</strong>:执行备份后,需要使用UNLOCK INSTANCE语句来释放之前由LOCK INSTANCE FOR BACKUP获得的锁,从而恢复正常操作。</p><p><strong>与传统备份命令的对比</strong>:相比于传统的备份方法,如使用FLUSH TABLES WITH READ LOCK,LOCK INSTANCE FOR BACKUP提供了更小的性能影响,因为它不会完全阻止写操作,只是限制了可能引起数据不一致的活动,更适合于高可用性和高性能要求的生产环境。</p><h2 id="3-全量备份"><a href="#3-全量备份" class="headerlink" title="3.全量备份"></a>3.全量备份</h2><p>登陆数据库查看现有的的数据,可以看到现在有一个tes1的库</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img1.avif"></p><p>进行全量备份,最后看到 completed OK!代表成功</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --target-dir /data/backup --datadir /var/lib/mysql --user root --password 123456 --host 172.17.0.2 --port 3306</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img3.avif"></p><p>在&#x2F;data&#x2F;backup目录下可以看到备份的数据</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img4.avif"></p><p>登陆数据库删除tes1库</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img5.avif"></p><h2 id="4-准备备份"><a href="#4-准备备份" class="headerlink" title="4.准备备份"></a>4.准备备份</h2><p>使用Percona XtraBackup进行全量备份后,<strong>在某些特定场景下</strong>确实可以直接使用备份数据,但这并不意味着不需要准备备份 prepare step 。备份准备是确保数据一致性的一个重要步骤,尤其是在进行数据恢复操作之前。具体是否需要准备备份取决于你的备份目的和后续操作:</p><ul><li><strong>立即恢复</strong>: 如果你计划立即在相同或类似的MySQL环境中恢复这个备份,你应该执行备份准备步骤。这一步骤会应用未完成的事务日志 redo log ,确保备份数据的一致性,并将数据文件转换成可以直接用于启动MySQL服务的状态。</li></ul><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --prepare --target-dir <span class="tag">&lt;<span class="name">备份目录</span>&gt;</span></span><br></pre></td></tr></table></figure><ul><li><p><strong>备份存档或复制</strong>: 如果你只是想创建一个备份副本用于存档或者复制到其他服务器上,理论上可以在不进行准备的情况下直接复制备份目录。但请注意,未经准备的备份在恢复时仍需经过准备步骤才能使用。</p></li><li><p><strong>增量备份基础</strong>: 如果计划在这个全量备份的基础上执行增量备份,也不需要立即准备这个全量备份。增量备份会记录自上次备份以来的变化,因此全量备份保持原样即可。</p></li></ul><p>总结来说,尽管在某些情况下全量备份后直接存档或作为增量备份基础可以不立即执行准备步骤,但在准备将数据用于恢复或确保数据一致性时,备份准备是必不可少的。最佳实践中,建议在备份流程中包括准备步骤,以确保备份数据随时可用于快速且可靠地恢复。</p><h2 id="5-数据恢复"><a href="#5-数据恢复" class="headerlink" title="5.数据恢复"></a>5.数据恢复</h2><p>停止MySQL服务进行恢复数据</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br><span class="line">rsync <span class="operator">-</span>avrP <span class="operator">/</span>data<span class="operator">/</span>backup<span class="operator">/</span> <span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img6.avif"></p><p>恢复数据时,一定要记得更改数据目录下的文件拥有者以及所属组权限,否则mysql无法启动</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">chown</span> -R mysql:mysql /var/lib/mysql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img7.avif"></p><p>重启数据库查看数据是否恢复,可以看到之前被删除的tes1数据库已经成功恢复</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img8.avif"></p><h2 id="6-总结"><a href="#6-总结" class="headerlink" title="6.总结"></a>6.总结</h2><p>需要注意的是,在执行恢复之前需要关闭MySQL服务器。您不能恢复到正在运行的mysqld实例的数据目录 导入部分备份时除外 。由于文件的属性将被保留,在大多数情况下,您需要mysql在启动数据库服务器之前将文件的属主和属组更改为mysql.mysql。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/01/87f98269/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】Percona XtraBackup基础篇</title>
      <link>https://blog.eucalyptus.cc/2024/07/01/171bd5b5/</link>
      <guid>https://blog.eucalyptus.cc/2024/07/01/171bd5b5/</guid>
      <pubDate>Mon, 01 Jul 2024 08:57:02 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;h2 id=&quot;1-关于Percona-XtraBackup&quot;&gt;&lt;a href=&quot;#1-关于Percona-XtraBackup&quot; class=&quot;headerlink&quot; title=&quot;1.关于Percona XtraBackup&quot;&gt;&lt;/a&gt;1.关于Percona</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><h2 id="1-关于Percona-XtraBackup"><a href="#1-关于Percona-XtraBackup" class="headerlink" title="1.关于Percona XtraBackup"></a>1.关于Percona XtraBackup</h2><p>Percona XtraBackup是世界上唯一的开源、免费的MySQL热备份 为InnoDB和XtraDB执行非阻塞备份的软件 数据库。使用Percona XtraBackup,您可以获得以下好处:</p><blockquote><ul><li><p>快速可靠地完成备份</p></li><li><p>备份期间不中断的事务处理</p></li><li><p>节省磁盘空间和网络带宽</p></li><li><p>自动备份验证</p></li><li><p>更快的恢复时间导致更高的延迟</p></li></ul></blockquote><h2 id="2-Percona-XtraBackup有哪些特点"><a href="#2-Percona-XtraBackup有哪些特点" class="headerlink" title="2. Percona XtraBackup有哪些特点?"></a>2. Percona XtraBackup有哪些特点?</h2><p>以下是Percona XtraBackup功能的简短列表。</p><blockquote><ul><li><p>创建热InnoDB备份而无需暂停数据库</p></li><li><p>对MySQL进行增量备份</p></li><li><p>将压缩的MySQL备份流式传输到另一台服务器</p></li><li><p>在线在MySQL服务器之间移动表</p></li><li><p>轻松创建新的MySQL复制副本</p></li><li><p>备份MySQL而不增加服务器负载</p></li><li><p>备份锁是Percona Server 5.6 中可用的<code>FLUSH TABLES WITH READ LOCK</code>的轻量级替代方案。Percona XtraBackup使用它们自动复制非InnoDB数据,以避免阻塞修改InnoDB表的DML查询。</p></li><li><p>Percona XtraBackup根据每秒IO操作数执行限制。</p></li><li><p>Percona XtraBackup跳过辅助索引页,并在准备紧凑备份时重新创建它们。</p></li><li><p>Percona XtraBackup甚至可以从完整备份中导出单个表,无论InnoDB版本如何。</p></li><li><p>使用Percona XtraBackup导出的表可以导入Percona Server 5.1、5.5或5.6 或MySQL 5.6 。</p></li></ul></blockquote><h2 id="3-安装Percona-XtraBackup"><a href="#3-安装Percona-XtraBackup" class="headerlink" title="3.安装Percona XtraBackup"></a>3.安装Percona XtraBackup</h2><h3 id="3-1-环境信息"><a href="#3-1-环境信息" class="headerlink" title="3.1.环境信息"></a>3.1.环境信息</h3><table><thead><tr><th>主机IP</th><th>操作系统</th><th>Mysql版本</th><th>XtraBackup版本</th></tr></thead><tbody><tr><td>172.17.0.2</td><td>CentOS Stream release 9</td><td>8.0.37</td><td>8.0.35</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr></tbody></table><h3 id="3-2-安装步骤"><a href="#3-2-安装步骤" class="headerlink" title="3.2.安装步骤"></a>3.2.安装步骤</h3><p>Percona XtraBackup的安装方法有三中YUM仓库安装,RPM包安装,源码编译安装,下面介绍到的是YUM仓库安装</p><ul><li>以<code>root</code>用户身份或使用sudo运行以下命令来安装Percona yum仓库:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> yum install \</span><br><span class="line">https://repo.percona.com/yum/percona-release-latest.\</span><br><span class="line">noarch.rpm</span><br></pre></td></tr></table></figure><ul><li>启用存储库:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo percona-release enable-only tools release</span><br></pre></td></tr></table></figure><p>如果Percona XtraBackup预期与 上游MySQL服务器,只需要开启 tools仓库:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo percona-release enable-only tools</span><br></pre></td></tr></table></figure><ul><li>通过运行以下命令安装Percona XtraBackup:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> yum install percona-xtrabackup-80</span><br></pre></td></tr></table></figure><blockquote><p>警告:</p><p>在CentOS 6上安装Percona XtraBackup之前,请确保安装了<code>libev</code>软件包。对于此操作系统,可以从EPEL存储库中获得<code>libev</code>包。</p></blockquote><ul><li>要对使用<code>LZ4</code>或<code>ZSTD</code>压缩算法进行的备份进行重新编译,请安装相应的软件包:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> yum install zstd</span><br></pre></td></tr></table></figure><h2 id="4-xtrabackup内部流程图"><a href="#4-xtrabackup内部流程图" class="headerlink" title="4. xtrabackup内部流程图"></a>4. xtrabackup内部流程图</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-07-01/img1.avif"></p><h2 id="5-Percona-XtraBackup基础语法"><a href="#5-Percona-XtraBackup基础语法" class="headerlink" title="5.Percona XtraBackup基础语法"></a>5.Percona XtraBackup基础语法</h2><p>Percona XtraBackup 提供了一系列丰富的命令行选项来执行MySQL和Percona Server的热备份操作。以下是一些基本和常用的语法示例,涵盖了全量备份、增量备份、备份准备和恢复等操作:</p><h3 id="5-1-全量备份"><a href="#5-1-全量备份" class="headerlink" title="5.1.全量备份"></a>5.1.全量备份</h3><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --user root --password <span class="tag">&lt;<span class="name">your_password</span>&gt;</span> \ 2 --host <span class="tag">&lt;<span class="name">hostname_or_ip</span>&gt;</span> --port <span class="tag">&lt;<span class="name">port_number</span>&gt;</span> \ 3 --target-dir <span class="tag">&lt;<span class="name">backup_directory</span>&gt;</span></span><br></pre></td></tr></table></figure><ul><li><code>--backup</code> 表示执行备份操作。</li><li><code>--user</code> 和 <code>--password</code> 分别指定MySQL的用户名和密码。</li><li><code>--host</code> 和 <code>--port</code> 指定MySQL服务器的地址和端口。</li><li><code>--target-dir</code> 指定备份文件存放的目录。</li></ul><h3 id="5-2-增量备份"><a href="#5-2-增量备份" class="headerlink" title="5.2.增量备份"></a>5.2.增量备份</h3><h4 id="5-2-1-基于全量备份的增量备份"><a href="#5-2-1-基于全量备份的增量备份" class="headerlink" title="5.2.1.基于全量备份的增量备份"></a>5.2.1.基于全量备份的增量备份</h4><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --incremental-basedir <span class="tag">&lt;<span class="name">full_backup_directory</span>&gt;</span> \ 2 --target-dir <span class="tag">&lt;<span class="name">incremental_backup_directory</span>&gt;</span> \ 3 --user root --password <span class="tag">&lt;<span class="name">your_password</span>&gt;</span> \ 4 --host <span class="tag">&lt;<span class="name">hostname_or_ip</span>&gt;</span> --port <span class="tag">&lt;<span class="name">port_number</span>&gt;</span></span><br></pre></td></tr></table></figure><ul><li><code>--incremental-basedir</code> 指定增量备份基于的全量备份目录。</li></ul><h4 id="5-2-2-基于前一个增量备份的增量备份"><a href="#5-2-2-基于前一个增量备份的增量备份" class="headerlink" title="5.2.2.基于前一个增量备份的增量备份"></a>5.2.2.基于前一个增量备份的增量备份</h4><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --backup --incremental-basedir <span class="tag">&lt;<span class="name">previous_incremental_backup_directory</span>&gt;</span> \ 2 --target-dir <span class="tag">&lt;<span class="name">new_incremental_backup_directory</span>&gt;</span> \ 3 --user root --password <span class="tag">&lt;<span class="name">your_password</span>&gt;</span> \ 4 --host <span class="tag">&lt;<span class="name">hostname_or_ip</span>&gt;</span> --port <span class="tag">&lt;<span class="name">port_number</span>&gt;</span></span><br></pre></td></tr></table></figure><h4 id="5-2-3-备份准备"><a href="#5-2-3-备份准备" class="headerlink" title="5.2.3.备份准备"></a>5.2.3.备份准备</h4><p>对于全量备份,执行以下命令准备数据以便恢复:</p><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --prepare --apply-log-only --target-dir <span class="tag">&lt;<span class="name">backup_directory</span>&gt;</span></span><br></pre></td></tr></table></figure><p>对于增量备份链,需要先对全量备份进行准备,然后依次对每个增量备份执行准备操作,最终对整个链进行最终的准备:</p><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">xtrabackup --prepare --apply-log-only --target-dir <span class="tag">&lt;<span class="name">prepared_full_backup_directory</span>&gt;</span> \ 2 --incremental-dir <span class="tag">&lt;<span class="name">incremental_backup_directory</span>&gt;</span></span><br></pre></td></tr></table></figure><h3 id="5-3-数据恢复"><a href="#5-3-数据恢复" class="headerlink" title="5.3.数据恢复"></a>5.3.数据恢复</h3><p>将准备好的备份数据恢复到MySQL数据目录:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 先停止MySQL服务</span></span><br><span class="line"><span class="built_in">sudo</span> systemctl stop mysql</span><br><span class="line"></span><br><span class="line"><span class="comment"># 将备份数据复制到MySQL数据目录 示例使用全量备份</span></span><br><span class="line">rsync -avP &lt;prepared_backup_directory&gt;/ /var/lib/mysql/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 调整文件权限和属主</span></span><br><span class="line"><span class="built_in">chown</span> -R mysql:mysql /var/lib/mysql/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 启动MySQL服务</span></span><br><span class="line"><span class="built_in">sudo</span> systemctl start mysql</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="6-总结"><a href="#6-总结" class="headerlink" title="6.总结"></a>6.总结</h2><p>本篇文章介绍了Percona XtraBackup工具的安装、使用以及原理,后面会发布Percona XtraBackup的实战篇</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/07/01/171bd5b5/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】lvm-snapshot实战篇</title>
      <link>https://blog.eucalyptus.cc/2024/06/28/ad243418/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/28/ad243418/</guid>
      <pubDate>Fri, 28 Jun 2024 02:00:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;1-简介&quot;&gt;&lt;a href=&quot;#1-简介&quot; class=&quot;headerlink&quot; title=&quot;1.简介&quot;&gt;&lt;/a&gt;1.简介&lt;/h2&gt;&lt;p&gt;LVM快照 LVM Snapshot 是Logical Volume Manager 逻辑卷管理器</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="1-简介"><a href="#1-简介" class="headerlink" title="1.简介"></a>1.简介</h2><p>LVM快照 LVM Snapshot 是Logical Volume Manager 逻辑卷管理器 的一个重要特性,它允许用户在某一时间点创建一个卷的只读副本,这个副本反映了原始卷在创建快照时刻的数据状态。这一功能对于数据备份、系统升级前的即时状态保存、数据迁移等场景非常有用。下面是LVM快照的一些关键点和工作原理:</p><h3 id="1-1-如何工作"><a href="#1-1-如何工作" class="headerlink" title="1.1.如何工作"></a>1.1.如何工作</h3><ul><li><p><strong>创建快照</strong>:当创建一个LVM快照时,LVM实际上并不立即复制原始卷的所有数据到新的快照卷上,这样做会非常耗时且占用大量空间。相反,LVM仅记录自快照创建以来发生变化的块。这时,快照卷和原始卷共享未变更的数据块。</p></li><li><p><strong>独立变化</strong>:随着时间推移,如果原始卷上的数据发生变化,LVM会将变化前的数据块复制到快照卷上,以保持快照数据的一致性。这意味着快照卷会逐渐占用更多的存储空间,因为它需要存储越来越多与原始卷不同的数据块。</p></li><li><p><strong>空间管理</strong>:LVM快照的大小 即它可以记录多少更改 是在创建时指定的,随着快照使用空间的增长,达到这个限制后,如果还有更多的更改,快照可能会失效或变得不可用,因此需要合理规划快照的大小。</p></li><li><p><strong>性能影响</strong>:由于LVM快照机制涉及到数据块的复制,尤其是在写密集型的应用中,创建和维护快照可能会对I&#x2F;O性能产生一定影响。因此,在生产环境中实施快照时,需要评估其对业务运行的潜在影响。</p></li></ul><h3 id="1-2-应用场景"><a href="#1-2-应用场景" class="headerlink" title="1.2.应用场景"></a>1.2.应用场景</h3><ul><li><strong>数据备份</strong>:在进行物理备份时,先创建LVM快照,然后从快照进行备份,这样可以避免备份过程中数据库的写操作影响数据一致性。</li><li><strong>系统测试</strong>:可以基于生产环境的快照创建一个测试环境,进行软件升级或配置更改的测试,而不影响生产数据。</li><li><strong>数据恢复</strong>:在数据损坏或误删的情况下,快照可以作为一种快速恢复手段,恢复到创建快照时的状态。</li></ul><h3 id="1-3-注意事项"><a href="#1-3-注意事项" class="headerlink" title="1.3.注意事项"></a>1.3.注意事项</h3><ul><li>快照应当视为临时状态的保存,不适合长期存储,因为随着更改量的累积,快照占用的空间会持续增长。</li><li>在使用LVM快照进行备份时,应确保快照的生命周期内数据变更量不要超过快照卷的容量,避免数据丢失。</li></ul><h3 id="1-4-优缺点"><a href="#1-4-优缺点" class="headerlink" title="1.4.优缺点"></a><strong>1.4.优缺点</strong></h3><table><thead><tr><th>优点</th><th>缺点</th></tr></thead><tbody><tr><td><strong>即时快照</strong>:能够在几秒钟内创建一个时间点的快照,几乎不影响系统运行</td><td><strong>空间消耗</strong>:随着数据变化,快照会占用额外的存储空间,且随时间推移可能迅速增长</td></tr><tr><td><strong>一致性备份</strong>:在创建快照前后使用适当的锁机制,可以保证数据的一致性</td><td><strong>性能影响</strong>:快照创建后,对源卷的写操作需要同时更新源卷和快照,可能导致I&#x2F;O性能下降</td></tr><tr><td><strong>在线备份</strong>:允许在不停机的情况下进行备份,适合生产环境的实时数据保护</td><td><strong>快照生存周期</strong>:快照卷有最大容量限制,一旦达到,快照将失效,且无法追加新变更</td></tr><tr><td><strong>灵活恢复</strong>:可以从快照恢复到任意时间点的数据,提供多种数据恢复方案</td><td><strong>管理复杂度</strong>:需要合理规划快照大小、监控空间使用,以及适时删除不再需要的快照</td></tr><tr><td><strong>灾难恢复</strong>:为灾难恢复提供快速的数据恢复点,减少RTO(恢复时间目标)</td><td><strong>硬件依赖</strong>:仅限于使用LVM管理的卷,对于非LVM环境不适用</td></tr><tr><td><strong>资源复用</strong>:快照可以用于测试、开发环境,无需额外复制大量数据,节省存储资源</td><td><strong>潜在风险</strong>:若源卷损坏,且快照未被妥善保护或管理,可能会失去所有数据</td></tr></tbody></table><h2 id="2-为什么选择lvm快照备份"><a href="#2-为什么选择lvm快照备份" class="headerlink" title="2.为什么选择lvm快照备份?"></a>2.为什么选择lvm快照备份?</h2><p>原因:因为锁表的时间不一致,在锁表的瞬间是不能写入的,对其进行快照备份,备份完成后立即解锁,然后服务可以正常使用 写入等操作 比如数据量大的时候,做快照一下子就拍了,然后立即解锁,就不影响写入等操作。如果用mysqldump备份,那么数据量大的时候,锁表时间长,就会影响效率</p><h2 id="3-创建LVM"><a href="#3-创建LVM" class="headerlink" title="3.创建LVM"></a><strong>3.创建LVM</strong></h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-28/img1.avif"></p><p>图片来源:</p><p><a href="">http://Linux下的磁盘管理之LVM详解及lvm的常用磁盘操作命令_yg hunter的博客-CSDN博客_lvm命令</a></p><h3 id="3-1-操作流程"><a href="#3-1-操作流程" class="headerlink" title="3.1.操作流程"></a><strong>3.1.操作流程</strong></h3><ul><li>flush table with read local;&#x2F;&#x2F;全局加锁</li><li>create snapshot;&#x2F;&#x2F;快照</li><li>show master status; show slave status;[可选]</li><li>unlock tables;&#x2F;&#x2F;释放锁</li><li>Copy files from the snapshot&#x2F;&#x2F;从快照卷中复制数据cp tar[40 m]</li><li>Unmount the snapshot&#x2F;&#x2F;挂载快照卷</li><li>Remove snapshot&#x2F;&#x2F;卸载并删除快照卷</li></ul><h3 id="3-2-正常安装MySQL后进行备份"><a href="#3-2-正常安装MySQL后进行备份" class="headerlink" title="3.2.正常安装MySQL后进行备份"></a><strong>3.2.正常安装MySQL后进行备份</strong></h3><p>1.安装系统<br>2.准备LVM<br>3.安装mysql,默认datadir &#x2F;var&#x2F;lib&#x2F;mysql</p><h3 id="3-3-MySQL运行一段时间后进行备份"><a href="#3-3-MySQL运行一段时间后进行备份" class="headerlink" title="3.3.MySQL运行一段时间后进行备份"></a><strong>3.3.MySQL运行一段时间后进行备份</strong></h3><p>3.3.1.准备lvm及文件系统&#x2F;&#x2F;先添加一块磁盘</p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># vgcreate datavg /dev/sdb</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-28/img2.avif"></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># lvcreate -L 2G -n mysql datavg //创建2G的VG</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># mkfs.xfs /dev/datavg/mysql //格式化磁盘分区</span></span><br></pre></td></tr></table></figure><h4 id="3-3-2-将数据迁移到LVM"><a href="#3-3-2-将数据迁移到LVM" class="headerlink" title="3.3.2.将数据迁移到LVM"></a>3.3.2.将数据迁移到LVM</h4><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># systemctl stop mysqld //停止MySQL服务</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># mount /dev/datavg/mysql /mnt/ //将快照挂载到临时目录</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># cp -a /var/lib/mysql/* /mnt/ //拷贝MySQL数据到挂载的临时目录</span></span><br><span class="line"></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># umount /mnt/ //卸载快照</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># vim /etc/fstab //更改配置文件设置自动挂载</span></span><br><span class="line">/dev/datavg/mysql /var/lib/mysql xfs defaults 0 0</span><br><span class="line"></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># mount -a //自动挂载/etc/fstab文件没有挂载的设备,不管已挂载过的设备</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># chown -R mysql.mysql /var/lib/mysql //递归更改/var/lib/mysql主组和属组</span></span><br><span class="line"><span class="section">[root localhost centos]</span><span class="comment"># systemctl restart mysqld //重启MySQL</span></span><br></pre></td></tr></table></figure><h4 id="3-3-3-LVM快照备份流程"><a href="#3-3-3-LVM快照备份流程" class="headerlink" title="3.3.3.LVM快照备份流程"></a>3.3.3.LVM快照备份流程</h4><h5 id="3-3-3-1-加全局锁"><a href="#3-3-3-1-加全局锁" class="headerlink" title="3.3.3.1.加全局锁"></a>3.3.3.1.加全局锁</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span>flush <span class="keyword">table</span> <span class="keyword">with</span> read <span class="keyword">local</span>;</span><br></pre></td></tr></table></figure><h5 id="3-3-3-2-创建快照"><a href="#3-3-3-2-创建快照" class="headerlink" title="3.3.3.2.创建快照"></a>3.3.3.2.创建快照</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">lvcreate <span class="operator">-</span>L <span class="number">500</span>M <span class="operator">-</span>s <span class="operator">-</span>n mysql<span class="operator">-</span>snap <span class="operator">/</span>dev<span class="operator">/</span>datavg<span class="operator">/</span>mysql;</span><br><span class="line">mysql <span class="operator">-</span>p<span class="string">&#x27;123456&#x27;</span> <span class="operator">-</span>e ‘<span class="keyword">show</span> master status’<span class="operator">&gt;</span> <span class="operator">/</span>backup<span class="operator">/</span> data <span class="operator">%</span>F _position.txt</span><br></pre></td></tr></table></figure><h5 id="3-3-3-3-释放锁"><a href="#3-3-3-3-释放锁" class="headerlink" title="3.3.3.3.释放锁"></a>3.3.3.3.释放锁</h5><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> snapshot;</span><br></pre></td></tr></table></figure><p><strong>注意事项:</strong></p><p><strong>加全局锁和创建快照必须在同一会话中完成</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">[root localhost centos]# <span class="built_in">echo</span> FLUSH TABLES WITH READ LOCK;SYSTEM lvcreate -L 500M -s -n mysql-snap /dev/datavg/mysql;</span><br><span class="line">| mysql -uroot -p<span class="string">&#x27;123456&#x27;</span></span><br></pre></td></tr></table></figure><h3 id="3-4-从快照中恢复"><a href="#3-4-从快照中恢复" class="headerlink" title="3.4.从快照中恢复"></a><strong>3.4.从快照中恢复</strong></h3><h4 id="3-4-1-停止MySQL服务"><a href="#3-4-1-停止MySQL服务" class="headerlink" title="3.4.1. 停止MySQL服务"></a>3.4.1. 停止MySQL服务</h4><p>首先,优雅地停止MySQL服务,以避免数据损坏:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br></pre></td></tr></table></figure><p>或在较旧的系统中可能是:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">service mysql stop</span><br></pre></td></tr></table></figure><h4 id="3-4-2-卸载原逻辑卷"><a href="#3-4-2-卸载原逻辑卷" class="headerlink" title="3.4.2. 卸载原逻辑卷"></a>3.4.2. 卸载原逻辑卷</h4><p>如果原逻辑卷仍然挂载,需要先卸载它。比如,如果MySQL数据目录挂载在<code>/var/lib/mysql</code>,则执行:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">umount /var/lib/mysql</span><br></pre></td></tr></table></figure><h4 id="3-4-3-挂载快照卷"><a href="#3-4-3-挂载快照卷" class="headerlink" title="3.4.3. 挂载快照卷"></a>3.4.3. 挂载快照卷</h4><p>创建一个临时目录,并将快照卷挂载到这个目录:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> /mnt/mysql_snapshot_recovery</span><br><span class="line">mount /dev/datavg/mysql-snap /mnt/mysql_snapshot_recovery</span><br></pre></td></tr></table></figure><p>这里<code>/dev/datavg/mysql-snap</code>是之前创建的快照逻辑卷的路径。</p><h4 id="3-4-4-复制数据"><a href="#3-4-4-复制数据" class="headerlink" title="3.4.4. 复制数据"></a>3.4.4. 复制数据</h4><p>将快照中的数据复制回原逻辑卷的位置。首先,确保原逻辑卷 例如<code>/dev/datavg/mysql</code> 未挂载。然后,使用<code>rsync</code>或<code>cp</code>命令将数据复制回去。<code>rsync</code>是一个较好的选择,因为它可以更高效地处理大文件和大量小文件:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">rsync <span class="operator">-</span>avHAXS <span class="comment">--delete /mnt/mysql_snapshot_recovery/ /var/lib/mysql/</span></span><br></pre></td></tr></table></figure><p>这会将快照中的所有内容同步到MySQL的原始数据目录中,并保持权限、时间戳等元数据的一致性。</p><h4 id="3-4-5-卸载快照卷"><a href="#3-4-5-卸载快照卷" class="headerlink" title="3.4.5. 卸载快照卷"></a>3.4.5. 卸载快照卷</h4><p>完成数据复制后,卸载快照卷:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">umount /mnt/mysql_snapshot_recovery</span><br></pre></td></tr></table></figure><h4 id="3-4-6-启动MySQL服务"><a href="#3-4-6-启动MySQL服务" class="headerlink" title="3.4.6. 启动MySQL服务"></a>3.4.6. 启动MySQL服务</h4><p>启动MySQL服务,检查数据是否恢复成功:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl <span class="keyword">start</span> mysqld</span><br></pre></td></tr></table></figure><p>或</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">service mysql <span class="keyword">start</span></span><br></pre></td></tr></table></figure><h4 id="3-4-7-验证数据"><a href="#3-4-7-验证数据" class="headerlink" title="3.4.7. 验证数据"></a>3.4.7. 验证数据</h4><h4 id="3-4-8-清理和后续操作"><a href="#3-4-8-清理和后续操作" class="headerlink" title="3.4.8. 清理和后续操作"></a>3.4.8. 清理和后续操作</h4><p>如果一切正常,你可以考虑删除快照 如果不再需要 ,以释放存储空间:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">lvremove /dev/datavg/mysql-snap</span><br></pre></td></tr></table></figure><h3 id="3-6-脚本制作快照"><a href="#3-6-脚本制作快照" class="headerlink" title="3.6.脚本制作快照"></a>3.6.脚本制作快照</h3><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#!/bin/bash</span></span><br><span class="line"><span class="comment"># 定义备份目录,使用日期作为目录名以保持备份的有序性</span></span><br><span class="line">back_dir /backup/mysql_$(date %F)</span><br><span class="line"></span><br><span class="line"><span class="comment"># 检查备份目录是否存在,不存在则创建</span></span><br><span class="line"><span class="section">[ ! -d $back_dir ]</span> &amp;&amp; mkdir -p $back_dir</span><br><span class="line"></span><br><span class="line"><span class="comment"># 锁定MySQL表并创建LVM快照。注意,这里直接在命令中使用了MySQL的root密码,这在安全性上是个问题。</span></span><br><span class="line"><span class="comment"># 使用-e参数将多行命令传递给mysql,同时建议通过配置文件或环境变量安全地传递密码。</span></span><br><span class="line">echo FLUSH TABLES WITH READ LOCK<span class="comment">; SYSTEM lvcreate -L 500M -s -n mysql-snap /dev/datavg/mysql; | mysql -u root -p&#x27;123456&#x27;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 挂载LVM快照为只读模式,避免对快照造成意外修改</span></span><br><span class="line">mount -o ro,nouuid /dev/datavg/mysql-snap /mnt/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 使用rsync进行数据同步,从快照目录到备份目录</span></span><br><span class="line">rsync -a /mnt/ $back_dir</span><br><span class="line"></span><br><span class="line"><span class="comment"># 检查rsync命令执行状态,如果成功 返回值为0 则进行以下操作</span></span><br><span class="line">if <span class="section">[ $? -eq 0 ]</span><span class="comment">; then</span></span><br><span class="line"><span class="comment"># 解除MySQL锁</span></span><br><span class="line">echo UNLOCK TABLES<span class="comment">; | mysql -u root -p&#x27;123456&#x27;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 卸载快照卷</span></span><br><span class="line">umount /mnt/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 删除快照,释放空间</span></span><br><span class="line">lvremove -f /dev/datavg/mysql-snap</span><br><span class="line">else</span><br><span class="line">echo 备份过程中发生错误,未执行卸载和删除快照操作。</span><br><span class="line">fi</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-7-定时任务管理Cron"><a href="#3-7-定时任务管理Cron" class="headerlink" title="3.7.定时任务管理Cron"></a>3.7.定时任务管理Cron</h3><p>要将上述LVM快照备份脚本设置为定时任务,可以使用Linux的Cron服务。以下是设置定时任务的步骤,假设脚本保存为<code>/usr/local/bin/lvm_mysql_backup.sh</code>,并且希望每天凌晨2点执行一次备份:</p><ul><li><strong>编辑Crontab配置</strong>:</li></ul><p>打开终端,运行以下命令来编辑Crontab配置 如果希望以root用户执行脚本,请使用<code>sudo crontab -e</code>,否则,直接使用<code>crontab -e</code>以当前用户身份编辑 :</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">crontab -e</span><br></pre></td></tr></table></figure><ul><li><strong>添加定时任务</strong>:</li></ul><p>在打开的Crontab文件中,移动光标到文件末尾,添加以下行来设置定时任务:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">0 2 * * * /usr/local/bin/lvm_mysql_backup.sh</span><br></pre></td></tr></table></figure><ul><li><p>这行配置的意思是每天凌晨2点整执行<code>/usr/local/bin/lvm_mysql_backup.sh</code>脚本。</p></li><li><p><strong>保存并退出</strong>:</p></li></ul><p>编辑完成后,保存文件。如果使用的是Nano编辑器,可以按<code>Ctrl O</code>然后回车保存,接着按<code>Ctrl X</code>退出编辑器。</p><ul><li><strong>权限设置</strong>:</li></ul><p>确保脚本具有执行权限。如果尚未设置,可以通过以下命令给予脚本执行权限:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> <span class="built_in">chmod</span> x /usr/local/bin/lvm_mysql_backup.sh</span><br></pre></td></tr></table></figure><ul><li><strong>测试与验证</strong>:</li></ul><p>可以通过查看Cron的日志 通常是<code>/var/log/syslog</code>或<code>/var/log/cron.log</code> 来确认任务是否按时执行。此外,可以在计划执行时间之前手动执行一次脚本,以确保脚本没有错误,并能正确完成备份任务。</p><p>请注意,为了安全和管理方便,确保脚本中不包含敏感信息 如数据库密码 ,而是通过安全的方式传递这些信息 例如通过环境变量或配置文件 。此外,定期检查备份目录的空间使用情况,确保有足够的空间进行备份,避免因空间不足导致备份失败。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/28/ad243418/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL备份】mysqldump基础篇</title>
      <link>https://blog.eucalyptus.cc/2024/06/27/34713a76/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/27/34713a76/</guid>
      <pubDate>Thu, 27 Jun 2024 09:20:43 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;1-简介&quot;&gt;&lt;a href=&quot;#1-简介&quot; class=&quot;headerlink&quot; title=&quot;1.简介&quot;&gt;&lt;/a&gt;1.简介&lt;/h2&gt;&lt;p&gt;**&lt;code&gt;mysqldump&lt;/code&gt; **是 MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="1-简介"><a href="#1-简介" class="headerlink" title="1.简介"></a>1.简介</h2><p>**<code>mysqldump</code> **是 MySQL 数据库管理系统的命令行实用程序,用于创建数据库的逻辑备份。它能够导出数据库的结构 如表结构、视图、触发器等 以及表中的数据为 SQL 格式的文本文件。</p><h2 id="2-基本用途"><a href="#2-基本用途" class="headerlink" title="2.基本用途"></a>2.基本用途</h2><ul><li><strong>全库备份</strong>:可以备份整个 MySQL 服务器上的所有数据库。</li><li><strong>单数据库备份</strong>:仅备份指定的单一数据库。</li><li><strong>表备份</strong>:备份特定数据库中的某几张表。</li></ul><h2 id="3-命令格式"><a href="#3-命令格式" class="headerlink" title="3.命令格式"></a>3.命令格式</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">mysqldump [选项] [数据库名 [表名...]]</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-1常用选项"><a href="#3-1常用选项" class="headerlink" title="3.1常用选项"></a><strong>3.1常用选项</strong></h3><table><thead><tr><th>序号</th><th>表名</th><th>描述</th></tr></thead><tbody><tr><td>选项</td><td>描述</td><td>-u 用户名, –user 用户名</td></tr><tr><td>-p[密码], –password[ 密码]</td><td>提供连接MySQL服务器的密码。如果仅使用 -p,将会提示输入密码。为安全起见,建议不在命令行直接暴露密码。</td><td>-h 主机名, –host 主机名</td></tr><tr><td>-P 端口, –port 端口</td><td>如果MySQL服务不是运行在默认的3306端口,可以用此选项指定端口号。</td><td>-A, –all-databases</td></tr><tr><td>-B, –databases</td><td>允许指定多个数据库进行备份,后面直接列出数据库名。</td><td>数据库名 [表名…]</td></tr><tr><td>&gt; 备份文件路径</td><td>输出重定向符号,用于指定备份文件的保存路径和名称。</td><td>–single-transaction</td></tr><tr><td>–lock-tables false</td><td>防止在备份时锁定表,通常与 –single-transaction 一起使用,尤其适用于InnoDB表。</td><td>–routines</td></tr><tr><td>–triggers</td><td>包含数据库中的触发器到备份中。</td><td>–events</td></tr><tr><td>–skip-add-drop-table</td><td>备份时不包含 DROP TABLE 语句,这样在恢复时不会删除已存在的表。</td><td>–quick</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr></tbody></table><h3 id="3-2常用命令"><a href="#3-2常用命令" class="headerlink" title="3.2常用命令"></a>3.2常用命令</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br></pre></td><td class="code"><pre><span class="line">**导出命令大全**</span><br><span class="line"><span class="comment">#导出education数据库里面的users表的表数据和表结构</span></span><br><span class="line">mysqldump -u[用户名] -h[ip] -p[密码] -P[端口号] 数据库名 表名 &gt;导出的文件名.sql</span><br><span class="line">mysqldump -uroot -h127.0.0.1 -proot -P3306 education <span class="built_in">users</span>&gt;d:/user.sql</span><br><span class="line"><span class="comment">#导出包括系统数据库在内的所有数据库 all.sql默认保存在bin文件夹下面</span></span><br><span class="line">mysqldump -uroot -proot --all-databases&gt;all.sql</span><br><span class="line"><span class="comment">#导出多张表:</span></span><br><span class="line">mysqldump -uroot -proot --databases <span class="built_in">test</span> --tables t1 t2&gt;two.sql</span><br><span class="line"><span class="comment">#只导出表结构不导表数据,添加“-d”命令参数</span></span><br><span class="line">mysqldump -uroot -h127.0.0.1 -proot -P3306 -d education <span class="built_in">users</span>&gt;d:/user.sql</span><br><span class="line"><span class="comment">#只导出表数据不导表结构,添加“-t”命令参数</span></span><br><span class="line">mysqldump -uroot -h127.0.0.1 -proot -P3306 -t education <span class="built_in">users</span>&gt;d:/user.sql</span><br><span class="line"><span class="comment">#只导出test数据库的表结构</span></span><br><span class="line">导出:mysqldump -uroot -proot --no-data --databases <span class="built_in">test</span>&gt;s1.sql</span><br><span class="line">导入:mysql -uroot -proot -h127.0.0.1 -P3306 <span class="built_in">test</span>&lt;s1.sql</span><br><span class="line"></span><br><span class="line">**导入命令大全**</span><br><span class="line">格式:mysql -h[ip] -P[(大写)端口] -u[用户名] -p[密码] [数据库名] &lt; d:XX.sql(路径)</span><br><span class="line">mysql -uroot -proot -h127.0.0.1 -P3306 education&lt;d:/database.sql</span><br><span class="line">mysql -uroot -proot -h127.0.0.1 -P3306 &lt;d:/all_database.sql</span><br><span class="line"><span class="comment">#命令行导入</span></span><br><span class="line">mysql&gt; use <span class="built_in">test</span>;</span><br><span class="line">mysql&gt; <span class="built_in">source</span> /home/test/database.sql</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="4-备份脚本"><a href="#4-备份脚本" class="headerlink" title="4.备份脚本"></a>4.备份脚本</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">#!/bin/bash</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 设置脚本名称、日期等信息</span></span><br><span class="line">NAME MySQL Database Backup Script</span><br><span class="line">DATE $(<span class="built_in">date</span> %Y-%m-%d-%H-%M)</span><br><span class="line">LOG_FILE /var/log/mysql_backup.log</span><br><span class="line"></span><br><span class="line"><span class="comment"># 使用环境变量或配置文件读取敏感信息,提高安全性</span></span><br><span class="line"><span class="built_in">source</span> /etc/mysql_backup.conf 2&gt;/dev/null <span class="comment"># 假设配置文件存放于此路径</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 若配置文件不存在,则设置默认值或提示错误</span></span><br><span class="line">: <span class="variable">$&#123;MYSQL_USER: mysql_user_not_set&#125;</span></span><br><span class="line">: <span class="variable">$&#123;MYSQL_PASSWORD: mysql_passwd_not_set&#125;</span></span><br><span class="line">: <span class="variable">$&#123;MYSQL_HOST: localhost&#125;</span></span><br><span class="line">: <span class="variable">$&#123;MYSQL_PORT: 3306&#125;</span></span><br><span class="line">: <span class="variable">$&#123;MYSQL_CHARSET: utf8mb4&#125;</span></span><br><span class="line">: <span class="variable">$&#123;BACKUP_PATH: /backups/mysql&#125;</span></span><br><span class="line">: <span class="variable">$&#123;MAX_BACKUPS: 10&#125;</span></span><br><span class="line">: <span class="variable">$&#123;EMAIL_TO: you example.com&#125;</span></span><br><span class="line">: <span class="variable">$&#123;EMAIL_FROM: backup_script example.com&#125;</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 创建备份目录 如果不存在</span></span><br><span class="line"><span class="built_in">mkdir</span> -p <span class="variable">$BACKUP_PATH</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 获取当前日期时间,用于备份文件命名</span></span><br><span class="line">DATE_TIME $(<span class="built_in">date</span> %Y%m%d_%H%M%S)</span><br><span class="line"></span><br><span class="line"><span class="comment"># 执行备份并压缩</span></span><br><span class="line">mysqldump --opt --all-databases --single-transaction --flush-logs --master-data 2 \</span><br><span class="line">-h<span class="variable">$MYSQL_HOST</span> -u<span class="variable">$MYSQL_USER</span> -p<span class="variable">$MYSQL_PASSWORD</span> \</span><br><span class="line">| gzip &gt; <span class="variable">$BACKUP_PATH</span>/mysql_backup_<span class="variable">$DATE_TIME</span>.sql.gz</span><br><span class="line"></span><br><span class="line"><span class="keyword">if</span> [ $? -eq 0 ]; <span class="keyword">then</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span>) - 数据库备份成功 &gt;&gt; <span class="variable">$LOG_FILE</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 删除超出保留数量的旧备份</span></span><br><span class="line">find <span class="variable">$BACKUP_PATH</span> -name *.sql.gz -<span class="built_in">type</span> f | <span class="built_in">sort</span> | <span class="built_in">head</span> -n -<span class="variable">$MAX_BACKUPS</span> | xargs -r <span class="built_in">rm</span> -f</span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span>) - 已清理过期备份文件 &gt;&gt; <span class="variable">$LOG_FILE</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 发送邮件通知 需要安装mail或msmtp等工具</span></span><br><span class="line">&#123;</span><br><span class="line"><span class="built_in">echo</span> 主题: MySQL 数据库备份通知</span><br><span class="line"><span class="built_in">echo</span> From: <span class="variable">$EMAIL_FROM</span></span><br><span class="line"><span class="built_in">echo</span> To: <span class="variable">$EMAIL_TO</span></span><br><span class="line"><span class="built_in">echo</span></span><br><span class="line"><span class="built_in">echo</span> 数据库备份已完成,备份文件:mysql_backup_<span class="variable">$DATE_TIME</span>.sql.gz</span><br><span class="line"><span class="built_in">echo</span> 备份路径:<span class="variable">$BACKUP_PATH</span></span><br><span class="line">&#125; | mail -s $(<span class="built_in">echo</span> -e MySQL Backup on <span class="variable">$DATE</span> ) <span class="variable">$EMAIL_TO</span></span><br><span class="line"><span class="keyword">else</span></span><br><span class="line"><span class="built_in">echo</span> $(<span class="built_in">date</span>) - 数据库备份失败,请检查错误日志 &gt;&gt; <span class="variable">$LOG_FILE</span></span><br><span class="line"><span class="comment"># 发送错误通知</span></span><br><span class="line">&#123;</span><br><span class="line"><span class="built_in">echo</span> 主题: MySQL 数据库备份失败通知</span><br><span class="line"><span class="built_in">echo</span> From: <span class="variable">$EMAIL_FROM</span></span><br><span class="line"><span class="built_in">echo</span> To: <span class="variable">$EMAIL_TO</span></span><br><span class="line"><span class="built_in">echo</span></span><br><span class="line"><span class="built_in">echo</span> 数据库备份失败,请立即检查。</span><br><span class="line">&#125; | mail -s $(<span class="built_in">echo</span> -e MySQL Backup Failure on <span class="variable">$DATE</span> ) <span class="variable">$EMAIL_TO</span></span><br><span class="line"><span class="keyword">fi</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>说明</strong>:</p><ul><li><strong>环境变量</strong>: 使用环境变量读取敏感信息,可以提高脚本的灵活性和安全性。这里假设存在一个<code>/etc/mysql_backup.conf</code>配置文件来集中管理这些变量,以避免硬编码。</li><li><strong>日志记录</strong>: 添加了日志文件,用于记录备份操作的详细信息,方便追踪和审计。</li><li><strong>备份压缩</strong>: 使用<code>gzip</code>命令对备份文件进行压缩,减少存储空间占用。</li><li><strong>自动清理</strong>: 使用<code>find</code>命令自动清理超过保留数量的旧备份文件,提高了脚本的自动化程度。</li><li><strong>邮件通知</strong>: 添加了成功和失败的邮件通知功能,可以及时提醒管理员备份状态,<code>mail</code>命令用于发送邮件,需确保系统已正确配置邮件发送工具。</li></ul><h2 id="5-定时执行备份脚本"><a href="#5-定时执行备份脚本" class="headerlink" title="5.定时执行备份脚本"></a>5.定时执行备份脚本</h2><ul><li><p><strong>编辑Crontab配置</strong>:首先,打开终端并以您的用户身份运行<code>crontab</code>命令来编辑Cron配置。如果您想要以root用户身份执行备份,可以使用<code>sudo crontab -e</code>,否则,只需输入<code>crontab -e</code>。</p></li><li><p><strong>添加定时任务</strong>:在打开的Crontab文件中,移动光标到文件末尾,然后添加以下行来设定定时任务。假设您的备份脚本名为<code>mysql_backup.sh</code>,且该脚本位于<code>/usr/local/bin/</code>目录下:</p></li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">0 2 * * * /usr/local/bin/mysql_backup.sh</span><br></pre></td></tr></table></figure><p>这行的意思是:每天的凌晨2点0分执行<code>/usr/local/bin/mysql_backup.sh</code>脚本。Cron任务的时间格式为分钟 小时 日 月 星期,从左到右依次对应。</p><ul><li><p><strong>保存并退出</strong>:编辑完成后,保存文件并退出编辑器。大多数情况下,您可以通过按下<code>Ctrl X</code>,然后按<code>Y</code>键确认保存,最后按回车键退出。</p></li><li><p><strong>测试与验证</strong>:您可以通过查看Cron的日志 通常是<code>/var/log/syslog</code>或<code>/var/log/cron.log</code>,具体取决于您的系统配置 来确认任务是否按时执行,或者等待下一个执行时间点查看是否收到了邮件通知 如果您的脚本配置了邮件通知功能 。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/27/34713a76/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>TIMESTAMP 和DATETIME 的区别</title>
      <link>https://blog.eucalyptus.cc/2024/06/27/f0d51d02/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/27/f0d51d02/</guid>
      <pubDate>Thu, 27 Jun 2024 06:26:29 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;DATETIME类型&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;存储范围&lt;/strong&gt;:&lt;code&gt;DATETIME&lt;/code&gt;类型可以存储从&lt;code&gt;1000-01-01</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>DATETIME类型</strong></p><ul><li><strong>存储范围</strong>:<code>DATETIME</code>类型可以存储从<code>1000-01-01 00:00:00</code>到<code>9999-12-31 23:59:59</code>的日期和时间值,精度可以达到微秒级别。</li><li><strong>时区处理</strong>:<code>DATETIME</code>类型不与特定时区关联。它直接存储你提供的日期和时间值,不包含任何时区信息。这意味着存储和检索时,值是不变的,非常适合不需要时区转换的场景。</li><li><strong>存储空间</strong>:通常情况下,<code>DATETIME</code>类型占用8字节的存储空间。</li></ul><p><strong>TIMESTAMP类型</strong></p><ul><li><strong>存储范围</strong>:<code>TIMESTAMP</code>类型可以存储从<code>1970-01-01 00:00:01</code> UTC到<code>2038-01-19 03:14:07</code> UTC的日期和时间值。注意,<code>TIMESTAMP</code>有一个固定的时间范围限制,且存在“2038年问题”,即在2038年后无法存储新的日期。</li><li><strong>时区处理</strong>:与<code>DATETIME</code>不同,<code>TIMESTAMP</code>是时区敏感的。当数据被插入或更新时,MySQL会根据系统的时区设置将客户端的时间转换为UTC 协调世界时 进行存储。当数据被检索时,这个过程会被逆向执行,将UTC时间转换回当前MySQL服务器的时区时间。这意味着,如果你在不同的时区查看同一个<code>TIMESTAMP</code>字段,显示的时间可能会有所不同。</li><li><strong>自动更新</strong>:<code>TIMESTAMP</code>列可以被设置为在行被创建或更新时自动更新到当前时间 使用<code>ON UPDATE CURRENT_TIMESTAMP</code> 。这是它常被用来记录记录创建或最后修改时间的原因。</li><li><strong>存储空间</strong>:<code>TIMESTAMP</code>类型通常占用4字节的存储空间 MySQL 5.6.4及以后版本可以存储到微秒,此时占用5字节或更多,具体取决于精度设置 。</li></ul><p><strong>应用场景</strong></p><ul><li><strong>DATETIME</strong>适用于需要宽泛日期范围且不需要时区转换的场景,如记录历史事件或维护长期的审计日志。</li><li><strong>TIMESTAMP</strong>则更适合需要考虑时区差异,或者利用其自动更新特性的场景,比如记录数据的创建和修改时间。</li></ul><p><strong>两者区别</strong></p><table><thead><tr><th>特性</th><th>DATETIME</th><th>TIMESTAMP</th></tr></thead><tbody><tr><td>存储范围</td><td>从1000-01-01 00:00:00到9999-12-31 23:59:59</td><td>从1970-01-01 00:00:01到2038-01-19 03:14:07</td></tr><tr><td>时区敏感性</td><td>不敏感,直接存储指定的时间</td><td>敏感,存储时转换为UTC,检索时转换回系统时区</td></tr><tr><td>自动更新</td><td>不提供自动更新到当前时间的功能</td><td>可以设置ON UPDATE CURRENT_TIMESTAMP自动更新</td></tr><tr><td>存储空间</td><td>8字节</td><td>通常为4字节 MySQL 5.6.4后,带微秒为5字节或以上</td></tr><tr><td>默认值</td><td>NULL</td><td>当前时间 CURRENT_TIMESTAMP ,除非明确设置</td></tr><tr><td>适用场景</td><td>需要宽泛日期范围,不关心时区转换</td><td>需要考虑时区差异,记录创建&#x2F;修改时间戳</td></tr></tbody></table><p><strong>注意事项</strong></p><p><a href="https://dev.mysql.com/doc/refman/8.0/en/data-type-defaults.html">https://dev.mysql.com/doc/refman/8.0/en/data-type-defaults.html</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-27/img1.avif"></p><p><code>explicit_defaults_for_timestamp</code> 是一个MySQL的系统变量,它的引入是为了改变MySQL中对<code>TIMESTAMP</code>列的默认行为,特别是在MySQL 5.6版本中。这个变量的主要作用和影响如下:</p><p><strong>背景</strong></p><p>在MySQL早期版本中,<code>TIMESTAMP</code>列有一些特殊的默认行为:</p><ul><li>如果一个表定义中只有一个<code>TIMESTAMP</code>列,则该列自动设置为当前时间戳,无论是插入新行还是更新行。</li><li>如果定义了两个<code>TIMESTAMP</code>列,其中一个可以指定为<code>ON UPDATE CURRENT_TIMESTAMP</code>,另一个则默认为插入时设置为当前时间戳。</li></ul><p><strong>explicit_defaults_for_timestamp 的作用</strong></p><p>当 <code>explicit_defaults_for_timestamp</code> 系统变量设置为 <code>ON</code> 时:</p><ul><li>上述<code>TIMESTAMP</code>列的默认自动行为被取消,意味着所有的<code>TIMESTAMP</code>列都需要明确指定是否需要自动填充当前时间戳,包括在插入和更新时。</li><li>你需要显式地使用 <code>DEFAULT CURRENT_TIMESTAMP</code> 和 <code>ON UPDATE CURRENT_TIMESTAMP</code> 来指定自动填充的行为。</li></ul><p><strong>配置与影响</strong></p><ul><li><strong>配置方式</strong>:可以通过在MySQL配置文件 如my.cnf或my.ini 中的 <code>[mysqld]</code> 部分设置 <code>explicit_defaults_for_timestamp ON</code>,或者在启动MySQL服务时通过命令行参数 <code>--explicit-defaults-for-timestamp ON</code> 来启用此特性。</li><li><strong>影响</strong>:这一改变增强了对<code>TIMESTAMP</code>列的控制,使得数据库管理员和开发者可以更加精确地控制哪些列需要自动更新,避免了过去因默认行为可能引起的混淆或不符合预期的数据处理问题。</li></ul><p><strong>版本注意事项</strong></p><ul><li>从MySQL 5.6.6开始引入了这个系统变量,但是默认值为 <code>OFF</code>,意味着老的行为仍然保持。</li><li>MySQL 8.0中,<code>explicit_defaults_for_timestamp</code> 已经被移除,因为8.0版本中<code>TIMESTAMP</code>列的默认行为已经永久性地变为需要显式指定,这实际上默认启用了之前通过该变量开启的功能。</li></ul><p>选择哪种类型取决于具体的应用需求,包括日期范围、时区处理需求以及是否需要自动更新特性。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/27/f0d51d02/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL小版本升级（8.0.36-＞8.0.37)</title>
      <link>https://blog.eucalyptus.cc/2024/06/21/9ce04f43/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/21/9ce04f43/</guid>
      <pubDate>Fri, 21 Jun 2024 06:37:36 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;关于MySQL升级的话MySQL官方文档上面介绍了2个方法,’就地升级’和‘逻辑升级’。’就地升级‘就是升级底层的RPM包&lt;br&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>关于MySQL升级的话MySQL官方文档上面介绍了2个方法,’就地升级’和‘逻辑升级’。’就地升级‘就是升级底层的RPM包<br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img1.avif"><br>而‘逻辑升级’就是将旧MySQL数据库上的信息迁移到新MySQL数据库上。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img2.avif"></p><p>本篇文章介绍到的是RPM包升级</p><p>升级MySQL版本的典型步骤包括:</p><ul><li><p><strong>备份</strong>:在进行任何数据库升级之前,最重要的是做好全面的数据备份,包括二进制日志、数据文件等,以防升级过程中发生任何不可预料的问题。</p></li><li><p><strong>下载新版本RPM包</strong>:从MySQL官方网站或其他可信源下载对应的新版本RPM包,确保下载的版本与你的系统架构 如x86_64 相匹配。</p></li><li><p><strong>停止MySQL服务</strong>:在升级前,你需要确保MySQL服务已经停止运行,以避免数据损坏或冲突。</p></li><li><p><strong>安装新版本RPM包</strong>:使用RPM命令 如<code>yum install</code>或<code>dnf install</code>,取决于你的系统包管理器 安装下载的新版本MySQL RPM包。这一步骤会自动处理依赖关系,并可能替换旧版本的文件和配置。</p></li><li><p><strong>数据兼容性检查与迁移</strong>:虽然直接使用RPM升级通常旨在保持向下兼容,但有时新版本可能会要求对数据结构进行调整。在重大版本升级时,遵循MySQL官方的升级指南特别重要,以检查和执行任何必要的数据迁移步骤。</p></li><li><p><strong>配置更新</strong>:升级后,可能需要手动调整或验证配置文件 如<code>my.cnf</code> ,以适应新版本的配置需求或利用新特性。</p></li><li><p><strong>启动MySQL服务并验证</strong>:完成上述步骤后,启动MySQL服务,并进行一系列的测试来验证升级是否成功,包括检查数据库的运行状态、数据的完整性以及新功能的可用性。</p></li><li><p><strong>性能与安全优化</strong>:根据需要,可能还要对新版本进行性能调优和安全加固。</p></li></ul><p><strong>1.停止MySQL服务</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br><span class="line">systemctl status mysqld</span><br></pre></td></tr></table></figure><p>**2.**卸载旧的MySQL8.0.36 RPM包,卸载的时候必须按顺序卸载,否则会由依赖报错</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">rpm -qa | grep mysql</span><br><span class="line">rpm -evh mysql-community-server-8.0.36-1.el7.x86_64</span><br><span class="line">rpm -evh mysql-community-client-8.0.36-1.el7.x86_64</span><br><span class="line">rpm -evh mysql-community-icu-data-files-8.0.36-1.el7.x86_64</span><br><span class="line">rpm -evh mysql-community-libs-8.0.36-1.el7.x86_64</span><br><span class="line">rpm -evh mysql-community-client-plugins-8.0.36-1.el7.x86_64</span><br><span class="line">rpm -evh mysql-community-common-8.0.36-1.el7.x86_64</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img3.avif"></p><p>**3.去官网下载新的MySQL RPM包 ** <a href="https://dev.mysql.com/downloads/mysql/">https://dev.mysql.com/downloads/mysql/</a></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">wget https://dev.mysql.com/get/Downloads/MySQL-8.0/mysql-8.0.37-1.el9.x86_64.rpm-bundle.tar</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img5.avif"></p><p><strong>4.解压并安装,安装的时候也要按顺序安装,否则会报依赖错误</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">tar -xvf mysql-8.0.37-1.el9.x86_64.rpm-bundle.tar</span><br><span class="line">rpm -ivh mysql-community-common-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-libs-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-client-plugins-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-libs-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-client-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-icu-data-files-8.0.37-1.el9.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-server-8.0.37-1.el9.x86_64.rpm</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>5.重启MySQL服务</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl <span class="keyword">start</span> mysqld</span><br></pre></td></tr></table></figure><p><strong>6.登陆MySQL查看版本</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> version()</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-21/img6.avif"></p><p><strong>注意事项:</strong></p><ul><li><p><strong>数据兼容性检查与迁移</strong>:不同版本的MySQL可能在数据存储格式、系统表结构、索引机制等方面有所差异。升级过程需要检查现有数据库的数据结构与新版本的兼容性,必要时对数据进行迁移或转换,确保数据能够在新版本中正确存储和访问。</p></li><li><p><strong>二进制日志与事务日志处理</strong>:在升级前,MySQL会检查并处理现有的二进制日志和事务日志,确保在升级过程中及升级后能够正确地恢复未完成的事务或重放日志,维持数据一致性。</p></li><li><p><strong>配置文件与系统变量更新</strong>:新版本MySQL可能引入新的配置选项,废弃旧的配置项,或者修改默认设置。升级过程中会自动或手动更新<code>my.cnf</code>等配置文件,以及相应的系统变量,以匹配新版本的要求。</p></li><li><p><strong>执行引擎与存储引擎升级</strong>:MySQL的核心执行引擎和存储引擎 如InnoDB 在不同版本间可能有显著改进。升级过程中会对这些引擎进行更新,包括但不限于性能优化、新功能集成和bug修复,这可能需要对存储的数据进行一定程度的重构或优化。</p></li><li><p><strong>API与协议变化</strong>:如果MySQL的客户端&#x2F;服务器协议、库接口 如libmysqlclient 有所改变,升级过程需要确保所有依赖这些API的应用程序也相应地更新,以保证与新版本数据库的兼容。</p></li><li><p><strong>功能与性能增强</strong>:新版本通常会引入新的SQL语法、函数、存储过程等特性,以及性能上的优化。升级过程中可能需要对数据库设计、查询语句、触发器、视图等进行审查和调整,以利用新版本的功能优势。</p></li><li><p><strong>安全与权限模型更新</strong>:MySQL的安全机制和权限系统也可能随版本升级而变化,涉及密码哈希算法、加密模块、安全相关的系统变量等。升级时会调整相关设置,确保数据库的安全性得到提升。</p></li><li><p><strong>备份与回滚策略</strong>:在执行升级前,通常需要进行全面的数据库备份,以防升级失败或出现意外情况。同时,制定详细的回滚计划,确保在出现问题时能够迅速恢复到升级前的状态。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/21/9ce04f43/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL 自旋锁（spin lock）</title>
      <link>https://blog.eucalyptus.cc/2024/06/17/906121fc/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/17/906121fc/</guid>
      <pubDate>Mon, 17 Jun 2024 05:37:29 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;什么是自旋锁?为什么要使用自旋锁?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;MySQL中的自旋锁,特别是在InnoDB存储引擎中,是一种特殊的锁机制,它用于解决并发控制问题,尤其是在短时间运行的事务中。自旋锁与传统的互斥锁 Mutex</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>什么是自旋锁?为什么要使用自旋锁?</strong></p><p>MySQL中的自旋锁,特别是在InnoDB存储引擎中,是一种特殊的锁机制,它用于解决并发控制问题,尤其是在短时间运行的事务中。自旋锁与传统的互斥锁 Mutex 有所不同,主要区别在于线程等待锁的行为。</p><p>在互斥锁机制下,如果一个线程尝试获取一个已经被其他线程持有的锁,该线程会立即放弃CPU使用权,进入睡眠状态,然后被放入操作系统等待队列。一旦锁被释放,操作系统会选择一个等待该锁的线程唤醒,这个过程涉及上下文切换,有一定的开销。</p><p>相比之下,自旋锁在发现锁已被占用时,并不会立即让出CPU,而是会在原地执行一个循环 即“自旋” ,反复检查锁是否已经释放。这样的好处是可以避免线程上下文切换的开销,对于预计等待时间很短的情况特别有利,因为它允许线程几乎立刻重新尝试获取锁。自旋锁适用于锁的持有时间很短,自旋等待的成本低于线程上下文切换成本的场景。</p><p>然而,如果锁被占用的时间较长,自旋锁就会导致等待的线程消耗CPU资源,进行无意义的循环操作,这被称为“忙等待”。为了避免这种情况,MySQL 特别是InnoDB 提供了参数 如 innodb_spin_wait_delay 来控制自旋的次数或等待时间,之后如果锁仍未获得,线程会退化为传统的睡眠等待,以防止CPU资源的过度浪费。</p><p>总的来说,自旋锁是一种优化并发性能的手段,适用于低冲突、短时间锁定的场景,旨在通过减少线程上下文切换来提升系统效率。但在实际应用中,需要权衡自旋等待与上下文切换的成本,合理配置以达到最佳性能。</p><p><strong>自旋锁是什么层的?</strong></p><p>自旋锁是在数据库管理系统 DBMS 的存储引擎层实现的,具体到MySQL,它主要是在InnoDB存储引擎内部实现的。InnoDB是MySQL中最常用的事务型存储引擎,支持ACID 原子性、一致性、隔离性、持久性 事务处理。</p><p>自旋锁属于较低级别的同步机制,位于操作系统的线程管理和数据库的并发控制之间。它主要用于解决数据库内部的数据结构访问冲突,比如缓冲池 Buffer Pool 中的页面、锁列表或其他内部资源的并发访问控制。在InnoDB中,当一个线程试图访问某个资源时,如果该资源已被其他线程占用,请求线程可能会先尝试使用自旋锁快速重试获取锁,而不是立即让出CPU控制权进入休眠状态。</p><p>因此,自旋锁的实现和管理是数据库引擎内部的细节,对上层SQL查询处理逻辑透明,用户在编写SQL语句时通常不需要直接考虑自旋锁的使用。开发者和DBA更多关注的是如何通过调整数据库参数 如前面提到的 innodb_spin_wait_delay 和 innodb_sync_spin_loops 来优化存储引擎的并发性能。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/17/906121fc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>ON DUPLICATE KEY UPDATE 子句和 REPLACE INTO 语句</title>
      <link>https://blog.eucalyptus.cc/2024/06/11/62c1ee8c/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/11/62c1ee8c/</guid>
      <pubDate>Tue, 11 Jun 2024 09:26:03 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;&lt;code&gt;ON DUPLICATE KEY UPDATE&lt;/code&gt; &lt;strong&gt;子句和&lt;/strong&gt; &lt;code&gt;REPLACE INTO&lt;/code&gt;&lt;/strong&gt; 语句都是 MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong><code>ON DUPLICATE KEY UPDATE</code> <strong>子句和</strong> <code>REPLACE INTO</code></strong> 语句都是 MySQL 提供的用于处理数据插入时的冲突解决策略,但它们在处理方式和效果上有着本质的区别:</p><p><strong>ON DUPLICATE KEY UPDATE</strong></p><ul><li><p><strong>操作流程</strong>:当尝试插入一条新记录时,如果该记录的主键或唯一索引与现有记录冲突,<strong><code>ON DUPLICATE KEY UPDATE</code></strong> 子句将触发,并执行更新操作,而不是插入新记录。只有冲突的行会被更新,不会影响到其他行。</p></li><li><p><strong>数据处理</strong>:它允许你指定哪些列需要在冲突发生时进行更新,以及如何更新这些列的值。这意味着你可以只修改部分字段而保留其他字段的原有值。</p></li><li><p><strong>资源消耗</strong>:由于它不涉及记录的删除,所以在处理冲突时相对节省资源。但如果更新涉及大量字段或并发操作,可能会影响性能。</p></li><li><p><strong>适用场景</strong>:适合于需要在插入时检查记录是否存在,并根据情况更新某些字段的场景,如统计计数、用户信息更新等。</p></li></ul><p><strong>REPLACE INTO</strong></p><ul><li><p><strong>操作流程</strong>:<strong><code>REPLACE INTO</code></strong> 在尝试插入新记录时,如果发现主键或唯一索引冲突,它会先删除原有的冲突行,然后插入新的记录。这实质上是“删除 插入”的操作。</p></li><li><p><strong>数据处理</strong>:整个记录会被替换,不仅仅是冲突的字段,这意味着如果新记录没有指定某些字段的值,这些字段将使用默认值或NULL 如果没有默认值 。原有的行数据将完全被新数据覆盖。</p></li><li><p><strong>资源消耗</strong>:相比** <code>ON DUPLICATE KEY UPDATE</code>,<code>REPLACE INTO</code> **可能会消耗更多的资源,因为它涉及到删除旧记录和插入新记录两个操作,特别是在处理大表时可能会影响性能。</p></li><li><p><strong>适用场景</strong>:适用于需要确保每个唯一键对应的记录完全替换的场景,例如,当需要确保数据的绝对新鲜性,不关心被替换记录的其他字段值时。</p></li></ul><p>总结:</p><ul><li><strong>数据保留性</strong>:**<code>ON DUPLICATE KEY UPDATE</code> <strong>保留了原有记录中未被更新字段的值,而</strong> <code>REPLACE INTO</code> **则会替换整行数据。</li><li><strong>资源和性能</strong>:<code>**ON DUPLICATE KEY UPDA**TE</code> 在处理冲突时较为轻量,而 <code>R**EPLACE INTO**</code>** **可能会因涉及删除和插入而消耗更多资源。</li><li><strong>应用场景</strong>:根据是否需要保留原有记录的非冲突字段值以及性能考量,选择合适的操作方式。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/11/62c1ee8c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>ON DUPLICATE KEY UPDATE 子句</title>
      <link>https://blog.eucalyptus.cc/2024/06/11/110765e0/</link>
      <guid>https://blog.eucalyptus.cc/2024/06/11/110765e0/</guid>
      <pubDate>Tue, 11 Jun 2024 09:04:41 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;&lt;code&gt;ON DUPLICATE KEY UPDATE&lt;/code&gt;&lt;/strong&gt; 是 MySQL 中的一个 SQL 语句中的子句,主要用于在执行 &lt;code&gt;INSERT&lt;/code&gt;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong><code>ON DUPLICATE KEY UPDATE</code></strong> 是 MySQL 中的一个 SQL 语句中的子句,主要用于在执行 <code>INSERT</code> 操作时处理可能出现的重复键值冲突。当尝试插入的记录导致唯一索引或主键约束冲突时 即试图插入的记录的键值已经存在于表中 ,此子句会触发一个更新操作,而不是抛出错误。</p><p>官方文档:<a href="https://dev.mysql.com/doc/refman/8.4/en/insert-on-duplicate.html">https://dev.mysql.com/doc/refman/8.4/en/insert-on-duplicate.html</a></p><p><strong>基本语法</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> table_name (column1, column2, ...)</span><br><span class="line"><span class="keyword">VALUES</span> (value1, value2, ...)</span><br><span class="line"><span class="keyword">ON</span> DUPLICATE KEY <span class="keyword">UPDATE</span></span><br><span class="line">column1 value1,</span><br><span class="line">column2 value2,</span><br><span class="line">...;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>ON DUPLICATE KEY UPDATE子句处理逻辑</strong></p><p>语句是根据唯一索引判断记录是否重复的。当执行插入操作时,如果唯一键不冲突(表中不存在记录),则执行插入操作;如果遇到唯一键冲突(表中存在记录),则会执行更新操作,使用给定的新值来更新冲突行中的列。</p><h2 id="示例"><a href="#示例" class="headerlink" title="示例"></a>示例</h2><p>假设我们有一个用户表 <code>users</code>,包含 <code>id</code> 主键 、<code>username</code> 用户名,唯一 和 <code>email</code> 三个字段。现在我们要插入或更新一条用户记录,如果用户名已经存在,则只更新用户的邮箱地址。</p><p>表结构如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> users (</span><br><span class="line">id <span class="type">INT</span> AUTO_INCREMENT <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">username <span class="type">VARCHAR</span>(<span class="number">255</span>) <span class="keyword">UNIQUE</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">255</span>)</span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>不存在记录,插入的情况</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-11/img1.avif"></p><p><strong>使用insert into插入已有的username,可以看到会报错</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-11/img2.avif"></p><p>** 使用<code>ON DUPLICATE KEY UPDATE</code> 子句插入已有的username,没有报错执行成功**</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-06-11/img3.avif"></p><p><strong>总结</strong>:在上面这个例子中,如果尝试插入的用户名 <code>&#39;杜甫&#39;</code> 已经存在于表中,由于 <code>username</code> 字段设置了唯一约束,这将触发** <code>ON DUPLICATE KEY UPDATE</code>** 子句。然后,这条 SQL 语句不会插入新的记录,而是执行更新操作,将该用户名对应的邮箱地址更新为 <code>&#39;libai 163.com&#39;</code>。如果用户名不存在,则正常插入新记录。</p><p>可能看到这里就会有人问了那么为什么不使用<strong>update</strong>呢,简单的来说不都是更新数据吗?</p><p>使用** <code>ON DUPLICATE KEY UPDATE</code> **与直接使用 **<code>UPDATE</code> **语句的主要区别在于处理数据插入和更新的策略和目的。</p><p>下面是选择** <code>ON DUPLICATE KEY UPDATE</code> <strong>而不直接使用</strong> <code>UPDATE</code>** 的几个主要原因:</p><ul><li><p><strong>同时处理插入与更新</strong>:**<code>ON DUPLICATE KEY UPDATE</code> **允许在一个操作中同时尝试插入新记录和更新现有记录。如果记录不存在,就插入新记录;如果存在 根据唯一索引或主键判断 ,则更新记录。这样可以在不确定记录是否存在的情况下,通过一次操作完成“插入或更新”,简化逻辑和代码。</p></li><li><p><strong>减少查询开销</strong>:相比于先执行查询判断记录是否存在,再根据结果决定执行 <strong><code>INSERT</code></strong> 或 <strong><code>UPDATE</code></strong>,**<code>ON DUPLICATE KEY UPDATE</code> **直接在数据库层面处理,减少了额外的查询请求,降低了网络和计算开销。</p></li><li><p><strong>原子性操作</strong>:在事务中使用时,<strong><code>ON DUPLICATE KEY UPDATE</code></strong> 作为一个整体操作,要么全部成功,要么全部失败,保证了数据操作的原子性,这对于维护数据一致性非常重要。</p></li><li><p><strong>避免并发冲突</strong>:在高并发环境下,先查询后更新可能会遇到“丢失更新”的问题。而 <code>**ON** **DUPLICATE KEY UPDATE**</code> 通过数据库的内置机制处理冲突,有助于减少这类并发问题。</p></li><li><p><strong>简化逻辑</strong>:对于批量数据处理,特别是导入大量数据时,使用** <code>ON DUPLICATE KEY UPDATE</code> **可以显著简化代码逻辑,避免编写复杂的循环判断逻辑。</p></li></ul><p><code>**总结**:**ON DUPLICATE KEY UPDATE**</code>** **提供了一种高效、简洁的方式来处理那些在插入数据时可能遇到的重复记录问题,特别适用于那些需要“如果存在则更新,否则插入”的场景,而直接使用 <code>UPDATE</code> 则更适合于确定记录已经存在并且需要修改的情况。</p><p>当然还有<code>**ON DUPLICATE KEY UPDATE**</code> 子句和 <strong><code>REPLACE INTO</code></strong> 语句的区别会在下一篇文章中介绍</p><p><strong>使用 <code>ON DUPLICATE KEY UPDATE</code> 子句的场景及优缺点</strong></p><table><thead><tr><th>使用场景</th><th>优点</th><th>缺点</th><th><strong>数据去重与更新</strong></th><th>自动处理冲突,减少编程逻辑</th><th>对于大量并发可能产生锁竞争,影响性能</th><th><strong>数据同步</strong></th><th>简化数据同步流程,避免手动检查</th><th>更新逻辑需精确设计,以免误更新非冲突字段</th></tr></thead><tbody><tr><td><strong>统计计数</strong></td><td>有效累加计数,避免重复记录</td><td>需要确保更新逻辑正确,避免数据不一致</td><td><strong>确保数据一致</strong></td><td>支持事务处理,增强数据完整性</td><td>对于复杂更新逻辑处理能力有限</td><td><strong>简化逻辑</strong></td><td>一行命令完成“插入或更新”,代码简洁</td><td>对唯一性约束依赖性强,表设计需预先规划</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td><td>—</td></tr></tbody></table>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/06/11/110765e0/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>EXPLAIN执行计划详解</title>
      <link>https://blog.eucalyptus.cc/2024/05/24/68f36497/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/24/68f36497/</guid>
      <pubDate>Fri, 24 May 2024 07:06:17 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;code&gt;EXPLAIN&lt;/code&gt; 是 MySQL 中的一个非常实用的命令,主要用于分析 SQL 查询语句的执行计划 Query Execution Plan,QEP 。通过这个命令,用户可以获取到数据库引擎如何执行特定的 SQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><code>EXPLAIN</code> 是 MySQL 中的一个非常实用的命令,主要用于分析 SQL 查询语句的执行计划 Query Execution Plan,QEP 。通过这个命令,用户可以获取到数据库引擎如何执行特定的 SQL 语句的详细信息,这对于优化查询性能、理解查询的工作方式以及识别潜在的性能瓶颈非常有帮助。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-24/img1.avif" alt="EXPLAIN执行计划"></p><h3 id="EXPLAIN输出字段说明"><a href="#EXPLAIN输出字段说明" class="headerlink" title="EXPLAIN输出字段说明"></a>EXPLAIN输出字段说明</h3><table><thead><tr><th>列名</th><th>含义</th></tr></thead><tbody><tr><td>id</td><td>操作表顺序</td></tr><tr><td>select_type</td><td>select类型</td></tr><tr><td>table</td><td>操作的表名</td></tr><tr><td>partitions</td><td>访问的分区信息,非分区表则为NULL</td></tr><tr><td>type</td><td>数据扫描方式</td></tr><tr><td>possible_keys</td><td>可能使用的索引</td></tr><tr><td>key</td><td>实际选用的索引,如果为NULL表示未使用索引</td></tr><tr><td>key_len</td><td>使用索引字段的长度,复合索引为所有字段长度之和</td></tr><tr><td>ref</td><td>使用那些列或者常量来查找数据</td></tr><tr><td>rows</td><td>预计检查的行数,为MySQL的行数估算值</td></tr><tr><td>filtered</td><td>返回行占表总行数的百分比估计</td></tr><tr><td>Extra</td><td>执行详情,附加信息</td></tr></tbody></table><h3 id="id"><a href="#id" class="headerlink" title="id"></a>id</h3><p>这是一个递增的数字,表示查询中SELECT子句或操作的执行顺序。具有相同ID号的行表示它们可以被同时执行。子查询的ID会大于其外层查询的ID。</p><h3 id="select-type"><a href="#select-type" class="headerlink" title="select_type"></a>select_type</h3><p>常见的类型有</p><ul><li><strong>SIMPLE</strong>:简单查询,不包含子查询或者qu<strong>UNION</strong></li><li><strong>PRIMARY</strong>:最外层的查询</li><li><strong>Subquery</strong>:子查询</li><li><strong>UNION</strong>、<strong>DEPENDENT UNION</strong>:UNION中的子查询依赖于外部查询</li><li><strong>UNION RESULT</strong>:UNION的结果</li><li><strong>Dependent subquery</strong>:依赖于外查询的子查询</li></ul><h3 id="table"><a href="#table" class="headerlink" title="table"></a>table</h3><p>显示这一行的数据来自哪个表。如果执行的是多表连接查询,这个列表会列出所有参与的表。</p><h3 id="partitions"><a href="#partitions" class="headerlink" title="partitions"></a>partitions</h3><p>在分区表的情况下,显示可能被访问的分区。如果不是分区表,则此列为NULL。</p><h3 id="type"><a href="#type" class="headerlink" title="type"></a>type</h3><ul><li><strong>ALL</strong>:全表扫描</li><li><strong>index</strong>:遍历索引树</li><li><strong>range</strong>:对索引树进行范围扫描</li><li><strong>ref</strong>:使用非唯一索引或唯一索引前缀进行查询</li><li><strong>eq_ref</strong>:多表连接中,使用主键或唯一索引进行查询</li><li><strong>const&#x2F;system</strong>:根据主键或唯一索引进行查询</li><li><strong>NULL</strong>:不需要访问表结构或索引直接得到结果</li></ul><h3 id="possible-keys"><a href="#possible-keys" class="headerlink" title="possible_keys"></a>possible_keys</h3><p>列出MySQL可能使用的索引来提高查询效率。如果该列为NULL,表示没有可用的索引。</p><h3 id="key"><a href="#key" class="headerlink" title="key"></a>key</h3><p>实际上被MySQL选择使用的索引。如果为NULL,则没有使用索引。</p><h3 id="key-len"><a href="#key-len" class="headerlink" title="key_len"></a>key_len</h3><p>使用的索引字段的长度。如果是复合索引,这个长度是组合索引中所有字段的长度总和。</p><h3 id="ref"><a href="#ref" class="headerlink" title="ref"></a>ref</h3><p>显示索引的哪一列 或常数 被用来执行比较操作。如果是func,表示使用了某些内部函数。</p><h3 id="row"><a href="#row" class="headerlink" title="row"></a>row</h3><p>MySQL预计为了找到所需的行而必须检查的行数。这不是实际的行数,而是一个估算值。</p><h3 id="filtered"><a href="#filtered" class="headerlink" title="filtered"></a>filtered</h3><p>表示MySQL通过查询条件过滤后,估计返回结果集的比例。</p><h3 id="Extra"><a href="#Extra" class="headerlink" title="Extra"></a>Extra</h3><p>常见的类型有</p><ul><li><strong>Using filesort</strong>:在没有索引的列上进行排序</li><li><strong>Using index</strong>:不需要回表</li><li><strong>Using where</strong>:部分条件不在索引中</li><li><strong>Using temporary</strong>:使用临时表来存储结果集,常用于分组</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/24/68f36497/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>ProxySQL路由策略实现读写分离</title>
      <link>https://blog.eucalyptus.cc/2024/05/22/0bac6373/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/22/0bac6373/</guid>
      <pubDate>Wed, 22 May 2024 06:00:08 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;目的:配置proxysql路由策略后将不同用户的不同请求路由到不同的节点,实现读写分离&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;img</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>目的:配置proxysql路由策略后将不同用户的不同请求路由到不同的节点,实现读写分离</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img1.avif"></p><p><strong>前提条件:</strong></p><ul><li>配置表mysql_replication_hostgroups,10为写组,20为读组<br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img2.avif"></li><li>mysql_users表中已添加用户writer用户加入10写组,reader用户加入20读组</li><li><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img3.avif"></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img4.avif"><br>** 配置路由策略:**</p><p>在mysql_query_rules表中配置, 将reader,writer用户的select 读 请求路由到20 读组 ,也就是后端的slave节点,将writer用户的DDL,DML请求路由到10 写组 ,也就是后端的master节点</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img7.avif"></p><p><strong>测试:</strong></p><p>用writer登陆,执行一个DQL,发现请求被路由到了slave节点 </p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img8.avif"><br> <br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img9.avif"><br>还是用writer用户登陆创建一个表,发现请求被路由到了master </p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img10.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-22/img11.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/22/0bac6373/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>关于Docker启动后如何添加新的端口映射</title>
      <link>https://blog.eucalyptus.cc/2024/05/15/38963bc2/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/15/38963bc2/</guid>
      <pubDate>Wed, 15 May 2024 06:30:48 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;前段时间在用docker部署服务的时候发现，容器已经启动，但是需要新的端口映射（&lt;strong&gt;即容器在启动的时候只进行了部分的端口映射&lt;/strong&gt;），经过查询资料后发现现在网上有2种方法，&lt;strong&gt;一中是修改json文件&lt;/strong&gt;。&lt;strong&gt;另一</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>前段时间在用docker部署服务的时候发现，容器已经启动，但是需要新的端口映射（<strong>即容器在启动的时候只进行了部分的端口映射</strong>），经过查询资料后发现现在网上有2种方法，<strong>一中是修改json文件</strong>。<strong>另一种是将已经运行的容器打包成一个新的镜像，然后基于打包后的镜像来在启动容器的时候开启全部的端口映射</strong>。但是经过我的测试发现第一种修改json文件的方式好像会重置容器。</p><h2 id="方法一"><a href="#方法一" class="headerlink" title="方法一"></a>方法一</h2><p><strong>停止docker服务</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop docker</span><br></pre></td></tr></table></figure><p>修改json文件，一般要修改的文件在&#x2F;var&#x2F;lib&#x2F;docker&#x2F;containers&#x2F;下，找到要修改的容器然后进入目录即可看到<strong>hostconfig.json</strong> 和<strong>config.v2.json</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-05-15/img1.avif" alt="配置文件"></p><ul><li><p><strong>config.v2.json：</strong> Docker容器的配置文件之一，包含了容器的配置信息，如环境变量、端口映射、卷挂载点等。版本2表示这是Docker引入新配置格式后的文件。</p></li><li><p><strong>hostconfig.json：</strong> 另一个重要的Docker容器配置文件，包含了容器的主机配置信息，比如网络模式、资源限制(如CPU份额和内存限制)、重启策略等。</p></li></ul><p><strong>按照格式添加端口即可</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-05-15/img2.avif" alt="添加端口"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-05-15/img3.avif" alt="添加端口2"></p><p><strong>启动docker服务</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl start docker</span><br></pre></td></tr></table></figure><p><strong>经过这种方式修改后确实会添加新的端口映射，但是容器也好像会被重置。除了这个问题因为这种方式还涉及到了docker的启停，若是容器过多的话会影响到别的业务（不推荐）</strong></p><h2 id="方法二"><a href="#方法二" class="headerlink" title="方法二"></a>方法二</h2><p>将容器打包成镜像，然后基于打包后的镜像来在启动容器的时候开启全部的端口映射即可</p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2024-05-15/img4.avif" alt="方法二"></p><p><strong>若是还有别的方法或者文章中有错误的话请指出！！！</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/15/38963bc2/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>基于ProxySQL中间件实现MySQL的读写分离</title>
      <link>https://blog.eucalyptus.cc/2024/05/14/e9a6d4ee/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/14/e9a6d4ee/</guid>
      <pubDate>Tue, 14 May 2024 06:16:45 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;h2 id=&quot;ProxySQL简介&quot;&gt;&lt;a href=&quot;#ProxySQL简介&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><h2 id="ProxySQL简介"><a href="#ProxySQL简介" class="headerlink" title="ProxySQL简介"></a>ProxySQL简介</h2><p><strong>ProxySQL</strong>是一个高性能的MySQL协议代理,它支持多种数据库后端,包括Amazon Aurora、RDS、ClickHouse、Galera、Group Replication、MariaDB Server、NDB、Percona Server等。它的设计目标是为了提高数据库访问的灵活性、性能和安全性。</p><p><strong>ProxySQL</strong>的核心功能包括:</p><ul><li><p><strong>读写分离</strong>:能够智能地将读请求路由到从库 Slave ,而写请求则发送到主库 Master ,以此来优化负载均衡和提高读取性能。</p></li><li><p><strong>负载均衡</strong>:可以根据不同的策略 如连接数、响应时间、服务器权重等 在多个后端数据库之间分配查询,以优化资源利用。</p></li><li><p><strong>高可用性</strong>:ProxySQL能够监控后端数据库的状态,如果某个数据库实例变得不可用,它会自动重新路由流量到其他健康的实例,从而提高系统的整体可用性。</p></li><li><p><strong>查询缓存</strong>:对于重复的查询,ProxyQL可以缓存结果,减少对数据库的访问,显著提升响应速度。</p></li><li><p><strong>安全控制</strong>:提供了白名单、黑名单以及查询过滤功能,帮助防止SQL注入攻击,增强数据库的安全性。</p></li><li><p><strong>动态配置与监控</strong>:允许管理员通过管理接口实时调整配置,同时提供详细的监控和日志记录功能,便于故障排查和性能调优。</p></li></ul><p><strong>ProxySQL</strong>作为一个中间件,位于应用程序和数据库之间,它理解MySQL协议,能够根据协议内容做出智能决策,而不仅仅是盲目地转发流量。这使得ProxySQL成为处理复杂数据库架构和提升数据库访问性能的强大工具。</p><h2 id="ProxySQL安装"><a href="#ProxySQL安装" class="headerlink" title="ProxySQL安装"></a>ProxySQL安装</h2><p>下面的安装教程是基于RedHat &#x2F; CentOS的,其他的操作系统可以去官网查看<a href="https://www.proxysql.com/documentation/installing-proxysql/">proxysql官网</a></p><p> 我们都知道在RedHat &#x2F; CentOS安装一个服务,一般有三种方法,RPM包安装,源码编译安装,YUM安装,相比于RPM需要依赖的安装和源码编译复杂的安装方式YUM安装是最简单的,下面介绍到的就是YUM安装。</p><h3 id="配置YUM仓库"><a href="#配置YUM仓库" class="headerlink" title="配置YUM仓库"></a>配置YUM仓库</h3><p>下面的仓库是2.6的版本,你可以选择需要的版本来配置,目前官方维护的版本有:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img1.avif"></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">cat &lt;&lt;EOF | tee /etc/yum.repos.d/proxysql.repo</span><br><span class="line"><span class="section">[proxysql_repo]</span></span><br><span class="line">name ProxySQL repository</span><br><span class="line">baseurl https://repo.proxysql.com/ProxySQL/proxysql-2.6.x/centos/\$releasever</span><br><span class="line">gpgcheck 1</span><br><span class="line">gpgkey https://repo.proxysql.com/ProxySQL/proxysql-2.6.x/repo_pub_key</span><br><span class="line">EOF</span><br></pre></td></tr></table></figure><h3 id="YUM安装"><a href="#YUM安装" class="headerlink" title="YUM安装"></a>YUM安装</h3><p>安装,查看版本,设置开机启动立即生效</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">yum -y install proxysql</span><br><span class="line">proxysql --version</span><br><span class="line">systemctl <span class="built_in">enable</span> --now proxysql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img2.avif"></p><h2 id="关于读写分离的实现"><a href="#关于读写分离的实现" class="headerlink" title="关于读写分离的实现"></a>关于读写分离的实现</h2><h3 id="集群信息"><a href="#集群信息" class="headerlink" title="集群信息"></a>集群信息</h3><table><thead><tr><th>proxysql</th><th>192.168.0.114</th><th>master</th><th>192.168.0.104</th></tr></thead><tbody><tr><td>slave1</td><td>192.168.0.103</td><td>slave2</td><td>192.168.0.102</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td><td>—</td></tr><tr><td>使用mysql客户端工具</td><td></td><td></td><td></td></tr></tbody></table><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -P 6032 -h 127.0.0.1 -uadmin -padmin</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img3.avif"></p><p><strong>在mysql_servers表中配置后端数据库信息</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> mysql_servers (hostgroup_id,hostname,port,weight,comment) <span class="keyword">values</span> (<span class="number">10</span>,<span class="string">&#x27;192.168.0.104&#x27;</span>,<span class="number">3306</span>,<span class="number">1</span>,<span class="string">&#x27;只写&#x27;</span>),(<span class="number">20</span>,<span class="string">&#x27;192.168.0.103&#x27;</span>,<span class="number">3306</span>,<span class="number">50</span>,<span class="string">&#x27;只读&#x27;</span>),(<span class="number">20</span>,<span class="string">&#x27;192.168.0.102&#x27;</span>,<span class="number">3306</span>,<span class="number">100</span>,<span class="string">&#x27;只读&#x27;</span>);</span><br><span class="line">load mysql servers <span class="keyword">to</span> runtime;</span><br><span class="line">save mysql servers <span class="keyword">to</span> disk;</span><br></pre></td></tr></table></figure><ul><li>设置的master的hostgroup_id为10 写组 ;</li><li>设置的slave的hostgroup_id为20 读组 ;</li><li>每次在proxysql执行完操作之后,需要手动加载至内存上,然后手动保存至磁盘上。</li></ul><p><strong>然后在搭建了MySQL主从复制的架构中的master上创建一个用户并授权</strong></p><p>** 注意:是master的mysql,不是Proxysql **</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">USER</span> <span class="string">&#x27;monitor&#x27;</span> <span class="string">&#x27;%&#x27;</span> IDENTIFIED <span class="keyword">WITH</span> caching_sha2_password <span class="keyword">BY</span> <span class="string">&#x27;new_password&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> replication client,replication slave <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;monitor&#x27;</span> <span class="string">&#x27;%&#x27;</span>;</span><br></pre></td></tr></table></figure><p><strong>在proxysql上添加该用户</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">set</span> mysql<span class="operator">-</span>monitor_username <span class="string">&#x27;monitor&#x27;</span>;</span><br><span class="line"><span class="keyword">set</span> mysql<span class="operator">-</span>monitor_password <span class="string">&#x27;password&#x27;</span>;</span><br><span class="line">load mysql variables <span class="keyword">to</span> runtime;</span><br><span class="line">save mysql variables <span class="keyword">to</span> disk;</span><br></pre></td></tr></table></figure><p>** 通过查看表mysql_server_ping_log了解后端云服务器状态信息**</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> mysql_server_ping_log limit <span class="number">3</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img4.avif"></p><p><strong>对后端定义的云服务器的分组进行读组和写组的设定</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> mysql_replication_hostgroups (writer_hostgroup,reader_hostgroup) <span class="keyword">values</span> (<span class="number">10</span>,<span class="number">20</span>);</span><br><span class="line">load mysql servers <span class="keyword">to</span> runtime;</span><br><span class="line">save mysql servers <span class="keyword">to</span> disk;</span><br></pre></td></tr></table></figure><p><strong>查看后端节点是否具有read_only权限</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> monitor.mysql_server_read_only_log limit <span class="number">3</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img5.avif"></p><p><strong>我们在后端的master上创建两个用户账户</strong></p><p>** 注意:是master的mysql,不是Proxysql **</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">USER</span> <span class="string">&#x27;reader&#x27;</span> <span class="string">&#x27;%&#x27;</span> IDENTIFIED <span class="keyword">WITH</span> caching_sha2_password <span class="keyword">BY</span> <span class="string">&#x27;new_password&#x27;</span>;</span><br><span class="line"><span class="keyword">CREATE</span> <span class="keyword">USER</span> <span class="string">&#x27;writer&#x27;</span> <span class="string">&#x27;%&#x27;</span> IDENTIFIED <span class="keyword">WITH</span> caching_sha2_password <span class="keyword">BY</span> <span class="string">&#x27;new_password&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> <span class="keyword">all</span> <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;reader&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;new_password&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> <span class="keyword">all</span> <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;writer&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;new_password&#x27;</span>;</span><br></pre></td></tr></table></figure><p><strong>在proxysql节点上添加刚才创建的用户</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> mysql_users(username,password,default_hostgroup,attributes,comment) <span class="keyword">values</span>(<span class="string">&#x27;writer&#x27;</span>,<span class="string">&#x27;password&#x27;</span>,<span class="number">10</span>,<span class="string">&#x27;&#123; address : % &#125;&#x27;</span>,<span class="string">&#x27;读写用户&#x27;</span>);</span><br><span class="line"><span class="keyword">insert into</span> mysql_users(username,password,default_hostgroup,attributes,comment) <span class="keyword">values</span>(<span class="string">&#x27;reader&#x27;</span>,<span class="string">&#x27;password&#x27;</span>,<span class="number">20</span>,<span class="string">&#x27;&#123; address : % &#125;&#x27;</span>,<span class="string">&#x27;只读用户&#x27;</span>);</span><br><span class="line">load mysql users <span class="keyword">to</span> runtime;</span><br><span class="line">save mysql users <span class="keyword">to</span> disk;</span><br></pre></td></tr></table></figure><p>至此,基本配置完毕</p><h2 id="测试读写分离"><a href="#测试读写分离" class="headerlink" title="测试读写分离"></a>测试读写分离</h2><p>我们在client端测试基于用户的读写分离</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img7.avif"></p><p>最后可以在stats库的stats_mysql_connection_pool 表中查看mysql后端链接和整体流量</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img8.avif"></p><p> 可以看到在102的节点上的 Queries 是15,而103节点上的 Queries 是6</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img9.avif"></p><p>这是因为我们配置的权重不同</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img10.avif"></p><p>当我们在client在执行一次查询,可以看到102节点上的 Queries增加了一次</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img11.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img12.avif"></p><h2 id="测试总结"><a href="#测试总结" class="headerlink" title="测试总结"></a>测试总结</h2><p>当我们用reader只读账号登陆和进行DML操作 <strong>这里也有个疑问,就是你可以在client上用只读用户登陆实例后可以进行DML,但是例如你执行了一个insert,你在cliet中可以查到你插入的值,但是你在登陆后端的server实例后会发现并没有这个插入的值</strong> ,会发现也是可行的, <strong>这里在slave节点上的实例中已经配置了read only</strong> 为什么呢?</p><p>在经过查询官方文档后发现我们没有配置路由测率和属性,也就是路由规则,我们在上面的测试中只是进行了基于用户的读写分离,而路由策略没有配置。 <strong>这里也可以理解为基于SQL语句实现读写分离</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img13.avif"></p><p>在mysql_query_rules中配置路由策略</p><p>下面的SQL将会限制只读用户的DML语句,关于这个表中的字段含义可以去看官方文档<a href="https://proxysql.com/documentation/main-runtime/#mysql_query_rules">Main (runtime tables definition) - ProxySQL</a></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> mysql_query_rules (rule_id, active, username,match_pattern, destination_hostgroup,apply) <span class="keyword">VALUES</span> (<span class="number">1</span>, <span class="number">1</span>,<span class="string">&#x27;reader&#x27;</span>, <span class="string">&#x27;^(SELECT)&#x27;</span>, <span class="number">20</span>, <span class="number">1</span>);</span><br><span class="line">load mysql query rules <span class="keyword">to</span> runtime;</span><br><span class="line">save mysql query rules <span class="keyword">to</span> disk;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>配置路由策略后在用只读用户去执行DML发现失败</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img14.avif"></p><h2 id="ProxySQL-Configuration-CLI"><a href="#ProxySQL-Configuration-CLI" class="headerlink" title="ProxySQL Configuration CLI"></a><strong>ProxySQL Configuration CLI</strong></h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-14/img15.avif"></p><p>关于上面<strong>proxysql</strong>数据库中内置库表的详解请参考官网文档<a href="https://proxysql.com/documentation/">Documentation - ProxySQL</a></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/14/e9a6d4ee/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中JOIN连接的实现算法</title>
      <link>https://blog.eucalyptus.cc/2024/05/07/d9200f5c/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/07/d9200f5c/</guid>
      <pubDate>Tue, 07 May 2024 06:52:49 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;我们都知道SQL的join关联表的使用方式,但是这次聊的是实现join的算法,join有三种算法,分别是Nested Loop Join,Hash join,Sort Merge Join。&lt;/p&gt;
&lt;h2 id=&quot;嵌套循环算法-NLJ&quot;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>我们都知道SQL的join关联表的使用方式,但是这次聊的是实现join的算法,join有三种算法,分别是Nested Loop Join,Hash join,Sort Merge Join。</p><h2 id="嵌套循环算法-NLJ"><a href="#嵌套循环算法-NLJ" class="headerlink" title="嵌套循环算法 NLJ"></a>嵌套循环算法 NLJ</h2><p>**嵌套循环算法 Nested-Loop Join,NLJ **是通过两层循环,用第一张表做Outter Loop,第二张表做Inner Loop,Outter Loop的每一条记录跟Inner Loop的记录作比较,符合条件的就输出。而NLJ又有3种细分的算法:嵌套循环算法又可以分为简单嵌套循环、索引嵌套循环、块嵌套循环。</p><h3 id="简单嵌套循环-SNLJ"><a href="#简单嵌套循环-SNLJ" class="headerlink" title="简单嵌套循环 SNLJ"></a>简单嵌套循环 SNLJ</h3><blockquote><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">` // 伪代码</span><br><span class="line">for (r in R) &#123;</span><br><span class="line">for (s in S) &#123;</span><br><span class="line">if (r satisfy condition s) &#123;</span><br><span class="line">output &lt;r, s&gt;;</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img1.avif"></p></blockquote><p>SNLJ就是两层循环全量扫描连接的两张表,得到符合条件的两条记录则输出,这也就是让两张表做笛卡尔积,比较次数是R * S,是比较暴力的算法,会比较耗时。</p><h3 id="索引嵌套循环-INLJ"><a href="#索引嵌套循环-INLJ" class="headerlink" title="索引嵌套循环* INLJ *"></a>索引嵌套循环* INLJ *</h3><blockquote><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">` // 伪代码</span><br><span class="line">for (r in R) &#123;</span><br><span class="line">for (si in SIndex) &#123;</span><br><span class="line">if (r satisfy condition si) &#123;</span><br><span class="line">output &lt;r, s&gt;;</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img2.avif"></p></blockquote><p>INLJ是在SNLJ的基础上做了优化,通过连接条件确定可用的索引,在Inner Loop中扫描索引而不去扫描数据本身,从而提高Inner Loop的效率。<br>而INLJ也有缺点,就是如果扫描的索引是非聚簇索引,并且需要访问非索引的数据,会产生一个回表读取数据的操作,这就多了一次随机的I&#x2F;O操作。</p><h3 id="块嵌套循环-BNLJ"><a href="#块嵌套循环-BNLJ" class="headerlink" title="块嵌套循环 *BNLJ *"></a>块嵌套循环 *BNLJ *</h3><blockquote><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">` // 伪代码</span><br><span class="line">for (r in R) &#123;</span><br><span class="line">for (sbu in SBuffer) &#123;</span><br><span class="line">if (r satisfy condition sbu) &#123;</span><br><span class="line">output &lt;r, s&gt;;</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line">&#125;`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img3.avif"></p></blockquote><p>扫描一个表的过程其实是先把这个表从磁盘上加载到内存中,然后在内存中比较匹配条件是否满足。但内存里可能并不能完全存放的下表中所有的记录。为了减少访问被驱动表的次数,我们可以首先将驱动表的数据批量加载到 Join Buffer 连接缓冲 ,然后当加载被驱动表的记录到内存时,就可以一次性和多条驱动表中的记录做匹配,这样可大大减少被驱动表的扫描次数,这就是 BNLJ 算法的思想。</p><h3 id="三种算法比较"><a href="#三种算法比较" class="headerlink" title="三种算法比较"></a>三种算法比较</h3><p>算法比较(外表大小R,内表大小S):</p><table><thead><tr><th>比较项</th><th>Simple Nested Loop Join</th><th>Block Nested Loop Join</th></tr></thead><tbody><tr><td>外表扫描次数</td><td>1</td><td>1</td></tr><tr><td>内表扫描次数</td><td>R</td><td>0</td></tr><tr><td>读取记录次数</td><td>R * S</td><td>R * IndexHeight</td></tr><tr><td>比较次数</td><td>R * S</td><td>R * S</td></tr><tr><td>回表次数</td><td>0</td><td>RS_Matches</td></tr></tbody></table><p><strong>整体效率比较:INLJ &gt; BNLJ &gt; SNLJ</strong></p><h2 id="哈希连接算法-Hash-Join"><a href="#哈希连接算法-Hash-Join" class="headerlink" title="哈希连接算法 Hash Join"></a>哈希连接算法 Hash Join</h2><p>MySQL 8.0.18支持在optimizer_switch中设置hash_join标志,以及优化器提示HASH_JOIN和NO_HASH_JOIN。在MySQL 8.0.19和更高版本中,这些都不再有任何效果。<br><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img6.avif"></p><p>从MySQL 8.0.20开始,对块嵌套循环的支持被删除,并且服务器在以前使用块嵌套循环的地方使用哈希连接。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img7.avif"></p><p>hash join的实现分为build table也就是被用来建立hash map的小表和probe table,首先依次读取小表的数据,对于每一行数据根据连接条件生成一个hash map中的一个元組,数据缓存在内存中,如果内存放不下需要dump到外存。依次扫描探测表拿到每一行数据根据join condition生成hash key映射hash map中对应的元組,元組对应的行和探测表的这一行有着同样的hash key, 这时并不能确定这两行就是满足条件的数据,需要再次过一遍join condition和filter,满足条件的数据集返回需要的投影列。</p><blockquote><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br></pre></td><td class="code"><pre><span class="line">`// 伪代码</span><br><span class="line">// 算法复杂度:O(M N)</span><br><span class="line">// 假设用户表有M条记录, 订单表有N条记录</span><br><span class="line">func HashJoin(users []TradeUser, orders []TradeOrder) []*UserOrderView &#123;</span><br><span class="line">var userOrderViews []*UserOrderView make([]*UserOrderView, 0)</span><br><span class="line"></span><br><span class="line">// 将用户表以用户ID为Key,用户为Value转换为Hash表</span><br><span class="line">// 算法复杂度:O(M)</span><br><span class="line">userTable : make(map[int]TradeUser)</span><br><span class="line">for _, user : range users &#123;</span><br><span class="line">userTable[user.Id] user</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">// 遍历订单表,查找用户</span><br><span class="line">// 算法复杂度:O(N)</span><br><span class="line">for _, order : range orders &#123;</span><br><span class="line">// 复杂度,接近:O(1)</span><br><span class="line">if user, exists : userTable[order.UserId]; exists &#123;</span><br><span class="line">// 添加视图结果</span><br><span class="line">userOrderViews append(userOrderViews, &amp;UserOrderView&#123;</span><br><span class="line">UserId: user.Id,</span><br><span class="line">UserName: user.Name,</span><br><span class="line">OrderId: order.Id,</span><br><span class="line">OrderAmount: order.Amount,</span><br><span class="line">&#125;)</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">return userOrderViews</span><br><span class="line">&#125;`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img8.avif"></p></blockquote><h3 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项:"></a><strong>注意事项:</strong></h3><ul><li>hash join本身的实现不要去判断哪个是小表,优化器生成执行计划时就已经确定了表的连接顺序,以左表为小表建立hash table,那对应的代价模型就会以左表作为小表来得出代价,这样根据代价生成的路径就是符合实现要求的。</li><li>hash table的大小、需要分配多少个桶这个是需要在一开始就做好的,那分配多少是一个问题,分配太大会造成内存浪费,分配太小会导致桶数过小开链过长性能变差,一旦超过这里的内存限制,会考虑dump到外存,不同数据库有它们自身的实现方式。</li><li>如何对数据hash,不同数据库有着自己的方式,不同的哈希方法也会对性能造成一定的影响。</li></ul><h3 id="工作原理"><a href="#工作原理" class="headerlink" title="工作原理:"></a><strong>工作原理:</strong></h3><p>构建阶段 Build Phase</p><ul><li>**选择构建表 Build Table **:算法通常会选择数据量较小的表作为构建表,以减少哈希表的构建时间和所需内存。但这不是绝对的,实际选择会根据统计信息和成本估算来决定。</li><li><strong>创建哈希表</strong>:对构建表中的每一行记录,取其连接列 即用于JOIN的列 的值,应用哈希函数计算出一个哈希码 hash code 。然后,根据这个哈希码将记录存储在一个哈希桶 hash bucket 中。如果有多个记录的连接列值经过哈希后得到相同的哈希码,这些记录会被组织成链表或其他数据结构存储在同一哈希桶内。</li></ul><p>哈希碰撞的解决方法在这边文章中有详细的介绍:<a href="https://blog.csdn.net/weixin_72610956/article/details/138523791">https://blog.csdn.net/weixin_72610956/article/details/138523791</a></p><p>探测阶段 Probe Phase</p><ul><li>**扫描探测表 Probe Table **:对另一个较大的表 探测表 进行扫描。</li><li><strong>哈希计算与匹配</strong>:对于探测表中的每一行,同样对其连接列值应用相同的哈希函数计算哈希码,然后在这个预先构建好的哈希表中查找对应的哈希桶。</li><li><strong>匹配与输出</strong>:如果找到匹配的哈希桶,就进一步检查桶内的链表或数据结构,进行精确的等值比较,以确保连接列的值确实相等。一旦找到匹配项,就结合两个表的相关字段生成结果集的行并输出。</li></ul><h3 id="优点"><a href="#优点" class="headerlink" title="优点:"></a><strong>优点:</strong></h3><ul><li><strong>性能优势</strong>:在数据量大时,哈希连接可以显著减少磁盘I&#x2F;O和CPU时间,因为它避免了嵌套循环的多次扫描和排序-合并连接中的排序开销。</li><li><strong>并行处理友好</strong>:哈希连接天然适合并行化处理,因为哈希表可以在不同的处理器或节点上并行构建和查询。</li><li><strong>内存依赖</strong>:哈希连接的效率高度依赖于可用内存,因为需要在内存中存储整个哈希表。如果内存不足,部分或全部哈希表可能需要溢写到磁盘,这会大大降低效率。</li></ul><h3 id="缺点"><a href="#缺点" class="headerlink" title="缺点:"></a><strong>缺点:</strong></h3><ul><li><strong>内存消耗</strong>:如前所述,构建哈希表需要足够的内存空间,特别是当构建表较大时。</li><li><strong>非等值连接不适用</strong>:哈希连接主要用于等值连接,对于非等值连接 如大于、小于等条件 不适用。</li><li><strong>预读取与优化</strong>:为了效率,数据库系统需要有效管理内存使用,并可能实施预读取策略来优化性能。</li></ul><h2 id="排序合并链接-SORT-MERGE-JOIN"><a href="#排序合并链接-SORT-MERGE-JOIN" class="headerlink" title="**排序合并链接 SORT MERGE JOIN **"></a>**排序合并链接 SORT MERGE JOIN **</h2><p>排序合并连接是嵌套循环连接的变种。如果两个数据集还没有排序,那么数据库会先对它们进行排序,这就是所谓的sort join操作。对于数据集里的每一行,数据库会从上一次匹配到数据的位置开始探查第二个数据集,这一步就是Merge join操作。</p><blockquote><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br></pre></td><td class="code"><pre><span class="line">`// 伪代码</span><br><span class="line">// 算法复杂度:O(M log M N log N)</span><br><span class="line">// 假设用户表有M条记录, 订单表有N条记录</span><br><span class="line">func SortJoin(users []TradeUser, orders []TradeOrder) []*UserOrderView &#123;</span><br><span class="line">var userOrderViews []*UserOrderView make([]*UserOrderView, 0)</span><br><span class="line"></span><br><span class="line">// 排序user表</span><br><span class="line">// 算法复杂度:O(M log M)</span><br><span class="line">sort.Slice(users, func(i, j int) bool &#123;</span><br><span class="line">return users[i].Id &lt; users[j].Id</span><br><span class="line">&#125;)</span><br><span class="line"></span><br><span class="line">// 排序order表</span><br><span class="line">// 算法复杂度:O(N log N)</span><br><span class="line">sort.Slice(orders, func(i, j int) bool &#123;</span><br><span class="line">return orders[i].Id &lt; orders[j].Id</span><br><span class="line">&#125;)</span><br><span class="line"></span><br><span class="line">// 遍历订单表,查找用户</span><br><span class="line">// 算法复杂度:O(M)</span><br><span class="line">userIdx : 0</span><br><span class="line">for _, order : range orders &#123;</span><br><span class="line">// 在user.id为主键的情况下,这里还可以执行二分查找</span><br><span class="line">for idx &lt; len(users) &amp;&amp; users[userIdx].Id &lt; order.UserId &#123;</span><br><span class="line">userIdx</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">// 如果找到用户,添加到结果集合</span><br><span class="line">if userIdx &lt; len(users) &amp;&amp; users[userIdx].id order.UserId &#123;</span><br><span class="line">// Join条件满足添加视图结果</span><br><span class="line">userOrderViews append(userOrderViews, &amp;UserOrderView&#123;</span><br><span class="line">UserId: user.Id,</span><br><span class="line">UserName: user.Name,</span><br><span class="line">OrderId: order.Id,</span><br><span class="line">OrderAmount: order.Amount,</span><br><span class="line">&#125;)</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">return userOrderViews</span><br><span class="line">&#125;`</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img9.avif"></p></blockquote><h3 id="工作流程"><a href="#工作流程" class="headerlink" title="工作流程:"></a><strong>工作流程:</strong></h3><ul><li><strong>排序阶段</strong>:</li></ul><p><strong>数据排序</strong>:首先,算法会对参与连接的两个表根据连接键进行排序。这一步骤是关键,因为只有排序后的数据才能有效地进行归并操作。如果表已经按照连接键排序,这一步可以省略。</p><ul><li><strong>索引利用</strong>:如果表上有适合的索引 如聚集索引或覆盖索引 ,数据库引擎可能会直接利用这些索引来避免全表排序。</li><li><strong>合并阶段</strong>:</li></ul><p><strong>双指针扫描</strong>:一旦两个表的数据都按连接键排序好了,算法会使用两个指针 或游标 分别指向两个表的开始。每个指针逐步向后移动,比较两个指针所指记录的连接键值。</p><ul><li><strong>匹配与输出</strong>:当两个指针指向的记录的连接键相等时,说明这两个记录应该被连接起来,此时就会输出 或累积到结果集中 这对匹配的记录。如果一个表的指针达到末尾,而另一个表还有剩余记录,则剩余的记录被视为不匹配,如果有外连接的情况,则可能作为NULL扩展输出。</li><li><strong>推进指针</strong>:匹配后,指针会根据排序顺序向后移动,继续寻找下一个匹配的记录。</li></ul><h3 id="优点-1"><a href="#优点-1" class="headerlink" title="优点:"></a><strong>优点:</strong></h3><ul><li><strong>效率</strong>:对于大表连接,特别是当连接键分布均匀,且数据已经排序或可以低成本排序时,SMJ比Nested-Loop Join更高效,因为它减少了不必要的比较次数。</li><li><strong>稳定性</strong>:由于是基于排序的,Sort Merge Join保证了输出结果的稳定性,即具有相同键值的记录保持原有的相对顺序。</li><li><strong>可预测性能</strong>:时间复杂度主要取决于排序操作,通常是O(n log n),对于大规模数据集来说,性能较为可预测。</li></ul><h3 id="缺点-1"><a href="#缺点-1" class="headerlink" title="缺点:"></a><strong>缺点:</strong></h3><ul><li><strong>内存和I&#x2F;O开销</strong>:排序操作可能需要额外的内存空间,并且如果数据不能完全放入内存,还需要磁盘I&#x2F;O操作,这可能会成为性能瓶颈。</li><li><strong>预处理时间</strong>:排序是预处理步骤,可能增加整体处理时间,尤其是在数据已经接近有序或只需要执行一次连接操作的情况下。</li></ul><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><table><thead><tr><th><strong>算法名称</strong></th><th><strong>时间复杂度</strong></th><th><strong>描述</strong></th></tr></thead><tbody><tr><td>Nested Loop Join</td><td>O(M*N)</td><td>适合小数据集,大数据集很慢</td></tr><tr><td>Sort Merge Join</td><td>O(M log M + N log N)</td><td>适合于当内存不足以存放整个数据集,需要小的分区上进行排序和合并</td></tr><tr><td>Hash Join</td><td>O(M*N)</td><td>适用于大数据集</td></tr></tbody></table>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/07/d9200f5c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL 中的HASH详解</title>
      <link>https://blog.eucalyptus.cc/2024/05/07/9be31efc/</link>
      <guid>https://blog.eucalyptus.cc/2024/05/07/9be31efc/</guid>
      <pubDate>Tue, 07 May 2024 03:17:25 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;MySQL中的哈希索引 Hash Index 是一种特殊的数据库索引类型,它利用哈希表 Hash Table 的数据结构来存储索引项。哈希表通过哈希函数 Hash Function 将索引列的值转化为一个固定长度的哈希码 Hash Code</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>MySQL中的哈希索引 Hash Index 是一种特殊的数据库索引类型,它利用哈希表 Hash Table 的数据结构来存储索引项。哈希表通过哈希函数 Hash Function 将索引列的值转化为一个固定长度的哈希码 Hash Code ,然后用这个哈希码作为索引项在表中定位数据记录的位置。这种方式使得对于等值查询 例如 <code>WHERE column value</code> 能够非常快速,理想情况下接近O(1)的时间复杂度。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img1.avif"></p><h2 id="HASH表结构"><a href="#HASH表结构" class="headerlink" title="HASH表结构"></a>HASH表结构</h2><p><strong>哈希表的基础结构设计主要包括以下几个关键组成部分:</strong></p><ul><li><p>**哈希函数 Hash Function **: 哈希函数是哈希表的核心,它的作用是将输入的键转换为一个确定的索引值,这个索引值用于决定数据在表中的存储位置。理想的哈希函数应能均匀分布不同的键值,减少冲突,并且计算速度快。常用的哈希函数有直接定址法、除留余数法、平方取中法、折叠法、随机数法等。</p></li><li><p>**数组 Bucket Array **: 哈希表通常由一个较大的数组构成,数组的每个元素称为一个“桶” Bucket 。哈希函数计算出的索引值就是数组的下标,指向存放相应键值对的位置。</p></li><li><p>**冲突解决策略 Collision Resolution Strategy **: 当两个或多个不同的键经过哈希函数计算后得到相同的索引值,就会发生冲突。解决冲突的方法有多种:</p></li></ul><p><strong>开放寻址法</strong>:在数组中寻找下一个可用的位置 例如线性探测、二次探测、双重散列等 。</p><ul><li><p><strong>链地址法</strong>:在每个桶内使用链表或其它动态数据结构存储具有相同哈希值的元素。</p></li><li><p><strong>再哈希法</strong>:使用第二个哈希函数来寻找下一个槽位。</p></li><li><p><strong>建立公共溢出区</strong>:为所有冲突的元素分配一个公共的区域。</p></li><li><p>**装载因子 Load Factor **: 装载因子定义为哈希表中已填入的元素数量与表总容量的比例。一个合适的装载因子可以平衡查找效率与空间利用率,过高会导致冲突增多,查找效率下降。</p></li><li><p>**动态调整 Resizing **: 为了维持高效的查找性能,当装载因子达到某个预设阈值时,哈希表会自动调整大小,通常是扩大数组长度并重新哈希所有元素。这一过程称为重哈希 Rehashing 。</p></li></ul><p>**装载因子 Load Factor **</p><p>装载因子是衡量哈希表中元素填充程度的一个重要指标,计算公式为:[ \text{装载因子} \frac{\text{哈希表中实际存储的元素数量}}{\text{哈希表的容量}} ],或者更简洁地表示为 ( \alpha \frac{n}{m} ),其中 ( n ) 是哈希表中元素的数量,( m ) 是哈希表的容量 即桶的数量 。</p><p>装载因子反映了哈希表的饱和度。较小的装载因子意味着哈希表有更多的空闲空间,可以减少哈希冲突,提高查找效率,但同时也会浪费更多的存储空间;相反,较大的装载因子虽然提高了空间利用率,但会增加冲突概率,降低操作效率,特别是在冲突较多时,查找、插入和删除操作可能退化为链表遍历或线性查找,时间复杂度可能变为O(n)。</p><p><strong>动态调整</strong></p><p>为了平衡存储效率和查询效率,哈希表通常会采用动态调整机制,即根据装载因子的变化自动调整哈希表的大小。主要涉及以下两个方面:</p><ul><li>**扩容 Resizing Up **: 当装载因子达到或超过一个预设的阈值 比如0.7或0.8 ,表明哈希表已较为拥挤,冲突增多,性能可能开始下降。此时,哈希表会自动进行扩容操作。扩容通常涉及以下步骤:</li></ul><p>新建一个更大的数组,其容量通常是原容量的两倍或更高倍数。</p><ul><li>将原有数组中的所有元素通过哈希函数重新映射到新数组中。因为容量变大,之前冲突的元素可能在新数组中找到不冲突的位置。</li><li>更新哈希表的容量和装载因子阈值。</li><li>**缩容 Resizing Down **: 少数情况下,如果哈希表中的元素数量显著减少,为了节省空间,也可以考虑缩容。缩容的决策较为复杂,因为它涉及到效率和空间使用的权衡,而且频繁缩容可能导致不必要的性能开销。因此,实际应用中,缩容的触发条件往往设置得比较保守,或者根本不实施自动缩容,仅在必要时手动干预。</li></ul><p>动态调整机制确保了哈希表在不同负载下的高效运行,是实现高效哈希表的关键技术之一。通过适时调整哈希表的大小,可以在保证查询效率的同时,合理利用内存资源。</p><h2 id="HASH冲突"><a href="#HASH冲突" class="headerlink" title="HASH冲突"></a>HASH冲突</h2><p>哈希冲突 Hash Collision或Hash Collision ,也称为哈希碰撞,是指在使用哈希函数将数据 如关键字key 映射到哈希表或哈希结构中的索引位置时,两个或多个不同的数据经过哈希处理后得到相同的哈希值,从而导致它们被映射到同一个索引位置的现象。由于哈希函数的输出范围通常是有限的,而输入数据的范围可能是无限的,因此在实际应用中,特别是在较大的数据集中,哈希冲突几乎是不可避免的。</p><p><strong>例:如下图我们依次将这些数对 12取余,将这些数添加到对应的关键字里,但是当我们添加16时,我们发现,16和4在散列表的位置冲突了,我们必须给16安排到别的位置去。</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img2.avif"></p><h2 id="解决方法"><a href="#解决方法" class="headerlink" title="解决方法"></a>解决方法</h2><p>解决哈希冲突的常用方法包括:</p><h3 id="链地址法"><a href="#链地址法" class="headerlink" title="链地址法"></a><strong>链地址法</strong></h3><p>**链地址法 Separate Chaining :**每个哈希表的槽位 bucket 存储一个链表,所有映射到该槽位的元素都放入这个链表中。这样,即使多个键值对映射到同一索引,也可以通过遍历链表来找到对应的值。</p><p>例如:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img3.avif"></p><h3 id="开放地址法"><a href="#开放地址法" class="headerlink" title="开放地址法"></a><strong>开放地址法</strong></h3><p>**线性探测 Linear Probing **: 发生冲突时,从发生冲突的桶开始,顺序检查下一个桶,直到找到一个空桶为止。如果达到表末尾还没找到空位,则可能需要循环回表头继续探测 称为“闭合”或“循环”探测 。这种方法简单,但可能导致数据在表中的聚集,影响查找效率。</p><p>例如:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img4.avif"></p><p>**二次探测 Quadratic Probing **: 探测序列是按照1^2, -1^2, 2^2, -2^2, …这样的平方数距离进行,即每次探测步长逐步增加。这种探测方式试图减少聚集现象,提高查找效率。</p><p>例如:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-05-07/img5.avif"></p><p>**双重散列 Double Hashing **: 使用两个不同的哈希函数H1和H2,当H1(key)导致冲突时,使用H2(key)来决定步长,即每次探测的位置是H1(key) i * H2(key),其中i是递增的探查序列。这种方法可以更有效地分散冲突,减少聚集。</p><h3 id="建立公共溢出区"><a href="#建立公共溢出区" class="headerlink" title="建立公共溢出区"></a>建立公共溢出区</h3><p>当哈希表的所有槽都被填满时,可以将额外的元素放入一个单独的溢出区或链表中。这种方法简单,但是查找效率较低,因为可能需要检查两个区域。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/05/07/9be31efc/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>ERROR：Temporary file write failure.</title>
      <link>https://blog.eucalyptus.cc/2024/04/26/325330b8/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/26/325330b8/</guid>
      <pubDate>Fri, 26 Apr 2024 07:58:00 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;背景:在执行DDL原句的时候失败报错&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;错误信息:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;(1878, ‘Temporary file write</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>背景:在执行DDL原句的时候失败报错</strong></p><p><strong>错误信息:</strong></p><p><strong>(1878, ‘Temporary file write failure.’)</strong></p><p><strong>排查报错原因:</strong></p><p>看报错是临时文件写入失败,在结合当时执行的sql来看确实是需要创建临时表</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">alter table</span> replace_test <span class="keyword">add</span> index age(age);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>这样一看在结合经验来看应该是临时目录满了,好家伙不看不知道,一看原来是磁盘都满了</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-26/img1.avif"></p><p>看一下磁盘满的原因,看起来是dd进程有大量的写入</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-26/img2.avif"></p><p>找一下导致磁盘满的大文件在哪里</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-26/img3.avif"></p><p>看起来主要是在var下面,然后一步一步定位到&#x2F;var&#x2F;lib&#x2F;mysql下面fulltmp文件</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-26/img4.avif"></p><p><strong>解决方法:</strong></p><p>这个文件应该是没什么用直接删除就好,删除之后磁盘下降</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-26/img5.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/26/325330b8/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>ERROR 3546 (HY000) at line 26: @@GLOBAL.GTID_PURGED cannot .....overlap with @@GLOBAL.GTID_EXECUTED</title>
      <link>https://blog.eucalyptus.cc/2024/04/24/9cfb4676/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/24/9cfb4676/</guid>
      <pubDate>Wed, 24 Apr 2024 09:27:36 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;报错场景:&lt;/p&gt;
&lt;p&gt;将master 节点的MySQL 备份导入到slave 节点时报错&lt;/p&gt;
&lt;p&gt;报错信息:&lt;/p&gt;
&lt;p&gt;ERROR 3546 (HY000) at line 26: GLOBAL.GTID_PURGED cannot be changed:</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>报错场景:</p><p>将master 节点的MySQL 备份导入到slave 节点时报错</p><p>报错信息:</p><p>ERROR 3546 (HY000) at line 26: GLOBAL.GTID_PURGED cannot be changed: the added gtid set must not overlap with GLOBAL.GTID_EXECUTED</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-24/img1.avif"></p><p>master备份时使用的语法</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">MySQL -uroot -p --all-databases &gt; 2024.4.24.sql</span><br></pre></td></tr></table></figure><p>报错原因:</p><p>如果在启用了GTID复制的环境中,不使用 <code>--set-gtid-purged OFF</code>参数进行备份,然后将备份数据导入到另一个同样启用GTID的数据库服务器,可能会引发GTID冲突。这是因为备份文件中包含了原服务器的GTID历史信息,导入时会尝试在目标服务器上应用这些GTID,如果目标服务器已经存在相同的GTID 例如,因为两台服务器原本就共享过一部分复制历史 ,则可能导致事务重复或跳过的问题。</p><p>解决方法:</p><p>备份时添加 <code>--set-gtid-purged OFF参数</code></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">MySQL <span class="operator">-</span>uroot <span class="operator">-</span>p <span class="comment">--all-databases --set-gtid-purged OFF &gt; 2024.4.24.sql</span></span><br></pre></td></tr></table></figure><p>添加<code>--set-gtid-purged OFF</code>参数后成功导入</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-24/img2.avif"></p><blockquote><p>知识点</p></blockquote><p><code>--set-gtid-purged OFF</code> 是 <code>mysqldump</code> 命令的一个参数,用于控制在生成数据库备份文件时如何处理全局事务标识符 Global Transaction Identifier, GTID 。具体来说,该参数的作用如下:</p><ul><li>阻止生成 GTID 相关的 SQL 语句:</li></ul><p>当在备份过程中指定 <code>--set-gtid-purged OFF</code> 时,<code>mysqldump</code> 不会在生成的备份脚本中包含 <code>SET GLOBAL.GTID_PURGED</code> 或 <code>SET SESSION.GTID_NEXT</code> 这类与GTID相关的SQL语句。这些语句通常用来标识备份文件中包含的事务已提交且应被视为已从服务器的GTID历史中清除。</p><ul><li>避免导入时的冲突:</li></ul><p>如果在启用了GTID复制的环境中,不使用此参数进行备份,然后将备份数据导入到另一个同样启用GTID的数据库服务器,可能会引发GTID冲突。这是因为备份文件中包含了原服务器的GTID历史信息,导入时会尝试在目标服务器上应用这些GTID,如果目标服务器已经存在相同的GTID 例如,因为两台服务器原本就共享过一部分复制历史 ,则可能导致事务重复或跳过的问题。</p><ul><li>使用 <code>--set-gtid-purged OFF</code> 可以避免在备份文件中记录GTID信息,从而使得导入数据时不会自动尝试更新目标服务器的GTID状态,降低了因GTID冲突而导致的数据恢复失败的风险。</li><li>应用场景:</li></ul><p>当备份单个数据库或特定表,并计划将这些数据导入到另一个独立的、GTID模式下运行的MySQL实例时,使用 <code>--set-gtid-purged OFF</code> 是合适的。在这种情况下,由于只迁移部分数据,而不是完整的复制链路,避免携带源服务器的GTID历史有助于保证目标服务器的GTID一致性。</p><ul><li>如果备份目的是为了在相同GTID环境下的不同节点间进行数据迁移或恢复,通常不需要使用此参数,因为在这种场景下保持GTID历史的连续性对于复制同步至关重要。<br>总结:</li></ul><p><code>--set-gtid-purged OFF</code> 参数在使用 <code>mysqldump</code> 备份启用了GTID复制的MySQL数据库时,用于禁用在备份脚本中记录GTID相关信息。这样做有助于避免在将备份数据导入到另一个GTID环境中时可能出现的GTID冲突,特别适用于仅迁移部分数据或独立数据库的场景。在需要保持完整复制链路或确保GTID历史连续性的场合,一般不建议使用此参数。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/24/9cfb4676/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL高可用搭建方案MHA</title>
      <link>https://blog.eucalyptus.cc/2024/04/08/c724aec1/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/08/c724aec1/</guid>
      <pubDate>Mon, 08 Apr 2024 09:15:27 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;MHA架构介绍&quot;&gt;&lt;a href=&quot;#MHA架构介绍&quot; class=&quot;headerlink&quot; title=&quot;MHA架构介绍&quot;&gt;&lt;/a&gt;MHA架构介绍&lt;/h2&gt;&lt;p&gt;MHA是Master High</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="MHA架构介绍"><a href="#MHA架构介绍" class="headerlink" title="MHA架构介绍"></a>MHA架构介绍</h2><p>MHA是Master High Availability的缩写,它是目前MySQL高可用方面的一个相对成熟的解决方案,其核心是使用perl语言编写的一组脚本,是一套优秀的作为MySQL高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中,MHA能做到在0~ 30秒之内自动完数据库的故障切换操作,并且能在最大程度上保证数据的一致性,以达到真正意义上的高可用。</p><p>基于MHA的架构不像MMM那样需要搭建主主复制,只需要搭建基本的主从复制架构即可。因为MHA在主库挂掉时,是在多个从库中选取出一个从库作为新的主库。MHA集群中的各节点彼此之间均需要基于<code>ssh</code> 互信通信,以实现远程控制及数据管理功能。</p><h2 id="MHA提供功能"><a href="#MHA提供功能" class="headerlink" title="MHA提供功能"></a>MHA提供功能</h2><ul><li>可以监控Master节点是否可用</li><li>当Master不可用时,能在多个Slave中选举出新的Master</li><li>提供了主从切换和故障转移功能,MHA会尝试在宕机的Master上保存binlog,在最大程度上保证事务不丢失。但如果是Master所在服务器已经无法访问,或硬件层面出现了问题,则无法成功保存binlog</li><li>MHA可以与半同步复制结合,避免从库之间出现数据不一致的情况</li><li>支持MySQL基于GTID和基于日志点的两种复制方式</li></ul><h2 id="MHA故障转移过程"><a href="#MHA故障转移过程" class="headerlink" title="MHA故障转移过程"></a>MHA故障转移过程</h2><ul><li>尝试使用 <code>ssh</code>- 从多个Slave中识别含有最新更新的Slave,将其作为备选的Master;</li><li>然后基于该Slave同步差异的中继日志 relaylog 到其他的Slave上;</li><li>接着同步从原Master上保存的二进制日志事件 binlog events ;</li><li>将备选的Master提升为新的Master;</li><li>使其他的Slave连接新的Master进行复制;</li><li>在新的Master启动vip地址,保证前端请求可以发送到新的Master。</li></ul><h2 id="MHA架构图"><a href="#MHA架构图" class="headerlink" title="MHA架构图"></a>MHA架构图</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img1.avif"></p><p>**本次实验所用机器说明 **</p><p>操作系统: CentOS Stream  9</p><p>数据库版本:MySQL8.0.36</p><p>MHA版本:0.58</p><table><thead><tr><th>名称</th><th>角色</th><th>IP</th><th>manger</th><th>集群管理节点</th><th>192.168.0.110</th><th>master</th><th>主库</th><th>192.168.0.104</th><th>slave1</th><th>从库</th><th>192.168.0.103</th><th>slave2</th><th>从库</th><th>192.168.0.102</th></tr></thead></table><p>本次实验的前提是建立在已经搭建好主从复制集群的前提下,MySQL的主从复制可以参考这篇文章:MySQL5.7.43 GTID主从复制配置</p><p>但是在使用MySQL8.0.36配置主从复制的时候和MySQL5.7.43有些地方不同需要注意</p><p>等主从复制集群搭建好后就可以开始按下面的步骤开始本次实验了</p><h2 id="配置ssh免密登陆"><a href="#配置ssh免密登陆" class="headerlink" title="配置ssh免密登陆"></a>配置ssh免密登陆</h2><p><strong>生成密钥</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ssh-keygen</span><br></pre></td></tr></table></figure><p>生成密钥和公钥后就可以在&#x2F;root&#x2F;.ssh&#x2F;下面看到,当然这是默认的路径</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img2.avif"></p><p><strong>将密钥拷贝到其他服务器上</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">ssh-copy-id -i /root/.ssh/id_rsa root 192.168.0.104</span><br><span class="line">ssh-copy-id -i /root/.ssh/id_rsa root 192.168.0.103</span><br><span class="line">ssh-copy-id -i /root/.ssh/id_rsa root 192.168.0.102</span><br></pre></td></tr></table></figure><p> 然后到集群中其他节点上进行同样的操作,由于是重复的操作这里就不演示了,最后测试能否免密登陆即可</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img3.avif"></p><h2 id="安装MHA软件包"><a href="#安装MHA软件包" class="headerlink" title="安装MHA软件包"></a>安装MHA软件包</h2><h3 id="MHA下载地址"><a href="#MHA下载地址" class="headerlink" title="MHA下载地址"></a>MHA下载地址</h3><p>mha4mysql-manager-0.58.tar.gz:</p><p>wget <a href="https://github.com/yoshinorim/mha4mysql-manager/releases/download/v0.58/mha4mysql-manager-0.58.tar.gz">https://github.com/yoshinorim/mha4mysql-manager/releases/download/v0.58/mha4mysql-manager-0.58.tar.gz</a></p><p>mha4mysql-node-0.58.tar.gz:</p><p>wget <a href="https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.58/mha4mysql-node-0.58.tar.gz">https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.58/mha4mysql-node-0.58.tar.gz</a></p><p><strong>在<code>manager</code>上安装<code>mha4mysql-manager</code>软件包</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line"></span><br><span class="line"><span class="comment">#下载依赖包</span></span><br><span class="line">yum install -y perl-DBD-MySQL \</span><br><span class="line">perl-Config-Tiny \</span><br><span class="line">perl-Log-Dispatch \</span><br><span class="line">perl-Parallel-ForkManager \</span><br><span class="line">perl-ExtUtils-CBuilder \</span><br><span class="line">perl-ExtUtils-MakeMaker \</span><br><span class="line">perl-CPAN</span><br><span class="line"></span><br><span class="line"><span class="comment">#进入安装目录</span></span><br><span class="line"><span class="built_in">cd</span> mha4mysql-manager-0.58</span><br><span class="line"></span><br><span class="line"><span class="comment">#编译安装</span></span><br><span class="line">perl Makefile.PL</span><br><span class="line">make &amp;&amp; make install</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>在所有节点上安装<code>mha4mysql-node</code>软件包</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#下载依赖包</span></span><br><span class="line">yum install -y perl-DBD-MySQL \</span><br><span class="line">perl-Config-Tiny \</span><br><span class="line">perl-Log-Dispatch \</span><br><span class="line">perl-Parallel-ForkManager \</span><br><span class="line">perl-ExtUtils-CBuilder \</span><br><span class="line">perl-ExtUtils-MakeMaker \</span><br><span class="line">perl-CPAN</span><br><span class="line"></span><br><span class="line"><span class="comment">#进入安装目录</span></span><br><span class="line"><span class="built_in">cd</span> mha4mysql-node-0.58</span><br><span class="line"></span><br><span class="line"><span class="comment">#编译安装</span></span><br><span class="line">perl Makefile.PL</span><br><span class="line">make &amp;&amp; make install</span><br></pre></td></tr></table></figure><p>关于执行perl Makefile.PL报错解决方法参考文章</p><p>Can’t locate IPC&#x2F;Cmd.pm in INC (you may need to install the IPC::Cmd module</p><p><a href="https://blog.51cto.com/u_16175492/6651879">https://blog.51cto.com/u_16175492&#x2F;6651879</a></p><p>这里模块的安装可能很慢请nai’xi</p><h2 id="配置manger节点"><a href="#配置manger节点" class="headerlink" title="配置manger节点"></a>配置manger节点</h2><p><strong>创建MHA的配置文件存放目录和工作目录</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root manager ~]</span><span class="comment"># mkdir /etc/mha</span></span><br><span class="line"><span class="section">[root manager ~]</span><span class="comment"># mkdir /home/mysql_mha</span></span><br></pre></td></tr></table></figure><p><strong>创建MHA的配置文件,并添加如下内容</strong></p><p><strong>这个组件secondary_check_script在安装的时候路径可能在&#x2F;usr&#x2F;bin&#x2F;下面,需要移动到&#x2F;usr&#x2F;local&#x2F;bin&#x2F;下面 ,或者在下面的配置文件中更改路径</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># mha用于访问数据库的账户和密码</span></span><br><span class="line">user mha</span><br><span class="line">password 密码</span><br><span class="line"><span class="comment"># 指定mha的工作目录</span></span><br><span class="line">manager_workdir /home/mysql_mha</span><br><span class="line"></span><br><span class="line"><span class="comment"># mha日志文件的存放路径</span></span><br><span class="line">manager_log /home/mysql_mha/manager.log</span><br><span class="line"></span><br><span class="line"><span class="comment"># 指定mha在远程节点上的工作目录</span></span><br><span class="line">remote_workdir /home/mysql_mha</span><br><span class="line"></span><br><span class="line"><span class="comment"># 可以使用sshssh_user root</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 用于主从复制的MySQL用户和密码</span></span><br><span class="line">repl_user repl</span><br><span class="line">repl_password 密码</span><br><span class="line"><span class="comment"># 指定间隔多少秒检测一次</span></span><br><span class="line">ping_interval 1</span><br><span class="line"></span><br><span class="line"><span class="comment"># 指定master节点存放binlog日志文件的目录</span></span><br><span class="line">master_binlog_dir /var/lib/mysql</span><br><span class="line"></span><br><span class="line"><span class="comment"># 指定一个脚本,该脚本实现了在主从切换之后,将虚拟IP漂移到新的Master上</span></span><br><span class="line">master_ip_failover_script /usr/local/bin/master_ip_failover</span><br><span class="line"></span><br><span class="line"><span class="comment"># 指定用于二次检查节点状态的脚本</span></span><br><span class="line">secondary_check_script /usr/local/bin/masterha_secondary_check -s 192.168.0.104 -s 192.168.0.103 -s 192.168.0.102</span><br><span class="line"></span><br><span class="line"><span class="comment"># 配置集群中的节点信息</span></span><br><span class="line"><span class="section">[server1]</span></span><br><span class="line">hostname 192.168.0.104</span><br><span class="line">port 3306</span><br><span class="line"><span class="comment"># 指定该节点可以参与Master选举</span></span><br><span class="line">candidate_master 1</span><br><span class="line"></span><br><span class="line"><span class="section">[server2]</span></span><br><span class="line">hostname 192.168.0.103</span><br><span class="line">port 3306</span><br><span class="line">candidate_master 1</span><br><span class="line"></span><br><span class="line"><span class="section">[server3]</span></span><br><span class="line">hostname 192.168.0.102</span><br><span class="line">port 3306</span><br><span class="line"><span class="comment"># 指定该节点不能参与Master选举</span></span><br><span class="line">no_master 1</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>编写配置文件中所配置的</strong>**<code>master_ip_failover</code>**<strong>脚本,该脚本是根据MHA的官方示例修改的,MHA默认并没有提供。需要注意脚本中的几处地方需要根据实际情况进行修改,已用注释标明</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br><span class="line">62</span><br><span class="line">63</span><br><span class="line">64</span><br><span class="line">65</span><br><span class="line">66</span><br><span class="line">67</span><br><span class="line">68</span><br><span class="line">69</span><br><span class="line">70</span><br><span class="line">71</span><br><span class="line">72</span><br><span class="line">73</span><br><span class="line">74</span><br><span class="line">75</span><br><span class="line">76</span><br><span class="line">77</span><br><span class="line">78</span><br><span class="line">79</span><br><span class="line">80</span><br><span class="line">81</span><br><span class="line">82</span><br><span class="line">83</span><br><span class="line">84</span><br><span class="line">85</span><br><span class="line">86</span><br><span class="line">87</span><br><span class="line">88</span><br><span class="line">89</span><br><span class="line">90</span><br><span class="line">91</span><br><span class="line">92</span><br><span class="line">93</span><br><span class="line">94</span><br><span class="line">95</span><br><span class="line">96</span><br><span class="line">97</span><br><span class="line">98</span><br><span class="line">99</span><br></pre></td><td class="code"><pre><span class="line"><span class="meta">#!/usr/bin/env perl</span></span><br><span class="line"></span><br><span class="line">use strict;</span><br><span class="line">use warnings FATAL &gt; <span class="string">&#x27;all&#x27;</span>;</span><br><span class="line"></span><br><span class="line">use Getopt::Long;</span><br><span class="line"></span><br><span class="line">my (</span><br><span class="line"><span class="variable">$command</span>, <span class="variable">$orig_master_host</span>, <span class="variable">$orig_master_ip</span>,<span class="variable">$ssh_user</span>,</span><br><span class="line"><span class="variable">$orig_master_port</span>, <span class="variable">$new_master_host</span>, <span class="variable">$new_master_ip</span>,<span class="variable">$new_master_port</span>,</span><br><span class="line"><span class="variable">$orig_master_ssh_port</span>,<span class="variable">$new_master_ssh_port</span>,<span class="variable">$new_master_user</span>,<span class="variable">$new_master_password</span></span><br><span class="line">);</span><br><span class="line"></span><br><span class="line"><span class="comment"># 这里定义的虚拟IP可以根据实际情况进行修改</span></span><br><span class="line">my <span class="variable">$vip</span> <span class="string">&#x27;192.168.0.111/24&#x27;</span>;</span><br><span class="line">my <span class="variable">$brdc</span> <span class="string">&#x27;192.168.0.255&#x27;</span>;</span><br><span class="line">my <span class="variable">$ifdev</span> <span class="string">&#x27;eth0&#x27;</span>;</span><br><span class="line">my <span class="variable">$key</span> <span class="string">&#x27;1&#x27;</span>;</span><br><span class="line"><span class="comment"># 这里的网卡名称 “eth0” 需要根据你机器的网卡名称进行修改</span></span><br><span class="line">my <span class="variable">$ssh_start_vip</span> <span class="built_in">sudo</span> /sbin/ifconfig eth0:<span class="variable">$key</span> <span class="variable">$vip</span> ;</span><br><span class="line">my <span class="variable">$ssh_stop_vip</span> <span class="built_in">sudo</span> /sbin/ifconfig eth0:<span class="variable">$key</span> down ;</span><br><span class="line">my <span class="variable">$ssh_Bcast_arp</span> <span class="built_in">sudo</span> /sbin/arping -I bond0 -c 3 -A <span class="variable">$vip</span> ;</span><br><span class="line"></span><br><span class="line">GetOptions(</span><br><span class="line"><span class="string">&#x27;command s&#x27;</span> &gt; \<span class="variable">$command</span>,</span><br><span class="line"><span class="string">&#x27;ssh_user s&#x27;</span> &gt; \<span class="variable">$ssh_user</span>,</span><br><span class="line"><span class="string">&#x27;orig_master_host s&#x27;</span> &gt; \<span class="variable">$orig_master_host</span>,</span><br><span class="line"><span class="string">&#x27;orig_master_ip s&#x27;</span> &gt; \<span class="variable">$orig_master_ip</span>,</span><br><span class="line"><span class="string">&#x27;orig_master_port i&#x27;</span> &gt; \<span class="variable">$orig_master_port</span>,</span><br><span class="line"><span class="string">&#x27;orig_master_ssh_port i&#x27;</span> &gt; \<span class="variable">$orig_master_ssh_port</span>,</span><br><span class="line"><span class="string">&#x27;new_master_host s&#x27;</span> &gt; \<span class="variable">$new_master_host</span>,</span><br><span class="line"><span class="string">&#x27;new_master_ip s&#x27;</span> &gt; \<span class="variable">$new_master_ip</span>,</span><br><span class="line"><span class="string">&#x27;new_master_port i&#x27;</span> &gt; \<span class="variable">$new_master_port</span>,</span><br><span class="line"><span class="string">&#x27;new_master_ssh_port&#x27;</span> &gt; \<span class="variable">$new_master_ssh_port</span>,</span><br><span class="line"><span class="string">&#x27;new_master_user&#x27;</span> &gt; \<span class="variable">$new_master_user</span>,</span><br><span class="line"><span class="string">&#x27;new_master_password&#x27;</span> &gt; \<span class="variable">$new_master_password</span></span><br><span class="line"></span><br><span class="line">);</span><br><span class="line"></span><br><span class="line"><span class="built_in">exit</span> &amp;main();</span><br><span class="line"></span><br><span class="line">sub main &#123;</span><br><span class="line"><span class="variable">$ssh_user</span> defined <span class="variable">$ssh_user</span> ? <span class="variable">$ssh_user</span> : <span class="string">&#x27;root&#x27;</span>;</span><br><span class="line"><span class="built_in">print</span> \n\nIN SCRIPT TEST <span class="variable">$ssh_user</span>|<span class="variable">$ssh_stop_vip</span> <span class="variable">$ssh_user</span>|<span class="variable">$ssh_start_vip</span> \n\n ;</span><br><span class="line"></span><br><span class="line"><span class="keyword">if</span> ( <span class="variable">$command</span> eq stop || <span class="variable">$command</span> eq stopssh ) &#123;</span><br><span class="line"></span><br><span class="line">my <span class="variable">$exit_code</span> 1;</span><br><span class="line"><span class="built_in">eval</span> &#123;</span><br><span class="line"><span class="built_in">print</span> Disabling the VIP on old master: <span class="variable">$orig_master_host</span> \n ;</span><br><span class="line">&amp;stop_vip();</span><br><span class="line"><span class="variable">$exit_code</span> 0;</span><br><span class="line">&#125;;</span><br><span class="line"><span class="keyword">if</span> ($ ) &#123;</span><br><span class="line">warn Got Error: $ \n ;</span><br><span class="line"><span class="built_in">exit</span> <span class="variable">$exit_code</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="built_in">exit</span> <span class="variable">$exit_code</span>;</span><br><span class="line">&#125;</span><br><span class="line">elsif ( <span class="variable">$command</span> eq start ) &#123;</span><br><span class="line"></span><br><span class="line">my <span class="variable">$exit_code</span> 10;</span><br><span class="line"><span class="built_in">eval</span> &#123;</span><br><span class="line"><span class="built_in">print</span> Enabling the VIP - <span class="variable">$vip</span> on the new master - <span class="variable">$new_master_host</span> \n ;</span><br><span class="line">&amp;start_vip();</span><br><span class="line">&amp;start_arp();</span><br><span class="line"><span class="variable">$exit_code</span> 0;</span><br><span class="line">&#125;;</span><br><span class="line"><span class="keyword">if</span> ($ ) &#123;</span><br><span class="line">warn $ ;</span><br><span class="line"><span class="built_in">exit</span> <span class="variable">$exit_code</span>;</span><br><span class="line">&#125;</span><br><span class="line"><span class="built_in">exit</span> <span class="variable">$exit_code</span>;</span><br><span class="line">&#125;</span><br><span class="line">elsif ( <span class="variable">$command</span> eq status ) &#123;</span><br><span class="line"><span class="built_in">print</span> Checking the Status of the script.. OK \n ;</span><br><span class="line"><span class="built_in">exit</span> 0;</span><br><span class="line">&#125;</span><br><span class="line"><span class="keyword">else</span> &#123;</span><br><span class="line">&amp;usage();</span><br><span class="line"><span class="built_in">exit</span> 1;</span><br><span class="line">&#125;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">sub <span class="function"><span class="title">start_vip</span></span>() &#123;</span><br><span class="line">ssh <span class="variable">$ssh_user</span>\ <span class="variable">$new_master_host</span> \ <span class="variable">$ssh_start_vip</span> \ ;</span><br><span class="line">&#125;</span><br><span class="line">sub <span class="function"><span class="title">stop_vip</span></span>() &#123;</span><br><span class="line">ssh <span class="variable">$ssh_user</span>\ <span class="variable">$orig_master_host</span> \ <span class="variable">$ssh_stop_vip</span> \ ;</span><br><span class="line">&#125;</span><br><span class="line"></span><br><span class="line">sub <span class="function"><span class="title">start_arp</span></span>() &#123;</span><br><span class="line">ssh <span class="variable">$ssh_user</span>\ <span class="variable">$new_master_host</span> \ <span class="variable">$ssh_Bcast_arp</span> \ ;</span><br><span class="line">&#125;</span><br><span class="line">sub usage &#123;</span><br><span class="line"><span class="built_in">print</span></span><br><span class="line">Usage: master_ip_failover --<span class="built_in">command</span> start|stop|stopssh|status --ssh_user user --orig_master_host host --orig_master_ip ip --orig_master_port port --new_master_host host --new_master_ip ip --new_master_port port\n ;</span><br><span class="line">&#125;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>还需要给该脚本添加可执行权限,否则MHA是无法调用的</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root manager ~]</span><span class="comment"># chmod a x /usr/local/bin/master_ip_failover</span></span><br></pre></td></tr></table></figure><p><strong>根据配置文件中<code>remote_workdir</code>的配置,需在其他节点上创建MHA的远程工作目录</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root master ~]</span><span class="comment"># mkdir /home/mysql_mha</span></span><br><span class="line"><span class="section">[root slave-01 ~]</span><span class="comment"># mkdir /home/mysql_mha</span></span><br><span class="line"><span class="section">[root slave-02 ~]</span><span class="comment"># mkdir /home/mysql_mha</span></span><br></pre></td></tr></table></figure><p><strong>在配置文件中指定了让<code>manager</code>使用<code>mha</code>这个用户来访问数据库节点,所以需要在<code>master</code>节点上创建<code>mha</code>用户</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;mha&#x27;</span> <span class="string">&#x27;%&#x27;</span> identified <span class="keyword">with</span> mysql_native_password <span class="keyword">by</span> <span class="string">&#x27;密码&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> <span class="keyword">all</span> privileges <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> <span class="string">&#x27;mha&#x27;</span> <span class="string">&#x27;%&#x27;</span>;</span><br><span class="line">flush privileges;</span><br></pre></td></tr></table></figure><p>完成以上所有步骤后,在<code>manager</code>节点上使用**<code>masterha_check_ssh</code><strong>和<code>masterha_check_repl</code> 对配置进行检查,其中</strong><code>masterha_check_ssh</code>**用于检查<code>ssh</code></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root manager ~]</span><span class="comment"># masterha_check_ssh --conf /etc/mha/mysql_mha.cnf</span></span><br><span class="line"><span class="section">[root manager ~]</span><span class="comment"># masterha_check_repl --conf /etc/mha/mysql_mha.cnf</span></span><br></pre></td></tr></table></figure><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br></pre></td><td class="code"><pre><span class="line">[root fa0b3e01d810 bin]# masterha_check_ssh <span class="comment">--conf /etc/mha/mysql_mha.cnf</span></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">15</span> <span class="number">2024</span> <span class="operator">-</span> [warning] <span class="keyword">Global</span> configuration file <span class="operator">/</span>etc<span class="operator">/</span>masterha_default.cnf <span class="keyword">not</span> found. Skipping.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">15</span> <span class="number">2024</span> <span class="operator">-</span> [info] Reading application <span class="keyword">default</span> configuration <span class="keyword">from</span> <span class="operator">/</span>etc<span class="operator">/</span>mha<span class="operator">/</span>mysql_mha.cnf..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">15</span> <span class="number">2024</span> <span class="operator">-</span> [info] Reading server configuration <span class="keyword">from</span> <span class="operator">/</span>etc<span class="operator">/</span>mha<span class="operator">/</span>mysql_mha.cnf..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">15</span> <span class="number">2024</span> <span class="operator">-</span> [info] Starting SSH connection tests..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">18</span> <span class="number">2024</span> <span class="operator">-</span> [debug]</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">16</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">18</span> <span class="number">2024</span> <span class="operator">-</span> [debug]</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">16</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">18</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">18</span> <span class="number">2024</span> <span class="operator">-</span> [debug]</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">15</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] Connecting via SSH <span class="keyword">from</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">22</span>) <span class="keyword">to</span> root <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">22</span>)..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">17</span> <span class="number">2024</span> <span class="operator">-</span> [debug] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">18</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="keyword">All</span> SSH connection tests passed successfully.</span><br><span class="line">Use <span class="keyword">of</span> uninitialized <span class="keyword">value</span> <span class="keyword">in</span> exit <span class="keyword">at</span> <span class="operator">/</span>usr<span class="operator">/</span><span class="keyword">local</span><span class="operator">/</span>bin<span class="operator">/</span>masterha_check_ssh line <span class="number">44.</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img4.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br></pre></td><td class="code"><pre><span class="line">[root fa0b3e01d810 bin]# masterha_check_repl <span class="comment">--conf /etc/mha/mysql_mha.cnf</span></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">38</span> <span class="number">2024</span> <span class="operator">-</span> [warning] <span class="keyword">Global</span> configuration file <span class="operator">/</span>etc<span class="operator">/</span>masterha_default.cnf <span class="keyword">not</span> found. Skipping.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">38</span> <span class="number">2024</span> <span class="operator">-</span> [info] Reading application <span class="keyword">default</span> configuration <span class="keyword">from</span> <span class="operator">/</span>etc<span class="operator">/</span>mha<span class="operator">/</span>mysql_mha.cnf..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">38</span> <span class="number">2024</span> <span class="operator">-</span> [info] Reading server configuration <span class="keyword">from</span> <span class="operator">/</span>etc<span class="operator">/</span>mha<span class="operator">/</span>mysql_mha.cnf..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">38</span> <span class="number">2024</span> <span class="operator">-</span> [info] MHA::MasterMonitor version <span class="number">0.58</span>.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Multi<span class="operator">-</span>master configuration <span class="keyword">is</span> detected. <span class="keyword">Current</span> <span class="keyword">primary</span>(writable) master <span class="keyword">is</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Master configurations <span class="keyword">are</span> <span class="keyword">as</span> below:</span><br><span class="line">Master <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">3306</span>), replicating <span class="keyword">from</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>), read<span class="operator">-</span><span class="keyword">only</span></span><br><span class="line">Master <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>), replicating <span class="keyword">from</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">3306</span>)</span><br><span class="line"></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] GTID failover mode <span class="number">1</span></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Dead Servers:</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Alive Servers:</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Alive Slaves:</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>:<span class="number">3306</span>) Version <span class="number">8.0</span><span class="number">.36</span> (oldest major version <span class="keyword">between</span> slaves) log<span class="operator">-</span>bin:enabled</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] GTID <span class="keyword">ON</span></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Replicating <span class="keyword">from</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="keyword">Primary</span> candidate <span class="keyword">for</span> the <span class="keyword">new</span> Master (candidate_master <span class="keyword">is</span> <span class="keyword">set</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>:<span class="number">3306</span>) Version <span class="number">8.0</span><span class="number">.36</span> (oldest major version <span class="keyword">between</span> slaves) log<span class="operator">-</span>bin:enabled</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] GTID <span class="keyword">ON</span></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Replicating <span class="keyword">from</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="keyword">Not</span> candidate <span class="keyword">for</span> the <span class="keyword">new</span> Master (no_master <span class="keyword">is</span> <span class="keyword">set</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="keyword">Current</span> Alive Master: <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>)</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking slave configurations..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking replication filtering settings..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] binlog_do_db , binlog_ignore_db</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Replication filtering <span class="keyword">check</span> ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] GTID (<span class="keyword">with</span> auto<span class="operator">-</span>pos) <span class="keyword">is</span> supported. Skipping <span class="keyword">all</span> SSH <span class="keyword">and</span> Node package checking.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking SSH publickey authentication settings <span class="keyword">on</span> the <span class="keyword">current</span> master..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] HealthCheck: SSH <span class="keyword">to</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span> <span class="keyword">is</span> reachable.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info]</span><br><span class="line"><span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>(<span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span>:<span class="number">3306</span>) (<span class="keyword">current</span> master)</span><br><span class="line"><span class="comment">--192.168.0.103(192.168.0.103:3306)</span></span><br><span class="line"><span class="comment">--192.168.0.102(192.168.0.102:3306)</span></span><br><span class="line"></span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking replication health <span class="keyword">on</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.103</span>..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking replication health <span class="keyword">on</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.102</span>..</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] ok.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Checking master_ip_failover_script status:</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] <span class="operator">/</span>usr<span class="operator">/</span><span class="keyword">local</span><span class="operator">/</span>bin<span class="operator">/</span>master_ip_failover <span class="comment">--command status --ssh_user root --orig_master_host 192.168.0.104 --orig_master_ip 192.168.0.104 --orig_master_port 3306</span></span><br><span class="line"></span><br><span class="line"><span class="keyword">IN</span> SCRIPT TEST root<span class="operator">|</span>sudo <span class="operator">/</span>sbin<span class="operator">/</span>ifconfig eth0:<span class="number">1</span> down root<span class="operator">|</span>sudo <span class="operator">/</span>sbin<span class="operator">/</span>ifconfig eth0:<span class="number">1</span> <span class="number">192.168</span><span class="number">.0</span><span class="number">.111</span><span class="operator">/</span><span class="number">24</span></span><br><span class="line"></span><br><span class="line">Checking the Status <span class="keyword">of</span> the script.. OK</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] OK.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [warning] shutdown_script <span class="keyword">is</span> <span class="keyword">not</span> defined.</span><br><span class="line">Mon Apr <span class="number">8</span> <span class="number">16</span>:<span class="number">54</span>:<span class="number">40</span> <span class="number">2024</span> <span class="operator">-</span> [info] Got exit code <span class="number">0</span> (<span class="keyword">Not</span> master dead).</span><br><span class="line"></span><br><span class="line">MySQL Replication Health <span class="keyword">is</span> OK.</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img5.avif"></p><p><strong>以上检测都通过后,就可以启动MHA服务了。启动命令如下</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root manager ~]</span><span class="comment"># nohup masterha_manager --conf /etc/mha/mysql_mha.cnf &amp;</span></span><br></pre></td></tr></table></figure><p><strong>启动完成后,可以使用<code>ps</code>命令查看<code>masterha_manager</code>进程是否存在,如下存在则代表启动成功</strong></p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root manager ~]</span><span class="comment"># ps aux |grep masterha_manager</span></span><br><span class="line">root 2842 0.3 1.1 299648 22032 pts/0 S 18:30 0:00 perl /usr/bin/masterha_manager --conf /etc/mha/mysql_mha.cnf</span><br><span class="line">root 2901 0.0 0.0 112728 976 pts/0 R 18:31 0:00 grep --color auto masterha_manager</span><br><span class="line"><span class="section">[root manager ~]</span><span class="comment"># </span></span><br></pre></td></tr></table></figure><p>** 最后我们需要到<code>master</code>节点上,手动去配置虚拟IP。因为MHA只会在主从切换时漂移虚拟IP到新的Master节点,而不会在第一次启动时主动去设置Master的虚拟IP,所以我们需要手动设置。设置虚拟IP的命令如下**</p><figure class="highlight ini"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="section">[root master ~]</span><span class="comment"># ifconfig eth0:1 192.168.0.111/24</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img6.avif"></p><p><strong>到此为止,我们就已经完成了MHA高可用架构的搭建,接下来我们对其进行一些简单的测试。例如,测试下是否能正常<code>ping</code> 通虚拟IP,毕竟应用端访问数据库时连接的是虚拟IP,所以首先得确保虚拟IP是能够被访问的。如下</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-08/img7.avif"></p><h2 id="MHA架构优缺点"><a href="#MHA架构优缺点" class="headerlink" title="MHA架构优缺点"></a><strong>MHA架构优缺点</strong></h2><h3 id="优点"><a href="#优点" class="headerlink" title="优点:"></a><strong>优点:</strong></h3><ul><li>使用Perl脚本语言开发并且完全开源,开发者可以根据自己的需求进行二次开发</li><li>能够支持基于GTID和基于日志点的复制模式</li><li>MHA在进行故障转移时更不易产生数据丢失</li><li>在一个监控节点上可以监控多个Replication集群</li></ul><h3 id="缺点"><a href="#缺点" class="headerlink" title="缺点:"></a><strong>缺点:</strong></h3><ul><li>MHA默认不提供虚拟IP功能,需要自行编写脚本或利用第三方工具来实现虚拟IP的配置</li><li>MHA启动后只会对Master进行监控,不会对Slave进行监控,也无法监控复制链路的情况</li><li>集群环境需要能够通过 <code>ssh</code>免密- MHA没有提供对Slave的读[负载均衡](<a href="https://cloud.tencent.com/product/clb?from_column">https://cloud.tencent.com/product/clb?from_column</a> 20065&amp;from 20065)功能,需要通过第三方工具来实现</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/08/c724aec1/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>kubeadm部署Kubernetes</title>
      <link>https://blog.eucalyptus.cc/2024/04/04/560ac167/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/04/560ac167/</guid>
      <pubDate>Thu, 04 Apr 2024 05:13:38 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在当今的云原生时代，Kubernetes（简称 K8s）已不再仅仅是一个容器编排工具，它是现代应用架构的基石，是连接开发效率与运维稳定性的桥梁。然而，对于许多初学者而言，K8s</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在当今的云原生时代，Kubernetes（简称 K8s）已不再仅仅是一个容器编排工具，它是现代应用架构的基石，是连接开发效率与运维稳定性的桥梁。然而，对于许多初学者而言，K8s 陡峭的学习曲线和复杂的组件依赖往往让人望而却步。尤其是当面对”节点未就绪”、”镜像拉取失败”或”网络插件冲突”等常见陷阱时，一次次的初始化失败极易消磨学习的热情。</p><p>本指南并非一份枯燥的命令罗列，而是一次真实的、基于 2C4G 低配云服务器的全流程实战记录。我们摒弃了理想化的实验室环境，直面国内网络访问受限、系统资源紧张以及 Docker 与 Kubelet 配置冲突等现实挑战。</p><h2 id="第一步：系统初始化（必须执行）"><a href="#第一步：系统初始化（必须执行）" class="headerlink" title="第一步：系统初始化（必须执行）"></a>第一步：系统初始化（必须执行）</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 关闭 Swap</span></span><br><span class="line"><span class="built_in">sudo</span> swapoff -a</span><br><span class="line"><span class="built_in">sudo</span> sed -i <span class="string">&#x27;/ swap / s/^\(.*\)$/#\1/g&#x27;</span> /etc/fstab</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 加载内核模块</span></span><br><span class="line"><span class="built_in">cat</span> &lt;&lt;<span class="string">EOF | sudo tee /etc/modules-load.d/k8s.conf</span></span><br><span class="line"><span class="string">overlay</span></span><br><span class="line"><span class="string">br_netfilter</span></span><br><span class="line"><span class="string">EOF</span></span><br><span class="line"><span class="built_in">sudo</span> modprobe overlay</span><br><span class="line"><span class="built_in">sudo</span> modprobe br_netfilter</span><br><span class="line"></span><br><span class="line"><span class="comment"># 3. 设置 sysctl</span></span><br><span class="line"><span class="built_in">cat</span> &lt;&lt;<span class="string">EOF | sudo tee /etc/sysctl.d/k99-kubernetes.conf</span></span><br><span class="line"><span class="string">net.bridge.bridge-nf-call-iptables  = 1</span></span><br><span class="line"><span class="string">net.bridge.bridge-nf-call-ip6tables = 1</span></span><br><span class="line"><span class="string">net.ipv4.ip_forward                 = 1</span></span><br><span class="line"><span class="string">EOF</span></span><br><span class="line"><span class="built_in">sudo</span> sysctl --system</span><br><span class="line"></span><br><span class="line"><span class="comment"># 4. 安装依赖</span></span><br><span class="line"><span class="built_in">sudo</span> apt-get update</span><br><span class="line"><span class="built_in">sudo</span> apt-get install -y apt-transport-https ca-certificates curl gnupg lsb-release conntrack</span><br></pre></td></tr></table></figure><h2 id="第二步：安装-Docker（如果已安装可跳过）"><a href="#第二步：安装-Docker（如果已安装可跳过）" class="headerlink" title="第二步：安装 Docker（如果已安装可跳过）"></a>第二步：安装 Docker（如果已安装可跳过）</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 添加 Docker GPG 密钥</span></span><br><span class="line">curl -fsSL https://download.docker.com/linux/ubuntu/gpg | <span class="built_in">sudo</span> gpg --dearmor -o /usr/share/keyrings/docker.gpg</span><br><span class="line"></span><br><span class="line"><span class="comment"># 添加 Docker 源</span></span><br><span class="line"><span class="built_in">echo</span> <span class="string">&quot;deb [arch=<span class="subst">$(dpkg --print-architecture)</span> signed-by=/usr/share/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu <span class="subst">$(lsb_release -cs)</span> stable&quot;</span> | <span class="built_in">sudo</span> <span class="built_in">tee</span> /etc/apt/sources.list.d/docker.list &gt; /dev/null</span><br><span class="line"></span><br><span class="line"><span class="comment"># 安装 Docker</span></span><br><span class="line"><span class="built_in">sudo</span> apt-get update</span><br><span class="line"><span class="built_in">sudo</span> apt-get install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin</span><br><span class="line"></span><br><span class="line"><span class="comment"># 启动并启用</span></span><br><span class="line"><span class="built_in">sudo</span> systemctl <span class="built_in">enable</span> docker</span><br><span class="line"><span class="built_in">sudo</span> systemctl start docker</span><br><span class="line"></span><br><span class="line"><span class="comment"># 将当前用户加入 docker 组（避免每次输 sudo）</span></span><br><span class="line"><span class="built_in">sudo</span> usermod -aG docker <span class="variable">$USER</span></span><br></pre></td></tr></table></figure><h2 id="第三步：安装-cri-dockerd（关键步骤！）"><a href="#第三步：安装-cri-dockerd（关键步骤！）" class="headerlink" title="第三步：安装 cri-dockerd（关键步骤！）"></a>第三步：安装 cri-dockerd（关键步骤！）</h2><p>这是让 K8s 兼容 Docker 的核心组件。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 下载 cri-dockerd 二进制文件（以 amd64 为例，如果是 arm64 请改链接）</span></span><br><span class="line">VERSION=<span class="string">&quot;0.3.12&quot;</span></span><br><span class="line">ARCH=<span class="string">&quot;amd64&quot;</span></span><br><span class="line">wget https://github.com/Mirantis/cri-dockerd/releases/download/v<span class="variable">$&#123;VERSION&#125;</span>/cri-dockerd-<span class="variable">$&#123;VERSION&#125;</span>.<span class="variable">$&#123;ARCH&#125;</span>.tgz</span><br><span class="line">tar -xvf cri-dockerd-<span class="variable">$&#123;VERSION&#125;</span>.<span class="variable">$&#123;ARCH&#125;</span>.tgz</span><br><span class="line"><span class="built_in">sudo</span> <span class="built_in">mv</span> cri-dockerd/cri-dockerd /usr/local/bin/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 安装 systemd 服务文件</span></span><br><span class="line">wget https://raw.githubusercontent.com/Mirantis/cri-dockerd/master/packaging/systemd/cri-docker.service</span><br><span class="line">wget https://raw.githubusercontent.com/Mirantis/cri-dockerd/master/packaging/systemd/cri-docker.socket</span><br><span class="line"></span><br><span class="line"><span class="built_in">sudo</span> <span class="built_in">mv</span> cri-docker.service cri-docker.socket /etc/systemd/system/</span><br><span class="line"></span><br><span class="line"><span class="comment"># 3. 修改 service 文件，指定 socket 路径</span></span><br><span class="line"><span class="built_in">sudo</span> sed -i -e <span class="string">&#x27;s,/usr/bin/cri-dockerd,/usr/local/bin/cri-dockerd,&#x27;</span> /etc/systemd/system/cri-docker.service</span><br><span class="line"></span><br><span class="line"><span class="comment"># 4. 启动 cri-dockerd</span></span><br><span class="line"><span class="built_in">sudo</span> systemctl daemon-reload</span><br><span class="line"><span class="built_in">sudo</span> systemctl <span class="built_in">enable</span> cri-docker.service</span><br><span class="line"><span class="built_in">sudo</span> systemctl <span class="built_in">enable</span> --now cri-docker.socket</span><br></pre></td></tr></table></figure><h2 id="第四步：安装-Kubeadm-Kubelet-Kubectl"><a href="#第四步：安装-Kubeadm-Kubelet-Kubectl" class="headerlink" title="第四步：安装 Kubeadm, Kubelet, Kubectl"></a>第四步：安装 Kubeadm, Kubelet, Kubectl</h2><p>我们使用阿里云源加速。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 添加阿里云 GPG 密钥</span></span><br><span class="line">curl -fsSL https://mirrors.aliyun.com/kubernetes/apt/doc/apt-key.gpg | <span class="built_in">sudo</span> apt-key add -</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 添加阿里云源</span></span><br><span class="line"><span class="built_in">cat</span> &lt;&lt;<span class="string">EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list</span></span><br><span class="line"><span class="string">deb https://mirrors.aliyun.com/kubernetes/apt/ kubernetes-xenial main</span></span><br><span class="line"><span class="string">EOF</span></span><br><span class="line"></span><br><span class="line"><span class="comment"># 3. 安装指定版本（推荐 1.28，稳定且兼容性好）</span></span><br><span class="line"><span class="built_in">sudo</span> apt-get update</span><br><span class="line"><span class="built_in">sudo</span> apt-get install -y kubelet=1.28.2-00 kubeadm=1.28.2-00 kubectl=1.28.2-00</span><br><span class="line"></span><br><span class="line"><span class="comment"># 4. 锁定版本</span></span><br><span class="line"><span class="built_in">sudo</span> apt-mark hold kubelet kubeadm kubectl</span><br><span class="line"></span><br><span class="line"><span class="comment"># 5. 启用 kubelet</span></span><br><span class="line"><span class="built_in">sudo</span> systemctl <span class="built_in">enable</span> kubelet</span><br></pre></td></tr></table></figure><h2 id="第五步：初始化集群（Init）"><a href="#第五步：初始化集群（Init）" class="headerlink" title="第五步：初始化集群（Init）"></a>第五步：初始化集群（Init）</h2><p>初始化之前我们需要手动从阿里云拉取 pause 镜像，并将其重命名为 Kubelet 期望的名字。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 从阿里云拉取 pause 镜像（版本 3.9 对应 K8s 1.28）</span></span><br><span class="line"><span class="built_in">sudo</span> docker pull registry.aliyuncs.com/google_containers/pause:3.9</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 将其标记为 Kubelet 默认寻找的名字</span></span><br><span class="line"><span class="built_in">sudo</span> docker tag registry.aliyuncs.com/google_containers/pause:3.9 registry.k8s.io/pause:3.9</span><br></pre></td></tr></table></figure><p>然后初始化，注意这里我们要显式指定 <code>--cri-socket</code> 指向 cri-dockerd。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> kubeadm init \</span><br><span class="line">  --pod-network-cidr=10.244.0.0/16 \</span><br><span class="line">  --image-repository=registry.aliyuncs.com/google_containers \</span><br><span class="line">  --cri-socket=unix:///var/run/cri-dockerd.sock \</span><br><span class="line">  --ignore-preflight-errors=NumCPU,Mem</span><br></pre></td></tr></table></figure><ul><li><code>--cri-socket</code>: 告诉 kubeadm 使用 cri-dockerd 而不是 containerd。</li><li><code>--ignore-preflight-errors=NumCPU,Mem</code>: 忽略 2C4G 的资源检查报错。</li></ul><p>等待初始化完成，看到 <code>Your Kubernetes control-plane has initialized successfully!</code> 后，执行提示中的命令：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> -p <span class="variable">$HOME</span>/.kube</span><br><span class="line"><span class="built_in">sudo</span> <span class="built_in">cp</span> -i /etc/kubernetes/admin.conf <span class="variable">$HOME</span>/.kube/config</span><br><span class="line"><span class="built_in">sudo</span> <span class="built_in">chown</span> $(<span class="built_in">id</span> -u):$(<span class="built_in">id</span> -g) <span class="variable">$HOME</span>/.kube/config</span><br></pre></td></tr></table></figure><h2 id="第六步：安装网络插件（Calico）"><a href="#第六步：安装网络插件（Calico）" class="headerlink" title="第六步：安装网络插件（Calico）"></a>第六步：安装网络插件（Calico）</h2><p>Calico 是生产环境的事实标准，功能更强（支持网络策略）。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.26.1/manifests/calico.yaml</span><br></pre></td></tr></table></figure><p>如果下载慢，可以使用这个国内镜像地址：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl apply -f https://ghproxy.net/https://raw.githubusercontent.com/projectcalico/calico/v3.26.1/manifests/calico.yaml</span><br></pre></td></tr></table></figure><p>等待 Pod 启动，Calico 需要一点时间来拉取镜像并启动。执行以下命令观察状态：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">watch kubectl get pods -n kube-system</span><br></pre></td></tr></table></figure><p>当所有 Pod 的状态都变为 Running 时，按 Ctrl+C 退出。</p><p>再次检查节点状态：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl get nodes</span><br></pre></td></tr></table></figure><p>此时，节点状态应该从 NotReady 变为 Ready。</p><h2 id="第七步：移除-Master-污点（单节点必备）"><a href="#第七步：移除-Master-污点（单节点必备）" class="headerlink" title="第七步：移除 Master 污点（单节点必备）"></a>第七步：移除 Master 污点（单节点必备）</h2><p>默认 Master 不跑业务，我们需要强制让它跑。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl taint nodes --all node-role.kubernetes.io/control-plane-</span><br></pre></td></tr></table></figure><h2 id="接下来做什么？"><a href="#接下来做什么？" class="headerlink" title="接下来做什么？"></a>接下来做什么？</h2><p>你可以尝试部署一个 Nginx 来测试网络是否通畅。</p><h3 id="创建-Deployment"><a href="#创建-Deployment" class="headerlink" title="创建 Deployment"></a>创建 Deployment</h3><p>执行以下命令，K8s 会从 Docker Hub 拉取 nginx:alpine 镜像并启动一个 Pod：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl create deployment my-nginx --image=nginx:alpine --port=80</span><br></pre></td></tr></table></figure><ul><li><code>my-nginx</code>: 你给这个应用起的名字。</li><li><code>--image=nginx:alpine</code>: 使用的镜像。</li><li><code>--port=80</code>: 告诉 K8s 这个容器监听 80 端口。</li></ul><h3 id="检查-Pod-状态"><a href="#检查-Pod-状态" class="headerlink" title="检查 Pod 状态"></a>检查 Pod 状态</h3><p>执行以下命令查看 Pod 是否运行成功：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl get pods</span><br></pre></td></tr></table></figure><ul><li><code>STATUS: Running</code> 表示容器已经成功启动。</li><li><code>READY: 1/1</code> 表示容器已准备好接收流量。</li><li>如果状态是 ContainerCreating，请稍等几秒再查，因为第一次需要拉取镜像。</li></ul><h3 id="暴露服务（让外部能访问）"><a href="#暴露服务（让外部能访问）" class="headerlink" title="暴露服务（让外部能访问）"></a>暴露服务（让外部能访问）</h3><p>默认情况下，Pod 只能在集群内部访问。为了让你的浏览器能访问它，我们需要创建一个 Service，并将其类型设置为 NodePort：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl expose deployment my-nginx --<span class="built_in">type</span>=NodePort --port=80</span><br></pre></td></tr></table></figure><h3 id="获取访问地址"><a href="#获取访问地址" class="headerlink" title="获取访问地址"></a>获取访问地址</h3><p>执行以下命令查看服务分配的端口：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl get svc my-nginx</span><br></pre></td></tr></table></figure><p>注意看 PORT(S) 列：<code>80:32124/TCP</code>。</p><ul><li>80 是容器内部端口。</li><li>32124 是映射到你服务器上的节点端口（你的数字可能不同，请以实际输出为准）。</li></ul><h3 id="浏览器访问"><a href="#浏览器访问" class="headerlink" title="浏览器访问"></a>浏览器访问</h3><p>打开浏览器，访问：</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">http://&lt;你的服务器公网IP&gt;:&lt;节点端口&gt;</span><br></pre></td></tr></table></figure><p>例如：<code>http://1.2.3.4:32124</code></p><p>如果你看到了 “Welcome to nginx!” 的页面，恭喜你！你已经成功用 Kubernetes 部署并暴露了一个应用！</p><h3 id="删除-Nginx"><a href="#删除-Nginx" class="headerlink" title="删除 Nginx"></a>删除 Nginx</h3><p>要删除刚才部署的 Nginx，你需要同时删除 Deployment（负责管理容器）和 Service（负责暴露端口）。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment"># 1. 删除 Deployment（这会自动删除对应的 Pod）</span></span><br><span class="line">kubectl delete deployment my-nginx</span><br><span class="line"></span><br><span class="line"><span class="comment"># 2. 删除 Service（释放节点端口）</span></span><br><span class="line">kubectl delete svc my-nginx</span><br></pre></td></tr></table></figure><h3 id="验证是否删除干净"><a href="#验证是否删除干净" class="headerlink" title="验证是否删除干净"></a>验证是否删除干净</h3><p>执行以下命令，确保列表中没有残留：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">kubectl get all</span><br></pre></td></tr></table></figure><p>如果输出中不再显示 my-nginx 相关的行，说明已经彻底清理完毕。你的集群又恢复到初始的干净状态了！</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Kubernetes/">Kubernetes</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Kubernetes/">Kubernetes</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/K8s/">K8s</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/04/560ac167/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL8.0.36 GTID主从同步失败排查</title>
      <link>https://blog.eucalyptus.cc/2024/04/03/9c0a6ac1/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/03/9c0a6ac1/</guid>
      <pubDate>Wed, 03 Apr 2024 09:22:42 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;报错信息:&lt;/strong&gt;&lt;/p&gt;
&lt;figure class=&quot;highlight sql&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td class=&quot;gutter&quot;&gt;&lt;pre&gt;&lt;span class=&quot;line&quot;&gt;1&lt;/span&gt;&lt;br&gt;&lt;span</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong>报错信息:</strong></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">Last_SQL_Error: Coordinator stopped because there were error(s) <span class="keyword">in</span> the worker(s). The most recent failure being: Worker <span class="number">1</span> failed executing transaction <span class="string">&#x27;6f577885-e5d0-11ee-a94a-0242c0a80067:1&#x27;</span> <span class="keyword">at</span> source log <span class="number">7364</span>ffd6441c<span class="operator">-</span>bin<span class="number">.000006</span>, end_log_pos <span class="number">724.</span> See error log <span class="keyword">and</span><span class="operator">/</span><span class="keyword">or</span> performance_schema.replication_applier_status_by_worker <span class="keyword">table</span> <span class="keyword">for</span> more details about this failure <span class="keyword">or</span> others, if any.</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>根据报错信息查看具体内容</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> performance_schema.replication_applier_status_by_worker\G</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-03/img1.avif"></p><p>解析binlog日志查看</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">mysqlbinlog -vvv 7364ffd6441c-bin.000006</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-03/img2.avif"></p><p> 看起来因该是主库的的一个school库被手动删除,而从库中没有这个school导致binlog不一致出现报错,那么只要在从库中将这个事务手动的跳过即可</p><p>首先停止线程</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">stop slave;</span><br></pre></td></tr></table></figure><p>跳过事务</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">set</span> session.gtid_next <span class="string">&#x27;6f577885-e5d0-11ee-a94a-0242c0a80067:1&#x27;</span>;</span><br><span class="line"><span class="keyword">begin</span>;</span><br><span class="line"><span class="keyword">commit</span>;</span><br><span class="line"><span class="keyword">Set</span> SESSION.GTID_NEXT AUTOMATIC;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>启动线程检查复制关系</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">start</span> slave;</span><br><span class="line"><span class="keyword">show</span> slave status\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-03/img3.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/03/9c0a6ac1/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>YUM安装MySQL报错合集</title>
      <link>https://blog.eucalyptus.cc/2024/04/02/d73665fb/</link>
      <guid>https://blog.eucalyptus.cc/2024/04/02/d73665fb/</guid>
      <pubDate>Tue, 02 Apr 2024 03:11:17 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;报错信息&quot;&gt;&lt;a href=&quot;#报错信息&quot; class=&quot;headerlink&quot; title=&quot;报错信息&quot;&gt;&lt;/a&gt;报错信息&lt;/h2&gt;&lt;figure class=&quot;highlight sql&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="报错信息"><a href="#报错信息" class="headerlink" title="报错信息"></a>报错信息</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">Error:</span><br><span class="line">Problem: cannot install the best candidate <span class="keyword">for</span> the job</span><br><span class="line"><span class="operator">-</span> nothing provides libcrypto.so<span class="number">.10</span>()(<span class="number">64</span>bit) needed <span class="keyword">by</span> mysql<span class="operator">-</span>community<span class="operator">-</span>server<span class="number">-8.0</span><span class="number">.36</span><span class="number">-1.</span>el7.x86_64 <span class="keyword">from</span> mysql80<span class="operator">-</span>community</span><br><span class="line"><span class="operator">-</span> nothing provides libssl.so<span class="number">.10</span>()(<span class="number">64</span>bit) needed <span class="keyword">by</span> mysql<span class="operator">-</span>community<span class="operator">-</span>server<span class="number">-8.0</span><span class="number">.36</span><span class="number">-1.</span>el7.x86_64 <span class="keyword">from</span> mysql80<span class="operator">-</span>community</span><br><span class="line"><span class="operator">-</span> nothing provides libcrypto.so<span class="number">.10</span>(libcrypto.so<span class="number">.10</span>)(<span class="number">64</span>bit) needed <span class="keyword">by</span> mysql<span class="operator">-</span>community<span class="operator">-</span>server<span class="number">-8.0</span><span class="number">.36</span><span class="number">-1.</span>el7.x86_64 <span class="keyword">from</span> mysql80<span class="operator">-</span>community</span><br><span class="line"><span class="operator">-</span> nothing provides libssl.so<span class="number">.10</span>(libssl.so<span class="number">.10</span>)(<span class="number">64</span>bit) needed <span class="keyword">by</span> mysql<span class="operator">-</span>community<span class="operator">-</span>server<span class="number">-8.0</span><span class="number">.36</span><span class="number">-1.</span>el7.x86_64 <span class="keyword">from</span> mysql80<span class="operator">-</span>community</span><br><span class="line"><span class="operator">-</span> nothing provides libcrypto.so<span class="number">.10</span>(OPENSSL_1<span class="number">.0</span><span class="number">.2</span>)(<span class="number">64</span>bit) needed <span class="keyword">by</span> mysql<span class="operator">-</span>community<span class="operator">-</span>server<span class="number">-8.0</span><span class="number">.36</span><span class="number">-1.</span>el7.x86_64 <span class="keyword">from</span> mysql80<span class="operator">-</span>community</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="解决方法"><a href="#解决方法" class="headerlink" title="解决方法"></a>解决方法</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">wget http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/compat-openssl10-1.0.2o-4.el8.x86_64.rpm</span><br><span class="line"></span><br><span class="line">rpm -ivh mysql80-community-release-el7-7.noarch.rpm</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="报错信息-1"><a href="#报错信息-1" class="headerlink" title="报错信息"></a>报错信息</h2><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br></pre></td><td class="code"><pre><span class="line">Import of key(s) didn<span class="string">&#x27;t help, wrong key(s)?</span></span><br><span class="line"><span class="string">Public key for mysql-community-client-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-community-clie nt-8.0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">Public key for mysql-community-client-plugins-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-commun ity-client-plugins-8.0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">Public key for mysql-community-common-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-community-comm on-8.0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">Public key for mysql-community-icu-data-files-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-commun ity-icu-data-files-8.0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">Public key for mysql-community-libs-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-community-libs-8 .0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">Public key for mysql-community-server-8.0.36-1.el7.x86_64.rpm is not installed. Failing package is: mysql-community-serv er-8.0.36-1.el7.x86_64</span></span><br><span class="line"><span class="string">GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql</span></span><br><span class="line"><span class="string">The downloaded packages were saved in cache until the next successful transaction.</span></span><br><span class="line"><span class="string">You can remove cached packages by executing &#x27;</span>yum clean packages<span class="string">&#x27;.</span></span><br><span class="line"><span class="string">Error: GPG check FAILED</span></span><br><span class="line"><span class="string"></span></span><br></pre></td></tr></table></figure><h2 id="解决方法-1"><a href="#解决方法-1" class="headerlink" title="解决方法"></a>解决方法</h2><p>去官网下载最新的GPG-KEY即可 ,记得文件的存放路径**&#x2F;etc&#x2F;pki&#x2F;rp-gpg&#x2F;**下</p><p>MySQL官方仓库:<a href="https://repo.mysql.com/">https://repo.mysql.com/</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-04-02/img1.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">wget https://repo.mysql.com/RPM-GPG-KEY-mysql</span><br><span class="line">wget https://repo.mysql.com/RPM-GPG-KEY-mysql-2023</span><br></pre></td></tr></table></figure><p>但是有意思的是上面这个报错解决了,但是又出现了一个新的error,意思就是找不到<strong>file:&#x2F;&#x2F;&#x2F;etc&#x2F;pki&#x2F;rpm-gpg&#x2F;RPM-GPG-KEY-mysql-2022</strong>这个文件了,对于这个error我这里是将之前下载的<strong>RPM-GPG-KEY-mysql-2023</strong>改名为<strong>RPM-GPG-KEY-mysql-2022</strong>即可解决这个问题,改名的话就不介绍了,毕竟这么简单不会有人还不会吧!</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">Curl error (37): Couldn<span class="string">&#x27;t read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022 [Couldn&#x27;</span>t open file /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2022]</span><br><span class="line">The downloaded packages were saved <span class="keyword">in</span> cache <span class="keyword">until</span> the next successful transaction.</span><br><span class="line">You can remove cached packages by executing <span class="string">&#x27;yum clean packages&#x27;</span>.</span><br><span class="line"></span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/04/02/d73665fb/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>使用mycli实现MySQL命令自动补全功能（Python-3.9.0）</title>
      <link>https://blog.eucalyptus.cc/2024/03/22/31807ff3/</link>
      <guid>https://blog.eucalyptus.cc/2024/03/22/31807ff3/</guid>
      <pubDate>Fri, 22 Mar 2024 05:28:12 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;当我们在CentOS中通过yum,rpm,编译安装MySQL后,一般在命令行中登陆MySQL后会发现没有tab补全功能,这个时候对我们来说不太友好,毕竟命令非常多不可能都记住,这个时候你可以考虑安装一些第三方工具或插件,如 &lt;code&gt;mycli&lt;/code&gt; 或</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>当我们在CentOS中通过yum,rpm,编译安装MySQL后,一般在命令行中登陆MySQL后会发现没有tab补全功能,这个时候对我们来说不太友好,毕竟命令非常多不可能都记住,这个时候你可以考虑安装一些第三方工具或插件,如 <code>mycli</code> 或 <code>pgcli</code>,它们提供了更强大的命令补全功能和易用的交互界面,可以帮助你更高效地管理数据库,下面介绍到的是mycli工具的安装。</p><h2 id="安装步骤"><a href="#安装步骤" class="headerlink" title="安装步骤"></a>安装步骤</h2><h3 id="安装相关的依赖"><a href="#安装相关的依赖" class="headerlink" title="安装相关的依赖"></a>安装相关的依赖</h3><p><strong>大部分依赖都来源于epel源</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">yum -y install epel-release</span><br><span class="line">yum -y install zlib-devel bzip2-devel openssl-devel ncurses-devel sqlite-devel readline-devel tk-devel gdbm-devel db4-devel libpcap-devel xz-devel gcc</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><strong>安装的过程中如果遇到没有的包,可以在镜像网站中下载,</strong><a href="https://developer.aliyun.com/mirror/">阿里巴巴开源镜像站</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-22/img1.avif"></p><p><strong>下载并解压python-3.9.0.tgz</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> /opt/python3.9.0</span><br><span class="line"><span class="built_in">cd</span> /opt/python3.9.0</span><br><span class="line"><span class="comment">#下载Python-3.9.0.tgz</span></span><br><span class="line">wget https://www.python.org/ftp/python/3.9.0/Python-3.9.0.tgz</span><br><span class="line"><span class="comment">#解压</span></span><br><span class="line">tar -xzvf Python-3.9.0.tgz</span><br></pre></td></tr></table></figure><h3 id="编译安装"><a href="#编译安装" class="headerlink" title="编译安装"></a>编译安装</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#进入到解压后的Python-3.9.0目录中,然后运行configure脚本检查系统依赖,并设置编译选项</span></span><br><span class="line"><span class="built_in">cd</span> Python-3.9.0/</span><br><span class="line">./configure --prefix /usr/local/python3.9.0</span><br><span class="line"><span class="comment">#编译</span></span><br><span class="line">make</span><br><span class="line"><span class="comment">#安装</span></span><br><span class="line">make install</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="配置环境变量"><a href="#配置环境变量" class="headerlink" title="配置环境变量"></a>配置环境变量</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#在~/.bashrc文件中配置环境变量</span></span><br><span class="line"><span class="built_in">export</span> PATH /usr/local/python3.9.0/bin:<span class="variable">$PATH</span></span><br><span class="line"><span class="comment">#然后运行下述命令使变量生效</span></span><br><span class="line"><span class="built_in">source</span> ~/.bashrc</span><br></pre></td></tr></table></figure><h3 id="安装mycli"><a href="#安装mycli" class="headerlink" title="安装mycli"></a>安装mycli</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/python3.9.0/bin/pip3 install mycli</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-22/img2.avif"></p><h3 id="登陆数据库测试"><a href="#登陆数据库测试" class="headerlink" title="登陆数据库测试"></a>登陆数据库测试</h3><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mycli -u root -p<span class="tag">&lt;<span class="name">密码</span>&gt;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-22/img3.avif"></p><h3 id="卸载mycli"><a href="#卸载mycli" class="headerlink" title="卸载mycli"></a>卸载mycli</h3><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">/usr/local/python3.9.0/bin/pip3 uninstall mycli</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-22/img4.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/03/22/31807ff3/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>关于在CentOS中卸载MySQL</title>
      <link>https://blog.eucalyptus.cc/2024/03/21/47bd5f2e/</link>
      <guid>https://blog.eucalyptus.cc/2024/03/21/47bd5f2e/</guid>
      <pubDate>Thu, 21 Mar 2024 10:14:01 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;想要卸载MySQL当然要知道自己的MySQL是用那种方法来安装的了,一般来说MySQL的安装方法在市面上有三种</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>想要卸载MySQL当然要知道自己的MySQL是用那种方法来安装的了,一般来说MySQL的安装方法在市面上有三种 编译安装、YUM安装、RPM安装,下面会介绍到后两种安装的卸载方法</p><p>首先查看是否安装MySQL,一般可以看到版本信息就证明安装了</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -V</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-21/img1.avif"></p><h2 id="卸载方法一-RPM"><a href="#卸载方法一-RPM" class="headerlink" title="卸载方法一 RPM"></a>卸载方法一 RPM</h2><p><strong>首先查看安装的rpm包</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">rpm -qa | grep -i msyql </span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2024-03-21/img2.avif"></p><p><strong>依次卸载rpm包,按照下面顺序卸载不然会报错</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">rpm -evh rpm包名</span><br></pre></td></tr></table></figure><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">mysql-community-server-8.0.36-1.el7.x86_64</span><br><span class="line">mysql-community-icu-data-files-8.0.36-1.el7.x86_64</span><br><span class="line">mysql-community-client-8.0.36-1.el7.x86_64</span><br><span class="line">mysql-community-libs-8.0.36-1.el7.x86_64</span><br><span class="line">mysql-community-client-plugins-8.0.36-1.el7.x86_64</span><br><span class="line">mysql-community-common-8.0.36-1.el7.x86_64</span><br></pre></td></tr></table></figure><h2 id="卸载方法二-YUM"><a href="#卸载方法二-YUM" class="headerlink" title="卸载方法二 YUM"></a>卸载方法二 YUM</h2><p>既然是用yum安装的MySQL那么直接删除MySQL的源,然后在卸载MySQL-server,最后在删除MySQL的配置文件就可以了….</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/03/21/47bd5f2e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker attach V/S Docker exec</title>
      <link>https://blog.eucalyptus.cc/2024/03/21/311216e4/</link>
      <guid>https://blog.eucalyptus.cc/2024/03/21/311216e4/</guid>
      <pubDate>Thu, 21 Mar 2024 01:46:30 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;docker exec和docker attach都是进入容器的命令但是它么两个有一些区别你们知道吗？&lt;/p&gt;
&lt;h2 id=&quot;docker-attach-语法&quot;&gt;&lt;a href=&quot;#docker-attach-语法&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>docker exec和docker attach都是进入容器的命令但是它么两个有一些区别你们知道吗？</p><h2 id="docker-attach-语法"><a href="#docker-attach-语法" class="headerlink" title="docker attach 语法"></a>docker attach 语法</h2><p>attach是Docker自带的命令，命令的语法为：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker attach 容器ID</span><br></pre></td></tr></table></figure><h2 id="docker-exec-语法"><a href="#docker-exec-语法" class="headerlink" title="docker exec 语法"></a>docker exec 语法</h2><p>从Docker的1.3版本起，Docker提供了更加方便的工具exec命令，可以在运行容器内直接执行任意命令。命令语法为：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker <span class="built_in">exec</span> -it 容器ID bash</span><br></pre></td></tr></table></figure><h2 id="两者区别"><a href="#两者区别" class="headerlink" title="两者区别"></a>两者区别</h2><ul><li><p>当多个窗口同是attach到同一个容器的时候，所有窗口都会同步显示；当某个窗口因命令阻塞时，其他窗口也无法执行操作。</p></li><li><p>可以使用 docker exec -it 容器id &#x2F;bin&#x2F;bash 进入容器并开启一个新的bash终端。 使用exit或者Ctrl+d退出容器终端时，不会导致容器的停止。</p></li><li><p>使用 docker attach 容器id 进入正在执行容器，不会启动新的终端， 使用exit或者Ctrl+d退出容器时，会导致容器的停止，但是使用Ctrl+p+q退出后容器不会停止。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/03/21/311216e4/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL YUM安装</title>
      <link>https://blog.eucalyptus.cc/2024/03/08/dc0f013f/</link>
      <guid>https://blog.eucalyptus.cc/2024/03/08/dc0f013f/</guid>
      <pubDate>Fri, 08 Mar 2024 09:05:03 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;本次实验是在docker容器中安装centos7，然后再在centos7中安装postgresql。&lt;/p&gt;
&lt;h2 id=&quot;配置环境&quot;&gt;&lt;a href=&quot;#配置环境&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>本次实验是在docker容器中安装centos7，然后再在centos7中安装postgresql。</p><h2 id="配置环境"><a href="#配置环境" class="headerlink" title="配置环境"></a>配置环境</h2><table><thead><tr><th>Linux</th><th>PostgreSQL</th><th>Docker</th></tr></thead><tbody><tr><td>centos7</td><td>15</td><td>24.0.7</td></tr></tbody></table><h2 id="docker中的centos7中安装"><a href="#docker中的centos7中安装" class="headerlink" title="docker中的centos7中安装"></a>docker中的centos7中安装</h2><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img1.avif"></p><p>选择对应的版本然后在容器中的centos7中执行下面命令</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img2.avif"></p><p>但是启动容器的时候需要注意：</p><ol><li>开启端口映射</li><li>开启特权模式</li><li>启动init进程</li></ol><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker run -itd --name centos-postgresql -p 5433:5432 --privileged=<span class="literal">true</span> centos:centos7 /usr/sbin/init</span><br></pre></td></tr></table></figure><p>启动然后进入后先安装ibzstd.so.1依赖</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">yum install epel-release.noarch -y</span><br><span class="line"></span><br><span class="line">yum install libzstd.x86_64 -y</span><br></pre></td></tr></table></figure><h2 id="安装PostgreSQL"><a href="#安装PostgreSQL" class="headerlink" title="安装PostgreSQL"></a>安装PostgreSQL</h2><p>官网安装教程：<a href="https://www.postgresql.org/download/linux/redhat/">https://www.postgresql.org/download/linux/redhat/</a></p><p>安装完依赖后就可以按下面的顺序执行命令</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img3.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm</span><br><span class="line"></span><br><span class="line">yum install -y postgresql15-server</span><br><span class="line"></span><br><span class="line">/usr/pgsql-15/bin/postgresql-15-setup initdb</span><br><span class="line"></span><br><span class="line">systemctl <span class="built_in">enable</span> postgresql-15</span><br><span class="line"></span><br><span class="line">systemctl start postgresql-15</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img5.avif"></p><p>执行完成后就可以切换用户登陆postgresql了</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#切换用户</span></span><br><span class="line"></span><br><span class="line">su - postgres</span><br><span class="line"></span><br><span class="line"><span class="comment">#登陆数据库</span></span><br><span class="line"></span><br><span class="line">psql</span><br></pre></td></tr></table></figure><p>接下来配置数据库访问控制文件，主要是配置postgresql.conf 和 pg_hba.conf 两个。</p><ol><li>postgresql.conf 针对实例的配置</li><li>pg_hba.conf 针对数据库访问的控制</li></ol><p>切换到<code>/var/lib/pgsql/15/data</code>目录下</p><p>注意：这里<code>/var/lib/pgsql/15/data</code>的15要根据自己安装的版本来确定</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img6.avif"></p><p>配置postgresql.conf</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim postgresql.conf</span><br></pre></td></tr></table></figure><p>找到”#port”和”#listener_address”这两个参数，这两个参数是相邻的，将两行行首的”#”删除。</p><p>将<code>listen_addresses=&#39;localhost&#39;</code>改为当前服务器的IP，如果改为<code>listen_addresses=&#39;*&#39;</code>，将监听整个网络。默认的监听端口是5432，可以自行指定另外一个端口号。</p><p><code>max_connections</code>是客户端最大的连接数，缺省值100有点少，特别是业务系统，可以调整成1000或者更高。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img7.avif"></p><p>配置pg_hba.conf</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim pg_hba.conf</span><br></pre></td></tr></table></figure><p>将红框设置为 <code>10.10.100.0/24</code>，意思是10.10.100网段的IP连接此服务器上的PostgreSQL。如果想允许所有IP都可以连接此服务器，则可以配置成<code>0.0.0.0/0</code>，但这样是不安全的，可以把trust改为md5，表示需要密码访问，算是提供一个最低级的安全防护。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img8.avif"></p><p>配置完这两个文件后就可以重启数据库了</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl restart postgresql-15</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img9.avif"></p><p>记得关闭防火墙</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop firewalld</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img10.avif"></p><p>测试连接</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img11.avif"></p><h2 id="docker中直接安装"><a href="#docker中直接安装" class="headerlink" title="docker中直接安装"></a>docker中直接安装</h2><p>拉取postgresql镜像后直接启动容器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#拉取镜像</span></span><br><span class="line"></span><br><span class="line">docker search postgres</span><br><span class="line"></span><br><span class="line"><span class="comment">#启动容器</span></span><br><span class="line"></span><br><span class="line">docker run -itd --name postgresql -e POSTGRES_PASSWORD=数据库密码 -p 5555:5432 postgres</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img12.avif"></p><p>测试连接成功</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-08/img13.avif"></p><p>注意事项：</p><ol><li>两个centos7中的防火墙记得都要放行端口或者关闭</li><li>postgresql.conf 和 pg_hba.conf文件记得配置</li></ol>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/03/08/dc0f013f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>PostgreSQL编译安装教程</title>
      <link>https://blog.eucalyptus.cc/2024/03/07/7256ce63/</link>
      <guid>https://blog.eucalyptus.cc/2024/03/07/7256ce63/</guid>
      <pubDate>Thu, 07 Mar 2024 10:14:28 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;系统环境&quot;&gt;&lt;a href=&quot;#系统环境&quot; class=&quot;headerlink&quot; title=&quot;系统环境&quot;&gt;&lt;/a&gt;系统环境&lt;/h2&gt;&lt;ol&gt;
&lt;li&gt;操作系统：CentOS</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="系统环境"><a href="#系统环境" class="headerlink" title="系统环境"></a>系统环境</h2><ol><li>操作系统：CentOS 7.6.1810</li><li>PostgreSQL版本：16.0</li></ol><h2 id="下载压缩包"><a href="#下载压缩包" class="headerlink" title="下载压缩包"></a>下载压缩包</h2><p>官网地址：<a href="https://www.postgresql.org/ftp/source/">PostgreSQL: File Browser</a></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img2.avif"></p><h3 id="下载压缩包-1"><a href="#下载压缩包-1" class="headerlink" title="下载压缩包"></a>下载压缩包</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">wget https://ftp.postgresql.org/pub/source/v16.0/postgresql-16.0.tar.gz</span><br></pre></td></tr></table></figure><h3 id="解压压缩包"><a href="#解压压缩包" class="headerlink" title="解压压缩包"></a>解压压缩包</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">tar -xzvf postgresql-16.0.tar.gz</span><br></pre></td></tr></table></figure><h3 id="查看解压文件"><a href="#查看解压文件" class="headerlink" title="查看解压文件"></a>查看解压文件</h3><p>解压之后会看到下面的文件</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img3.avif"></p><h2 id="编译安装"><a href="#编译安装" class="headerlink" title="编译安装"></a>编译安装</h2><h3 id="检查系统环境并设置合适选项"><a href="#检查系统环境并设置合适选项" class="headerlink" title="检查系统环境并设置合适选项"></a>检查系统环境并设置合适选项</h3><p>进入postgresql-16.0目录，编译configure文件</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img4.avif"></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">./configure --prefix=/usr/local/pgsql</span><br></pre></td></tr></table></figure><p>参数：<code>--prefix=/usr/local/pgsql</code> 表示编译好的文件放到目录<code>/usr/local/pgsql</code>里，这个目录不用用户自己创建，编译过程会自动创建。</p><p>注意事项：</p><p>PostgreSQL编译过程会用到一些依赖的库，如果你的操作系统比较旧，编译过程可能会出现错误，告诉你要安装缺少的依赖库。</p><p>看到<code>./config.status</code>说明编译完成，可以看见config.status文件</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img5.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img6.avif"></p><h3 id="编译-安装"><a href="#编译-安装" class="headerlink" title="编译&#x2F;安装"></a>编译&#x2F;安装</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">make &amp;&amp; make install</span><br></pre></td></tr></table></figure><p>完成以后，在<code>--prefix=/usr/local/pgsql</code>参数对应的<code>/usr/local/pgsql</code>的目录就是我们所有PostgreSQL存放的文件，这里的data和log文件现在是没有的。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img7.avif"></p><h2 id="用户权限和环境变量设置"><a href="#用户权限和环境变量设置" class="headerlink" title="用户权限和环境变量设置"></a>用户权限和环境变量设置</h2><p>编译安装成功后，接下来要做的就是创建一个普通用户，因为默认Linux超级用户（root）不能启动PostgreSQL，所以需要创建一个普通用户来操作数据库。</p><h3 id="创建用户"><a href="#创建用户" class="headerlink" title="创建用户"></a>创建用户</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">#创建用户组postgres</span></span><br><span class="line"></span><br><span class="line">groupadd postgres</span><br><span class="line"></span><br><span class="line"><span class="comment">#创建用户postgres并设置groups、gid和家目录</span></span><br><span class="line"></span><br><span class="line">useradd -g postgres -G postgres -d /home/postgresql postgres</span><br><span class="line"></span><br><span class="line"><span class="comment">#设置用户密码</span></span><br><span class="line"></span><br><span class="line">passwd postgres</span><br></pre></td></tr></table></figure><h3 id="创建数据目录和日志目录"><a href="#创建数据目录和日志目录" class="headerlink" title="创建数据目录和日志目录"></a>创建数据目录和日志目录</h3><p>注意当前路径是在<code>/usr/local/pgsql</code>下</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> data <span class="built_in">log</span></span><br></pre></td></tr></table></figure><h3 id="设置权限"><a href="#设置权限" class="headerlink" title="设置权限"></a>设置权限</h3><p>接下来需要设置权限，将<code>/usr/local/pgsql</code> (我们安装PostgreSQL数据库的目录) 目录全部赋权给postgres用户</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">chown</span> -R postgres.postgres /usr/local/pgsql/</span><br></pre></td></tr></table></figure><h3 id="设置环境变量"><a href="#设置环境变量" class="headerlink" title="设置环境变量"></a>设置环境变量</h3><p>为了方便起见设置一下相关的环境变量，此处是要设置postgres用户的环境变量，所以首先要把Linux的登陆用户由root切换到以postgres用户登陆。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">su - postgres</span><br></pre></td></tr></table></figure><p>因为我们创建Linux用户”postgres”是指定了用户的目录为<code>/home/postgresql</code>，所以登陆后显示的目录是：<code>/home/postgresql</code></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img8.avif"></p><p>要创建环境变量，实际上就是对文件<code>.bash_profile</code>的修改，所以我们首先要找到这个文件，这个文件就在<code>/home/postgresql</code>里，由于这个文件是隐藏文件所以要加<code>-a</code>参数</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ll -a</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img9.avif"></p><p>编辑<code>.bash_profile</code>文件</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim .bash_profile</span><br></pre></td></tr></table></figure><p>添加下面的内容</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img10.avif"></p><p>使配置的环境变量生效</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">source</span> /home/postgresql/.bash_profile</span><br></pre></td></tr></table></figure><p>检查是否生效</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">psql -V</span><br></pre></td></tr></table></figure><p>看到安装PostgreSQL的版本号则代表生效</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img11.avif"></p><h2 id="初始化数据库"><a href="#初始化数据库" class="headerlink" title="初始化数据库"></a>初始化数据库</h2><p>新安装的PostgreSQL数据库系统，要先初始化基本的基础数据库，然后我们才能在上面创建我们自己的数据库。初始化数据库的指令是<code>initdb</code>，这个指令位于<code>/usr/local/pgsql/bin/</code></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img12.avif"></p><p>我们可以用指令<code>initdb --help</code>看看这个文件的帮助信息。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img13.avif"></p><p>如上图，可以看到在使用<code>initdb</code>进行初始化时，可以指定参数进行一些初始化工作，例如指定pgdata（postgresql数据库目录）、指定encoding（编码）、指定数据库超级用户的用户名和密码等等。注意，如果pgdata目录没有指定，则会默认使用环境变量中的PGDATA指定的目录作为数据库存放的目录，由于之前我们刚刚设置了<code>PGDATA=/usr/local/pgsql/data</code>环境变量，所以此处我们也就无需再额外指定，直接执行初始化命令即可。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">initdb</span><br></pre></td></tr></table></figure><p>若是执行initdb看到下面报错，说明现在登陆的不是postgres用户，需要切换到postgres用户来执行initdb命令</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img14.avif"></p><p>看到下面信息就代表成功</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img15.avif"></p><p>同时在<code>/usr/local/pgsql/data</code>的目录可以看到生成的数据和配置文件等。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img16.avif"></p><ol><li>base目录是表空间目录</li><li>global目录是相关全局变量的目录</li><li>pg_hba.conf是访问控制配置，127.0.0.1改为信任的客户端ip网段使其可以远程访问</li><li>postgresql.conf是PostgreSQL主配置文件，<code>listen_addresses=localhost</code>改为<code>*</code>使其监听整个网络，方便起见我这里将pg_hba.conf的ip地址修改为<code>0.0.0.0/0</code>，而加密方式改为md5，就表示需要密码访问，算是提供一个最低级的安全防护</li></ol><h2 id="数据库访问控制配置文件"><a href="#数据库访问控制配置文件" class="headerlink" title="数据库访问控制配置文件"></a>数据库访问控制配置文件</h2><p>主要是配置postgresql.conf 和 pg_hba.conf 两个。</p><ol><li>postgresql.conf 针对实例的配置</li><li>pg_hba.conf 针对数据库访问的控制</li></ol><h3 id="postgresql-conf"><a href="#postgresql-conf" class="headerlink" title="postgresql.conf"></a>postgresql.conf</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim postgresql.conf</span><br></pre></td></tr></table></figure><p>找到”#port”和”#listener_address”这两个参数，这两个参数是相邻的，将两行行首的”#”删除。</p><p>将<code>listen_addresses=&#39;localhost&#39;</code>改为当前服务器的IP，如果改为<code>listen_addresses=&#39;*&#39;</code>，将监听整个网络。默认的监听端口是5432，可以自行指定另外一个端口号。</p><p><code>max_connections</code>是客户端最大的连接数，缺省值100有点少，特别是业务系统，可以调整成1000或者更高。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img17.avif"></p><h3 id="pg-hba-conf"><a href="#pg-hba-conf" class="headerlink" title="pg_hba.conf"></a>pg_hba.conf</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim pg_hba.conf</span><br></pre></td></tr></table></figure><p>将红框设置为 <code>10.10.100.0/24</code>，意思是10.10.100网段的IP连接此服务器上的PostgreSQL。如果想允许所有IP都可以连接此服务器，则可以配置成<code>0.0.0.0/0</code>，但这样是不安全的，可以把trust改为md5，表示需要密码访问，算是提供一个最低级的安全防护。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img18.avif"></p><h2 id="PostgreSQL启动与关闭"><a href="#PostgreSQL启动与关闭" class="headerlink" title="PostgreSQL启动与关闭"></a>PostgreSQL启动与关闭</h2><h3 id="手动"><a href="#手动" class="headerlink" title="手动"></a>手动</h3><p>启动与关闭数据库是执行<code>pg_ctl</code>命令，在执行时，需要指定数据库路径和日志文件路径，格式如下：</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_ctl -D &lt;数据存放路径&gt; -l &lt;日志文件路径&gt; [ stop | start ]</span><br></pre></td></tr></table></figure><p>如果已经指定了环境变量PGDATA，”数据存放路径”参数可以省略。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">pg_ctl -D /usr/local/pgsql/data -l /usr/local/pgsql/log/pg_server.log start</span><br></pre></td></tr></table></figure><h3 id="自动"><a href="#自动" class="headerlink" title="自动"></a>自动</h3><p>此步骤需要root用户操作，如果你是用PostgreSQL的用户postgres登陆的话，要用<code>exit</code>指令退出，回到root登陆才能操作。</p><p>PostgreSQL解压后的安装包目录中提供了数据库启动与关闭的脚本，此脚本不但可以帮助我们简化操作，而且可以用作开机启动的脚本和service&#x2F;systemctl控制服务的脚本。目录里<code>linux</code>文件就是我们要找的文件。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img19.avif"></p><p>如果找不到linux文件可以执行下面命令查看</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">find / -name macos</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img20.avif"></p><p>把文件<code>linux</code>拷贝到目录<code>/etc/init.d/</code>下，并改名为postgresql。</p><p>把脚本文件<code>postgresql</code>加入到开机启动的程序列表。</p><p>赋予<code>postgresql</code>文件有执行的权限。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cp</span> /opt/postgresql/postgresql-16.0/contrib/start-scripts/linux /etc/init.d/postgresql</span><br><span class="line"></span><br><span class="line">chkconfig --add postgresql或者systemctl <span class="built_in">enable</span> postgresql</span><br><span class="line"></span><br><span class="line"><span class="built_in">chmod</span> 755 /etc/init.d/postgresql</span><br></pre></td></tr></table></figure><p>主要设置文件<code>postgresql</code>的四个变量的值。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim /etc/init.d/postgresql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img21.avif"></p><ul><li><code>prefix</code> 是软件的安装路径</li><li><code>PGDATA</code> 是数据存放路径</li><li><code>PGUSER</code> 是启动PostgreSQL服务器的用户</li><li><code>PGLOG</code> 是日志文件</li></ul><p>以后可以开机启动和通过service命令控制启动和关闭了。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">service postgresql start/stop</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img22.avif"></p><h2 id="客户端测试连接"><a href="#客户端测试连接" class="headerlink" title="客户端测试连接"></a>客户端测试连接</h2><p>可以通过PostgreSQL自带的客户端工具程序psql来进行连接，这个psql指令文件位于<code>/usr/local/pgsql/bin</code>目录下，因为我们做了变量环境设置，所以可以在任何目录下直接输入psql连接PostgreSQL服务器。温馨提示：用客户端程序psql连接数据库前，要把当前Linux登陆用户从root切换到postgres用户，这个是我们创建的PostgreSQL的超级用户。</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">su - postgres</span><br><span class="line"></span><br><span class="line">psql</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img23.avif"></p><p>可以看到，已经连接上了数据库服务器。</p><h3 id="设置用户postgres密码"><a href="#设置用户postgres密码" class="headerlink" title="设置用户postgres密码"></a>设置用户postgres密码</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">postgres<span class="operator">=</span># \password</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img24.avif"></p><p>命令<code>\l</code>是显示数据库。更多的SQL操作命令可以参考PostgreSQL的官方文档。退出pgsql客户端命令是<code>\q</code>或者<code>exit</code>。</p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img25.avif"></p><h2 id="DBeaver连接测试"><a href="#DBeaver连接测试" class="headerlink" title="DBeaver连接测试"></a>DBeaver连接测试</h2><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img26.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/PostgreSQL/2024-03-07/img27.avif"></p><p>测试连接成功，PostgreSQL安装到此完毕。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/PostgreSQL/">PostgreSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/PostgreSQL/">PostgreSQL</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/03/07/7256ce63/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>物化视图（Materialized view）详解</title>
      <link>https://blog.eucalyptus.cc/2024/01/29/51160aff/</link>
      <guid>https://blog.eucalyptus.cc/2024/01/29/51160aff/</guid>
      <pubDate>Mon, 29 Jan 2024 05:53:03 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是物化视图&quot;&gt;&lt;a href=&quot;#什么是物化视图&quot; class=&quot;headerlink&quot; title=&quot;什么是物化视图&quot;&gt;&lt;/a&gt;什么是物化视图&lt;/h2&gt;&lt;p&gt;物化视图 Materialized View</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是物化视图"><a href="#什么是物化视图" class="headerlink" title="什么是物化视图"></a>什么是物化视图</h2><p>物化视图 Materialized View 是一种预先计算和存储的查询结果,类似于数据库中的表。与普通视图不同,物化视图在创建时会将查询的结果物理存储在内存或磁盘上,而不是在查询时动态计算。</p><h2 id="物化视图与视图的区别"><a href="#物化视图与视图的区别" class="headerlink" title="物化视图与视图的区别"></a>物化视图与视图的区别</h2><ul><li>视图是虚拟的,逻辑存在的,只有定义没有存储数据;</li><li>物化视图是真实的,物理存在的,里面存储着预计算的数据;</li><li>视图的目的是简化降低查询的复杂度,而物化视图的目的是提高查询性能。</li></ul><h2 id="物化视图语法"><a href="#物化视图语法" class="headerlink" title="物化视图语法"></a>物化视图语法</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> materialized <span class="keyword">view</span> view_name</span><br><span class="line">[refresh &#123;fast <span class="operator">|</span> complete <span class="operator">|</span> force &#125; &#123;<span class="keyword">start</span> <span class="keyword">with</span> date_exp]</span><br><span class="line">[next expr] <span class="operator">|</span> <span class="keyword">on</span> demand&#125;]</span><br><span class="line">[enable query rewrite]</span><br><span class="line"><span class="keyword">as</span> <span class="keyword">select</span> <span class="keyword">select</span> columns1,columns2 <span class="keyword">from</span> table_name <span class="keyword">where</span> <span class="keyword">condition</span></span><br><span class="line">[<span class="keyword">with</span> [<span class="keyword">cascaded</span> <span class="operator">|</span> <span class="keyword">local</span>] <span class="keyword">check</span> option];</span><br></pre></td></tr></table></figure><ul><li>create materialized view 是创建物化视图的关键字</li><li>view_name是创建物化视图的名字</li><li>refresh是指定物化视图的刷新方式,刷新方式包括 【<strong>fast</strong>表示只刷新需要更新的数据】【<strong>complete</strong>表示重新计算整个物化视图】【<strong>force</strong>表示根据实际需要选择刷新方式】【<strong>on demand</strong>表示手动触发刷新】</li><li>start with 表示物化视图第一次刷新的时间点 可以是一个日期表达式 date_exp), 例如 <em>TO_DATE(‘2022-01-01’, ‘YYYY-MM-DD’)</em></li><li>next表示下一次刷新的时间间隔 可以是一个字面量表达式或数值表达式 expr ,例如** <em><strong>‘SYSDATE 1’</strong></em> **表示每隔一天刷新一次</li><li>enable query rewrite是一个可选项 用于启用查询重写功能 以便优化查询性能</li><li>[with [cascaded | local] check option]是可选项 【用于指定检查约束条件 **cascaded **表示检查约束应用于基础表和物化视图 】【<strong>local</strong>表示检查约束条件是否满足物化视图】</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/01/29/51160aff/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>REPLACE INTO</title>
      <link>https://blog.eucalyptus.cc/2024/01/16/d6843b40/</link>
      <guid>https://blog.eucalyptus.cc/2024/01/16/d6843b40/</guid>
      <pubDate>Tue, 16 Jan 2024 02:43:27 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;简介&quot;&gt;&lt;a href=&quot;#简介&quot; class=&quot;headerlink&quot; title=&quot;简介&quot;&gt;&lt;/a&gt;简介&lt;/h2&gt;&lt;p&gt;在数据库中,REPLACE INTO 是一种用于插入或更新数据的 DML SQL 语句。它与 INSERT INTO</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="简介"><a href="#简介" class="headerlink" title="简介"></a>简介</h2><p>在数据库中,REPLACE INTO 是一种用于插入或更新数据的 DML SQL 语句。它与 INSERT INTO 语句类似,但具有一些特殊的行为。</p><h2 id="语法"><a href="#语法" class="headerlink" title="语法"></a>语法</h2><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">REPLACE INTO table_name (column1, column2, ...)</span><br><span class="line">VALUES (value1, value2, ...);</span><br></pre></td></tr></table></figure><h2 id="replace-into在binlog中的表现形式"><a href="#replace-into在binlog中的表现形式" class="headerlink" title="replace into在binlog中的表现形式"></a>replace into在binlog中的表现形式</h2><h3 id="表中只有PK-primary-key"><a href="#表中只有PK-primary-key" class="headerlink" title="表中只有PK primary key"></a>表中只有PK primary key</h3><p>PK冲突 binlog update</p><p>PK不冲突 binlog insert</p><h3 id="表中PK-primary-key-和UK-unikue-key-共存"><a href="#表中PK-primary-key-和UK-unikue-key-共存" class="headerlink" title="表中PK primary key 和UK unikue key 共存"></a>表中PK primary key 和UK unikue key 共存</h3><p>PK冲突 UK不冲突 binlog delete insert</p><p>PK不冲突 UK冲突 binlog update</p><p>PK冲突 UK冲突 binlog delete insert</p><p>PK不冲突 UK不冲突 binlog (insert)</p><h2 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h2><ul><li>插入数据的表必须有主键或者是唯一索引,否则的话,replace into 会直接插入数据,这将导致表中出现重复的数据;</li><li>如果数据库里边有这条记录,则直接修改这条记录;如果没有则,则直接插入,在有外键的情况下,对主表进行这样操作时,因为如果主表存在一条记录,被从表所用时,直接使用replace into是会报错的,这和replace into的内部原理是相关 先删除然后再插入 ;</li><li>频繁的REPLACE INTO 会造成新纪录的主键的值迅速增大。总有一天。达到最大值后就会因为数据太大溢出了。就没法再插入新纪录了。数据表满了,不是因为空间不够了,而是因为主键的值没法再增加了;</li><li>replace操作在自增主键的情况下 表中有自增主键时 ,某些情况冲突时执行的是delete insert,但是在记录binlog时,却记录成了update操作,update操作不会涉及到auto_increment的修改。备库应用了binlog之后,备库的表的auto_increment属性不变。如果主备库发生主从切换,备库变为原来的主库,写新的主库则有风险发生主键冲突。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2024/01/16/d6843b40/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>公用表达式 Common Table Expressions - CTE</title>
      <link>https://blog.eucalyptus.cc/2023/12/19/a3d6b68e/</link>
      <guid>https://blog.eucalyptus.cc/2023/12/19/a3d6b68e/</guid>
      <pubDate>Tue, 19 Dec 2023 08:48:23 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在介绍CTE之前先介绍一下子查询、派生表、临时表。&lt;/p&gt;
&lt;h2 id=&quot;子查询&quot;&gt;&lt;a href=&quot;#子查询&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在介绍CTE之前先介绍一下子查询、派生表、临时表。</p><h2 id="子查询"><a href="#子查询" class="headerlink" title="子查询"></a>子查询</h2><p>子查询是嵌套在另一个查询(如select、insert、update和delete)中的查询。子查询又称为内部查询,而包含子查询的查询称为外部查询。 子查询可以在使用表达式的任何地方使用,并且必须在括号中关闭。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img1.avif"></p><h2 id="派生表"><a href="#派生表" class="headerlink" title="派生表"></a>派生表</h2><p>派生表是从select语句返回的虚拟表。派生表类似于临时表,但是在SELECT语句中使用派生表比临时表简单得多,因为派生表没有创建临时表的步骤。派生表会在使用过后即时清除的,所以我们在简化复杂查询的时候可以考虑使用。</p><p><strong>注意:派生表和子查询通常可以互换使用,但是与子查询不同的是,派生表必须具有别名。</strong></p><h3 id="派生表语法"><a href="#派生表语法" class="headerlink" title="派生表语法"></a>派生表语法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> column_list <span class="keyword">FROM</span></span><br><span class="line">( <span class="keyword">SELECT</span> column_list <span class="keyword">FROM</span> table_1) derived_table_name <span class="comment">--派生表</span></span><br><span class="line"><span class="keyword">WHERE</span> derived_table_name.c1 <span class="operator">&gt;</span> <span class="number">0</span>;</span><br></pre></td></tr></table></figure><p><strong>注意:派生表之间不可以相互引用。例如:SELECT … FROM (SELECT … FROM …) AS d1, (SELECT … FROM d1 …) AS d2,第一个查询标记为d1,在第二个查询语句中使用d1是不允许的。</strong></p><h2 id="临时表"><a href="#临时表" class="headerlink" title="临时表"></a>临时表</h2><ul><li>临时表是一种特殊类型的表,它允许您存储一个临时结果集,可以在单个会话中多次重用。</li><li>使用CREATE TEMPORARY TABLE语句创建临时表。请注意,在CREATE和TABLE关键字之间添加TEMPORARY关键字。</li><li>当会话结束或连接终止时,MySQL会自动删除临时表。当您不再使用临时表时,也可以使用DROP TABLE语句来显式删除临时表。</li><li>一个临时表只能由创建它的客户机访问。不同的客户端可以创建具有相同名称的临时表,而不会导致错误,因为只有创建临时表的客户端才能看到它。 但是,在同一个会话中,两个临时表不能共享相同的名称。</li><li>临时表可以与数据库中的普通表具有相同的名称。 不推荐使用相同名称。例如,如果在示例数据库(yiibaidb)中创建一个名为employees的临时表,则现有的employees表将变得无法访问。 对employees表发出的每个查询现在都是指employees临时表。 当删除您临时表时,永久employees表可以再次访问。</li></ul><h3 id="临时表语法"><a href="#临时表语法" class="headerlink" title="临时表语法"></a>临时表语法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#创建临时表</span><br><span class="line"><span class="keyword">CREATE</span> TEMPORARY <span class="keyword">TABLE</span> table_name (</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">10</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line"><span class="keyword">value</span> <span class="type">INTEGER</span> <span class="keyword">NOT NULL</span></span><br><span class="line">);</span><br><span class="line">#删除临时表</span><br><span class="line"><span class="keyword">drop</span> temporary <span class="keyword">table</span> table_name;</span><br></pre></td></tr></table></figure><h2 id="什么是公用表达式"><a href="#什么是公用表达式" class="headerlink" title="什么是公用表达式"></a>什么是公用表达式</h2><p>MySQL 从 8.0 开始支持 WITH 语法,即:Common Table Expressions - CTE,公用表表达式。官网:<a href="https://dev.mysql.com/doc/refman/8.0/en/with.html">公用表达式</a></p><p>CTE Common Table Expression,公共表表达式 是一个命名的临时结果集,它存在于单个语句的作用域中,以后可以在该语句中多次被引用。如下查询语句的<strong>with cte as (select 1 as one, 2 as two)</strong><br>即为公共表表达式,它是一个命名的 名字叫cte 结果集,而且在该条语句中它可以被当做临时表来引用 最后的select语句引用了它 。初次接触CTE是不是感觉跟派生表子查询很像?没错 他们确实在某些方面很像,如它们都有名字、它们都在单条语句中生效。</p><h2 id="CTE语法"><a href="#CTE语法" class="headerlink" title="CTE语法"></a>CTE语法</h2><p>CTE语法属于DML</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> cte_name (column_list) <span class="keyword">as</span> (</span><br><span class="line">query</span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> cte_name;</span><br></pre></td></tr></table></figure><p><strong>查询中的列数必须与 column_list 中的列数相同。 如果省略 column_list,CTE 将使用定义 CTE 的查询的列列表。</strong></p><h2 id="CTE示例"><a href="#CTE示例" class="headerlink" title="CTE示例"></a>CTE示例</h2><p>创建测试环境:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br></pre></td><td class="code"><pre><span class="line">#创建department表</span><br><span class="line"><span class="keyword">create table</span></span><br><span class="line">department (</span><br><span class="line">id <span class="type">bigint</span> auto_increment comment <span class="string">&#x27;主键ID&#x27;</span> <span class="keyword">primary key</span>,</span><br><span class="line">dept_name <span class="type">varchar</span>(<span class="number">32</span>) <span class="keyword">not null</span> comment <span class="string">&#x27;部门名称&#x27;</span>,</span><br><span class="line">parent_id <span class="type">bigint</span> <span class="keyword">default</span> <span class="number">0</span> <span class="keyword">not null</span> comment <span class="string">&#x27;父级id&#x27;</span></span><br><span class="line">);</span><br><span class="line">#插入数据</span><br><span class="line"><span class="keyword">insert into</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">values</span></span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;总部&#x27;</span>, <span class="number">0</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;研发部&#x27;</span>, <span class="number">1</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;测试部&#x27;</span>, <span class="number">1</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;Java组&#x27;</span>, <span class="number">2</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;Python组&#x27;</span>, <span class="number">2</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;前端组&#x27;</span>, <span class="number">2</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;供应链测试组&#x27;</span>, <span class="number">3</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;商城测试组&#x27;</span>, <span class="number">3</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;供应链产品组&#x27;</span>, <span class="number">4</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;商城产品组&#x27;</span>, <span class="number">4</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;Java1组&#x27;</span>, <span class="number">5</span>),</span><br><span class="line">(<span class="keyword">null</span>, <span class="string">&#x27;Java2组&#x27;</span>, <span class="number">5</span>);</span><br></pre></td></tr></table></figure><h3 id="基本的CTE语法"><a href="#基本的CTE语法" class="headerlink" title="基本的CTE语法"></a>基本的CTE语法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> cte1 <span class="keyword">as</span> (<span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> department <span class="keyword">where</span> id <span class="keyword">in</span> (<span class="number">1</span>, <span class="number">2</span>)),</span><br><span class="line">cte2 <span class="keyword">as</span> (<span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> department <span class="keyword">where</span> id <span class="keyword">in</span> (<span class="number">2</span>, <span class="number">3</span>))</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">cte1</span><br><span class="line"><span class="keyword">join</span> cte2</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">cte1.id cte2.id;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img2.avif"></p><h3 id="一个CTE引用另一个CTE"><a href="#一个CTE引用另一个CTE" class="headerlink" title="一个CTE引用另一个CTE"></a>一个CTE引用另一个CTE</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> cte1 <span class="keyword">as</span> (<span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> department <span class="keyword">where</span> id <span class="number">1</span>),</span><br><span class="line">cte2 <span class="keyword">as</span> (<span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> cte1)</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span> cte2;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img3.avif"></p><h2 id="递归CTE"><a href="#递归CTE" class="headerlink" title="递归CTE"></a>递归CTE</h2><h3 id="什么是递归CTE"><a href="#什么是递归CTE" class="headerlink" title="什么是递归CTE"></a>什么是递归CTE</h3><p>RCTE Recursive Common Table Expressions,递归公共表表达式 是一种会引用自身的CTE,一般用于生成序列、遍历层次数据结构。下面看一个生成1至10的序列样例。RCTE有如下几个特点:</p><ul><li>必须使用with recursive定义,否则报错<strong>ERROR 1146 (42S02): Table ‘[db_name].[cte_name]’ doesn’t exist</strong></li><li>as后面定义的语句必须用小括号括起来</li><li>小括号中的查询语句包含两个select子句,两个select子句使用<strong>union all</strong>或者<strong>union distinct</strong>连接。第一个select的查询结果集作为初始数据集;第二个select是循环迭代部分</li></ul><h3 id="RCTE语法"><a href="#RCTE语法" class="headerlink" title="RCTE语法"></a>RCTE语法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> <span class="keyword">recursive</span> cte_name <span class="keyword">as</span> (</span><br><span class="line">initial_query <span class="comment">-- anchor member</span></span><br><span class="line"><span class="keyword">union</span> <span class="keyword">all</span></span><br><span class="line">recursive_query <span class="comment">-- recursive member that references to the cte name</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> cte_name;</span><br></pre></td></tr></table></figure><h2 id="递归CTE由三个主要部分组成"><a href="#递归CTE由三个主要部分组成" class="headerlink" title="递归CTE由三个主要部分组成"></a>递归CTE由三个主要部分组成</h2><ul><li>形成 CTE 结构的基本结果集的初始查询 initial_query ,初始查询部分被称为锚成员;</li><li>递归查询部分是引用 CTE 名称的查询,因此称为递归成员。递归成员由一个 union all 或 union distinct 运算符与锚成员相连;</li><li>终止条件是当递归成员没有返回任何行时,确保递归停止。</li></ul><h3 id="递归CTE执行顺序"><a href="#递归CTE执行顺序" class="headerlink" title="递归CTE执行顺序"></a>递归CTE执行顺序</h3><ul><li>首先,将成员分为两个:锚点和递归成员。</li><li>接下来,执行锚成员形成基本结果集 R0 ,并使用该基本结果集进行下一次迭代。</li><li>然后,将 Ri 结果集作为输入执行递归成员,并将 Ri 1 作为输出。</li><li>之后,重复第三步,直到递归成员返回一个空结果集,换句话说,满足终止条件。</li><li>最后,使用 union all 运算符将结果集从 R0 到 Rn 组合。</li></ul><h3 id="递归成员限制"><a href="#递归成员限制" class="headerlink" title="递归成员限制"></a>递归成员限制</h3><ul><li>聚合函数,如 max、min、sum、avg、count 等。</li><li>group by 子句</li><li>order by 子句</li><li>limit 子句</li><li>distinct</li></ul><p><strong>上述约束不适用于锚点成员。 另外,只有在使用 union 运算符时,要禁止 distinct 才适用。 如果使用 union distinct 运算符,则允许使用 distinct。</strong></p><h3 id="递归CTE示例"><a href="#递归CTE示例" class="headerlink" title="递归CTE示例"></a>递归CTE示例</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> <span class="keyword">recursive</span> cte_count (n)</span><br><span class="line"><span class="keyword">as</span> (</span><br><span class="line"><span class="keyword">select</span> <span class="number">1</span></span><br><span class="line"><span class="keyword">union</span> <span class="keyword">all</span></span><br><span class="line"><span class="keyword">select</span> n <span class="number">1</span></span><br><span class="line"><span class="keyword">from</span> cte_count</span><br><span class="line"><span class="keyword">where</span> n <span class="operator">&lt;</span> <span class="number">3</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span> n <span class="keyword">from</span> cte_count;</span><br></pre></td></tr></table></figure><p>select 1是作为基本结果集返回1的锚成员;</p><p>select n 1 from cte_count where n &lt; 3是递归成员,因为它引用了 cte_count 的 CTE 名称。递归成员中的表达式 &lt; 3 是终止条件。当 n 等于 3,递归成员将返回一个空集合,将停止递归。</p><p>下图显示了上述CTE的元素:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img4.avif"></p><p>递归CTE返回以下输出:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"> ------</span><br><span class="line">| n |</span><br><span class="line">------</span><br><span class="line">| 1 |</span><br><span class="line">| 2 |</span><br><span class="line">| 3 |</span><br><span class="line">------ </span><br></pre></td></tr></table></figure><h4 id="示例执行步骤"><a href="#示例执行步骤" class="headerlink" title="示例执行步骤"></a>示例执行步骤</h4><ul><li>首先,分离锚和递归成员;</li><li>接下来,锚定成员形成初始行 select 1,因此第一次迭代在 n 1 时产生 1 1 2;</li><li>然后,第二次迭代对第一次迭代的输出 2 进行操作,并且在 n 2 时产生 2 1 3;</li><li>之后,在第三次操作 n 3 之前,满足终止条件 n &lt;3 ,因此查询停止;</li><li>最后,使用 union all 运算符组合所有结果集 1,2 和 3。</li></ul><h3 id="使用RCTE遍历department表"><a href="#使用RCTE遍历department表" class="headerlink" title="使用RCTE遍历department表"></a>使用RCTE遍历department表</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br></pre></td><td class="code"><pre><span class="line">#查询部门id <span class="number">2</span>的所有下级部门和本级</span><br><span class="line"><span class="keyword">with</span> <span class="keyword">recursive</span></span><br><span class="line">cte_tab <span class="keyword">as</span> (</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line">id,</span><br><span class="line">dept_name,</span><br><span class="line">parent_id,</span><br><span class="line"><span class="number">1</span> <span class="keyword">as</span> level</span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="number">2</span></span><br><span class="line"><span class="keyword">union</span> <span class="keyword">all</span></span><br><span class="line"><span class="keyword">select</span></span><br><span class="line">d.id,</span><br><span class="line">d.dept_name,</span><br><span class="line">d.parent_id,</span><br><span class="line">level <span class="number">1</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">cte_tab c</span><br><span class="line"><span class="keyword">inner</span> <span class="keyword">join</span> department d <span class="keyword">on</span> c.id d.parent_id</span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">cte_tab;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img5.avif"></p><h2 id="CTE-Derived-Table"><a href="#CTE-Derived-Table" class="headerlink" title="CTE&amp;Derived Table"></a>CTE&amp;Derived Table</h2><p>针对 from 子句里面的 subquery,MySQL 在不同版本中,是做过一系列的优化,接下来我们就来看看。</p><h3 id="5-6版本中"><a href="#5-6版本中" class="headerlink" title="5.6版本中"></a>5.6版本中</h3><p>MySQL 会对每一个 Derived Table 进行物化,生成一个临时表保存 Derived Table 的结果,然后利用临时表来完成父查询的操作,具体如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line">explain</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">(</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&lt;</span> <span class="number">1000</span></span><br><span class="line">) t1</span><br><span class="line"><span class="keyword">join</span> (</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&gt;</span> <span class="number">990</span></span><br><span class="line">) t2 <span class="keyword">on</span> t1.id t2.id;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img6.avif"></p><h3 id="5-7版本中"><a href="#5-7版本中" class="headerlink" title="5.7版本中"></a>5.7版本中</h3><p>MySQL 引入了 Derived Merge 新特性,允许符合条件的 Derived Table 中的子表与父查询的表进行合并,具体如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line">explain</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">(</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&lt;</span> <span class="number">1000</span></span><br><span class="line">) t1</span><br><span class="line"><span class="keyword">join</span> (</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&gt;</span> <span class="number">990</span></span><br><span class="line">) t2 <span class="keyword">on</span> t1.id t2.id;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img7.avif"></p><h3 id="8-0版本"><a href="#8-0版本" class="headerlink" title="8.0版本"></a>8.0版本</h3><p>我们可以使用 CTE 实现,其执行计划也是和 Derived Table 一样</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br></pre></td><td class="code"><pre><span class="line">explain</span><br><span class="line"><span class="keyword">with</span></span><br><span class="line">t1 <span class="keyword">as</span> (</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&lt;</span> <span class="number">1000</span></span><br><span class="line">),</span><br><span class="line">t2 <span class="keyword">as</span> (</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">department</span><br><span class="line"><span class="keyword">where</span></span><br><span class="line">id <span class="operator">&gt;</span> <span class="number">990</span></span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span></span><br><span class="line"><span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span></span><br><span class="line">t1</span><br><span class="line"><span class="keyword">join</span> t2 <span class="keyword">on</span> t1.id t2.id;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-19/img8.avif"></p><p>从测试结果来看,CTE 似乎是 Derived Table 的一个替代品?其实不是的,虽然 CTE 内部优化流程与 Derived Table 类似,但是两者还是区别的,具体如下:</p><ul><li>派生表在查询语句中只能引用一次,而CTE可以引用多次</li><li>CTE可以引用自身 递归</li><li>CTE可以引用其他CTE</li><li>CTE相比排查表可读性更高,CTE在语句开头定义临时结果集而不是像派生表一样嵌入到查询语句中</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/12/19/a3d6b68e/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>人机验证解决VAPTCHA</title>
      <link>https://blog.eucalyptus.cc/2023/12/14/a5bd3270/</link>
      <guid>https://blog.eucalyptus.cc/2023/12/14/a5bd3270/</guid>
      <pubDate>Thu, 14 Dec 2023 12:51:49 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、引言&quot;&gt;&lt;a href=&quot;#一、引言&quot; class=&quot;headerlink&quot; title=&quot;一、引言&quot;&gt;&lt;/a&gt;一、引言&lt;/h2&gt;&lt;p&gt;CAPTCHA 是“Completely Automated Public Turing Test* to Tell</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、引言"><a href="#一、引言" class="headerlink" title="一、引言"></a>一、引言</h2><p>CAPTCHA 是“Completely Automated Public Turing Test* to Tell Humans Apart（全自动区分计算机和人类的图灵测试）”的首字母缩写。它是指各种认证方法，这些方法利用一个对于人类来说很简单但对机器来说很难的挑战来测试用户，以验证用户是否为人类。 CAPTCHA 可防止诈骗者和垃圾邮件发送者使用机器人填写用于恶意目的的 Web 表单。</p><p>传统 CAPTCHA 要求用户阅读并正确重新输入无法通过光学字符识别 (OCR) 技术解释的失真文本。 最新的 CAPTCHA 技术使用 AI 驱动的行为和风险分析，根据活动模式（而不是单个离散任务）对人类用户进行认证。</p><p>许多网站都要求用户在登录到帐户档案、提交注册表、发表评论或执行黑客可能使用机器人执行的某些其他操作之前回答 CAPTCHA 问题。 回答这种问题，即表明用户是人类，并被允许在网站上继续执行活动。</p><p>注意事项：</p><ul><li>如果你使用的主题后台有CAPTCHA的API调用接口，您直接调用即可  </li><li>如果你使用的主题后台没有CAPTCHA的API调用接口，则您需要自己部署代码然后调用CAPTCHA的API接口实现人机验证</li></ul><h2 id="二、主题有自带"><a href="#二、主题有自带" class="headerlink" title="二、主题有自带"></a>二、主题有自带</h2><h3 id="2-1、注册"><a href="#2-1、注册" class="headerlink" title="2.1、注册"></a>2.1、注册</h3><p>CAPTCHA官网：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.vaptcha.com/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.vaptcha.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.vaptcha.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">VAPTCHA 官方网站</div>            <div class="tag-link-sitename">官网</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></p><h3 id="2-2、创建验证单元"><a href="#2-2、创建验证单元" class="headerlink" title="2.2、创建验证单元"></a>2.2、创建验证单元</h3><p>完成注册后，您将能够在管理界面中生成CAPTCHA的验证ID（VID）和密钥（KEY）。随后，只需在后台的主题设置中进行相应的配置即可启用CAPTCHA功能。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-12-14/1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-12-14/2.avif"></p><h3 id="2-3、后台设置"><a href="#2-3、后台设置" class="headerlink" title="2.3、后台设置"></a>2.3、后台设置</h3><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-12-14/3.avif"></p><h2 id="三、主题没有自带"><a href="#三、主题没有自带" class="headerlink" title="三、主题没有自带"></a>三、主题没有自带</h2><h3 id="3-1、代码配置"><a href="#3-1、代码配置" class="headerlink" title="3.1、代码配置"></a>3.1、代码配置</h3><p>配置流程：</p><ul><li>创建验证单元，获取VID和Key 。点击创建。  </li><li>将<code>https://v-cn.vaptcha.com/v3.js</code>引入到你的页面。  </li><li>将 VAPTCHA 初始化到你需要的位置，具体 web 端部署请查看：Web 客户端部署。  </li><li>用户验证通过得到token，与表单数据一同提交到服务端。  </li><li>服务端得到token后，向 VAPTCHA 服务器验证token的有效性，验证通过说明此次请求有效，服务端验证流程请查看：服务端二次验证。</li></ul><p>本文不深入探讨具体的部署步骤，若需了解详细的部署流程，您请参阅 <div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.vaptcha.com/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.vaptcha.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.vaptcha.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">VAPTCHA 官方配置指南</div>            <div class="tag-link-sitename">官方文档</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>。</p><h3 id="3-2、插件"><a href="#3-2、插件" class="headerlink" title="3.2、插件"></a>3.2、插件</h3><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://pan.baidu.com/s/1sqwhLY4g8t0-0iQoPOHKJQ?pwd=kupa">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://pan.baidu.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://pan.baidu.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">VAPTCHA 插件百度网盘下载</div>            <div class="tag-link-sitename">提取码：kupa</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p>上传安装插件之后即可在后台配置</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-12-14/4.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/VAPTCHA/">VAPTCHA</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/12/14/a5bd3270/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>学SQL JOINS看这一篇文章就够了</title>
      <link>https://blog.eucalyptus.cc/2023/12/04/c9420d4b/</link>
      <guid>https://blog.eucalyptus.cc/2023/12/04/c9420d4b/</guid>
      <pubDate>Mon, 04 Dec 2023 08:04:51 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在数据库中,连接 Join 是用于将两个或多个表中的数据关联起来的操作。连接操作有多种类型,其中包括内连接和外连接。内连接的话只有一种而外连接的话有六种,当然还有一种连接叫做交叉连接。&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;内连接:join , inner</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在数据库中,连接 Join 是用于将两个或多个表中的数据关联起来的操作。连接操作有多种类型,其中包括内连接和外连接。内连接的话只有一种而外连接的话有六种,当然还有一种连接叫做交叉连接。</p><ul><li>内连接:join , inner join</li><li>外连接:left join , left outer join , right join , right outer join , union</li><li>交叉连接:cross join</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img1.avif"></p><h2 id="下面以实例进行分析"><a href="#下面以实例进行分析" class="headerlink" title="下面以实例进行分析"></a>下面以实例进行分析</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line">#首先创建两张表a和b</span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">show</span> <span class="keyword">create table</span> a\G</span><br><span class="line"><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">Table</span>: a</span><br><span class="line"><span class="keyword">Create Table</span>: <span class="keyword">CREATE TABLE</span> a (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">name <span class="type">varchar</span>(<span class="number">20</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb3</span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.01</span> sec)</span><br><span class="line"></span><br><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">show</span> <span class="keyword">create table</span> b\G</span><br><span class="line"><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">Table</span>: b</span><br><span class="line"><span class="keyword">Create Table</span>: <span class="keyword">CREATE TABLE</span> b (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">age <span class="type">int</span> <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB <span class="keyword">DEFAULT</span> CHARSET utf8mb3</span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.01</span> sec)</span><br></pre></td></tr></table></figure><p>两张表格式如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img2.avif"></p><h3 id="内连接"><a href="#内连接" class="headerlink" title="内连接"></a>内连接</h3><h4 id="inner-join-或者join-等同于inner-join"><a href="#inner-join-或者join-等同于inner-join" class="headerlink" title="inner join 或者join 等同于inner join"></a>inner join 或者join 等同于inner join</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br><span class="line"><span class="keyword">or</span></span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">inner</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img3.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img4.avif"></p><p>这种场景下得到的是满足某一条件的A,B内部的数据;正因为得到的是内部共有数据,所以连接方式称为内连接。</p><h3 id="外连接"><a href="#外连接" class="headerlink" title="外连接"></a>外连接</h3><h4 id="left-join-或者left-outer-join-等同于left-join"><a href="#left-join-或者left-outer-join-等同于left-join" class="headerlink" title="left join 或者left outer join(等同于left join)"></a>left join 或者left outer join(等同于left join)</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">left</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br><span class="line"><span class="keyword">or</span></span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">left</span> <span class="keyword">outer</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p>结果如下,TableA中B不存在的记录填充Null</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img5.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img6.avif"></p><p>这种场景下得到的是A的所有数据,和满足某一条件的B的数据。</p><h4 id="left-join-或者left-outer-join-等同于left-join-where-B-column-is-null"><a href="#left-join-或者left-outer-join-等同于left-join-where-B-column-is-null" class="headerlink" title="[ left join 或者left outer join(等同于left join) ] [ where B.column is null ]"></a>[ left join 或者left outer join(等同于left join) ] [ where B.column is null ]</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">left</span> <span class="keyword">outer</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id <span class="keyword">where</span> b.id <span class="keyword">is</span> <span class="keyword">not null</span>;</span><br></pre></td></tr></table></figure><p>结果:</p><p>left join表a的数据全部显示,匹配表b的数据也显示,而b.id再次过滤掉 表b的id为空的</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img7.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img8.avif"></p><p>这种场景下得到的是A中的所有数据减去 与B满足同一条件 的数据 ,然后得到的A剩余数据。</p><h4 id="right-join-或者right-outer-join-等同于right-join"><a href="#right-join-或者right-outer-join-等同于right-join" class="headerlink" title="right join 或者right outer join(等同于right join)"></a>right join 或者right outer join(等同于right join)</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">right</span> <span class="keyword">outer</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br><span class="line"><span class="keyword">or</span></span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">right</span> <span class="keyword">outer</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p>TableB中A不存在的记录填充Null</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img9.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img10.avif"></p><p>这种场景下得到的是B的所有数据,和满足某一条件的A的数据。</p><h4 id="right-join-或者right-outer-join-等同于right-join-where-A-column-is-null"><a href="#right-join-或者right-outer-join-等同于right-join-where-A-column-is-null" class="headerlink" title="[ right join 或者right outer join(等同于right join) ] [ where A.column is null ]"></a>[ right join 或者right outer join(等同于right join) ] [ where A.column is null ]</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">right</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id <span class="keyword">where</span> a.id <span class="keyword">is</span> <span class="keyword">not null</span>;</span><br></pre></td></tr></table></figure><p>结果:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img11.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img12.avif"></p><p>这种场景下得到的是B中的所有数据减去 与A满足同一条件 的数据“,然后得到的B剩余数据。</p><h4 id="full-join-mysql不支持-但是可以用-left-join-union-right-join代替"><a href="#full-join-mysql不支持-但是可以用-left-join-union-right-join代替" class="headerlink" title="full join mysql不支持,但是可以用 left join union right join代替"></a>full join mysql不支持,但是可以用 left join union right join代替</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">left</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id <span class="keyword">union</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">right</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p>union过后,重复的记录会合并 id为2,3,4的三条记录</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img13.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img14.avif"></p><p>这种场景下得到的是满足某一条件的公共记录,和独有的记录。</p><h4 id="full-join-is-null-mysql不支持-但是可以用-left-join-is-null-union-right-join-is-null代替"><a href="#full-join-is-null-mysql不支持-但是可以用-left-join-is-null-union-right-join-is-null代替" class="headerlink" title="full join is null mysql不支持,但是可以用 left join is null union right join is null代替"></a>full join is null mysql不支持,但是可以用 left join is null union right join is null代替</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">left</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id <span class="keyword">where</span> b.id <span class="keyword">is</span> <span class="keyword">null</span> <span class="keyword">union</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">right</span> <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id <span class="keyword">where</span> a.id <span class="keyword">is</span> <span class="keyword">null</span>;</span><br></pre></td></tr></table></figure><p>结果:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img15.avif"></p><p>应用场景:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img16.avif"></p><h3 id="交叉连接"><a href="#交叉连接" class="headerlink" title="交叉连接"></a>交叉连接</h3><h4 id="cross-join"><a href="#cross-join" class="headerlink" title="cross join"></a>cross join</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">cross</span> <span class="keyword">join</span> b;</span><br></pre></td></tr></table></figure><p>结果:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img17.avif"></p><h4 id="cross-join-where"><a href="#cross-join-where" class="headerlink" title="cross join where"></a>cross join where</h4><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">cross</span> <span class="keyword">join</span> b <span class="keyword">where</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p>这种情况下实际上实现了内连接的效果</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img18.avif"></p><h2 id="注意事项"><a href="#注意事项" class="headerlink" title="注意事项"></a>注意事项</h2><ul><li>一般cross join后面加上where条件,但是用cross join on也是被解释为cross join where 显示连接 ;</li><li>一般内连接都需要加上on限定条件,如果不加会被解释为交叉连接;</li><li>如果连接表格使用的是逗号,会被解释为交叉连接 隐式连接 。</li></ul><p>注:隐式连接 Implicit Join 会出现数据冗余和性能问题,主要是因为它使用逗号分隔表名的方式进行连接,而没有明确指定连接条件,这样就会导致以下两个问题:</p><ul><li>数据冗余问题: 隐式连接会产生笛卡尔积,即将左表的每一行与右表的每一行进行组合,然后返回所有可能的组合结果,包括那些并不符合连接条件的组合。这就会导致结果集中出现多余的数据,从而产生数据冗余的问题。</li><li>性能问题: 隐式连接的查询效率很低,因为它会处理大量的无用数据,浪费了系统资源和时间。当表a和表b的记录数都很大时,隐式连接会产生庞大的临时表,消耗大量内存和CPU资源。此外,由于没有明确指定连接条件,数据库引擎会对每一个可能组合进行比较,这会进一步降低查询效率。</li></ul><h2 id="问题分析"><a href="#问题分析" class="headerlink" title="问题分析"></a>问题分析</h2><h3 id="EXPLAIN扫描行数不同"><a href="#EXPLAIN扫描行数不同" class="headerlink" title="EXPLAIN扫描行数不同"></a>EXPLAIN扫描行数不同</h3><p>当我们使用explain执行计划,分析select * from a join b on a.id b.id;语句时会发现两张表的数据基本相同,通过唯一主键索引关联,数据是一对一的,为什么扫描的行数不同。</p><p>语法:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">explain <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> a <span class="keyword">join</span> b <span class="keyword">on</span> a.id b.id;</span><br></pre></td></tr></table></figure><p>结果:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img19.avif"></p><p>分析:</p><p>sql join执行流程</p><ul><li>从a表取出一行</li><li>从取出的这一行取出字段1,然后到表b中查找a.id b.id</li><li>取出从表b中获取到的数据,跟从表a中的数据组成一行,作为结果集的一部分</li></ul><p>explain执行计划的第一行,实际上就是表a的全表扫描,扫描行数比较大</p><p>执行计划的第二行,实际代表的是用表a去表b中查找数据,这里用到了索引,所以扫描行数是一行。</p><h3 id="SQL-JOINS执行顺序"><a href="#SQL-JOINS执行顺序" class="headerlink" title="SQL JOINS执行顺序"></a>SQL JOINS执行顺序</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img20.avif"></p><ul><li>A left join B 返回 A 表数据,附带 B 表中符合条件的数据</li><li>A left join B right join C</li><li>A left join B 假设等于结果 AB</li><li>AB left join C 返回 AB ,附带 C中符合条件的数据</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-12-04/img21.avif"></p><ul><li>A left join B 返回 A 表数据,附带 B 表中符合条件的数据</li><li>A left join B right join C</li><li>A left join B 假设等于结果 AB</li><li>AB right join C 返回 C ,附带 AB 中符合条件的数据</li></ul><p>通过上述两个sql可以看到sql join的执行顺序</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/12/04/c9420d4b/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>【MySQL】MySQL分库分表详解[通俗易懂]</title>
      <link>https://blog.eucalyptus.cc/2023/11/17/faddb3ab/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/17/faddb3ab/</guid>
      <pubDate>Fri, 17 Nov 2023 06:12:20 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>在互联网还未崛起的时代,我们的传统应用都有这样一个特点:访问量、数据量都比较小,单库单表都完全可以支撑整个业务。随着互联网的发展和用户规模的迅速扩大,对系统的要求也越来越高。因此传统的MySQL单库单表架构的性能问题就暴露出来了。而有下面几个因素会影响数据库性能:</p><h3 id="1-1-数据量"><a href="#1-1-数据量" class="headerlink" title="1.1 数据量"></a>1.1 数据量</h3><p>MySQL单库数据量在5000万以内性能比较好,超过阈值后性能会随着数据量的增大而变弱。MySQL单表数据量是500w-1000w之间性能比较好,超过1000w性能也会下降。</p><h3 id="1-2-磁盘"><a href="#1-2-磁盘" class="headerlink" title="1.2 磁盘"></a>1.2 磁盘</h3><p>因为单个服务的磁盘空间是有限制的,如果并发压力下,所有的请求都访问同一个节点,肯定会对磁盘IO造成非常大的影响。</p><h3 id="1-3-数据库连接"><a href="#1-3-数据库连接" class="headerlink" title="1.3 数据库连接"></a>1.3 数据库连接</h3><p>数据库连接是非常稀少的资源,如果一个库里既有用户、商品、订单相关的数据,当海量用户同时操作时,数据库连接就很可能成为瓶颈。</p><p>为了提升性能,所以我们必须要解决上述几个问题,那就有必要引进<strong>分库分表</strong>。</p><h2 id="二、垂直拆分-or-水平拆分"><a href="#二、垂直拆分-or-水平拆分" class="headerlink" title="二、垂直拆分 or 水平拆分?"></a>二、垂直拆分 or 水平拆分?</h2><p>[关系型数据库](<a href="https://cloud.tencent.com/product/cdb-overview?from_column">https://cloud.tencent.com/product/cdb-overview?from_column</a> 20065&amp;from 20065)本身比较容易成为系统瓶颈,单机存储容量、连接数、处理能力都有限。当单表的数据量达到1000W或100G以后,由于查询维度较多,即使添加从库、优化索引,做很多操作时性能仍下降严重。此时就要考虑对其进行切分了,切分的目的就在于减少数据库的负担,缩短查询时间。</p><p>数据库分布式核心内容无非就是<strong>数据切分 Sharding</strong>,以及切分后对数据的定位、整合。数据切分就是将数据分散存储到多个数据库中,使得单一数据库中的数据量变小,通过扩充主机的数量缓解单一数据库的性能问题,从而达到提升数据库操作性能的目的。</p><p>数据切分根据其切分类型,可以分为两种方式:<strong>垂直(纵向)切分</strong>和<strong>水平(横向)切分</strong></p><p>当我们单个库太大时,我们先要看一下是因为表太多还是数据量太大,如果是<strong>表太多</strong>,则应该将部分表进行迁移(可以按业务区分),这就是所谓的<strong>垂直切分</strong>。如果是<strong>数据量太大</strong>,则需要将表拆成更多的小表,来减少单表的数据量,这就是所谓的<strong>水平拆分</strong>。</p><h2 id="三、垂直拆分"><a href="#三、垂直拆分" class="headerlink" title="三、垂直拆分"></a>三、垂直拆分</h2><p>垂直切分常见有<strong>垂直分库</strong>和<strong>垂直分表</strong>两种。</p><h3 id="3-1-垂直分库"><a href="#3-1-垂直分库" class="headerlink" title="3.1 垂直分库"></a>3.1 垂直分库</h3><p>垂直分库针对的是一个系统中的不同业务进行拆分,比如用户一个库,商品一个库,订单一个库。 一个购物网站对外提供服务时,会同时对用户、商品、订单表进行操作。没拆分之前, 全部都是落到单一的库上的,这会让数据库的单库处理能力成为瓶颈。如果垂直分库后还是将用户、商品、订单放到同一个服务器上,只是分到了不同的库,这样虽然会减少单库的压力,但是随着用户量增大,这会让整个数据库的处理能力成为瓶颈,还有单个服务器的磁盘空间、内存也会受非常大的影响。 所以我们要将其拆分到多个服务器上,这样上面的问题都解决了,以后也不会面对单机资源问题。这种做法与”微服务治理”的做法相似,每个微服务使用单独的一个数据库。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img1.jpg"></p><h3 id="3-2-垂直分表"><a href="#3-2-垂直分表" class="headerlink" title="3.2 垂直分表"></a>3.2 垂直分表</h3><p>也就是“大表拆小表”,<strong>基于列字段</strong>进行的。一般是表中的字段较多,将不常用的, 数据较大,长度较长 比如text类型字段 的字段数据拆分到“扩展表“。一般是针对那种几百列的大表,也避免查询时,数据量太大造成的**“跨页”问题**。MySQL底层是通过<strong>数据页</strong>存储的,一条记录占用空间过大会导致跨页 <strong>页溢出</strong> ,造成额外的性能开销 IO操作变多 。另外数据库以页为单位将数据加载到内存中,而页中存储的是行数据,页大小固定,一行数据占用空间越小,页中存储的行数据就越多。这样表中字段长度较短且访问频率较高,内存能加载更多的数据,内存命中率更高,减少了磁盘IO,从而提升了数据库性能。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img2.jpg"></p><h3 id="3-3-垂直拆分的优缺点"><a href="#3-3-垂直拆分的优缺点" class="headerlink" title="3.3 垂直拆分的优缺点"></a>3.3 垂直拆分的优缺点</h3><p>优点:</p><ul><li>解决业务系统层面的耦合,业务清晰</li><li>与微服务的治理类似,也能对不同业务的数据进行分级管理、维护、监控、扩展等</li><li>高并发场景下,垂直切分一定程度的提升IO、数据库连接数、单机硬件资源的瓶颈</li></ul><p>缺点:</p><ul><li>部分表无法join,只能通过接口聚合方式解决,提升了开发的复杂度</li><li>单机的ACID被打破,需要引入分布式事务,而分布式事务处理复杂</li><li>依然存在单表数据量过大的问题 需要水平切分</li><li>靠外键去进行约束的场景会受到影响</li></ul><h2 id="四、水平拆分"><a href="#四、水平拆分" class="headerlink" title="四、水平拆分"></a>四、水平拆分</h2><p>当一个应用难以再细粒度的垂直切分,或切分后数据量行数巨大,存在单库读写、存储性能瓶颈,这时候就需要进行水平切分了。</p><p>水平切分分为<strong>库内分表</strong>和<strong>分库分表</strong>,是根据表内数据内在的逻辑关系,将同一个表按不同的条件分散到多个数据库或多个表中,每个表中只包含一部分数据,从而使得单个表的数据量变小,达到分布式的效果。如图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img3.jpg"></p><h3 id="4-1-水平分表"><a href="#4-1-水平分表" class="headerlink" title="4.1 水平分表"></a>4.1 水平分表</h3><p>和垂直分表有一点类似,不过垂直分表是基于列的,而水平分表是基于全表的。水平拆分可以大大减少单表数据量,提升查询效率。这里的水平分表指的是在一个数据库进行的<strong>库内分表</strong>。</p><p>库内分表只解决了单一表数据量过大的问题,但没有将表分布到不同机器的库上,因此对于减轻MySQL数据库的压力来说,帮助不是很大,大家还是竞争同一个物理机的CPU、内存、网络IO,最好通过分库分表来解决。</p><h3 id="4-2-水平分库分表"><a href="#4-2-水平分库分表" class="headerlink" title="4.2 水平分库分表"></a>4.2 水平分库分表</h3><p>将单张表的数据切分到多个服务器上去,每个服务器具有相同的库与表,只是表中数据集合不同。 水平分库分表能够有效的缓解单机和单库的性能瓶颈和压力,突破IO、连接数、硬件资源等的瓶颈。</p><h3 id="4-3-水平拆分的优缺点"><a href="#4-3-水平拆分的优缺点" class="headerlink" title="4.3 水平拆分的优缺点"></a>4.3 水平拆分的优缺点</h3><p>优点:</p><ul><li>不存在单库数据量过大、高并发的性能瓶颈,提升系统稳定性和负载能力</li><li>应用端改造较小,不需要拆分业务模块</li></ul><p>缺点:</p><ul><li>ACID被打破,跨分片的事务一致性难以保证</li><li>跨库的join关联查询性能较差</li><li>数据多次扩展难度和维护量极大</li><li>靠外键去进行约束的场景会受到影响</li><li>依赖单库的自增ID会受到影响</li></ul><h2 id="五、几种常用的分库分表的策略"><a href="#五、几种常用的分库分表的策略" class="headerlink" title="五、几种常用的分库分表的策略"></a>五、几种常用的分库分表的策略</h2><h3 id="5-1-根据数值范围"><a href="#5-1-根据数值范围" class="headerlink" title="5.1 根据数值范围"></a>5.1 根据数值范围</h3><p>按照时间区间或ID区间来切分。例如:按日期将不同月甚至是日的数据分散到不同的库中;将userId为1<del>9999的记录分到第一个库,10000</del>20000的分到第二个库,以此类推。某种意义上,某些系统中使用的“冷热数据分离“,将一些使用较少的历史数据迁移到其他库中,业务功能上只提供热点数据的查询,也是类似的实践。</p><p>这样的优点在于:</p><ul><li>单表大小可控</li><li>天然便于水平扩展,后期如果想对整个分片集群扩容时,只需要添加节点即可,无需对其他分片的数据进行迁移</li><li>使用分片字段进行范围查找时,连续分片可快速定位分片进行快速查询,有效避免跨分片查询的问题。</li></ul><p>缺点:</p><ul><li><strong>热点数据</strong>成为性能瓶颈。连续分片可能存在数据热点,例如按时间字段分片,有些分片存储最近时间段内的数据,可能会被频繁的读写,而有些分片存储的历史数据,则很少被查询</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img4.jpg"></p><h3 id="5-2-根据数值取模"><a href="#5-2-根据数值取模" class="headerlink" title="5.2 根据数值取模"></a>5.2 根据数值取模</h3><p>一般采用hash取模mod的切分方式,例如:将 Customer 表根据 cusno 字段切分到4个库中,余数为0的放到第一个库,余数为1的放到第二个库,以此类推。这样同一个用户的数据会分散到同一个库中,如果查询条件带有cusno字段,则可明确定位到相应库去查询。再比如说有用户表user,将其分成3个表user0,user1,user2.路由规则是对3取模,当uid 1时,对应到的是user1,uid 2时,对应的是user2.</p><p>优点:</p><ul><li>数据分片相对比较均匀,不容易出现热点和并发访问的瓶颈</li></ul><p>缺点:</p><ul><li>后期分片集群扩容时,需要迁移旧的数据 使用<strong>一致性hash算法</strong>能较好的避免这个问题 ,否则会导致历史数据失效。</li><li>容易面临跨分片查询的复杂问题。比如上例中,如果频繁用到的查询条件中不带cusno时,将会导致无法定位数据库,从而需要同时向4个库发起查询,再在内存中合并数据,取最小集返回给应用,分库反而成为拖累。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img5.jpg"></p><h3 id="5-3-根据地理位置"><a href="#5-3-根据地理位置" class="headerlink" title="5.3 根据地理位置"></a>5.3 根据地理位置</h3><p>根据地理位置,将相同地区的放到一张表中,比如华南区一个表,华北一个表。</p><h2 id="六、分库分表后带来的问题"><a href="#六、分库分表后带来的问题" class="headerlink" title="六、分库分表后带来的问题"></a>六、分库分表后带来的问题</h2><p>分库分表能有效的缓解单机和单库带来的性能瓶颈和压力,突破网络IO、硬件资源、连接数的瓶颈,同时也带来了一些问题。下面将描述这些技术挑战以及对应的解决思路。</p><h3 id="6-1-事务一致性问题"><a href="#6-1-事务一致性问题" class="headerlink" title="6.1 事务一致性问题"></a>6.1 事务一致性问题</h3><h4 id="6-1-1-分布式事务"><a href="#6-1-1-分布式事务" class="headerlink" title="6.1.1 分布式事务"></a>6.1.1 分布式事务</h4><p>当更新内容同时分布在不同库中,不可避免会带来跨库事务问题。跨分片事务也是分布式事务,没有简单的方案,一般可使用“XA协议“和“两阶段提交“处理。</p><p>分布式事务的几种解决方案:</p><ul><li>使用[分布式事务中间件](<a href="https://cloud.tencent.com/product/dtf?from_column">https://cloud.tencent.com/product/dtf?from_column</a> 20065&amp;from 20065)</li><li>使用MySQL自带的针对跨库的事务一致性方案(XA),不过性能要比单库的慢10倍左右。</li><li>能否避免掉跨库操作(比如将用户和商品放在同一个库中)</li></ul><p>分布式事务能最大限度保证了数据库操作的原子性。但在提交事务时需要协调多个节点,推后了提交事务的时间点,延长了事务的执行时间。导致事务在访问共享资源时发生冲突或死锁的概率增高。随着数据库节点的增多,这种趋势会越来越严重,从而成为系统在数据库层面上水平扩展的枷锁。</p><h4 id="6-1-2-最终一致性"><a href="#6-1-2-最终一致性" class="headerlink" title="6.1.2 最终一致性"></a>6.1.2 最终一致性</h4><p>对于那些性能要求很高,但对一致性要求不高的系统,往往不苛求系统的实时一致性,只要在允许的时间段内达到最终一致性即可,可采用事务补偿的方式。与事务在执行中发生错误后立即回滚的方式不同,<strong>事务补偿</strong>是一种事后检查补救的措施,一些常见的实现方法有:对数据进行对账检查,基于日志进行对比,定期同标准数据来源进行同步等等。事务补偿还要结合业务系统来考虑。</p><h3 id="6-2-跨节点关联查询-join-问题"><a href="#6-2-跨节点关联查询-join-问题" class="headerlink" title="6.2 跨节点关联查询 join 问题"></a>6.2 跨节点关联查询 join 问题</h3><p>切分之前,系统中很多列表和详情页所需的数据可以通过sql join来完成。而切分之后,数据可能分布在不同的节点上,此时join带来的问题就比较麻烦了,考虑到性能,尽量避免使用join查询。</p><p>解决这个问题的一些方法:</p><h4 id="6-2-1-全局表"><a href="#6-2-1-全局表" class="headerlink" title="6.2.1 全局表"></a>6.2.1 全局表</h4><p>全局表,也可看做是“数据字典表“,就是系统中所有模块都可能依赖的一些表,为了避免跨库join查询,可以将这类表在每个数据库中都保存一份。这些数据通常很少会进行修改,所以也不担心一致性的问题。</p><h4 id="6-2-2-字段冗余"><a href="#6-2-2-字段冗余" class="headerlink" title="6.2.2 字段冗余"></a>6.2.2 字段冗余</h4><p>一种典型的反范式设计,利用空间换时间,为了性能而避免join查询。例如:订单表保存userId时候,也将userName冗余保存一份,这样查询订单详情时就不需要再去查询“买家user表“了。</p><p>但这种方法适用场景也有限,比较适用于依赖字段比较少的情况。而冗余字段的数据一致性也较难保证,就像上面订单表的例子,买家修改了userName后,是否需要在历史订单中同步更新呢?这也要结合实际业务场景进行考虑。</p><h4 id="6-2-3-数据组装"><a href="#6-2-3-数据组装" class="headerlink" title="6.2.3 数据组装"></a>6.2.3 数据组装</h4><p>在系统层面,分两次查询,第一次查询的结果集中找出关联数据id,然后根据id发起第二次请求得到关联数据。最后将获得到的数据进行字段拼装。</p><h4 id="6-2-4-ER分片"><a href="#6-2-4-ER分片" class="headerlink" title="6.2.4 ER分片"></a>6.2.4 ER分片</h4><p>关系型数据库中,如果可以先确定表之间的关联关系,并将那些存在关联关系的表记录存放在同一个分片上,那么就能较好的避免跨分片join问题。在1:1或1:n的情况下,通常按照主表的ID主键切分。如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img6.jpg"></p><p>这样一来,Data Node1上面的order订单表与orderdetail订单详情表就可以通过orderId进行局部的关联查询了,Data Node2上也一样。</p><h3 id="6-3-跨节点分页、排序、函数问题"><a href="#6-3-跨节点分页、排序、函数问题" class="headerlink" title="6.3 跨节点分页、排序、函数问题"></a>6.3 跨节点分页、排序、函数问题</h3><p>跨节点多库进行查询时,会出现limit分页、order by排序等问题。分页需要按照指定字段进行排序,当排序字段就是分片字段时,通过分片规则就比较容易定位到指定的分片;当排序字段非分片字段时,就变得比较复杂了。需要先在不同的分片节点中将数据进行排序并返回,然后将不同分片返回的结果集进行汇总和再次排序,最终返回给用户。如图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img7.jpg"></p><p>上图中只是取第一页的数据,对性能影响还不是很大。但是如果取得页数很大,情况则变得复杂很多,因为各分片节点中的数据可能是随机的,为了排序的准确性,需要将所有节点的前N页数据都排序好做合并,最后再进行整体的排序,这样的操作时很耗费CPU和内存资源的,所以页数越大,系统的性能也会越差。</p><p>在使用Max、Min、Sum、Count之类的函数进行计算的时候,也需要先在每个分片上执行相应的函数,然后将各个分片的结果集进行汇总和再次计算,最终将结果返回。如图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img8.jpg"></p><p>总之，因为我们是将数据分散存储到不同的库、表里的,当我们查询指定数据列表时,数据来源于不同的子库或者子表,就必然会引发结果集合并、排序的问题。如果每次查询都需要排序、合并等操作,性能肯定会受非常大的影响。走缓存是一种解决方案。</p><h3 id="6-4-全局主键避重问题"><a href="#6-4-全局主键避重问题" class="headerlink" title="6.4 全局主键避重问题"></a>6.4 全局主键避重问题</h3><p>在分库分表环境中,由于表中数据同时存在不同数据库中,主键值平时使用的自增长将无用武之地,某个分区数据库自生成的ID无法保证全局唯一。因此需要单独设计全局主键,以避免跨库主键重复问题。有一些常见的主键生成策略:</p><h4 id="6-4-1-UUID"><a href="#6-4-1-UUID" class="headerlink" title="6.4.1 UUID"></a>6.4.1 UUID</h4><p>UUID标准形式包含32个16进制数字,分为5段,形式为8-4-4-4-12的36个字符,例如:550e8400-e29b-41d4-a716-446655440000</p><p>UUID是主键是最简单的方案,本地生成,性能高,没有网络耗时。但缺点也很明显,由于UUID非常长,会占用大量的存储空间;另外,作为主键建立索引和基于索引进行查询时都会存在性能问题,在InnoDB下,UUID的无序性会引起数据位置频繁变动。</p><h4 id="6-4-2-结合数据库维护主键ID表"><a href="#6-4-2-结合数据库维护主键ID表" class="headerlink" title="6.4.2 结合数据库维护主键ID表"></a>6.4.2 结合数据库维护主键ID表</h4><p>在数据库中建立 sequence 表:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> sequence (</span><br><span class="line">id <span class="type">bigint</span>(<span class="number">20</span>) unsigned <span class="keyword">NOT NULL</span> auto_increment,</span><br><span class="line">stub <span class="type">char</span>(<span class="number">1</span>) <span class="keyword">NOT NULL</span> <span class="keyword">default</span> <span class="string">&#x27;&#x27;</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id ),</span><br><span class="line"><span class="keyword">UNIQUE</span> KEY stub ( stub )</span><br><span class="line">) ENGINE MyISAM;</span><br></pre></td></tr></table></figure><p>复制</p><p>stub字段设置为唯一索引,同一stub值在sequence表中只有一条记录,可以同时为多张表生成全局ID。sequence表的内容,如下所示:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"> ------------------- ------</span><br><span class="line">| <span class="built_in">id</span> | stub |</span><br><span class="line">------------------- ------</span><br><span class="line">| 72157623227190423 | a |</span><br><span class="line">------------------- ------ </span><br></pre></td></tr></table></figure><p>复制</p><p>使用 MyISAM 存储引擎而不是 InnoDB,以获取更高的性能。MyISAM使用的是表级别的锁,对表的读写是串行的,所以不用担心在并发时两次读取同一个ID值。</p><p>当需要全局唯一的64位ID时,执行:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">REPLACE <span class="keyword">INTO</span> sequence (stub) <span class="keyword">VALUES</span> (<span class="string">&#x27;a&#x27;</span>);</span><br><span class="line"><span class="keyword">SELECT</span> LAST_INSERT_ID(); </span><br></pre></td></tr></table></figure><p>复制</p><p>这两条语句是Connection级别的,select last_insert_id() 必须与 replace into 在同一数据库连接下才能得到刚刚插入的新ID。</p><p>使用replace into代替insert into好处是避免了表行数过大,不需要另外定期清理。</p><p>此方案较为简单,但缺点也明显:存在单点问题,强依赖DB,当DB异常时,整个系统都不可用。配置主从可以增加可用性,但当主库挂了,主从切换时,数据一致性在特殊情况下难以保证。另外性能瓶颈限制在单台MySQL的读写性能。</p><p>flickr团队使用的一种主键生成策略,与上面的sequence表方案类似,但更好的解决了单点和性能瓶颈的问题。</p><p>这一方案的整体思想是:建立2个以上的全局ID生成的服务器,每个服务器上只部署一个数据库,每个库有一张sequence表用于记录当前全局ID。表中ID增长的步长是库的数量,起始值依次错开,这样能将ID的生成散列到各个数据库上。如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img9.jpg"></p><p>由两个数据库服务器生成ID,设置不同的auto_increment值。第一台sequence的起始值为1,每次步长增长2,另一台的sequence起始值为2,每次步长增长也是2。结果第一台生成的ID都是奇数 1, 3, 5, 7 … ,第二台生成的ID都是偶数 2, 4, 6, 8 … 。</p><p>这种方案将生成ID的压力均匀分布在两台机器上。同时提供了系统容错,第一台出现了错误,可以自动切换到第二台机器上获取ID。但有以下几个缺点:系统添加机器,水平扩展时较复杂;每次获取ID都要读写一次DB,DB的压力还是很大,只能靠堆机器来提升性能。</p><p>可以基于flickr的方案继续优化,使用批量的方式降低数据库的写压力,每次获取一段区间的ID号段,用完之后再去数据库获取,可以大大减轻数据库的压力。如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img10.jpg"></p><p>还是使用两台DB保证可用性,数据库中只存储当前的最大ID。ID生成服务每次批量拉取6个ID,先将max_id修改为5,当应用访问ID生成服务时,就不需要访问数据库,从号段缓存中依次派发0<del>5的ID。当这些ID发完后,再将max_id修改为11,下次就能派发6</del>11的ID。于是,数据库的压力降低为原来的1&#x2F;6。</p><h4 id="6-4-3-Snowflake分布式自增ID算法"><a href="#6-4-3-Snowflake分布式自增ID算法" class="headerlink" title="6.4.3 Snowflake分布式自增ID算法"></a>6.4.3 Snowflake分布式自增ID算法</h4><p>Twitter的snowflake算法解决了分布式系统生成全局ID的需求,生成64位的Long型数字,组成部分:</p><ul><li>第一位未使用</li><li>接下来41位是毫秒级时间,41位的长度可以表示69年的时间</li><li>5位datacenterId,5位workerId。10位的长度最多支持部署1024个节点</li><li>最后12位是毫秒内的计数,12位的计数顺序号支持每个节点每毫秒产生4096个ID序列</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img11.jpg"></p><p>这样的好处是:毫秒数在高位,生成的ID整体上按时间趋势递增;不依赖第三方系统,稳定性和效率较高,理论上QPS约为409.6w&#x2F;s 1000*2^12 ,并且整个分布式系统内不会产生ID碰撞;可根据自身业务灵活分配bit位。</p><p>不足就在于:强依赖机器时钟,如果时钟回拨,则可能导致生成ID重复。</p><p>综上</p><p>结合数据库和snowflake的唯一ID方案,可以参考业界较为成熟的解法:[Leaf——美团点评分布式ID生成系统](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Ftech.meituan.com%2FMT_Leaf.html),并考虑到了高可用、容灾、分布式下时钟等问题。</p><h3 id="6-5-数据迁移、扩容问题"><a href="#6-5-数据迁移、扩容问题" class="headerlink" title="6.5 数据迁移、扩容问题"></a>6.5 数据迁移、扩容问题</h3><p>当业务高速发展,面临性能和存储的瓶颈时,才会考虑分片设计,此时就不可避免的需要考虑历史数据迁移的问题。一般做法是先读出历史数据,然后按指定的分片规则再将数据写入到各个分片节点中。此外还需要根据当前的数据量和QPS,以及业务发展的速度,进行容量规划,推算出大概需要多少分片 一般建议单个分片上的单表数据量不超过1000W</p><p>如果采用数值范围分片,只需要添加节点就可以进行扩容了,不需要对分片数据迁移。如果采用的是数值取模分片,针对数据量的递增,可能需要动态的增加表,此时因为reHash有可能导致数据迁移问题,则考虑后期的扩容问题就相对比较麻烦。</p><h3 id="6-6-外键约束问题"><a href="#6-6-外键约束问题" class="headerlink" title="6.6 外键约束问题"></a>6.6 外键约束问题</h3><p>外键约束问题比较难解决,不能完全依赖数据库本身来完成之前的功能。如果需要对分库后的单表做外键约束,就需要分库后每个单库的数据是内聚的,否则就只能靠应用层的判断,容错方式了。</p><h2 id="七-什么时候考虑切分"><a href="#七-什么时候考虑切分" class="headerlink" title="七. 什么时候考虑切分"></a>七. 什么时候考虑切分</h2><p>下面讲述一下什么时候需要考虑做数据切分。</p><h3 id="7-1-能不切分尽量不要切分"><a href="#7-1-能不切分尽量不要切分" class="headerlink" title="7.1 能不切分尽量不要切分"></a>7.1 能不切分尽量不要切分</h3><p>并不是所有表都需要进行切分,主要还是看数据的增长速度。切分后会在某种程度上提升业务的复杂度,数据库除了承载数据的存储和查询外,协助业务更好的实现需求也是其重要工作之一。</p><p>不到万不得已不用轻易使用分库分表这个大招,避免“过度设计“和“过早优化“。分库分表之前,不要为分而分,先尽力去做力所能及的事情,例如:升级硬件、升级网络、读写分离、索引优化等等。当数据量达到单表的瓶颈时候,再考虑分库分表。</p><h3 id="7-2-数据量过大-正常运维影响业务访问"><a href="#7-2-数据量过大-正常运维影响业务访问" class="headerlink" title="7.2 数据量过大,正常运维影响业务访问"></a>7.2 数据量过大,正常运维影响业务访问</h3><p>这里说的运维,指:</p><ul><li>对数据库备份,如果单表太大,备份时需要大量的磁盘IO和网络IO。例如1T的数据,网络传输占50MB时候,需要20000秒才能传输完毕,整个过程的风险都是比较高的</li><li>对一个很大的表进行DDL修改时,MySQL会锁住全表,这个时间会很长,这段时间业务不能访问此表,影响很大。如果使用pt-online-schema-change,使用过程中会创建触发器和影子表,也需要很长的时间。在此操作过程中,都算为风险时间。将数据表拆分,总量减少,有助于降低这个风险。</li><li>大表会经常访问与更新,就更有可能出现锁等待。将数据切分,用空间换时间,变相降低访问压力</li></ul><h3 id="7-3-随着业务发展-需要对某些字段垂直拆分"><a href="#7-3-随着业务发展-需要对某些字段垂直拆分" class="headerlink" title="7.3 随着业务发展,需要对某些字段垂直拆分"></a>7.3 随着业务发展,需要对某些字段垂直拆分</h3><p>举个例子,假如项目一开始设计的用户表如下:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">id bigint #用户的ID</span><br><span class="line">name varchar #用户的名字</span><br><span class="line">last_login_time datetime #最近personal_info text #私人信息</span><br><span class="line">..... #其他信息字段</span><br></pre></td></tr></table></figure><p>复制</p><p>在项目初始阶段,这种设计是满足简单的业务需求的,也方便快速迭代开发。而当业务快速发展时,用户量从10w激增到10亿,用户非常的活跃,每次</p><p>personal_info 属性是更新和查询频率较低的,并且text字段占据了太多的空间。这时候,就要对此垂直拆分出 user_ext 表了。</p><h3 id="7-4-数据量快速增长"><a href="#7-4-数据量快速增长" class="headerlink" title="7.4 数据量快速增长"></a>7.4 数据量快速增长</h3><p>随着业务的快速发展,单表中的数据量会持续增长,当性能接近瓶颈时,就需要考虑水平切分,做分库分表了。此时一定要选择合适的切分规则,提前预估好数据容量</p><h3 id="7-5-安全性和可用性"><a href="#7-5-安全性和可用性" class="headerlink" title="7.5 安全性和可用性"></a>7.5 安全性和可用性</h3><p>鸡蛋不要放在一个篮子里。在业务层面上垂直切分,将不相关的业务的数据库分隔,因为每个业务的数据量、访问量都不同,不能因为一个业务把数据库搞挂而牵连到其他业务。利用垂直切分,一个数据库出现问题,只会影响到部分业务,不会使所有的业务都瘫痪。利用水平切分,当一个数据库出现问题时,不会影响到100%的用户,每个库只承担业务的一部分数据,这样整体的可用性就能提高。</p><h2 id="八、案例分析"><a href="#八、案例分析" class="headerlink" title="八、案例分析"></a>八、案例分析</h2><h3 id="8-1-用户中心业务场景"><a href="#8-1-用户中心业务场景" class="headerlink" title="8.1 用户中心业务场景"></a>8.1 用户中心业务场景</h3><p>用户中心是一个非常常见的业务,主要提供用户注册、</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">User(uid, login_name, passwd, sex, age, nickname)</span><br><span class="line">uid为用户ID, 主键</span><br><span class="line">login_name, passwd, sex, age, nickname, 用户属性</span><br></pre></td></tr></table></figure><p>复制</p><p>任何脱离业务的架构设计都是耍流氓,在进行分库分表前,需要对业务场景需求进行梳理:</p><ul><li>用户侧:前台访问,访问量较大,需要保证高可用和高一致性。主要有两类需求:<br>用户- 用户信息查询:- 运营侧:后台访问,支持运营需求,按照年龄、性别、登陆时间、注册时间等进行分页的查询。是内部系统,访问量较低,对可用性、一致性的要求不高。</li></ul><h3 id="8-2-水平切分方法"><a href="#8-2-水平切分方法" class="headerlink" title="8.2 水平切分方法"></a>8.2 水平切分方法</h3><p>当数据量越来越大时,需要对数据库进行水平切分,上文描述的切分方法有”根据数值范围”和”根据数值取模”。</p><p>“根据数值范围“:以主键uid为划分依据,按uid的范围将数据水平切分到多个数据库上。例如:user-db1存储uid范围为0<del>1000w的数据,user-db2存储uid范围为1000w</del>2000wuid数据。</p><ul><li>优点是:扩容简单,如果容量不够,只要增加新db即可。</li><li>不足是:请求量不均匀,一般新注册的用户活跃度会比较高,所以新的user-db2会比user-db1负载高,导致服务器利用率不平衡</li></ul><p>“根据数值取模“:也是以主键uid为划分依据,按uid取模的值将数据水平切分到多个数据库上。例如:user-db1存储uid取模得1的数据,user-db2存储uid取模得0的uid数据。</p><ul><li>优点是:数据量和请求量分布均均匀</li><li>不足是:扩容麻烦,当容量不够时,新增加db,需要rehash。需要考虑对数据进行平滑的迁移。</li></ul><h3 id="8-3-非uid的查询方法"><a href="#8-3-非uid的查询方法" class="headerlink" title="8.3 非uid的查询方法"></a>8.3 非uid的查询方法</h3><p>水平切分后,对于按uid查询的需求能很好的满足,可以直接路由到具体数据库。而按非uid的查询,例如login_name,就不知道具体该访问哪个库了,此时需要遍历所有库,性能会降低很多。</p><p>对于用户侧,可以采用“建立非uid属性到uid的映射关系“的方案;对于运营侧,可以采用“前台与后台分离“的方案。</p><h4 id="8-3-1-建立非uid属性到uid的映射关系"><a href="#8-3-1-建立非uid属性到uid的映射关系" class="headerlink" title="8.3.1 建立非uid属性到uid的映射关系"></a>8.3.1 建立非uid属性到uid的映射关系</h4><p>1 映射关系</p><p>例如:login_name不能直接定位到数据库,可以建立login_name→uid的映射关系,用索引表或缓存来存储。当访问login_name时,先通过映射表查询出login_name对应的uid,再通过uid定位到具体的库。</p><p>映射表只有两列,可以承载很多数据,当数据量过大时,也可以对映射表再做水平切分。这类kv格式的索引结构,可以很好的使用cache来优化查询性能,而且映射关系不会频繁变更,缓存命中率会很高。</p><p>2 基因法</p><p>分库基因:假如通过uid分库,分为8个库,采用uid%8的方式进行路由,此时是由uid的最后3bit来决定这行User数据具体落到哪个库上,那么这3bit可以看为分库基因。</p><p>上面的映射关系的方法需要额外存储映射表,按非uid字段查询时,还需要多一次数据库或cache的访问。如果想要消除多余的存储和查询,可以通过f函数取login_name的基因作为uid的分库基因。生成uid时,参考上文所述的分布式唯一ID生成方案,再加上最后3位bit值 f(login_name)。当查询login_name时,只需计算f(login_name)%8的值,就可以定位到具体的库。不过这样需要提前做好容量规划,预估未来几年的数据量需要分多少库,要预留一定bit的分库基因。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img12.jpg"></p><h4 id="8-3-2-前台与后台分离"><a href="#8-3-2-前台与后台分离" class="headerlink" title="8.3.2 前台与后台分离"></a>8.3.2 前台与后台分离</h4><p>对于用户侧,主要需求是以单行查询为主,需要建立login_name&#x2F;phone&#x2F;email到uid的映射关系,可以解决这些字段的查询问题。</p><p>而对于运营侧,很多批量分页且条件多样的查询,这类查询计算量大,返回数据量大,对数据库的性能消耗较高。此时,如果和用户侧公用同一批服务或数据库,可能因为后台的少量请求,占用大量数据库资源,而导致用户侧访问性能降低或超时。</p><p>这类业务最好采用“前台与后台分离“的方案,运营侧后台业务抽取独立的service和db,解决和前台业务系统的耦合。由于运营侧对可用性、一致性的要求不高,可以不访问实时库,而是通过binlog异步同步数据到运营库进行访问。在数据量很大的情况下,还可以使用ES搜索引擎或Hive来满足后台复杂的查询方式。</p><h2 id="九、使用分库分表中间件"><a href="#九、使用分库分表中间件" class="headerlink" title="九、使用分库分表中间件"></a>九、使用分库分表中间件</h2><p>站在巨人的肩膀上能省力很多,目前分库分表已经有一些较为成熟的开源解决方案:</p><ul><li>[sharding-jdbc 当当 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2Fshardingjdbc)</li><li>[TSharding 蘑菇街 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2Fbaihui212%2Ftsharding)</li><li>[Atlas 奇虎360 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2FQihoo360%2FAtlas)</li><li>[Cobar 阿里巴巴 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2Falibaba%2Fcobar)</li><li>[MyCAT 基于Cobar ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> http%3A%2F%2F<a href="http://www.mycat.io%2F">www.mycat.io%2F</a>)</li><li>[Oceanus 58同城 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2F58code%2FOceanus)</li><li>[Vitess 谷歌 ](<a href="https://cloud.tencent.com/developer/tools/blog-entry?target">https://cloud.tencent.com/developer/tools/blog-entry?target</a> https%3A%2F%2Fgithub.com%2Fvitessio%2Fvitess)</li></ul><p>简单介绍其中的两个中简介:</p><p>Mycat</p><p>Mycat发展到现在,适用的场景已经很丰富,而且不断有新用户给出新的创新性的方案,以下是几个典型的应用场景:</p><ul><li>单纯的读写分离,此时配置最为简单,支持读写分离,主从切换</li><li>分库分表,对于超过1000万的表进行分片,最大支持1000亿的单表分片</li><li>多租户应用,每个应用一个库,但应用程序只连接Mycat,从而不改造程序本身,实现多租户化报表系统,借助于Mycat的分表能力,处理大规模报表的统计</li><li>替代Hbase,分析大数据作为海量数据实时查询的一种简单有效方案,比如100亿条频繁查询的记录需要在3秒内查询出来结果,除了基于主键的查询,还可能存在范围查询或其他属性查询,此时Mycat可能是最简单有效的选择.</li></ul><p>Sharding-JDBC</p><p>当当网开发的简单易用、轻量级的中间件。</p><p>一些分库分表中间件的简介图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-17/img13.jpg"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/17/faddb3ab/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>全文索引&amp;amp;前缀索引</title>
      <link>https://blog.eucalyptus.cc/2023/11/10/e2396abf/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/10/e2396abf/</guid>
      <pubDate>Fri, 10 Nov 2023 07:58:08 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是全文索引&quot;&gt;&lt;a href=&quot;#什么是全文索引&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是全文索引"><a href="#什么是全文索引" class="headerlink" title="什么是全文索引?"></a>什么是全文索引?</h2><p>全文索引是一种用于支持文本数据搜索的索引类型,它可以帮助数据库系统高效地执行全文搜索操作,包括模糊匹配、关键词搜索等。在MySQL中,全文索引通常用于对文本类型的字段进行高效的搜索。</p><p>全文索引与传统的B-tree索引不同,它使用了全文搜索引擎的特定算法和数据结构来实现对文本内容的索引和搜索。全文索引不仅考虑单词的出现,还会考虑到词语的语义、词根等信息,并能够支持自然语言查询。</p><h2 id="全文索引语法"><a href="#全文索引语法" class="headerlink" title="全文索引语法"></a>全文索引语法</h2><h3 id="创建全文索引"><a href="#创建全文索引" class="headerlink" title="创建全文索引"></a>创建全文索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">#在创建表的时候创建</span><br><span class="line"><span class="keyword">create table</span> ... ,fulltext key idexname(columnname1,columnname2);</span><br><span class="line">#在变更表结构的时候创建</span><br><span class="line"><span class="keyword">alter table</span> tablename <span class="keyword">add</span> fulltext indexname(columnname);</span><br><span class="line">#在创建好表后在添加</span><br><span class="line"><span class="keyword">create</span> fulltext index indexname <span class="keyword">on</span> tablename(columnname);</span><br></pre></td></tr></table></figure><h3 id="全文索引使用方法"><a href="#全文索引使用方法" class="headerlink" title="全文索引使用方法"></a>全文索引使用方法</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> tablename <span class="keyword">where</span> <span class="keyword">match</span>(columnname) against(<span class="string">&#x27;search keywords&#x27;</span>);</span><br></pre></td></tr></table></figure><ul><li>MATCH后面括号内的字段列表指定了在哪些字段上执行全文搜索</li><li>AGAINST后面的’search keywords’是要搜索的关键词或短语。</li></ul><h2 id="全文索引解决了什么问题"><a href="#全文索引解决了什么问题" class="headerlink" title="全文索引解决了什么问题?"></a>全文索引解决了什么问题?</h2><ul><li><strong>效率问题</strong>:在传统的数据库索引中,针对文本数据的搜索通常需要扫描整个文本字段,这会导致查询速度变慢,尤其是当数据量非常大时。全文索引通过对文本数据进行分词、建立倒排索引等技术,能够快速定位到包含检索关键词的文档或记录,大大提高了查询速度和检索效率。</li><li><strong>准确性问题</strong>:传统的数据库索引只能进行精确匹配,无法应对用户输入的模糊关键词或短语。而全文索引通过处理文本数据的分词、词干提取和停用词过滤等操作,使得搜索引擎能够理解用户输入的自然语言,并进行模糊匹配和相关性评分,从而提供更加准确和全面的搜索结果。这样,用户可以通过输入自然语言的关键词或短语来进行搜索,而不仅限于精确匹配整个单词,从而提高了搜索结果的准确性和相关性。</li></ul><h2 id="全文索引失效情况"><a href="#全文索引失效情况" class="headerlink" title="全文索引失效情况"></a>全文索引失效情况</h2><ul><li><strong>高峰查询压力:</strong> 当系统面临突发的高峰查询压力时,全文索引可能无法满足实时性能需求,导致搜索延迟或超时,甚至系统崩溃。</li><li><strong>特殊字符和语言处理:</strong> 在处理特殊字符、非拉丁字母语言的全文搜索时,全文索引的分词和匹配效果可能会受到影响,需要特殊的处理和配置。</li><li><strong>大数据量和性能问题:</strong> 随着数据量的增加,全文索引可能需要占用大量的存储空间,并且搜索性能可能会下降,需要合理的优化和分区策略。</li><li><strong>复杂的查询需求:</strong> 在需要支持复杂的逻辑查询、布尔搜索、模糊查询等高级搜索需求时,全文索引可能无法提供足够的灵活性和效率,需要额外的处理和优化。</li><li><strong>数据更新频繁:</strong> 如果数据更新频繁,包括插入、删除和更新操作,全文索引的维护成本可能会变得较高,影响系统的实时性能。</li><li><strong>跨语言搜索:</strong> 在需要支持多种不同语言的跨语言搜索时,全文索引的分词和索引策略可能需要针对不同语言做特殊处理,否则可能导致搜索效果不佳。</li></ul><h2 id="什么是前缀索引"><a href="#什么是前缀索引" class="headerlink" title="什么是前缀索引"></a>什么是前缀索引</h2><p>前缀索引是数据库中一种特殊的索引类型,它不是对整个列值进行索引,而是只对列值的前缀部分进行索引。这种索引类型可以在某些特定情况下提供性能优势,并减少索引存储空间的需求。</p><h2 id="前缀索引语法"><a href="#前缀索引语法" class="headerlink" title="前缀索引语法"></a>前缀索引语法</h2><h3 id="创建前缀索引"><a href="#创建前缀索引" class="headerlink" title="创建前缀索引"></a>创建前缀索引</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> index index_name <span class="keyword">on</span> table_name(column_name(length));</span><br></pre></td></tr></table></figure><h2 id="前缀索引解决了什么问题"><a href="#前缀索引解决了什么问题" class="headerlink" title="前缀索引解决了什么问题?"></a>前缀索引解决了什么问题?</h2><ul><li><strong>快速搜索提示和自动补全:</strong> 在用户输入时,系统需要快速给出可能的匹配结果以进行搜索提示或自动补全。使用前缀索引可以高效地找到具有特定前缀的数据项,从而提供实时的、基于用户输入前缀的匹配建议。</li><li><strong>减少数据项的搜索范围:</strong> 当数据项非常庞大时,需要对可能的候选项进行快速筛选,以减少搜索的范围。前缀索引可以帮助系统高效地缩小搜索范围,从而提高搜索的效率</li><li><strong>提高响应速度:</strong> 对于需要实时响应的场景,如搜索提示和自动补全,前缀索引能够快速地返回可能的匹配结果,从而提高了系统的响应速度和用户体验。</li></ul><h2 id="前缀索引失效情况"><a href="#前缀索引失效情况" class="headerlink" title="前缀索引失效情况"></a>前缀索引失效情况</h2><ul><li><strong>短前缀匹配:</strong> 当需要匹配的前缀较短,且数据量较大时,前缀索引可能会失效。例如,在一个包含许多短字符串的数据集中,使用前缀索引可能无法提供足够的过滤效果,导致性能下降。</li><li><strong>前缀重叠:</strong> 当不同词语的前缀出现重叠时,前缀索引可能无法准确匹配。例如,如果有 apple 和 application 两个词,它们的前缀 app 就会重叠,这样就会导致前缀索引难以区分。</li><li><strong>频繁更新:</strong> 如果数据集经常变化,特别是频繁插入、删除或更新数据的情况下,维护前缀索引的成本可能会变得过高,导致索引失效。</li><li><strong>特殊字符和符号:</strong> 对于包含特殊字符、符号或者是需要考虑字符编码的文本内容,前缀索引的匹配效果可能会受到影响,因为需要考虑字符编码和分词规则。</li><li><strong>模糊查询需求:</strong> 在需要支持模糊查询、纠错或者近义词匹配的场景下,简单的前缀索引可能无法满足复杂的匹配需求。</li><li><strong>多语言支持:</strong> 当涉及多种语言的数据时,尤其是非拉丁字母的语言,前缀索引的实现可能会变得更加复杂,需要考虑不同语言的字符编码和分词规则。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/10/e2396abf/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>深入浅出MySQL语法：从基础到进阶实战解析</title>
      <link>https://blog.eucalyptus.cc/2023/11/09/7535da6f/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/09/7535da6f/</guid>
      <pubDate>Thu, 09 Nov 2023 09:29:44 GMT</pubDate>
      
        
        
          
          
      <description>&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;持续更新中….&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;前言&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;在当今这个数据驱动的时代,数据库管理系统作为信息技术领域的基石,其重要性不言而喻。而MySQL,作为全球最受欢迎的开源关系型数据库之一,凭借其强大</description>
          
        
      
      
      
      <content:encoded><![CDATA[<hr><p><strong>持续更新中….</strong></p><p><strong>前言</strong></p><p>在当今这个数据驱动的时代,数据库管理系统作为信息技术领域的基石,其重要性不言而喻。而MySQL,作为全球最受欢迎的开源关系型数据库之一,凭借其强大的性能、高度的灵活性以及广泛的应用场景,长期以来一直是开发者和数据管理员的首选工具。随着技术的飞速发展,MySQL不断进化,引入了诸多新特性与优化,以满足日益增长的数据处理需求和挑战。</p><p>本文旨在深入探讨MySQL语法的持续更新,带领读者踏上一场从基础到进阶的探索之旅。我们不仅会回顾MySQL的核心语法及其发展历程,更重要的是,将聚焦于近年来MySQL引入的重大更新与改进。这包括但不限于SQL标准的兼容性增强、性能优化、安全性的提升、以及为应对大数据和云计算环境所做的调整。</p><p>通过实例解析和最佳实践</p><p>不论是对于MySQL的老用户,还是刚刚踏入这个领域的新人,本文都力求成为一份宝贵的参考资料,帮助大家紧跟技术潮流,解锁MySQL的全部潜力。让我们一起启程,深入探索MySQL语法的广阔天地,携手应对数据管理的新挑战</p><h2 id="锁"><a href="#锁" class="headerlink" title="锁"></a>锁</h2><p>参考文章:看一遍就理解:MySQL中的锁</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line">#创建共享锁和排他锁</span><br><span class="line"><span class="keyword">select</span> ... <span class="keyword">for</span> share;<span class="operator">/</span>lock <span class="keyword">in</span> share mode;</span><br><span class="line"><span class="keyword">select</span> ... <span class="keyword">for</span> <span class="keyword">update</span>;</span><br><span class="line">#创建全局锁</span><br><span class="line">flush tables <span class="keyword">with</span> read lock;</span><br><span class="line">#创建表级锁</span><br><span class="line">lock tables tablename write;<span class="operator">/</span>read;</span><br><span class="line">#释放锁</span><br><span class="line">unlock tables;</span><br><span class="line">#查看进程中是否有锁等待</span><br><span class="line"><span class="keyword">show</span> processlist;</span><br></pre></td></tr></table></figure><hr><h2 id="索引"><a href="#索引" class="headerlink" title="索引"></a>索引</h2><p>参考文章:一篇文章让你了解MySQL中的索引</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br></pre></td><td class="code"><pre><span class="line">#创建普通索引 辅助,联合,覆盖</span><br><span class="line"><span class="keyword">alter table</span> tablename <span class="keyword">add</span> index indxname(columnname1,columnname2);</span><br><span class="line">#创建主键索引</span><br><span class="line"><span class="keyword">alter table</span> tablename <span class="keyword">add</span> <span class="keyword">primary key</span>(columnname);</span><br><span class="line">#创建唯一索引</span><br><span class="line"><span class="keyword">alter table</span> tablename <span class="keyword">add</span> <span class="keyword">UNIQUE</span>(columnname);</span><br><span class="line">#删除索引</span><br><span class="line"><span class="keyword">drop</span> index indexname <span class="keyword">on</span> tablename;</span><br><span class="line">#查看一张表中的索引</span><br><span class="line"><span class="keyword">show</span> index <span class="keyword">from</span> tablename;</span><br><span class="line">#查看<span class="keyword">select</span>语句执行的时候是否使用了索引</span><br><span class="line">explain <span class="keyword">select</span> ...;</span><br><span class="line">#以树状的方式查看<span class="keyword">sql</span>语句的执行计划</span><br><span class="line">expalin format tree select...</span><br><span class="line">#在执行一条查询语句的时候指定索引</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> table_name force<span class="operator">/</span>use index (index_name) <span class="keyword">where</span> <span class="keyword">condition</span>;</span><br><span class="line">#添加约束</span><br><span class="line"><span class="keyword">alter table</span> table_name <span class="keyword">add constraint</span> check_name (<span class="keyword">condition</span>);</span><br></pre></td></tr></table></figure><h3 id="全文索引"><a href="#全文索引" class="headerlink" title="全文索引"></a>全文索引</h3><p>参考文章:全文索引&amp;前缀索引</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">#在创建表的时候创建</span><br><span class="line"><span class="keyword">create table</span> ... ,fulltext key idexname(columnname1,columnname2);</span><br><span class="line">#在变更表结构的时候创建</span><br><span class="line"><span class="keyword">alter table</span> tablename <span class="keyword">add</span> fulltext indexname(columnname);</span><br><span class="line">#在创建好表后在添加</span><br><span class="line"><span class="keyword">create</span> fulltext index indexname <span class="keyword">on</span> tablename(columnname);</span><br><span class="line">#使用方法</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> tablename <span class="keyword">where</span> <span class="keyword">match</span>(columnname) against(<span class="string">&#x27;search keywords&#x27;</span>);</span><br></pre></td></tr></table></figure><h3 id="前缀索引"><a href="#前缀索引" class="headerlink" title="前缀索引"></a>前缀索引</h3><p> 参考文章:全文索引&amp;前缀索引</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#创建前缀索引</span><br><span class="line"><span class="keyword">create</span> index index_name <span class="keyword">on</span> table_name(column_name(length));</span><br></pre></td></tr></table></figure><hr><h2 id="事务隔离级别"><a href="#事务隔离级别" class="headerlink" title="事务隔离级别"></a>事务隔离级别</h2><p>参考文章:ACID模型</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">#开启事务,提交事务<span class="operator">/</span>回滚事务</span><br><span class="line"><span class="keyword">begin</span>;<span class="operator">/</span><span class="keyword">start</span> transaction;</span><br><span class="line"><span class="keyword">commit</span>;</span><br><span class="line"><span class="keyword">rollback</span>;</span><br><span class="line">#查看当前隔离级别</span><br><span class="line"><span class="keyword">select</span> transaction_isolation;</span><br><span class="line">#设置隔离级别<span class="operator">/</span>这里隔离级别的设置是在一个session中,如果session中断隔离级别设置也将重置</span><br><span class="line"><span class="keyword">set</span> <span class="keyword">global</span><span class="operator">/</span>session transaction isolation level (READ UNCOMMITTED<span class="operator">/</span>READ COMMITTED<span class="operator">/</span>REPEATABLE READ<span class="operator">/</span>SERIALIZABLE) ;</span><br><span class="line">#查看正在执行中的事务</span><br><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> INFORMATION_SCHEMA.INNODB_TRX <span class="keyword">WHERE</span> TRX_STATE <span class="string">&#x27;RUNNING&#x27;</span>\G</span><br></pre></td></tr></table></figure><hr><h2 id="Online-DDL"><a href="#Online-DDL" class="headerlink" title="Online DDL"></a>Online DDL</h2><p>参考文章:你知道Online DDL吗?</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> tbl_name <span class="keyword">ADD</span> <span class="keyword">COLUMN</span> col_name col_type, ALGORITHM INPLACE, LOCK <span class="keyword">NONE</span>;</span><br><span class="line">#其中的ALGORITHM有如下选择</span><br><span class="line"><span class="keyword">copy</span>、inplace、instant、<span class="keyword">default</span></span><br><span class="line">#其中的LOCK有如下选择</span><br><span class="line">SHARE、<span class="keyword">NONE</span>、EXCLUSIVE、<span class="keyword">DEFAULT</span></span><br></pre></td></tr></table></figure><hr><h2 id="表"><a href="#表" class="headerlink" title="表"></a>表</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br></pre></td><td class="code"><pre><span class="line">#查看一个表的创建语法</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">create table</span> tablename\G</span><br><span class="line">#修改表的引擎</span><br><span class="line"><span class="keyword">alter table</span> tablename engine enginename;</span><br><span class="line">#查看表的结构</span><br><span class="line"><span class="keyword">show</span> columns <span class="keyword">from</span> tablename;<span class="operator">/</span><span class="keyword">describe</span> tablename;</span><br><span class="line">#复制表(创建新表并复旧表的数据,索引不会跟着复制)</span><br><span class="line"><span class="keyword">create table</span> newtable_name engine engine_name <span class="keyword">as</span> <span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> oldtable_name;</span><br><span class="line">#查看一个表的具体信息 包括存储引擎,创建时间,索引大小...</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">table</span> status <span class="keyword">like</span> <span class="string">&#x27;table_name&#x27;</span>\G</span><br><span class="line">#删除表中的全部数据</span><br><span class="line"><span class="keyword">truncate</span> <span class="keyword">table</span> <span class="keyword">user</span>;</span><br><span class="line">#优化表的性能和空间利用,回收空间碎片</span><br><span class="line">optimize <span class="keyword">table</span> table_name;</span><br><span class="line">#检查和修复表</span><br><span class="line"><span class="keyword">check</span> <span class="keyword">table</span> table_name;</span><br><span class="line">#分析表的索引和统计信息,并根据这些信息优化查询执行计划</span><br><span class="line">analyze <span class="keyword">table</span> table_name;</span><br><span class="line">#查看表的完整字段信息</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">full</span> fields<span class="operator">/</span>columns <span class="keyword">from</span> table_name;</span><br><span class="line">#创建会话临时表</span><br><span class="line"><span class="keyword">create</span> temporary <span class="keyword">table</span> .....;</span><br></pre></td></tr></table></figure><hr><h2 id="CHECK-TABLE"><a href="#CHECK-TABLE" class="headerlink" title="CHECK TABLE"></a>CHECK TABLE</h2><p><a href="https://dev.mysql.com/doc/refman/5.7/en/check-table.html">MySQL :: MySQL 5.7 Reference Manual :: 13.7.2.2 CHECK TABLE Statement</a></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br></pre></td><td class="code"><pre><span class="line">#用于检查表是否有错误,比如数据损坏或者表结构有问题,执行期间会锁表</span><br><span class="line"><span class="keyword">CHECK</span> <span class="keyword">TABLE</span> tbl_name [, tbl_name] ... [option] ...</span><br><span class="line"></span><br><span class="line">option: &#123;</span><br><span class="line"><span class="keyword">FOR</span> UPGRADE</span><br><span class="line"><span class="operator">|</span> QUICK</span><br><span class="line"><span class="operator">|</span> FAST</span><br><span class="line"><span class="operator">|</span> MEDIUM</span><br><span class="line"><span class="operator">|</span> EXTENDED</span><br><span class="line"><span class="operator">|</span> CHANGED</span><br><span class="line">&#125;</span><br><span class="line"><span class="comment">--FOR UPGRADE: 在升级MySQL服务器之前,检查表是否兼容新版本。</span></span><br><span class="line"><span class="comment">--QUICK: 执行快速检查,这种方式不会检查表中的每一行数据,主要用于检查表结构。</span></span><br><span class="line"><span class="comment">--FAST: 在MyISAM存储引擎中等同于QUICK,在InnoDB中没有效果。</span></span><br><span class="line"><span class="comment">--EXTENDED: 执行更详细的检查,比默认检查更彻底,可能更慢。</span></span><br><span class="line"><span class="comment">--CHANGED: 仅检查自最后一次检查以来被修改过的记录。</span></span><br></pre></td></tr></table></figure><hr><h2 id="InnoDB"><a href="#InnoDB" class="headerlink" title="InnoDB"></a>InnoDB</h2><p>参考文章:InnoDB存储引擎</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">#查看InnoDB存储引擎状态</span><br><span class="line"><span class="keyword">show</span> engine innodb status\G</span><br><span class="line">#修改表的存储引擎</span><br><span class="line"><span class="keyword">alter table</span> table_name engine engine_name;</span><br><span class="line">#创建表的时候设置引擎</span><br><span class="line"><span class="keyword">create</span> ... engine engine_name;</span><br><span class="line">#查看当前数据库支持的存储引擎</span><br><span class="line"><span class="keyword">show</span> engines\G</span><br></pre></td></tr></table></figure><hr><h2 id="查看变量"><a href="#查看变量" class="headerlink" title="查看变量"></a>查看变量</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line">#查询和修改 MySQL 服务器的配置变量</span><br><span class="line"><span class="keyword">show</span> variables <span class="keyword">like</span> <span class="string">&#x27;variables_name&#x27;</span>;</span><br><span class="line">#查看服务器的状态变量以及对应的值</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">global</span> status <span class="keyword">like</span> <span class="string">&#x27;variables_name&#x27;</span>;</span><br><span class="line">#查看查询分析器是否开启</span><br><span class="line"><span class="keyword">show</span> variables <span class="keyword">like</span> <span class="string">&#x27;profiling&#x27;</span>;</span><br><span class="line">#开启查询分析器</span><br><span class="line"><span class="keyword">set</span> profiling <span class="number">1</span>;</span><br><span class="line">#查询<span class="keyword">sql</span>分析结果</span><br><span class="line"><span class="keyword">show</span> profiles;</span><br><span class="line">#查询特定语句执行详细信息</span><br><span class="line"><span class="keyword">show</span> profile <span class="keyword">for</span> query query_id;</span><br><span class="line">#查看数据库的版本</span><br><span class="line"><span class="keyword">select</span> version();</span><br></pre></td></tr></table></figure><hr><h2 id="查看二进制日志"><a href="#查看二进制日志" class="headerlink" title="查看二进制日志"></a>查看二进制日志</h2><p>参考文章:MySQL数据库日志详解</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#查看二进制日志</span><br><span class="line"><span class="keyword">show</span> binlog events <span class="keyword">in</span> <span class="string">&#x27;log_name&#x27;</span>\G</span><br><span class="line">#显示二进制日志文件列表,可以查看log_name和log_size</span><br><span class="line"><span class="keyword">show</span> <span class="type">binary</span> logs;</span><br></pre></td></tr></table></figure><hr><h2 id="单位的转换"><a href="#单位的转换" class="headerlink" title="单位的转换"></a>单位的转换</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#将字节转换为KB</span><br><span class="line"><span class="keyword">select</span> byte_size <span class="operator">/</span><span class="number">1024</span>;</span><br><span class="line">#将KB转换为字节</span><br><span class="line"><span class="keyword">select</span> KB <span class="operator">*</span> <span class="number">1024</span>;</span><br></pre></td></tr></table></figure><hr><h2 id="函数"><a href="#函数" class="headerlink" title="函数"></a>函数</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br></pre></td><td class="code"><pre><span class="line">#随机生成一个uuid</span><br><span class="line"><span class="keyword">select</span> uuid();</span><br><span class="line">#随机生成一个<span class="number">0</span><span class="operator">~</span><span class="number">1</span>之间的浮点数</span><br><span class="line"><span class="keyword">select</span> rand();</span><br><span class="line"><span class="keyword">select</span> <span class="built_in">floor</span>(rand() <span class="operator">*</span> <span class="number">100</span>);<span class="comment">--返回0~100之间的随机整数</span></span><br><span class="line">#向下取整并返回不大于给定参数的最大参数</span><br><span class="line"><span class="keyword">select</span> <span class="built_in">floor</span>(<span class="number">3</span>,<span class="number">4</span>);<span class="comment">--返回3</span></span><br><span class="line">#获取最后插入的自增ID值的<span class="keyword">SQL</span>查询语句</span><br><span class="line"><span class="keyword">select</span> last_insert_id();</span><br><span class="line">#将多个字符串连接成一个字符串</span><br><span class="line"><span class="keyword">select</span> concat(column_?) <span class="keyword">as</span> info <span class="keyword">from</span> <span class="keyword">table</span>;</span><br><span class="line">#多维数据聚合扩展语法,通常在<span class="keyword">group</span> <span class="keyword">by</span>子句中创建超级汇总行</span><br><span class="line"><span class="keyword">select</span> ... <span class="keyword">group</span> <span class="keyword">by</span> <span class="keyword">rollup</span>(column_?);</span><br><span class="line">#窗口函数<span class="operator">/</span>分析函数 窗口函数的标志是<span class="keyword">over</span>)</span><br><span class="line"><span class="keyword">function</span> (expression)</span><br><span class="line"><span class="keyword">OVER</span> (</span><br><span class="line">[ <span class="keyword">PARTITION</span> <span class="keyword">BY</span> expr_list ]</span><br><span class="line">[ <span class="keyword">ORDER</span> <span class="keyword">BY</span> order_list</span><br><span class="line">[ frame_clause ]</span><br><span class="line">]</span><br><span class="line">)</span><br><span class="line">#frame_clause语法</span><br><span class="line"><span class="keyword">ROWS</span></span><br><span class="line">&#123; UNBOUNDED PRECEDING <span class="operator">|</span> unsigned_value PRECEDING <span class="operator">|</span> <span class="keyword">CURRENT</span> <span class="type">ROW</span> &#125; <span class="operator">|</span></span><br><span class="line">&#123;<span class="keyword">BETWEEN</span></span><br><span class="line">&#123; UNBOUNDED PRECEDING <span class="operator">|</span> unsigned_value &#123; PRECEDING <span class="operator">|</span> FOLLOWING &#125; <span class="operator">|</span></span><br><span class="line"><span class="keyword">CURRENT</span> <span class="type">ROW</span>&#125;</span><br><span class="line"><span class="keyword">AND</span></span><br><span class="line">&#123; UNBOUNDED FOLLOWING <span class="operator">|</span> unsigned_value &#123; PRECEDING <span class="operator">|</span> FOLLOWING &#125; <span class="operator">|</span></span><br><span class="line"><span class="keyword">CURRENT</span> <span class="type">ROW</span> &#125;&#125;</span><br></pre></td></tr></table></figure><hr><h2 id="外键"><a href="#外键" class="headerlink" title="外键"></a>外键</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#创建表的时候创建外键</span><br><span class="line"><span class="keyword">create</span> ... <span class="keyword">constraint</span> constraint_name <span class="keyword">foreign key</span>(外键列名) <span class="keyword">references</span> 关联表名(关联列名);</span><br><span class="line">#为已有的表添加外键</span><br><span class="line"><span class="keyword">alter table</span> table_name <span class="keyword">add constraint</span> constraint_name <span class="keyword">foreign key</span>(外键列名) <span class="keyword">references</span> 关联表名(关联列名);</span><br></pre></td></tr></table></figure><hr><h2 id="CTE语法"><a href="#CTE语法" class="headerlink" title="CTE语法"></a>CTE语法</h2><p> 参考文章:Common Table Expressions - CTE</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">with</span> cte_name (column1, column2, ..., columnN) <span class="keyword">as</span> (</span><br><span class="line"><span class="keyword">select</span> expression1, expression2, ..., expressionN</span><br><span class="line"><span class="keyword">from</span> tables</span><br><span class="line"><span class="keyword">where</span> conditions</span><br><span class="line">)</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span></span><br><span class="line"><span class="keyword">from</span> cte_name;</span><br></pre></td></tr></table></figure><hr><h2 id="特殊的DML语法"><a href="#特殊的DML语法" class="headerlink" title="特殊的DML语法"></a>特殊的DML语法</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">#在发生重复键冲突时,不会报错或拒绝插入,而是执行 <span class="keyword">UPDATE</span> 操作来更新已存在的记录</span><br><span class="line"><span class="keyword">insert into</span> ... <span class="keyword">on</span> duplicate key <span class="keyword">update</span>;</span><br><span class="line">#如果表中不存在具有相同主键或唯一索引的记录,则执行插入操作,类似于 <span class="keyword">INSERT INTO</span> 语句;如果表中已经存在具有相同主键或唯一索引的记录,则先删除该记录,然后再插入新的记录,相当于先执行 <span class="keyword">DELETE</span> 操作,再执行 <span class="keyword">INSERT</span> 操作</span><br><span class="line">replace <span class="keyword">into</span> table_name (column1, column2, ...) <span class="keyword">values</span> (value1, value2, ...);</span><br><span class="line"></span><br></pre></td></tr></table></figure><hr><h2 id="视图"><a href="#视图" class="headerlink" title="视图"></a>视图</h2><p>参考文章:物化视图 Materialized view 详解</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line">#普通视图创建语法</span><br><span class="line"><span class="keyword">create</span> <span class="keyword">view</span> view_name <span class="keyword">as</span> <span class="keyword">select</span> columns1,columns2 <span class="keyword">from</span> table_name <span class="keyword">where</span> <span class="keyword">condition</span>;</span><br><span class="line">#创建物化视图语法</span><br><span class="line"><span class="keyword">create</span> materialized <span class="keyword">view</span> view_name</span><br><span class="line">[refresh &#123;fast <span class="operator">|</span> complete <span class="operator">|</span> force &#125; &#123;<span class="keyword">start</span> <span class="keyword">with</span> date_exp]</span><br><span class="line">[next expr] <span class="operator">|</span> <span class="keyword">on</span> demand&#125;]</span><br><span class="line">[enable query rewrite]</span><br><span class="line"><span class="keyword">as</span> <span class="keyword">select</span> <span class="keyword">select</span> columns1,columns2 <span class="keyword">from</span> table_name <span class="keyword">where</span> <span class="keyword">condition</span></span><br><span class="line">[<span class="keyword">with</span> [<span class="keyword">cascaded</span> <span class="operator">|</span> <span class="keyword">local</span>] <span class="keyword">check</span> option];</span><br></pre></td></tr></table></figure><hr><h2 id="存储过程"><a href="#存储过程" class="headerlink" title="存储过程"></a>存储过程</h2><p>参考文章:<a href="https://blog.51cto.com/u_13341/7517619">https://blog.51cto.com/u_13341&#x2F;7517619</a></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">#查看某个存储过程的详细创建语句</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">create</span> <span class="keyword">procedure</span> procedure_name;</span><br><span class="line">#查看所有的存储过程</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">procedure</span> status;</span><br><span class="line">#查看某个特定数据库中的存储过程</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">procedure</span> status <span class="keyword">where</span> db <span class="string">&#x27;db_name&#x27;</span>;</span><br><span class="line">#调用创建的存储过程</span><br><span class="line"><span class="keyword">call</span> <span class="keyword">procedure</span>;</span><br><span class="line">#调用存储过程中传递参数</span><br><span class="line"><span class="keyword">call</span> <span class="keyword">procedure</span>(<span class="string">&#x27;parameter1&#x27;</span>,<span class="string">&#x27;parameter2&#x27;</span>);</span><br></pre></td></tr></table></figure><hr><h2 id="触发器"><a href="#触发器" class="headerlink" title="触发器"></a>触发器</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br></pre></td><td class="code"><pre><span class="line">#创建触发器的语法,可以说触发器是实际是存储过程</span><br><span class="line">delimiter <span class="operator">/</span><span class="operator">/</span></span><br><span class="line"><span class="keyword">create</span> <span class="keyword">trigger</span> trigger_name</span><br><span class="line">trigger_time trigger_event</span><br><span class="line"><span class="keyword">on</span> table_name</span><br><span class="line"><span class="keyword">for</span> <span class="keyword">each</span> <span class="type">row</span></span><br><span class="line"><span class="keyword">begin</span></span><br><span class="line"><span class="comment">-- 触发器要执行的SQL语句</span></span><br><span class="line"><span class="comment">-- 注意:这里可以有多个SQL语句,需要使用分号隔开</span></span><br><span class="line"><span class="keyword">end</span><span class="operator">/</span><span class="operator">/</span></span><br><span class="line">delimiter ;</span><br><span class="line">trigger_name:触发器的名称,需要在数据库中唯一。</span><br><span class="line">trigger_time:触发时机,指定触发器何时执行。可选值为:</span><br><span class="line"><span class="comment">--BEFORE:在操作执行前触发。</span></span><br><span class="line"><span class="comment">--AFTER:在操作执行后触发。</span></span><br><span class="line">trigger_event:触发事件,指明哪种数据库操作会激活触发器。可选值为:</span><br><span class="line"><span class="comment">--INSERT:插入操作。</span></span><br><span class="line"><span class="comment">--UPDATE:更新操作。</span></span><br><span class="line"><span class="comment">--DELETE:删除操作。</span></span><br><span class="line">table_name:表名,即触发器监视的表。</span><br><span class="line"><span class="keyword">FOR</span> <span class="keyword">EACH</span> <span class="type">ROW</span>:表示对于受触发事件影响的每一行数据都会执行一次触发器中的代码。</span><br><span class="line"><span class="keyword">BEGIN</span> ... <span class="keyword">END</span>;:包裹触发器要执行的具体<span class="keyword">SQL</span>语句。</span><br><span class="line">#查看数据库中所有的触发器</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">trigger</span>;</span><br><span class="line">#查看指定数据库中的触发器</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">trigger</span> <span class="keyword">from</span> table_nmae;</span><br><span class="line">#根据触发器的名字直接查询</span><br><span class="line"><span class="keyword">show</span> <span class="keyword">trigger</span> <span class="keyword">like</span> <span class="string">&#x27;trigger_name_pattern&#x27;</span>;</span><br></pre></td></tr></table></figure><hr><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img1.avif"></p><p><strong>如果有什么命令不对的话望指出…..</strong></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/09/7535da6f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>你知道Online DDL吗?</title>
      <link>https://blog.eucalyptus.cc/2023/11/09/14b17fdb/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/09/14b17fdb/</guid>
      <pubDate>Thu, 09 Nov 2023 06:25:47 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;#Online%20DDL%E8%AF%AD%E6%B3%95%C2%A0&quot;&gt;Online DDL语法&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id=&quot;什么是Online-DDL&quot;&gt;&lt;a href=&quot;#什么是Online-DDL&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong><a href="#Online%20DDL%E8%AF%AD%E6%B3%95%C2%A0">Online DDL语法</a></strong></p><h2 id="什么是Online-DDL"><a href="#什么是Online-DDL" class="headerlink" title="什么是Online DDL?"></a>什么是Online DDL?</h2><p>在线DDL Online Data Definition Language 是指在数据库运行状态下执行数据定义语言 DDL 操作,例如创建、修改或删除表结构、索引等操作,而不会造成数据库的长时间锁定或无法使用。传统的DDL操作通常需要对受影响的表进行排他锁定,这可能导致其他会话无法对该表进行读写操作,从而影响了数据库的正常使用。</p><h2 id="Online-DDL解决了什么问题"><a href="#Online-DDL解决了什么问题" class="headerlink" title="Online DDL解决了什么问题?"></a>Online DDL解决了什么问题?</h2><ul><li><strong>减少系统停机时间</strong>:传统的DDL操作通常需要锁定受影响的表,这可能导致数据库在执行DDL操作期间无法对外提供服务,造成系统停机时间。在线DDL能够在不中断正常服务的情况下执行表结构的变更,从而减少系统停机时间,提高系统可用性。</li><li><strong>提高并发性能</strong>:通过在线DDL,数据库系统可以允许DDL操作与其他事务并发执行,减少对表的锁定时间,提高了数据库的并发性能,使得用户可以在不受影响的情况下继续进行数据操作。</li><li><strong>降低业务风险</strong>:在线DDL可以避免由于长时间锁定表而导致的业务中断和故障。这对于对数据库连续性和可用性要求较高的业务尤为重要,能够降低业务风险。</li><li><strong>提高管理效率</strong>: 在线DDL使得数据库管理员可以在不停机的情况下进行表结构调整,从而提高了管理效率,并且减少了对业务的影响。</li><li><strong>解决锁等待</strong>:在传统的DDL操作中,数据库通常需要对受影响的表进行排他锁定,这可能导致其他会话无法对该表进行读写操作,从而产生锁等待现象。而在线DDL可以有效解决传统DDL操作可能引发的锁等待问题。</li></ul><p>总之,通过解决上述问题,在线DDL提高了数据库系统的可用性、并发性和管理效率,使得数据库在不中断服务的情况下能够进行结构调整,适应了现代业务对数据库连续性和稳定性的要求。</p><h2 id="分类"><a href="#分类" class="headerlink" title="分类"></a>分类</h2><p>目前支持的主流算法有三种:</p><ul><li><strong>COPY</strong> —— MySQL 5.6之前非Online,都是执行这种算法</li><li><strong>INPLACE</strong> —— MySQL 5.6出现的</li><li><strong>INSTANT</strong> —— MySQL 8.0.12出现的</li></ul><p>这时就有疑问了,这么多算法头都大了</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img1.avif"></p><p>我们知道要想把一件东西放进冰箱需要三个阶段,而在DDL操作,执行时,不管何种算法,也都会经历三个阶段,准备阶段【prepare】、执行阶段【DDL】、提交阶段【commit】。不同之处是,在三个阶段中分别做了不同的处理,接下来我们仔细分析一下不同算法的这三个阶段。</p><h3 id="Copy"><a href="#Copy" class="headerlink" title="Copy"></a>Copy</h3><ul><li>Copy算法指的是创建一个新的表,将原表的数据复制到新表中,然后对新表进行结构修改,最后删除原表。这个算法的优点是修改过程中不会影响原表的读写操作,但需要较多的空间和时间。</li><li>适用场景:适用于需要做大量结构修改、或者表的大小不是特别大的情况。</li></ul><p>下面是copy算法的三个阶段</p><h4 id="准备-Prepare"><a href="#准备-Prepare" class="headerlink" title="准备 Prepare"></a>准备 Prepare</h4><ul><li>对表加元数据共享锁,读取frm元数据 此时DDL不能并发执行,DML可以并发</li><li>共享锁升级为排他锁 此时DDL,DML都不能并发执行</li><li>在server层通过create like语句,创建临时表,engine层也生成对应的ibd,frm文件 8.0之后没有.frm文件</li></ul><h4 id="执行-Execute"><a href="#执行-Execute" class="headerlink" title="执行 Execute"></a>执行 Execute</h4><ul><li>修改临时表元数据 加列</li><li>拷贝元数据到临时表【<strong>最耗时</strong>,表中的数据需要一行一行的拷贝】</li><li>删除原表及文件</li><li>重命名临时表及文件</li></ul><h4 id="提交-Commit"><a href="#提交-Commit" class="headerlink" title="提交 Commit"></a>提交 Commit</h4><ul><li>提交事务,释放锁</li></ul><h4 id="copy算法流程"><a href="#copy算法流程" class="headerlink" title="copy算法流程"></a>copy算法流程</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img2.avif"></p><h3 id="Inplace"><a href="#Inplace" class="headerlink" title="Inplace"></a>Inplace</h3><ul><li>Inplace算法指的是直接在原表上进行结构修改,不创建新表。这个算法的优点是不需要额外的存储空间,但可能会产生较大的锁、阻塞和性能开销。</li><li>适用场景:适用于对表进行小范围的结构修改、或者表的大小较大但有足够的空闲空间的情况。</li></ul><p>对于 Inplace 算法,它的核心思想是在原表上直接进行结构修改,不创建新的表。然而,在实际的数据库系统中,即使使用 Inplace 算法,也可能会需要创建临时的数据结构来完成修改操作,这些临时数据结构通常并不是完全独立的新表,而是一种用于辅助修改操作的数据结构。因此,严格意义上讲,即使使用 Inplace 算法,也可能会涉及到创建临时的数据结构。</p><h4 id="准备-Prepare-1"><a href="#准备-Prepare-1" class="headerlink" title="准备 Prepare"></a>准备 Prepare</h4><ul><li>对表加元数据共享升级锁,并升级为排他锁 此时DML不能并行</li><li>判断使用inplace算法</li><li>判断语句是”rebulid table“还是”no-rebuild“</li><li>申请row log空间,用于存放DDL执行阶段产生的DML操作。 no-rebuild不需要 【在 innodb_sort_buffer块中】</li></ul><p>那么inplace算法是如何判断是否需要rebuild table的呐?</p><p>inplace算法判断是否需要重建新表通常会考虑以下几个因素:</p><ul><li><strong>表的大小</strong>:如果表的大小较小,那么执行 Inplace 修改可能比较快速,并且不会对数据库的整体性能产生太大影响。因此,对于小型表的结构修改,通常不需要进行重建。</li><li><strong>可用空间:</strong> Inplace 算法还会考虑表的碎片化程度和可用空间大小。如果表的碎片化比较严重,或者表中有足够的连续空闲空间,那么执行 Inplace 修改可能会比较顺利,不需要重建表。</li><li><strong>修改类型</strong>:某些特定类型的结构修改可能无法通过 Inplace 算法进行处理,比如涉及到对表的物理结构有较大改动的情况。在这种情况下, Inplace 算法可能会判断需要使用重建表的方式来完成修改。</li></ul><h4 id="执行-Execute-1"><a href="#执行-Execute-1" class="headerlink" title="执行 Execute"></a>执行 Execute</h4><ul><li>释放排他锁,保留元数据共享升级锁 此时DML可以并行</li><li>扫描原表主键以及二级索引的所有数据页,生成B Tree,存储到临时文件中;【<strong>在engine扫描,最耗时</strong>】</li><li>将所有对原表的DML操作记录在日志文件row log中,并回放部分row_log</li></ul><h4 id="提交-Commit-1"><a href="#提交-Commit-1" class="headerlink" title="提交 Commit"></a>提交 Commit</h4><ul><li>升级元数据共享升级锁,产生排他锁锁表; 此时DDL不能并行</li><li>重做row log中的内容; no-rebuild不需要</li><li>重命名原表文件,将临时文件名改名为原表文件名,删除原表文件</li><li>提交事务,变更完成</li></ul><h4 id="inplace算法流程"><a href="#inplace算法流程" class="headerlink" title="inplace算法流程"></a>inplace算法流程</h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img3.avif"></p><p>注意事项:</p><ul><li>在DDL期间产生的数据,会按照正常操作一样,写入原表,记redolog、undolog、binlog,并同步到从库去执行,只是额外会记录在row log中,并且写入row log的操作本身也会记录redolog</li><li>而在提交阶段才进行row log重做,此阶段会锁表,此时主库 新表空间 row log 和从库 表空间 数据是一致的,在主库DDL操作执行完成并提交,这个DDL才会写入binlog传到从库执行,在从库执行该DDL时,这个DDL对于从库本地来讲仍然是online的,也就是在从库本地直接写入数据是不会阻塞的,也会像主库一样产生row log。</li><li>但是对于主库同步过来DML,此时会被阻塞,是offline的,DDL是排他锁的在复制线程中也是一样,所以不只会阻塞该表,而是后续所有从主库同步过来的操作 主要是在复制线程并行时会排他,同一时间只有他自己在执行 。所以大表的DDL操作,会造成同步延迟。</li></ul><hr><p>值得思考的是,虽然三个阶段 准备、执行、提交 中,有两个阶段 准备、提交 都无法进行CRUD,但实际上,整个DDL中执行阶段时间占比最长,例如30分钟的DDL,准备 提交阶段只占用1分钟的时间,剩下的29分钟都在执行,那么对于业务层来说,绝大部分时间都是能正常访问的,所以就做到了Oline DDL了。</p><p>那么当我们需要在这一分钟之内的时候插入大量的数据哪?</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img4.avif"></p><p>那我们来看一下下面的这个算法。</p><h3 id="Instant"><a href="#Instant" class="headerlink" title="Instant"></a>Instant</h3><ul><li>Instant算法是一种特殊的算法,只需修改数据字典中的元数据,无需拷贝数据也无需重建整表,同样,也无需加排他MDL锁,原表数据也不受影响。整个DDL过程几乎是瞬间完成的,也不会阻塞DML。</li><li>适用场景:适用于对表进行极小范围的结构修改、或者要求对数据库性能影响极小的情况。</li></ul><p>这个新特性是8.0.12引入的 腾讯DBA团队贡献 。执行DDL操作时,ALGORITHM选项可以不指定,这时候MySQL按照INSTANT、INPLACE、COPY的顺序自动选择合适的模式。也可以指定ALGORITHM DEFAULT,也是同样的效果。如果指定了ALGORITHM选项,但不支持的话,会直接报错。</p><p>MySQL 8.0.12 才提出的新算法,目前只支持添加列等少量操作 还不是太成熟,企业中一般都是5.6、5.7版本 ,利用 8.0 新的表结构设计,可以直接修改表的 metadata 数据,省掉了 rebuild 的过程,极大的缩短了 DDL 语句的执行时间。</p><h2 id="利用第三方工具实现Online-DDL"><a href="#利用第三方工具实现Online-DDL" class="headerlink" title="利用第三方工具实现Online DDL"></a>利用第三方工具实现Online DDL</h2><p>有一些第三方工具也可以实现 DDL 操作,最常见的是 percona 的 pt-online-schema-change 工具 简称为 pt-osc ,和 github 的 gh-ost 工具,均支持 MySQL 5.5 以上的版本。</p><h3 id="gh-ost"><a href="#gh-ost" class="headerlink" title="gh-ost"></a>gh-ost</h3><p>参考文章:[MySQL 最佳实践:gh-ost 工具使用详解](<a href="https://cloud.tencent.com/developer/article/1671012?from_column">https://cloud.tencent.com/developer/article/1671012?from_column</a> 20421&amp;from 20421)</p><h3 id="pt-osc"><a href="#pt-osc" class="headerlink" title="pt-osc"></a>pt-osc</h3><p>参考文章:<a href="https://cloud.tencent.com/developer/article/1674215">PT-OSC在线DDL变更工具使用攻略</a></p><h2 id="一些补充"><a href="#一些补充" class="headerlink" title="一些补充"></a>一些补充</h2><p>那么支持Inplace算法的DDL一定是online的吗?</p><ul><li>从概念上来说,inplace和online是两个不同维度的事</li><li>copy和inplace指的是DDL内部的执行算法,可以理解称成:copy是在server层的操作,inplace是在innodb层的操作</li><li>其实,对用户来说,关心online与否,通常至于一个问题有关:是否允许并发DML</li><li>用一句哲学经典术语:copy算法执行的DDL不是online的,inplace算法执行的DDL不一定是online的</li></ul><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><p>常用的DDL的执行方式:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img5.avif"></p><p>DDL语句使用的算法及是否允许并发DML,是否需要重建表等,可参考</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-09/img6.avif"></p><h2 id="Online-DDL语法"><a href="#Online-DDL语法" class="headerlink" title="Online DDL语法"></a>Online DDL语法</h2><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> tbl_name <span class="keyword">ADD</span> <span class="keyword">COLUMN</span> col_name col_type, ALGORITHM INPLACE, LOCK <span class="keyword">NONE</span>;</span><br></pre></td></tr></table></figure><p>其中的ALGORITHM有如下选择:</p><ul><li><strong>INPLACE</strong>:替换:直接在原表上面执行DDL的操作。</li><li><strong>COPY</strong>:复制:使用一种临时表的方式,克隆出一个临时表,在临时表上执行DDL,然后再把数据导入到临时表中,在重命名等。这期间需要多出一倍的磁盘空间来支撑这样的 操作。执行期间,表不允许DML的操作。</li><li><strong>INSTSNT</strong>:</li><li><strong>DEFAULT</strong>:默认方式,有MySQL自己选择,优先使用INPLACE的方式。</li></ul><p>其中的LOCK有如下选项:</p><ul><li><strong>SHARE</strong>:共享锁,执行DDL的表可以读,但是不可以写。</li><li><strong>NONE</strong>:没有任何限制,执行DDL的表可读可写</li><li><strong>EXCLUSIVE</strong>:排它锁,执行DDL的表不可以读,也不可以写。</li><li><strong>DEFAULT</strong>:默认值,也就是在DDL语句中不指定LOCK子句的时候使用的默认值。如果指定LOCK的值为DEFAULT,那就是交给MySQL子句去觉得锁还是不锁表。不建议使用,如果你确定你的DDL语句不会锁表,你可以不指定lock或者指定它的值为default,否则建议指定它的锁类型。</li></ul><p>执行DDL操作时,ALGORITHM选项可以不指定,这时候MySQL按照INSTANT、INPLACE、COPY的顺序自动选择合适的模式。也可以指定ALGORITHM DEFAULT,也是同样的效果。如果指定了ALGORITHM选项,但不支持的话,会直接报错。</p><p>本文章已经生成可运行项目 一键运行**</p><p>生成项目</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/09/14b17fdb/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>三分钟搞懂MySQL5.6优化&amp;索引下推</title>
      <link>https://blog.eucalyptus.cc/2023/11/08/075d3cdf/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/08/075d3cdf/</guid>
      <pubDate>Wed, 08 Nov 2023 02:14:32 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;p&gt;如果你在面试中,听到MySQL5.6”、“索引优化” 之类的词语,你就要立马get到,这个问的是“索引下推”。&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;什么是索引下推&quot;&gt;&lt;a href=&quot;#什么是索引下推&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><p>如果你在面试中,听到MySQL5.6”、“索引优化” 之类的词语,你就要立马get到,这个问的是“索引下推”。</p></blockquote><h2 id="什么是索引下推"><a href="#什么是索引下推" class="headerlink" title="什么是索引下推"></a>什么是索引下推</h2><p>索引下推(Index Condition Pushdown,简称ICP),是MySQL5.6版本的新特性,它能减少回表查询次数,提高查询效率。</p><h2 id="索引下推优化的原理"><a href="#索引下推优化的原理" class="headerlink" title="索引下推优化的原理"></a>索引下推优化的原理</h2><p>我们先简单了解一下MySQL大概的架构:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-08/img1.avif"></p><p><strong>如果现在有一个需求:检索出表中**<strong>名字是张三,而且年龄是10岁的用户</strong></strong>。那么,SQL语句是这么写的:**</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> <span class="keyword">user</span> <span class="keyword">where</span> name <span class="string">&#x27;张三&#x27;</span> <span class="keyword">and</span> age <span class="number">10</span>;</span><br></pre></td></tr></table></figure><p>假如你了解索引最左匹配原则,那么就知道这个语句在搜索索引树的时候,只能用张三,找到的第一个满足条件的记录id为1。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-08/img2.avif"></p><p>那接下来的步骤是什么呢?</p><p><strong>没有使用ICP</strong></p><p>在MySQL 5.6之前,存储引擎根据通过联合索引找到name 张三的主键id 1、4 ,逐一进行回表扫描,去聚簇索引找到完整的行记录,server层再对数据根据age 10进行筛选。</p><p>我们看一下示意图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-08/img3.avif"></p><p>可以看到需要回表两次,把我们联合索引的另一个字段age浪费了。</p><p><strong>使用ICP</strong></p><p>而MySQL 5.6 以后, 存储引擎根据 name,age 联合索引,找到name 张三,由于联合索引中包含age列,所以存储引擎直接再联合索引里按照age 10过滤。按照过滤后的数据再一一进行回表扫描。</p><p>我们看一下示意图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-08/img4.avif"></p><p>可以看到只回表了一次。</p><p>除此之外我们还可以看一下执行计划,看到Extra一列中有Using index condition 这就是用到了索引下推。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"> <span class="comment">---- ------------- ------- ------------ ------- --------------- ---------- --------- ------ ------ ---------- -----------------------</span></span><br><span class="line"><span class="operator">|</span> id <span class="operator">|</span> select_type <span class="operator">|</span> <span class="keyword">table</span> <span class="operator">|</span> partitions <span class="operator">|</span> type <span class="operator">|</span> possible_keys <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> SIMPLE <span class="operator">|</span> tuser <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">range</span> <span class="operator">|</span> na_index <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> na_index <span class="operator">|</span> <span class="number">102</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="number">2</span> <span class="operator">|</span> <span class="number">25.00</span> <span class="operator">|</span> <span class="keyword">Using</span> index <span class="keyword">condition</span> <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> na_index <span class="operator">|</span> <span class="number">102</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="number">2</span> <span class="operator">|</span> <span class="number">25.00</span> <span class="operator">|</span> <span class="keyword">Using</span> index <span class="keyword">condition</span> <span class="operator">|</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="使用索引下推的前提条件"><a href="#使用索引下推的前提条件" class="headerlink" title="使用索引下推的前提条件"></a>使用索引下推的前提条件</h2><ul><li><p>只能用于InnoDB和MyISAM存储引擎及其分区表</p></li><li><p>对于InnoDB存储引擎来说,索引下推只适用于二级索引 也叫辅助索引</p></li><li><p>只能用于range、 ref、 eq_ref、ref_or_null访问方法;</p><blockquote><p>        1.Range(范围访问):</p><p>当查询涉及范围、不等于或者某些特定的值时,MySQL可能会使用Range访问方法。典型的情况是在SQL语句中使用了比较运算符 如 &gt;、&lt;、&gt; 、&lt; 或者 BETWEEN 等操作符,这些操作需要检索一个范围内的值。</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`SELECT * FROM users WHERE age &gt; 25 AND age &lt; 35;`</span><br></pre></td></tr></table></figure><p>        2.Ref(索引查找访问):</p><p>当查询通过普通的非唯一索引进行查找时,MySQL可能会使用Ref访问方法。这通常发生在查询条件中包含了被索引列的等值匹配 情况,也就是一般的索引查找。</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`SELECT * FROM users WHERE username &#x27;john&#x27;;`</span><br></pre></td></tr></table></figure><p>        3.Eq_ref(唯一索引查找):</p><p>当查询通过唯一索引进行查找时,MySQL可能会使用Eq_ref访问方法。这种情况通常发生在查询条件中包含了主键或者唯一索引列的等值匹配 情况。</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`SELECT * FROM users WHERE id 100;`</span><br></pre></td></tr></table></figure><p>        4.Ref_or_null(索引查找或者NULL值查找):</p><p>当查询条件中包含了对索引列的等值匹配或者 NULL 值匹配时,MySQL可能会使用Ref_or_null访问方法。这种情况通常发生在索引列允许为空 NULL 的情况下。</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">`SELECT * FROM users WHERE username &#x27;alice&#x27; OR username IS NULL;`</span><br></pre></td></tr></table></figure></blockquote></li><li><p>在某些情况下,引用了子查询的条件不能下推</p><blockquote><p>当涉及到子查询的条件下推时,让我们通过一个具体的例子来说明这个概念。</p><p>假设我们有两个表:orders 订单表 和 customers 顾客表 。orders表包含了订单信息,其中包括订单号 order_id 、顾客ID customer_id 和订单金额 amount 等字段;customers表包含了顾客信息,其中包括顾客ID customer_id 、顾客姓名 customer_name 等字段。</p><p>现在,我们想要查询出所有订单金额大于某个特定顾客的平均订单金额的订单。换句话说,我们需要找出那些订单金额高于某个特定顾客平均订单金额的订单。</p><p>一种实现这个查询的方式是使用子查询:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">`SELECT *</span><br><span class="line">FROM orders</span><br><span class="line">WHERE amount &gt; (</span><br><span class="line">SELECT AVG(amount)</span><br><span class="line">FROM order</span><br><span class="line">WHERE customer_id &#x27;123&#x27;</span><br><span class="line">);`</span><br></pre></td></tr></table></figure><p>在这个查询中,子查询 SELECT AVG(amount) FROM orders WHERE customer_id ‘123’ 用于计算顾客ID为’123’的平均订单金额,然后外部查询根据这个平均金额来筛选出符合条件的订单。</p><p>然而,在这种情况下,子查询的条件无法被完全下推到数据存储引擎层执行。因为外部查询引用了子查询的结果,数据库系统需要先计算子查询的结果,然后才能将外部查询的条件应用到子查询的结果上。这可能会导致性能问题,特别是在订单表非常大的情况下。</p><p>为了优化这个查询,我们可以重写查询,将子查询的结果作为一个变量引入外部查询,从而避免对子查询的引用。或者,我们也可以考虑使用连接或其他更有效的查询方式来实现相同的逻辑,以减少对子查询的依赖,从而提高查询性能。</p><p><strong>当然一些简单的子查询也是可以进行下推的</strong></p><p>特别是对于能够被转换成连接或者关联子查询的简单子查询,数据库系统通常能够将其条件下推到数据存储引擎层执行。</p><p>例如,考虑以下简单的子查询示例:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">`SELECT *</span><br><span class="line">FROM orders</span><br><span class="line">WHERE customer_id IN</span><br><span class="line">SELECT customer_id</span><br><span class="line">FROM customers</span><br><span class="line">WHERE customer_name &#x27;Alice&#x27;</span><br><span class="line">);`</span><br></pre></td></tr></table></figure><p>在这个查询中,子查询 SELECT customer_id FROM customers WHERE customer_name ‘Alice’ 返回了顾客名为’Alice’的顾客ID列表,外部查询根据这个列表来筛选出对应顾客的订单。</p><p>对于这种简单的子查询,数据库系统通常能够将子查询的条件下推到数据存储引擎层执行,以提高查询性能。因为这种情况下,子查询可以被优化成连接操作,使得条件可以在数据存储引擎层执行,而不需要额外的计算和数据传输开销。</p><p>总的来说,对于简单的、能够被转换成连接或者关联子查询的子查询,数据库系统通常能够进行下推优化,以提高查询性能。然而,在涉及复杂逻辑或者依赖外部查询条件的子查询时,就可能会遇到条件无法下推的情况,影响查询性能。因此,在实际编写查询语句时,需要考虑查询的复杂度和优化方式,以提高查询性能。</p></blockquote></li><li><p>引用了存储函数的条件不能下推,因为存储引擎无法调用存储函数。</p><blockquote><p>当涉及存储函数时,我们可以举一个简单的例子来说明。假设我们有一个数据库中包含了订单信息的表 orders,其中包括订单号 order_id 、订单金额 amount 等字段。此外,我们在数据库中创建了一个存储函数 calculate_discount,它接受订单金额作为参数,并返回折扣金额。这个存储函数的逻辑可能是根据订单金额的不同区间来计算不同的折扣金额。</p><p>下面是一个简化的示例:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">`CREATE FUNCTION calculate_discount(amount DECIMAL) RETURNS DECIMAL</span><br><span class="line">BEGIN</span><br><span class="line">DECLARE discount DECIMAL;</span><br><span class="line">IF amount &gt; 100 THEN</span><br><span class="line">SET discount amount * 0.1; -- 10% discount for amount over 100</span><br><span class="line">ELSE</span><br><span class="line">SET discount 0;</span><br><span class="line">END IF;</span><br><span class="line">RETURN discount;</span><br><span class="line">END;`</span><br></pre></td></tr></table></figure><p>在这个例子中,calculate_discount 存储函数接受订单金额作为参数,并根据订单金额的不同情况返回对应的折扣金额。这是一个非常简单的示例,实际的存储函数可能会更复杂,包括更多的逻辑和计算。</p><p>现在,假设我们想要查询出折扣金额大于某个特定值的订单,我们可能会编写类似以下的查询:</p><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">`SELECT *</span><br><span class="line">FROM orders</span><br><span class="line">WHERE calculate_discount(amount) &gt; 5;`</span><br></pre></td></tr></table></figure><p>在这个查询中,我们在条件中使用了 calculate_discount 存储函数,来筛选出折扣金额大于5的订单。由于存储函数的计算需要在数据库引擎外部进行,数据库系统无法将这个条件下推到数据存储引擎层执行,从而可能影响查询性能。</p><p>因此,当涉及到存储函数时,需要注意查询的性能,并考虑是否有其他方式可以重写查询以避免对存储函数的依赖,或者通过其他手段来优化查询性能。</p></blockquote></li></ul><h2 id="相关系统参数"><a href="#相关系统参数" class="headerlink" title="相关系统参数"></a>相关系统参数</h2><p>索引条件下推默认是开启的,可以使用系统参数optimizer_switch来控制器是否开启。</p><p>查看默认状态:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">select</span> optimizer_switch\G</span><br><span class="line"><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span> <span class="number">1.</span> <span class="type">row</span> <span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span><span class="operator">*</span></span><br><span class="line">optimizer_switch: index_merge <span class="keyword">on</span>,index_merge_union <span class="keyword">on</span>,index_merge_sort_union <span class="keyword">on</span>,index_merge_intersection <span class="keyword">on</span>,engine_condition_pushdown <span class="keyword">on</span>,index_condition_pushdown <span class="keyword">on</span>,mrr <span class="keyword">on</span>,mrr_cost_based <span class="keyword">on</span>,block_nested_loop <span class="keyword">on</span>,batched_key_access off,materialization <span class="keyword">on</span>,semijoin <span class="keyword">on</span>,loosescan <span class="keyword">on</span>,firstmatch <span class="keyword">on</span>,duplicateweedout <span class="keyword">on</span>,subquery_materialization_cost_based <span class="keyword">on</span>,use_index_extensions <span class="keyword">on</span>,condition_fanout_filter <span class="keyword">on</span>,derived_merge <span class="keyword">on</span>,use_invisible_indexes off,skip_scan <span class="keyword">on</span>,hash_join <span class="keyword">on</span>,subquery_to_derived off,prefer_ordering_index <span class="keyword">on</span>,hypergraph_optimizer off,derived_condition_pushdown <span class="keyword">on</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span> (<span class="number">0.01</span> sec)</span><br></pre></td></tr></table></figure><p>开启和关闭索引下推</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#关闭</span><br><span class="line"><span class="keyword">set</span> optimizer_switch index_condition_pushdown off ;</span><br><span class="line">#开启</span><br><span class="line"><span class="keyword">set</span> optimizer_switch index_condition_pushdown <span class="keyword">on</span> ;</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/08/075d3cdf/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>readview的可见性算法</title>
      <link>https://blog.eucalyptus.cc/2023/11/07/43e0ee4d/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/07/43e0ee4d/</guid>
      <pubDate>Tue, 07 Nov 2023 06:17:20 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在之前的文章MVCC详解-CSDN博客中我们已经介绍过了MVCC的原理 read view undo log ,今天来详细的说一下readview的匹配规则 可见性算法&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;隔离级别在RC,RR的前提下&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Read</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在之前的文章MVCC详解-CSDN博客中我们已经介绍过了MVCC的原理 read view undo log ,今天来详细的说一下readview的匹配规则 可见性算法</p><p><strong>隔离级别在RC,RR的前提下</strong></p><p>Read View是如何保证可见性判断的呢?我们先看看Read view 的几个重要属性</p><ul><li>m_ids:当前系统中那些活跃(未提交)的读写事务ID, 它数据结构为一个List。</li><li>min_limit_id:表示在生成ReadView时,当前系统中活跃的读写事务中最小的事务id,即m_ids中的最小值。</li><li>max_limit_id:表示生成ReadView时,系统中应该分配给下一个事务的id值。</li><li>creator_trx_id: 创建当前read view的事务ID</li></ul><h2 id="可见性算法-read-view匹配规则"><a href="#可见性算法-read-view匹配规则" class="headerlink" title="**可见性算法 read view匹配规则 **"></a>**可见性算法 read view匹配规则 **</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img1.avif"></p><p>如下:</p><ul><li>如果数据事务ID trx_id &lt; min_limit_id,表明生成该版本的事务在生成Read View前,已经提交(因为事务ID是递增的),所以该版本可以被当前事务访问。</li><li>如果trx_id&gt; max_limit_id,表明生成该版本的事务在生成ReadView后才生成,所以该版本不可以被当前事务访问。</li><li>如果 min_limit_id &lt;trx_id&lt; max_limit_id,需腰分3种情况讨论</li></ul><p>                 1 .如果m_ids包含trx_id,则代表Read View生成时刻,这个事务还未提交,但是如果数据的trx_id等于creator_trx_id的话,表明数据是自己生成的,因此是<strong>可见</strong>的。</p><p>                 2 如果m_ids包含trx_id,并且trx_id不等于creator_trx_id,则Read View生成时,事务未提交,并且不是自己生产的,所以当前事务也是<strong>看不见</strong>的;</p><p>                 3 .如果m_ids不包含trx_id,则说明你这个事务在Read View生成之前就已经提交了,修改的结果,当前事务是能看见的。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/07/43e0ee4d/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL中的刷脏机制详解</title>
      <link>https://blog.eucalyptus.cc/2023/11/07/f1900617/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/07/f1900617/</guid>
      <pubDate>Tue, 07 Nov 2023 03:31:40 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;h2 id=&quot;名词解释&quot;&gt;&lt;a href=&quot;#名词解释&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><h2 id="名词解释"><a href="#名词解释" class="headerlink" title="名词解释"></a>名词解释</h2><p><strong>脏页</strong>:当内存数据页跟磁盘数据页内容不一致的时候,我们称这个内存页为“脏页”。<br><strong>干净页</strong>:内存数据写入到磁盘后,内存和磁盘上的数据页的内容就一致了,称为“干净页”。<br><strong>LSN</strong>:称为日志的逻辑序列号(log sequence number),在innodb存储引擎中,lsn占用8个字节。LSN的值会随着日志的写入而逐渐增大。事务中更新操作会产生一个新的LSN。LSN不仅存在于redo log中,还存在于数据页中。<br><strong>刷脏</strong>:刷脏 Flush 是指将内存中已被修改的数据块写回到持久化存储 如磁盘 的操作。<br><strong>write pos</strong>:write pos指的是WAL中当前用于写入日志的位置指针<br><strong>checkpoint</strong>:Checkpoint是数据库中周期性将内存中的修改数据页刷新到磁盘的操作,以确保数据库的持久化和一致性。</p></blockquote><h2 id="为什么要刷脏"><a href="#为什么要刷脏" class="headerlink" title="为什么要刷脏?"></a>为什么要刷脏?</h2><ul><li>数据持久性</li><li>数据一致性</li><li>缓存管理</li><li>保证系统性能</li></ul><h2 id="刷脏时机"><a href="#刷脏时机" class="headerlink" title="刷脏时机"></a>刷脏时机</h2><ul><li>checkpoint刷脏</li><li>空闲时刷脏</li><li>MySQL正常关闭时刷脏</li></ul><h2 id="空闲时刷脏"><a href="#空闲时刷脏" class="headerlink" title="空闲时刷脏"></a>空闲时刷脏</h2><p>MySQL会在自认为系统“空闲”的时候或者当系统更新很频繁,redo log很快就写满的情况下,合理的定时进行刷脏</p><h2 id="正常关闭时刷脏"><a href="#正常关闭时刷脏" class="headerlink" title="正常关闭时刷脏"></a>正常关闭时刷脏</h2><p>MySQL 正常关闭的情况。这时候,MySQL 会把内存的脏页都 flush 到磁盘上,这样下次 MySQL 启动的时候,就可以直接从磁盘上读数据,启动速度会很快。</p><p>如果关闭的时候不刷脏,启动的时候就需要去读redo log然后同步数据到磁盘,这样启动速度会变慢</p><h2 id="checkpoint机制"><a href="#checkpoint机制" class="headerlink" title="checkpoint机制"></a>checkpoint机制</h2><h3 id="Redo-Log可能会出现的问题"><a href="#Redo-Log可能会出现的问题" class="headerlink" title="Redo Log可能会出现的问题"></a>Redo Log可能会出现的问题</h3><ul><li>缓冲池不够用</li><li>redo log写满了</li><li>当数据库宕机时,重新应用redo log</li></ul><p>checkpoint机制可以解决上面的三个问题:</p><ul><li>缓冲池不够用时,将脏页刷新到磁盘</li><li>redo log写满时,将脏页刷新到磁盘</li><li>缩短数据库恢复时间</li></ul><h4 id="缓冲池不够用时"><a href="#缓冲池不够用时" class="headerlink" title="缓冲池不够用时"></a>缓冲池不够用时</h4><p>当缓冲池中的空间无法存放新读取的页,这个时候innodb就会进行页的淘汰。使用LRU算法,将淘汰LRU链表尾部的页,如果这个被释放的页时脏页,就要强制执行checkpoint,将脏页刷新到磁盘。</p><h4 id="缩短数据库恢复时间"><a href="#缩短数据库恢复时间" class="headerlink" title="缩短数据库恢复时间"></a>缩短数据库恢复时间</h4><p>当数据库宕机时,数据库不需要重做所有的日志,因为checkpoint之前的页都已经刷新回磁盘了。所以数据库就只需要针对checkpoint后的redo log进行恢复就可以了,这样就减少了恢复的时间。</p><h4 id="redo-log写满"><a href="#redo-log写满" class="headerlink" title="redo log写满"></a>redo log写满</h4><p>日志组的概念</p><ul><li>MySQL为了优化磁盘持久的开销,会有一个组提交 group commit 机制</li><li>每个innodb,至少有一个重做日志文件组,每个文件组下面,至少有两个redo log文件</li><li>事务日志组路径,当前目录是指的MySQL数据目录为日志组目录</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img1.avif"></p><ul><li>事务日志组中的事务文件的个数,默认两个</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img2.avif"></p><ul><li>日志组中每个重做日志的大小一致,并且循环使用。单个文件默认大小是48M,最大是512G,最大值是组内文件的大小总和</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img3.avif"></p><p>所谓的redo log不可用就是,就是所有redo file都写满的时候</p><p>InnoDB以环形方式写入数据到重做日志的:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img4.avif"></p><p>checkpoint每次刷新多少页到磁盘?每次从哪里取脏页?什么时间触发checkpoint?</p><p>InnoDB存储引擎内部,两种checkpoint,分别为:</p><ul><li>Sharp Checkpoint</li><li>Fuzzy Checkpoint</li></ul><h5 id="Sharp-Checkpoint-强制落盘"><a href="#Sharp-Checkpoint-强制落盘" class="headerlink" title="Sharp Checkpoint 强制落盘"></a>Sharp Checkpoint 强制落盘</h5><p>Sharp Checkpoint发生在数据库关闭时,将所有的脏页都刷新回磁盘,这是默认的工作方式,即参数:innodb_fast_shutdown 1。</p><p>不适用于数据库运行时的刷新。</p><h5 id="Fuzzy-Checkpoint-模糊落盘"><a href="#Fuzzy-Checkpoint-模糊落盘" class="headerlink" title="Fuzzy Checkpoint 模糊落盘"></a>Fuzzy Checkpoint 模糊落盘</h5><p>在数据库运行时,InnoDB存储引擎内部采用Fuzzy Checkpoint,只刷新一部分脏页。</p><p>几种发生Fuzzy Checkpoint的情况:<br><strong>①MasterThread Checkpoint</strong></p><p>异步刷新,每秒或每10秒从缓冲池脏页列表刷新一定比例的页回磁盘。异步刷新,即此时InnoDB存储引擎可以进行其他操作,用户查询线程不会受阻。<br><strong>②FLUSH_LRU_LIST Checkpoint</strong></p><p>BP中有脏页换出需要执行落盘</p><p>InnoDB存储引擎需要保证LRU列表中差不多有100个空闲页可供使用。在InnoDB 1.1.x版本之前,用户查询线程会检查LRU列表是否有足够的空间操作。如果没有,根据LRU算法,溢出LRU列表尾端的页,如果这些页有脏页,需要进行checkpoint。因此叫:flush_lru_list checkpoint。</p><p>InnoDB 1.2.x开始,这个检查放在了单独的进程 Page Cleaner 中进行。好处:1.减少master Thread的压力 2.减轻用户线程阻塞。</p><p>设置参数:innodb_lru_scan_dept:控制LRU列表中可用页的数量,该值默认1024<br><strong>③Async&#x2F;Sync Flush Checkpoint</strong></p><p>指重做日志不可用的情况,需要强制刷新页回磁盘,此时的页时脏页列表选取的。</p><p>这种情况是保证重做日志的可用性,说白了就是,重做日志中可以循环覆盖的部分空间太少了,换种说法,就是极短时间内产生了大量的redo log。</p><p>接下来会有几个变量,图解也不难,仔细看看。</p><p>InnoDB存储引擎,通过LSN Log Sequence Number 来标记版本,LSN是8字节的数字。每个页有LSN,重做日志有LSN,checkpoint有LSN。<br><strong>写入日志的LSN:redo_lsn</strong><br><strong>刷新回磁盘的最新页LSN:checkpoint_lsn</strong></p><p>有如下定义:</p><p>checkpoint_age redo_lsn - checkpoint_lsn</p><p>async_water_mark 75% * total_redo_file_size</p><p>sync_water_mark 90% * total_redo_file_size</p><p>刷新过程如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-07/img5.avif"></p><p>这里总结下来就是:</p><ul><li>当redo log超过75%小于90%就会执行异步落盘。</li><li>当redo log超过90%,就会执行同步落盘操作。回阻塞写操作。<br><strong>④Dirty Page too much Checkpoint</strong></li></ul><p>脏页率超过75%执行落盘</p><p>即脏页太多,强制checkpoint.保证缓冲池有足够可用的页。</p><p>参数设置:innodb_max_dirty_pages_pct 75 表示:当缓冲池中脏页的数量占75%时,强制checkpoint。1.0.x之后默认75</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/07/f1900617/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>洞悉MySQL底层架构：游走在缓冲与磁盘之间</title>
      <link>https://blog.eucalyptus.cc/2023/11/02/ac6408c4/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/02/ac6408c4/</guid>
      <pubDate>Thu, 02 Nov 2023 10:10:14 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;p&gt;提起MySQL,其实网上已经有一大把教程了,为什么我还要写这篇文章呢,大概是因为网上很多网站都是比较零散,而且描述不够直观,不能对MySQL相关知识有一个系统的学习,导致不能形成知识体系。为此我撰写了这篇文章,试图让这些底层架构相关知识更加直观易懂</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><p>提起MySQL,其实网上已经有一大把教程了,为什么我还要写这篇文章呢,大概是因为网上很多网站都是比较零散,而且描述不够直观,不能对MySQL相关知识有一个系统的学习,导致不能形成知识体系。为此我撰写了这篇文章,试图让这些底层架构相关知识更加直观易懂:</p></blockquote><ul><li>尽量以<code>图文</code>的方式描述技术原理;</li><li>涉及到关键的技术,附加<code>官网</code>或者<code>技术书籍</code>来源,方便大家进一步扩展学习;</li><li>涉及到的<code>背景知识</code>尽可能做一个交代,比如讨论到log buffer的刷盘方式,延伸一下IO写磁盘相关知识点。</li></ul><p>好了,MySQL从不会到精通系列马上就要开始了 看完之后还是不会的话..请忽略这句话 。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img1.gif"></p><p>可能会有同学问:为啥不直接学更加先进的TiDB,或者是强大的OceanBase。</p><p>其实,MySQL作为老牌的应用场景广泛的关系型开源数据库,其底层架构是很值得我们学习的,吸收其设计精华,那么我们在平时的方案设计工作中也可以借鉴,如果项目中用的是MySQL,那么就能够把数据库用的更好了,了解了MySQL底层的执行原理,对于调优工作也是有莫大帮助的。本文我重点讲述MySQL底层架构,涉及到:</p><ul><li><strong>内存结构</strong>:<code>buffer pool</code>、<code>log buffer</code>、<code>change buffer</code>、buffer pool的页淘汰机制是怎样的;</li><li><strong>磁盘结构</strong>:<code>系统表空间</code>、<code>独立表空间</code>、<code>通用表空间</code>、<code>undo表空间</code>、<code>redo log</code>;</li><li>以及<code>IO</code>相关底层原理、查询<code>SQL执行流程</code>、数据<code>页结构</code>和<code>行结构</code>描述、<code>聚集索引</code>和<code>辅助索引</code>的底层数据组织方式、<code>MVCC</code>多版本并发控制的底层实现原理,以及可<code>重复读</code>、<code>读已提交</code>是怎么通过MVCC实现的。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img2.avif"></p><p>看完文本文,您将了解到:</p><ul><li>**整体架构:**InnoDB存储架构是怎样的 (1、MySQL架构)</li><li>**工作原理:**查询语句的底层执行流程是怎样的 (2、查询SQL执行流程)</li><li>**IO性能:**文件<code>IO操作</code>写磁盘有哪几种方式,有什么IO优化方式 (3.1.2、关于磁盘IO的方式)</li><li><strong>缓存:</strong><code>InnoDB缓存</code>(buffer pool, log buffer)的刷新方式有哪些 3.1.2.2、innodb_flush_method</li><li>**缓存:**log buffer是在什么时候写入到磁盘的 3.10.2、如何保证数据不丢失 - 其中第四步log buffer持久化到磁盘的时机为</li><li>**缓存:**为什么redo log prepare状态也要写磁盘? 3.10.2、如何保证数据不丢失 - 为什么第二步redo log prepare状态也要写磁盘?</li><li>**缓存:**脏页写盘一般发生在什么时候 3.10.2、如何保证数据不丢失 - 其中第五步:脏页刷新到磁盘的时机为</li><li>**缓存:**为什么唯一索引的更新不可以借助change buffer 3.2、Change Buffer</li><li><strong>缓存:</strong><code>log buffer</code>的日志刷盘控制参数<code>innodb_flush_log_at_trx_commit</code>对写性能有什么影响 3.4.1、配置参数</li><li>**缓存:**buffer pool的LRU是如何实现的,为什么要这样实现 3.1.1、缓冲池LRU算法</li><li>**表存储:**系统表空间的结构,MySQL InnoDB磁盘存储格式,各种<code>表空间</code>(系统表空间,独立表空间,通用表空间)的作用和优缺点是什么,<code>ibdata</code>、<code>ibd</code>、<code>frm</code>文件分别是干嘛的 3.5、表空间</li><li>**行字段存储:**底层页和行的存储格式 3.6、InnoDB底层逻辑存储结构</li><li><strong>行字段存储:</strong><code>varchar</code>,<code>null</code>底层是如何存储的,最大可用存储多大的长度 3.6.3.1、MySQL中varchar最大长度是多少</li><li>**行字段存储:**行记录太长了,一页存不下,该怎么存储? 3.6.3.2、行记录超过页大小如何存储</li><li>**索引:**数据库<code>索引</code>的组织方式是怎样的,明白为什么要采用<code>B 树</code>,而不是哈希表、二叉树或者B树 3.7、索引 - 为什么MySQL使用B 树</li><li>**索引:**索引组织方式是怎样的,为什么<code>大字段</code>会影响表性能(查询性能,更新性能) 3.7、索引</li><li><strong>索引:</strong><code>覆盖索引</code>、<code>联合索引</code>什么情况下会生效 3.7.2、辅助索引</li><li>**索引:**什么是<code>索引下推</code>,索引下推减少了哪方面的开销? 3.7.2、辅助索引 - 索引条件下推</li><li><strong>索引:</strong><code>Change Buffer</code>对二级索引DML语句有什么优化 3.2、Change Buffer</li><li>**数据完整性:**MySQL是如何保证数据完整性的,<code>redo log</code>、<code>undo log</code>和<code>buffer pool</code>数据完整性的关键作用分别是什么 3.10.2、如何保证数据不丢失</li><li><strong>MVCC:</strong><code>MVCC</code>底层是怎么实现的,可重复读和读已提交是怎么实现的 3.11.2、MVCC实现原理</li><li>双写缓冲区有什么作用 3.9、Doublewrite Buffer</li><li>Redo Log在一个事务中是在什么时候写入的?binlog和Redo Log有什么区别? 3.10.1、Redo Log在事务中的写入时机</li></ul><h2 id="1、MySQL架构"><a href="#1、MySQL架构" class="headerlink" title="1、MySQL架构"></a>1、MySQL架构</h2><p>如下图为MySQL架构涉及到的常用组件:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img3.avif"></p><h2 id="2、查询SQL执行流程"><a href="#2、查询SQL执行流程" class="headerlink" title="2、查询SQL执行流程"></a>2、查询SQL执行流程</h2><p>有如下表格:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img4.avif"></p><p>我们执行以下sql:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> t_user <span class="keyword">where</span> user_id <span class="number">10000</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><h3 id="2-1、MySQL客户端与服务器建立连接"><a href="#2-1、MySQL客户端与服务器建立连接" class="headerlink" title="2.1、MySQL客户端与服务器建立连接"></a>2.1、MySQL客户端与服务器建立连接</h3><p>如下图,建立过程:</p><ul><li>客户端通过mysql命令发起连接请求;</li><li>经过三次握手后与服务端建立TCP连接;</li><li>连接器接收到请求之后使用用户密码进行[身份验证](<a href="https://cloud.tencent.com/product/mfas?from_column">https://cloud.tencent.com/product/mfas?from_column</a> 20065&amp;from 20065);</li><li>验证通过之后,获取用户的权限信息缓存起来,<strong>该连接后面都是基于该缓存中的权限执行sql</strong>;</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img5.avif"></p><p>对于Java应用程序来说,一般会把建立好的连接放入数据库连接池中进行复用,只要这个连接不关闭,就会一直在MySQL服务端保持着,可以通过<code>show processlist</code>命令查看,如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img6.avif"></p><p>注意,这里有个Time,表示这个连接多久没有动静了,上面例子是656秒没有动静,<strong>默认地,如果超过8个小时还没有动静,连接器就会自动断开连接</strong>,可以通过<code>wait_timeout</code>参数进行控制。</p><h3 id="2-2、执行SQL"><a href="#2-2、执行SQL" class="headerlink" title="2.2、执行SQL"></a>2.2、执行SQL</h3><p>如下图,执行sql:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img7.avif"></p><ul><li>服务端接收到客户端的查询sql之后,先尝试从查询缓存中查询该sql是否已经有缓存的结果了,如果有则直接返回结果,如果没有则执行下一步;</li><li>分析器拿到sql之后会尝试对sql语句进行词法分析和语法分析,校验语法的正确性,通过之后继续往下执行;</li><li>优化器拿到分析器的sql之后,开始继续解析sql,判断到需要走什么索引,根据实际情况重写sql,最终生成执行计划;</li><li>执行器根据执行计划执行sql,执行之前会先进行操作权限校验;然后根据表存储引擎调用对饮接口进行查询数据,这里的扫描行数就是指的接口返回的记录数,执行器拿到返回记录之后进一步加工,如本例子:</li><li>执行器拿到select * from t_user where user_id 10000的所有记录,在依次判断user_name是不是等于 arthinking ,获取到匹配的记录。</li></ul><h2 id="3、InnoDB引擎架构"><a href="#3、InnoDB引擎架构" class="headerlink" title="3、InnoDB引擎架构"></a>3、InnoDB引擎架构</h2><p>如下图,为存储引擎的架构:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img8.avif"></p><p>其实内存中的结构不太好直接观察到,不过磁盘的还是可以看到的,我们找到磁盘中MySQL的数据文件夹看看:</p><p><code>cd innodb_data_home_dir</code> 查看MySQL 数据目录:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br></pre></td><td class="code"><pre><span class="line"><span class="operator">|</span><span class="operator">-</span> ib_buffer_pool <span class="operator">/</span><span class="operator">/</span> 保存缓冲池中页面的表空间ID和页面ID,用于重启恢复缓冲池</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> ib_logfile0 <span class="operator">/</span><span class="operator">/</span> redo log 磁盘文件<span class="number">1</span></span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> ib_logfile1 <span class="operator">/</span><span class="operator">/</span> redo log 磁盘文件<span class="number">2</span>,默认情况下,重做日志存在磁盘的这两个文件中,循环的方式写入重做日志</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> ibdata1 <span class="operator">/</span><span class="operator">/</span> 系统表空间文件</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> ibtmp1 <span class="operator">/</span><span class="operator">/</span> 默认临时表空间文件,可通过innodb_temp_data_file_path属性指定文件位置</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysql<span class="operator">/</span></span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysql<span class="operator">-</span>bin<span class="number">.000001</span> <span class="operator">/</span><span class="operator">/</span> bin log文件</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysql<span class="operator">-</span>bin<span class="number">.000001</span> <span class="operator">/</span><span class="operator">/</span> bin log文件</span><br><span class="line">...</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysql<span class="operator">-</span>bin.index <span class="operator">/</span><span class="operator">/</span> bin log文件索引</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysqld.local.err <span class="operator">/</span><span class="operator">/</span> 错误日志</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> mysqld.local.pid <span class="operator">/</span><span class="operator">/</span> mysql进程号</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> performance_schema<span class="operator">/</span> <span class="operator">/</span><span class="operator">/</span> performance_schema数据库</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> sys<span class="operator">/</span> <span class="operator">/</span><span class="operator">/</span> sys数据库</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> test<span class="operator">/</span> <span class="operator">/</span><span class="operator">/</span> 数据库文件夹</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> db.opt <span class="operator">/</span><span class="operator">/</span> test数据库配置文件,包含数据库字符集属性</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> t.frm <span class="operator">/</span><span class="operator">/</span> 数据表元数据文件,不管是使用独立表空间还是系统表空间,每个表都对应有一个</span><br><span class="line"><span class="operator">|</span><span class="operator">-</span> t.ibd <span class="operator">/</span><span class="operator">/</span> 数据库表独立表空间文件,如果使用的是独立表空间,则一个表对应一个ibd文件,否则保存在系统表空间文件中</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>innodb_data_home_dir[30]</p><p>ib_buffer_pool[31]</p><p>ib_logfile0[32]</p><p>ibtmp1[33]</p><p>db.opt[34]</p><p>接下来我们逐一来介绍。</p><h3 id="3-1、buffer-pool"><a href="#3-1、buffer-pool" class="headerlink" title="3.1、buffer pool"></a>3.1、buffer pool</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img9.avif"></p><p><code>buffer pool</code> <code>缓冲池</code> 是<code>主内存</code>中的一个区域,在InnoDB访问<code>表数据</code>和<code>索引数据</code>的时候,会顺便把对应的数据页缓存到缓冲池中。如果直接从缓冲池中直接读取数据将会加快处理速度。在专用服务器上,通常将80%左右的物理内存分配给缓冲池。</p><p>为了提高缓存管理效率,缓冲池把页面链接为列表,使用<code>改进版的LRU算法</code>将很少使用的数据从缓存中老化淘汰掉。</p><h4 id="3-1-1、缓冲池LRU算法"><a href="#3-1-1、缓冲池LRU算法" class="headerlink" title="3.1.1、缓冲池LRU算法"></a><em>3.1.1、缓冲池LRU算法</em></h4><p>通过使用改进版的LRU算法来管理缓冲池列表。</p><p>当需要把新页面存储到缓冲池中的时候,将淘汰最近最少使用的页面,并将新页面添加到旧子列表的头部。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img10.avif"></p><p>该算法运行方式:</p><ul><li>默认 3&#x2F;8缓冲池用于旧子列表;</li><li>当新页面如缓冲池时,<strong>首先将其插入旧子列表头部</strong>;</li><li>重复访问旧子列表的页面,将使其移动至新子列表的头部;</li><li>随着数据库的运行,页面逐步移至列表尾部,缓冲池中未被方位的页面最终将被老化淘汰。</li></ul><p>相关优化参数:</p><ul><li>innodb_old_blocks_pct :控制LRU列表中旧子列表的百分比,默认是37,也就是3&#x2F;8,可选范围为5~95;</li><li>innodb_old_blocks_time :指定第一次访问页面后的时间窗口,该时间窗口内访问页面不会使其移动到LRU列表的最前面。默认是1000,也就是1秒。</li></ul><blockquote><p><strong>innodb_old_blocks_time</strong>很重要,有了这1秒,对于全表扫描,由于是顺序扫描的,一般同一个数据页的数据都是在一秒内访问完成的,不会升级到新子列表中,一直在旧子列表淘汰数据,所以不会影响到新子列表的缓存。</p></blockquote><h4 id="3-1-2、关于磁盘IO的方式"><a href="#3-1-2、关于磁盘IO的方式" class="headerlink" title="3.1.2、关于磁盘IO的方式"></a><em>3.1.2、关于磁盘IO的方式</em></h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img11.avif"></p><p><code>O_DIRECT</code>是<code>innodb_flush_method</code>参数的一个可选值。</p><p>这里先介绍下和数据库性能密切相关的文件IO操作方法</p><h5 id="3-1-2-1、文件IO操作方法"><a href="#3-1-2-1、文件IO操作方法" class="headerlink" title="3.1.2.1、文件IO操作方法"></a>3.1.2.1、文件IO操作方法</h5><p>数据库系统是基于文件系统的,其性能和设备读写的机制有密切的关系。</p><h6 id="open-打开文件-1"><a href="#open-打开文件-1" class="headerlink" title="open:打开文件[1]"></a><strong>open:打开文件[1]</strong></h6><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">int open(const char *pathname, int flags);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>系统调用Open会为该进程一个文件描述符fd,常用的flags如下:</p><ul><li><code>O_WRONLY</code>:表示我们以 写 的方式打开,告诉内核我们需要向文件中写入数据;</li><li><code>O_DSYNC</code>:每次write都等待物理I&#x2F;O完成,但是如果写操作不影响读取刚写入的数据,则不等待文件属性更新;</li><li><code>O_SYNC</code>:每次write都等到物理I&#x2F;O完成,包括write引起的文件属性的更新;</li><li><code>O_DIRECT</code>:执行磁盘IO时绕过缓冲区高速缓存(内核缓冲区),从用户空间直接将数据传递到文件或磁盘设备,称为直接IO direct IO 。因为没有了OS cache,所以会O_DIRECT降低文件的顺序读写的效率。</li></ul><h6 id="write-写文件-2"><a href="#write-写文件-2" class="headerlink" title="write:写文件^2"></a><strong>write:写文件^2</strong></h6><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">ssize_t write(int fd, const void *buf, size_t count);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>使用open打开文件获取到文件描述符之后,可以调用write函数来写文件,具体表现根据open函数参数的不同而不同弄。</p><h6 id="fsync-fdatasync-刷新文件-3"><a href="#fsync-fdatasync-刷新文件-3" class="headerlink" title="fsync &amp; fdatasync:刷新文件[3]"></a><strong>fsync &amp; fdatasync:刷新文件[3]</strong></h6><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">#include &lt;unistd.h&gt;</span><br><span class="line"></span><br><span class="line">int fsync(int fd);</span><br><span class="line"></span><br><span class="line">int fdatasync(int fd);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><ul><li><code>fdatasync</code>:操作完write之后,我们可以调用fdatasync将文件数据块flush到磁盘,只要fdatasync返回成功,则可以认为数据已经写到磁盘了;</li><li><code>fsync</code>:与O_SYNC参数类似,fsync还会更新文件metadata到磁盘;</li><li><code>sync</code>:sync只是将修改过的块缓冲区写入队列,然后就返回,不等实际写磁盘操作完成;</li></ul><p><strong>为了保证文件更新成功持久化到硬盘,除了调用write方法,还需要调用fsync。</strong></p><p>大致交互流程如下图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img12.avif"></p><p>更多关于磁盘IO的相关内容,可以阅读:On Disk IO, Part 1: Flavors of IO[27]</p><p>**fsync性能问题:**除了刷脏页到磁盘,fsync还会同步文件metadata,而文件数据和metadata通常存放在磁盘不同地方,所以fsync至少需要两次IO操作。</p><p><strong>对fsync性能的优化建议</strong>:由于以上性能问题,如果能够减少metadata的更新,那么就可以使用fdatasync了。因此需要确保文件的尺寸在write前后没有发生变化。为此,可以创建固定大小的文件进行写,写完则开启新的文件继续写。</p><h5 id="3-1-2-2、innodb-flush-method"><a href="#3-1-2-2、innodb-flush-method" class="headerlink" title="3.1.2.2、innodb_flush_method"></a>3.1.2.2、innodb_flush_method</h5><p><code>innodb_flush_method</code>定义用于将数据刷新到<code>InnoDB</code>数据文件和日志文件的方法,这可能会影响I&#x2F;O吞吐量。</p><p>以下是具体参数说明:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img13.avif"></p><p>比较常用的是这三种:</p><h6 id="fsync"><a href="#fsync" class="headerlink" title="fsync"></a><strong>fsync</strong></h6><p>默认值,使用<code>fsync()</code>系统调用来flush数据文件和日志文件到磁盘;</p><h6 id="O-DSYNC"><a href="#O-DSYNC" class="headerlink" title="O_DSYNC"></a><strong>O_DSYNC</strong></h6><p>由于open函数的O_DSYNC参数在许多Unix系统上都存中问题,因此InnoDB不直接使用O_DSYNC。</p><p><code>InnoDB</code>用于<code>O_SYNC</code> 打开和刷新日志文件,<code>fsync()</code>刷新数据文件。</p><p>表现为:写日志操作是在write函数完成,数据文件写入是通过<code>fsync()</code>系统调用来完成;</p><h6 id="O-DIRECT"><a href="#O-DIRECT" class="headerlink" title="O_DIRECT"></a><strong>O_DIRECT</strong></h6><p>使用<code>O_DIRECT</code> 在Solaris上对应为<code>directio()</code> 打开数据文件,并用于<code>fsync()</code>刷新数据文件和日志文件。此选项在某些GNU&#x2F;Linux版本,FreeBSD和Solaris上可用。</p><p>表现为:数据文件写入直接从buffer pool到磁盘,不经过操作系统缓冲,日志还是需要经过操作系统缓存;</p><h6 id="O-DIRECT-NO-FSYNC"><a href="#O-DIRECT-NO-FSYNC" class="headerlink" title="O_DIRECT_NO_FSYNC"></a><strong>O_DIRECT_NO_FSYNC</strong></h6><p>在刷新I&#x2F;O期间<code>InnoDB</code>使用<code>O_DIRECT</code>,并且每次write操作后跳过<code>fsync()</code>系统调用。</p><p>此设置适用于某些类型的文件系统,但不适用于其他类型的文件系统。例如,它不适用于XFS。如果不确定所使用的文件系统是否需要fsync() 例如保留所有文件元数据 ,请改用O_DIRECT。</p><p>如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img14.avif"></p><blockquote><p><strong>为什么使用了O_DIRECT配置后还需要调用fsync()?</strong> 参考MySQL的这个bug:Innodb calls fsync for writes with innodb_flush_method O_DIRECT[35] Domas进行的一些测试表明,如果没有fsync,某些文件系统 XFS 不会同步元数据。如果元数据会更改,那么您仍然需要使用fsync 或O_SYNC来打开文件 。 例如,如果在启用O_DIRECT的情况下增大文件大小,它仍将写入文件的新部分,但是由于元数据不能反映文件的新大小,因此如果此刻系统发生崩溃,文件尾部可能会丢失。 为此:<strong>当重要的元数据发生更改时,请继续使用fsync或除O_DIRECT之外,也可以选择使用O_SYNC。</strong></p></blockquote><p>MySQL从v5.6.7起提供了<code>O_DIRECT_NO_FSYNC</code>选项来解决此类问题。</p><h3 id="3-2、Change-Buffer"><a href="#3-2、Change-Buffer" class="headerlink" title="3.2、Change Buffer"></a>3.2、Change Buffer</h3><p>change buffer是一种特殊的数据结构,当二级索引页(非唯一索引)不在缓冲池中时,它们会缓存这些更改 。当页面通过其他读取操作加载到缓冲池中时,再将由<code>INSERT</code>,<code>UPDATE</code>或<code>DELETE</code>操作 DML 产生的change buffer合并到buffer pool的数据页中。</p><blockquote><p><strong>为什么唯一索引不可以使用chage buffer?</strong> 针对唯一索引,如果buffer pool不存在对应的数据页,还是需要先去磁盘加载数据页,才能判断记录是否重复,这一步避免不了。 而普通索引是非唯一的,插入的时候以相对随机的顺序发生,删除和更新也会影响索引树中不相邻的二级索引树,<strong>通过使用合并缓冲,避免了在磁盘产生大量的随机IO访问获取普通索引页。</strong> <strong>问题</strong> 当有许多受影响的行和许多辅助索引要更新时,change buffer合并可能需要几个小时,在此期间,I&#x2F;O会增加,可能会导致查询效率大大降低,即使在事务提交之后,或者服务器重启之后,change buffer合并操作也会继续发生。相关阅读:Section 14.22.2, “Forcing InnoDB Recovery” <a href="https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html">https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html</a></p></blockquote><h3 id="3-3、自适应哈希索引"><a href="#3-3、自适应哈希索引" class="headerlink" title="3.3、自适应哈希索引"></a>3.3、自适应哈希索引</h3><p>自适应哈希索引功能由<code>innodb_adaptive_hash_index</code>变量启用 ,或在服务器启动时由<code>--skip-innodb-adaptive-hash-index</code>禁用。</p><h3 id="3-4、Log-Buffer"><a href="#3-4、Log-Buffer" class="headerlink" title="3.4、Log Buffer"></a>3.4、Log Buffer</h3><p>log buffer(日志缓冲区)用于保存要写入磁盘上的log file(日志文件)的数据。日志缓存区的内容会定期刷新到磁盘。</p><p>日志缓冲区大小由<code>innodb_log_buffer_size</code>变量定义 。默认大小为16MB。较大的日志缓冲区可以让大型事务在提交之前无需将redo log写入磁盘。</p><p>如果您有更新,插入或者删除多行的事务,尝试增大日志缓冲区的大小可以节省磁盘I&#x2F;O。</p><h4 id="3-4-1、配置参数"><a href="#3-4-1、配置参数" class="headerlink" title="3.4.1、配置参数"></a><em>3.4.1、配置参数</em></h4><p><strong>innodb_flush_log_at_trx_commit</strong></p><p><code>innodb_flush_log_at_trx_commit</code> 变量控制如何将日志缓冲区的内容写入并刷新到磁盘。</p><p>该参数控制是否严格存储ACID还是尝试获取更高的性能,可以通过该参数获取更好的性能,但是会导致在系统崩溃的过程中导致数据丢失。</p><p>可选参数:</p><ul><li>0,事务提交之后,日志只记录到log buffer中,每秒写一次日志到缓存并刷新到磁盘,尚未刷新的日志可能会丢失;</li><li>1,要完全符合ACID,必须使用该值,表示日志在每次事务提交时写入缓存并刷新到磁盘;</li><li>2,每次事务提交之后,日志写到page cache,每秒刷一次到磁盘,尚未刷新的日志可能会丢失;</li></ul><p><strong>innodb_flush_log_at_timeout</strong></p><p><code>innodb_flush_log_at_timeout</code> 变量控制日志刷新频率。可让您将日志刷新频率设置为<code>*N*</code>秒 其中<code>*N*</code>为<code>1 ... 2700</code>,默认值为1</p><blockquote><p>为了保证数据不丢失,请执行以下操作:</p></blockquote><ul><li>如果启用了binlog,则设置:sync_binlog 1;</li><li>innodb_flush_log_at_trx_commit 1;</li></ul><p>配置效果如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img15.avif"></p><h3 id="3-5、表空间"><a href="#3-5、表空间" class="headerlink" title="3.5、表空间"></a>3.5、表空间</h3><p>一个<code>InnoDB</code>表及其索引可以在建在系统表空间中,或者是在一个 独立表空间 中,或在 通用表空间。</p><ul><li>当 innodb_file_per_table 启用时,通常是将表存放在独立表空间中,这是默认配置;</li><li>当 innodb_file_per_table 禁用时,则会在系统表空间中创建表;</li><li>要在通用表空间中创建表,请使用 CREATE TABLE … TABLESPACE 语法。有关更多信息,请参见官方文档 14.6.3.3 General Tablespaces。</li></ul><p>表空间概览图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img16.avif"></p><h4 id="表空间涉及的文件"><a href="#表空间涉及的文件" class="headerlink" title="表空间涉及的文件"></a><em>表空间涉及的文件</em></h4><p>相关文件默认在磁盘中的<code>innodb_data_home_dir</code>目录下:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">|- ibdata1 // 系统表空间文件</span><br><span class="line">|- ibtmp1 // 默认临时表空间文件,可通过innodb_temp_data_file_path属性指定文件位置</span><br><span class="line">|- test/ // 数据库文件夹</span><br><span class="line">|- db.opt // test数据库配置文件,包含数据库字符集属性</span><br><span class="line">|- t.frm // 数据表元数据文件,不管是使用独立表空间还是系统表空间,每个表都对应有一个</span><br><span class="line">|- t.ibd // 数据库表独立表空间文件,如果使用的是独立表空间,则一个表对应一个ibd文件,否则保存在系统表空间文件中</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p><strong>frm文件</strong></p><p>创建一个<code>InnoDB</code>表时,MySQL 在数据库目录中创建一个.frm文件。frm文件包含MySQL表的元数据(如表定义)。每个InnoDB表都有一个.frm文件。</p><p>与其他MySQL存储引擎不同, <code>InnoDB</code>它还在<code>系统表空间</code>内的自身内部数据字典中编码有关表的信息。MySQL删除表或数据库时,将删除一个或多个<code>.frm</code>文件以及<code>InnoDB</code>数据字典中的相应条目。</p><p>因此,在InnoDB中,您不能仅通过移动<code>.frm</code> 文件来移动表。有关移动<code>InnoDB</code> 表的信息,请参见官方文档14.6.1.4 Moving or Copying InnoDB Tables <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-migration.html%E3%80%82">https://dev.mysql.com/doc/refman/5.7/en/innodb-migration.html。</a></p><p><strong>ibd文件</strong></p><p>对于在独立表空间创建的表,还会在数据库目录中生成一个 .ibd表空间文件。</p><p>在<code>通用表空间</code>中创建的表在现有的常规表空间 .ibd文件中创建。常规表空间文件可以在<strong>MySQL数据目录内部或外部创建</strong>。有关更多信息,请参见官方文档14.6.3.3 General Tablespaces。 <a href="https://dev.mysql.com/doc/refman/5.7/en/general-tablespaces.html">https://dev.mysql.com/doc/refman/5.7/en/general-tablespaces.html</a></p><p><strong>ibdata文件</strong></p><p>系统表空间文件,在 <code>InnoDB</code>系统表空间中创建的表在ibdata中创建。</p><h4 id="3-5-1、系统表空间"><a href="#3-5-1、系统表空间" class="headerlink" title="3.5.1、系统表空间"></a><em>3.5.1、系统表空间</em></h4><p>系统表空间由一个或多个数据文件(ibdata文件)组成。其中包含与<code>InnoDB</code>相关对象有关的元数据 <code>InnoDB</code> <strong>数据字典</strong> <strong>data dictionary</strong> ,以及<strong>更改缓冲区</strong> <strong>change buffer</strong> , <strong>双写缓冲区</strong> <strong>doublewrite buffer</strong> 和<strong>撤消日志</strong> <strong>undo logs</strong> 的存储区 。</p><p><code>InnoDB</code> 如果表是在系统表空间中创建的,则系统表空间中也包含表的表数据和索引数据。</p><h5 id="系统表空间的问题"><a href="#系统表空间的问题" class="headerlink" title="系统表空间的问题"></a>系统表空间的问题</h5><p>在MySQL 5.6.7之前,默认设置是将所有<code>InnoDB</code>表和索引保留 在系统表空间内,这通常会导致该文件变得非常大。因为系统表空间永远不会缩小,所以如果先加载然后删除大量临时数据,则可能会出现存储问题。</p><p>在MySQL 5.7中,默认设置为 <strong>独立表空间</strong>模式,其中每个表及其相关索引存储在单独的 <strong>.ibd文件中</strong>。此默认设置使使用<strong>Barracuda</strong>文件格式的<code>InnoDB</code>功能更容易使用,例如表<strong>压缩</strong>,<strong>页外列的</strong>有效存储以及大索引键前缀 <code>innodb_large_prefix</code> 。</p><p>将所有表数据保留在系统表空间或单独的 <code>.ibd</code>文件中通常会对存储管理产生影响。</p><p><code>InnoDB</code>在MySQL 5.7.6中引入了<strong>通用表空间</strong>[6],这些表空间也由<code>.ibd</code>文件表示 。通用表空间是使用<code>CREATE TABLESPACE</code>语法创建的共享表空间。它们可以在MySQL数据目录之外创建,能够容纳多个表,并支持所有行格式的表。</p><h4 id="3-5-2、独立表空间"><a href="#3-5-2、独立表空间" class="headerlink" title="3.5.2、独立表空间"></a><em>3.5.2、独立表空间</em></h4><p>MySQL 5.7中,配置参数:<code>innodb_file_per_table</code>,默认处于启用状态,这是一个重要的配置选项,会影响<code>InnoDB</code>[文件存储](<a href="https://cloud.tencent.com/product/cfs?from_column">https://cloud.tencent.com/product/cfs?from_column</a> 20065&amp;from 20065),功能的可用性和I&#x2F;O特性等。</p><p>启用之后,每个表的数据和索引是存放在单独的.ibd文件中的,而不是在系统表空间的共享ibdata文件中。</p><h5 id="优点"><a href="#优点" class="headerlink" title="优点"></a>优点</h5><ul><li>您可以更加灵活的选择<code>数据压缩</code>[4]的行格式,如:</li><li>默认情况下 innodb_page_size 16K ,<code>前缀索引</code>^5最多包含768个字节。如果开启innodb_large_prefix,且Innodb表的存储行格式为 DYNAMIC 或 COMPRESSED,则前缀索引最多可包含3072个字节,前缀索引也同样适用;</li><li><code>TRUNCATE TABLE</code>执行的更快,并且回收的空间不会继续保留,而是让操作系统使用;</li><li>可以在单独的存储设备上创建每表文件表空间数据文件,以进行I &#x2F; O优化,空间管理或备份。请参见 14.6.1.2 Creating Tables Externally <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-create-table-external.html">https://dev.mysql.com/doc/refman/5.7/en/innodb-create-table-external.html</a>;</li></ul><h5 id="缺点"><a href="#缺点" class="headerlink" title="缺点"></a>缺点</h5><ul><li>独立表空间中的未使用空间只能由同一个表使用,如果管理不当,会造成空间浪费;</li><li>多个表需要刷盘,只能执行多次fsync,无法合并多个表的写操作,这可能会导致更多的fsync操作总数;</li><li><strong>mysqld</strong>必须为每个表文件空间保留一个打开的文件句柄,如果表数量多,可能会影响性能;</li><li>每个表都需要自己的数据文件,需要更多的文件描述符;</li></ul><blockquote><p>即使启用了innodb_file_per_table参数,每张表空间存放的只是数据、索引和插入缓存Bitmap页,其他数据如回滚信息、插入缓冲索引页、系统事务信息、二次写缓冲等还是存放在原来的共享表空间中。</p></blockquote><h4 id="3-5-3、通用表空间"><a href="#3-5-3、通用表空间" class="headerlink" title="3.5.3、通用表空间"></a><em>3.5.3、通用表空间</em></h4><p>通用表空间使用<code>CREATE TABLESPACE</code>语法创建。</p><p>类似于系统表空间,通用表空间是共享表空间,可以存储多个表的数据。</p><p>通用表空间比独立表空间具有潜在的内存优势,服务器在表空间的生存期内将表空间元数据保留在内存中。一个通用表空间通常可以存放多个表数据,消耗更少的表空间元数据内存。</p><p>数据文件可以放置在MySQL数据目录或独立于MySQL数据目录。</p><h4 id="3-5-4、undo表空间"><a href="#3-5-4、undo表空间" class="headerlink" title="3.5.4、undo表空间"></a><em>3.5.4、undo表空间</em></h4><p>undo表空间包含undo log。</p><p><code>innodb_rollback_segments</code>变量定义分配给每个撤消表空间的回滚段的数量。</p><p>undo log可以存储在一个或多个undo表空间中,而不是系统表空间中。</p><p>在默认配置中,撤消日志位于系统表空间中。SSD存储更适合undo log的I&#x2F;O模式,为此,可以把undo log存放在有别于系统表空间的ssd硬盘中。</p><p><code>innodb_undo_tablespaces</code> 配置选项控制undo表空间的数量。</p><h4 id="3-5-5、临时表空间"><a href="#3-5-5、临时表空间" class="headerlink" title="3.5.5、临时表空间"></a><em>3.5.5、临时表空间</em></h4><p>由用户创建的非压缩临时表和磁盘内部临时表是在共享临时表空间中创建的。</p><p><code>innodb_temp_data_file_path</code> 配置选项指定零时表空间文件的路径,如果未指定,则默认在 <code>innodb_data_home_dir</code>目录中创建一个略大于12MB 的自动扩展数据文件<code>ibtmp1</code> 。</p><p>使用<code>ROW_FORMAT COMPRESSED</code>属性创建的压缩临时表,是在独立表空间中的临时文件目录中创建的 。</p><p>服务启动的时候创建临时表空间,关闭的时候销毁临时表空间。如果临时表空间创建失败,则意味着服务启动失败。</p><h3 id="3-6、InnoDB底层逻辑存储结构"><a href="#3-6、InnoDB底层逻辑存储结构" class="headerlink" title="3.6、InnoDB底层逻辑存储结构"></a>3.6、InnoDB底层逻辑存储结构</h3><p>在介绍索引之前,我们有必要了解一下InnoDB底层的逻辑存储结构,因为索引是基于这个底层逻辑存储结构创建的。截止到目前,我们所展示的都仅仅是物理磁盘中的逻辑视图,接下来我们就来看看底层的视图。</p><h4 id="3-6-1、ibd文件组织结构"><a href="#3-6-1、ibd文件组织结构" class="headerlink" title="3.6.1、ibd文件组织结构"></a><em>3.6.1、ibd文件组织结构</em></h4><p>现在<strong>我们打开一个表空间ibd文件,看看里面都是如何组织数据的?</strong></p><p>如下图,表空间由段(segment)、区(extent)、页(page)组成。</p><p>InnoDB最小的存储单位是页,默认每个页大小是16k。</p><p>而InnoDB存储引擎是面向行的(row-oriented),数据按行进行存放,每个页规定最多允许存放的行数 16k&#x2F;2 - 200,即7992行。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img17.avif"></p><p>段:如数据段、索引段、回滚段等。<strong>InnoDB存储引擎是B 树索引组织的</strong>,所以数据即索引,索引即数据。B 树的叶子节点存储的都是数据段的数据。</p><h4 id="3-6-2、数据页结构-13"><a href="#3-6-2、数据页结构-13" class="headerlink" title="3.6.2、数据页结构[13]"></a><em>3.6.2、数据页结构[13]</em></h4><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img18.avif"></p><p>关于Infimun和Supremum:首次创建索引时,InnoDB会在根页面中自动设置一个最小记录和一个最高记录,并且永远不会删除它们。最低记录和最高记录可以视为索引页开销的一部分。最初,它们都存在于根页面上,但是随着索引的增长,最低记录将存在于第一或最低叶子页上,最高记录将出现在最后或最大关键字页上。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img19.avif"></p><h4 id="3-6-3、行记录结构描述-14"><a href="#3-6-3、行记录结构描述-14" class="headerlink" title="3.6.3、行记录结构描述[14]"></a><em>3.6.3、行记录结构描述[14]</em></h4><p>先来讲讲Compact行记录格式,Compact是MySQL5.0引入的,设计目标是高效的存储数据,让一个页能够存放更多的数据,从而实现更快的B 树查找。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img20.avif"></p><p><strong>记录头用于将连续的记录链接在一起,并用于行级锁定。</strong></p><p>每行数据除了用户定义的列外,还有两个隐藏列:</p><ul><li>6个字节的事务ID列;</li><li>7个字节的回滚指针列;</li><li>如果InnoDB没有指定主键,还会增加一个6个字节的rowid列;</li></ul><p>而记录头信息包[12]含如下内容:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img21.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img22.avif"></p><blockquote><p>更详细的页结构参考官网:22.2 InnoDB Page Structure <a href="https://dev.mysql.com/doc/internals/en/innodb-page-structure.html">https://dev.mysql.com/doc/internals/en/innodb-page-structure.html</a> 更详细的行结构参考官网:22.1 InnoDB Record Structure <a href="https://dev.mysql.com/doc/internals/en/innodb-record-structure.html">https://dev.mysql.com/doc/internals/en/innodb-record-structure.html</a> 更详细的行格式参考官网:14.11 InnoDB Row Formats <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html">https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html</a></p></blockquote><p>根据以上格式,可以得出数据页内的记录组织方式:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img23.avif"></p><h5 id="3-6-3-1、MySQL中varchar最大长度是多少"><a href="#3-6-3-1、MySQL中varchar最大长度是多少" class="headerlink" title="3.6.3.1、MySQL中varchar最大长度是多少"></a>3.6.3.1、MySQL中varchar最大长度是多少</h5><p>上面表格描述我们知道,一个字段最长限制是65535个字节,这是存储长度的限制。</p><p>而MySQL中对存储是有限制的,具体参考:8.4.7 Limits on Table Column Count and Row Size <a href="https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html">https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html</a></p><ul><li>MySQL对每个表有4096列的硬限制,但是对于给定的表,有效最大值可能会更少;</li><li><strong>MySQL表的每行行最大限制为65,535字节</strong>,这是逻辑的限制;实际存储的时候,表的物理最大行大小略小于页面的一半。如果一行的长度少于一页的一半,则所有行都将存储在本地页面内。如果它超过一页的一半,那么将选择可变长度列用于外部页外存储,直到该行大小控制在半页之内为止。</li></ul><p>而实际能够存储的字符是跟编码有关的。</p><blockquote><p>背景知识:</p></blockquote><ul><li>MySQL 4.0版本以下,varchar(10),代表10个<strong>字节</strong>,如果存放UTF8汉字,那么只能存3个 每个汉字3字节 ;</li><li>MySQL 5.0版本以上,varchar(10),指的是10个<strong>字符</strong>,无论存放的是数字、字母还是UTF8汉字 每个汉字3字节 ,都可以存放10个,最大大小是65532<strong>字节</strong>;</li></ul><p><strong>因此,Mysql5根据编码不同,存储大小也不同。</strong></p><p>那么假设我们使用的是utf8编码,那么每个字符最多占用3个字节,也就是最多定义varchar(21845)个字符,如果是ascii编码,一个字符相当于一个字节,最多定义varchar(65535)个字符,下面我们验证下。</p><p>我们尝试创建一个这样的字段:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> t10 ( id <span class="type">int</span>(<span class="number">11</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line">a <span class="type">int</span>(<span class="number">11</span>) <span class="keyword">NOT NULL</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB CHARSET ascii ROW_FORMAT Compact;</span><br><span class="line"></span><br><span class="line"><span class="keyword">alter table</span> t10 <span class="keyword">add</span> str <span class="type">varchar</span>(<span class="number">21845</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>;</span><br><span class="line"></span><br><span class="line"><span class="keyword">alter table</span> t10 <span class="keyword">add</span> str <span class="type">varchar</span>(<span class="number">65535</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>发现提示这个错误:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> <span class="keyword">alter table</span> t10 <span class="keyword">add</span> str <span class="type">varchar</span>(<span class="number">65535</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>;</span><br><span class="line">ERROR <span class="number">1118</span> (<span class="number">42000</span>): <span class="type">Row</span> size too large. The maximum <span class="type">row</span> size <span class="keyword">for</span> the used <span class="keyword">table</span> type, <span class="keyword">not</span> counting BLOBs, <span class="keyword">is</span> <span class="number">65535.</span> This includes storage overhead, <span class="keyword">check</span> the manual. You have <span class="keyword">to</span> change <span class="keyword">some</span> columns <span class="keyword">to</span> TEXT <span class="keyword">or</span> BLOBs</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>原因是按照以上的行格式介绍,<code>变长字段长度列表</code>记录也需要占用空间,占用2个字节,另外这里是允许为空字段,在8位之内,所以NULL标志位占用1个字节,所以我们总共可以存储的字符数是:</p><blockquote><p>65535 - 2 - 2 - 4 - 4 65534 其中 -2 个字节表示变长字段列表,-1表示NULL标志位,两个-4表示两个int类型字段占用大小</p></blockquote><p>所以实际上能够容纳的varchar大小为:65524,我们验证下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img24.avif"></p><h5 id="3-6-3-2、行记录超过页大小如何存储"><a href="#3-6-3-2、行记录超过页大小如何存储" class="headerlink" title="3.6.3.2、行记录超过页大小如何存储"></a>3.6.3.2、行记录超过页大小如何存储</h5><p>MySQL表的内部表示具有65,535字节的最大行大小限制。<code>InnoDB</code> 对于4KB,8KB,16KB和32KB <code>innodb_page_size</code> 设置,表的最大行大小 适用于本地存储在数据库页面内的数据 略小于页面的一半 。如果包含 可变长度列的<code>InnoDB</code> 行超过最大行大小,那么将选择可变长度列用于外部页外存储。</p><p>可变长度列由于太长而无法容纳在B树页面上,这个时候会把可变长度列存储在单独分配的磁盘页面上,这些页面称为<code>溢出页面</code>,这些列称为<code>页外列</code>。页外列的值存储在由溢出页面构成的<code>单链接列表</code>中。</p><p><code>InnoDB</code>存储引擎支持四种行格式:<code>REDUNDANT</code>,<code>COMPACT</code>, <code>DYNAMIC</code>,和<code>COMPRESSED</code>。不同的行格式,对溢出的阈值和处理方式有所区别,详细参考:14.11 InnoDB Row Formats <a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html#innodb-row-format-compact%E3%80%82">https://dev.mysql.com/doc/refman/5.7/en/innodb-row-format.html#innodb-row-format-compact。</a></p><p><strong>COMPACT行格式处理方式</strong></p><p>使用<code>COMPACT</code>行格式的表将前768个字节的变长列值 <code>VARCHAR</code>, <code>VARBINARY</code>和 <code>BLOB</code>和 <code>TEXT</code>类型 存储在B树节点内的索引记录中,其余的存储在溢出页上。</p><p>如果列的值等于或小于<strong>768个字节</strong>,则不使用溢出页,因此可以节省一些I &#x2F; O。</p><p>如果查过了768个字节,那么会按照如下方式进行存储:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img25.avif"></p><p><strong>DYNAMIC行格式处理方式</strong></p><p><code>DYNAMIC</code>行格式提供与<code>COMPACT</code>行格式相同的存储特性,但改进了超长可变长度列的存储能力和支持大索引键前缀。</p><p><code>InnoDB</code> 可以完全在页外存储过长的可变长度列值 针对 <code>VARCHAR</code>, <code>VARBINARY</code>和 <code>BLOB</code>和 <code>TEXT</code>类型 ,而聚集索引记录仅包含指向溢出页的20字节指针。大于或等于768字节的固定长度字段被编码为可变长度字段。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img26.avif"></p><blockquote><p><strong>表中大字段引发的问题</strong> 如果一个表中有过多的可变长度大字段,导致一行记录太长,而整个时候使用的是COMPACT行格式,那么就可能会插入数据报错。 如,页面大小事16k,根据前面描述我们知道,MySQL限制一页最少要存储两行数据,如果很多可变长度大字段,在使用COMPACT的情况下,仍然会把大字段的前面768个字节存在索引页中,可以算出最多支持的大字段:<code>1024 * 16 / 2 / 768 10.67</code>,那么超过10个可变长度大字段就会插入失败了。 这个时候可以把row format改为:DYNAMIC。</p></blockquote><h3 id="3-7、索引"><a href="#3-7、索引" class="headerlink" title="3.7、索引"></a>3.7、索引</h3><p>前面我们了解了InnoDB底层的存储结构,即:以B 树的方式组织数据页。另外了解了数据页中的数据行的存储方式。</p><p>而构建B 树索引的时候必须要选定一个或者多个字段作为索引的值,如果索引选择的是主键,那么我们就称为聚集索引,否则就是二级索引。</p><blockquote><p>为什么MySQL使用B 树?</p></blockquote><ul><li>哈希表虽然可以提供O(1)的单行数据操作性能,但却不能很好的支持排序和范围查找,会导致全表扫描;</li><li>B树可以再非叶子节点存储数据,但是这可能会导致查询连续数据的时候增加更多的I&#x2F;O操作;</li><li>而B 树数据都存放在叶子节点,叶子节点通过指针相互连接,可以减少顺序遍历时产生的额外随机I&#x2F;O</li></ul><p>更新详细解释: 为什么 MySQL 使用 B 树[29]</p><h4 id="3-7-1、聚集索引"><a href="#3-7-1、聚集索引" class="headerlink" title="3.7.1、聚集索引"></a><em>3.7.1、聚集索引</em></h4><p>了解到上面的底层逻辑存储结构之后,我们进一步来看看InnoDB是怎么通过B 树来组织存储数据的。</p><p>首先来介绍下聚集索引。</p><h5 id="聚集索引"><a href="#聚集索引" class="headerlink" title="聚集索引"></a>聚集索引</h5><p>主键索引的InnoDB术语。</p><p>下面我们创建一张测试表,并插入数据,来构造一颗B 树:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> t20 (</span><br><span class="line">id <span class="type">int</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">a <span class="type">int</span> <span class="keyword">NOT NULL</span>,</span><br><span class="line">b <span class="type">int</span>,</span><br><span class="line">c <span class="type">int</span>,</span><br><span class="line"><span class="keyword">PRIMARY KEY</span> ( id )</span><br><span class="line">) ENGINE InnoDB;</span><br><span class="line"></span><br><span class="line"><span class="keyword">insert into</span> t20 <span class="keyword">values</span>(<span class="number">20</span>, <span class="number">1</span>, <span class="number">2</span>, <span class="number">1</span>);</span><br><span class="line"><span class="keyword">insert into</span> t20 <span class="keyword">values</span>(<span class="number">40</span>, <span class="number">1</span>, <span class="number">2</span>, <span class="number">5</span>);</span><br><span class="line"><span class="keyword">insert into</span> t20 <span class="keyword">values</span>(<span class="number">30</span>, <span class="number">3</span>, <span class="number">2</span>, <span class="number">4</span>);</span><br><span class="line"><span class="keyword">insert into</span> t20 <span class="keyword">values</span>(<span class="number">50</span>, <span class="number">3</span>, <span class="number">6</span>, <span class="number">2</span>);</span><br><span class="line"><span class="keyword">insert into</span> t20 <span class="keyword">values</span>(<span class="number">10</span>, <span class="number">1</span>, <span class="number">1</span>, <span class="number">1</span>);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>可以看到,虽然我们是id乱序插入的,但是插入之后查出来的确是排序好的:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img27.avif"></p><p>这个排序就是B 索引树构建的。</p><p>我们可以通过这个在线的动态演示工具 <a href="https://www.cs.usfca.edu/~galles/visualization/BPlusTree.html%E6%9D%A5%E7%9C%8B%E7%9C%8BB">https://www.cs.usfca.edu/~galles/visualization/BPlusTree.html来看看B</a> 树的构造过程,最终结果如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img28.avif"></p><blockquote><p>实际存放在数据库中的模型因页面大小不一样而有所不同,这里为了简化模型,我们按照B 树的通用模型来解释数据的存储结构。</p></blockquote><p>类似的,我们的数据也是这种组织形式的,该B 树中,我们以主键为索引进行构建,并且把完整的记录存到对应的页下面:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img29.avif"></p><p>其中蓝色的是索引页,橙色的是数据页。</p><p>每个页的大小默认为16k,如果插入新的数据行,这个时候就要申请新的数据页了,然后挪动部分数据过去,重新调整B 树,这个过程称为<code>页分裂</code>,这个过程会影响性能。</p><p>相反的,如果<code>InnoDB</code>索引页的填充因子下降到之下<code>MERGE_THRESHOLD</code>,默认情况下为50 如果未指定 ,则<code>InnoDB</code>尝试收缩索引树以释放页面。</p><p>自增主键的插入是递增顺序插入的,每次添加记录都是追加的,不涉及到记录的挪动,不会触发叶子节点的分裂,而一般业务字段做主键,往往都不是有序插入的,写成本比较高,所以我们<strong>更倾向于使用自增字段作为主键。</strong></p><h5 id="聚集索引注意事项"><a href="#聚集索引注意事项" class="headerlink" title="聚集索引注意事项"></a>聚集索引注意事项</h5><ul><li>当在表上面定义了<code>PRIMARY KEY</code>之后,InnoDB会把它作为聚集索引。为此,为你的每个表定义一个<code>PRIMARY KEY</code>。如果没有唯一并且非空的字段或者一组列,那么请添加一个自增列;</li><li>如果您没有为表定义<code>PRIMARY KEY</code>,则MySQL会找到第一个不带null值的UNIQUE索引,并其用作聚集索引;</li><li>如果表没有<code>PRIMARY KEY</code>或没有合适的<code>UNIQUE</code>索引,则<code>InnoDB</code> 内部会生成一个隐藏的聚集索引<code>GEN_CLUST_INDEX</code>,作为行ID,行ID是一个6字节的字段,随着数据的插入而自增。</li></ul><h5 id="聚集索引查找"><a href="#聚集索引查找" class="headerlink" title="聚集索引查找"></a>聚集索引查找</h5><p>根据索引进行查找id 50的记录,如下图,沿着B 树一直往下寻找,最终找到第四页**,然后把该页加载到buffer pool中,在缓存中遍历对比查找**,由于里面的行记录是顺序组织的,所以很快就可以定位到记录了。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img30.avif"></p><h4 id="3-7-2、辅助索引"><a href="#3-7-2、辅助索引" class="headerlink" title="3.7.2、辅助索引"></a><em>3.7.2、辅助索引</em></h4><p>除了聚集索引之外的所有索引都称为辅助索引(二级索引)。在InnoDB中,辅助索引中每个记录都包含该行的主键列以及为辅助索引指定的列。</p><p>在辅助索引中查找到记录,可以得到记录的主键索引ID,然后可以通过这个主键索引ID去聚集索引中搜索具体的记录,这个过程称为<strong>回表</strong>操作。</p><p><strong>如果主键较长,则辅助索引将使用更多空间,因此具有短的主键是有利的。</strong></p><p>下面我们给刚刚的表添加一个组合联合索引</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="comment">-- 添加多一个字段</span></span><br><span class="line"><span class="keyword">alter table</span> t20 <span class="keyword">add</span> <span class="keyword">column</span> d <span class="type">varchar</span>(<span class="number">20</span>) <span class="keyword">not null</span> <span class="keyword">default</span> <span class="string">&#x27;&#x27;</span>;</span><br><span class="line"><span class="comment">-- 添加一个联合索引</span></span><br><span class="line"><span class="keyword">alter table</span> t20 <span class="keyword">add</span> index idx_abc(a, b, c);</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>添加之后组合索引B 树如下,其中索引key为abc三个字段的组合,索引存储的记录为主键ID:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img31.avif"></p><h5 id="覆盖索引-Using-index"><a href="#覆盖索引-Using-index" class="headerlink" title="覆盖索引(Using index)"></a>覆盖索引(Using index)</h5><p>InnoDB存储引擎支持覆盖索引,即从辅助索引中就可以得到查询的记录,而不需要回表去查询聚集索引中的记录,从而减少大量的IO操作。下面的查询既是用到了覆盖索引 idx_abc:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> a, b <span class="keyword">from</span> t20 <span class="keyword">where</span> a <span class="operator">&gt;</span> <span class="number">2</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>执行结果如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img32.avif"></p><p>可以发现,Extra这一列提示Using index,使用到了覆盖索引,扫描的行数为2。<strong>注意:这里的扫描行数指的是MySQL执行器从引擎取到两条记录,引擎内部可能会遍历到多条记录进行条件比较。</strong></p><h5 id="最左匹配原则"><a href="#最左匹配原则" class="headerlink" title="最左匹配原则"></a>最左匹配原则</h5><p>由于InnoDB索引式B 树构建的,因此可以利用索引的“最左前缀”来定位记录。</p><p>也就是说,不仅仅是用到索引的全部定义字段会走索引,只要满足最左前缀,就可以利用索引来加速检索。这个最左前缀可以是联合索引的最左n个字段。</p><h5 id="索引条件下推-Using-index-condition"><a href="#索引条件下推-Using-index-condition" class="headerlink" title="索引条件下推(Using index condition)"></a>索引条件下推(Using index condition)</h5><p>索引条件下推 Index Condition Pushdown (ICP),是针对MySQL使用索引从表中检索行的情况的一种优化。</p><p><strong>为什么叫下推呢,就是在满足要求的情况下,把索引的条件丢给存储引擎去判断,而不是把完整的记录传回My</strong>[SQL Server](<a href="https://cloud.tencent.com/product/sqlserver?from_column">https://cloud.tencent.com/product/sqlserver?from_column</a> 20065&amp;from 20065)<strong>层去判断。</strong></p><p>ICP支持<code>range</code>, <code>ref</code>, <code>eq_ref</code>, 和 <code>ref_or_null</code>类型的查找,支持MyISAM和InnoDB存储引擎。</p><p>不能将引用子查询的条件下推,触发条件不能下推。详细规则参考:Index Condition Pushdown <a href="https://dev.mysql.com/doc/refman/5.6/en/index-condition-pushdown-optimization.html">https://dev.mysql.com/doc/refman/5.6/en/index-condition-pushdown-optimization.html</a></p><p>如果不使用ICP,则存储引擎将遍历索引以在聚集索引中定位行,并将结果返回给MySQL Server层,MySQL Server层继续根据<code>WHERE</code>条件进行筛选行。</p><p>启用ICP后,如果<code>WHERE</code>可以仅使用索引中的列来评估部分条件,则MySQL Server层会将这部分条件压入<code>WHERE</code>条件下降到存储引擎。然后,存储引擎通过使用索引条目来判断索引条件,在满足条件的情况下,才回表去查找记录返回给MySQL Server层。</p><p><strong>ICP的目标是减少回表扫描的行数,从而减少I &#x2F; O操作。对于<code>InnoDB</code>表,ICP仅用于二级索引。</strong></p><p>使用索引下推的时候,执行计划中的Extra会提示:<code>Using index condition</code>,而不是<code>Using index</code>,因为必须回表查询整行数据。<code>Using index</code>代表使用到了覆盖索引。</p><h3 id="3-8、InnoDB-Data-Directory"><a href="#3-8、InnoDB-Data-Directory" class="headerlink" title="3.8、InnoDB Data Directory"></a>3.8、InnoDB Data Directory</h3><p>InnoDB数据字典(Data Directory)存放于系统表空间中,主要包含元数据,用于追踪表、索引、表字段等信息。由于历史的原因,InnoDB数据字典中的元数据与<code>.frm</code>文件中的元数据重复了。</p><h3 id="3-9、Doublewrite-Buffer"><a href="#3-9、Doublewrite-Buffer" class="headerlink" title="3.9、Doublewrite Buffer"></a>3.9、Doublewrite Buffer</h3><p>双写缓冲区(Doublewrite Buffer)是一个存储区,是InnoDB在tablespace上的128个页 2个区 ,大小是2MB[7]。</p><blockquote><p>版本区别:在MySQL 8.0.20之前,doublewrite缓冲区存储区位于<code>InnoDB</code>系统表空间中。从MySQL 8.0.20开始,doublewrite缓冲区存储区位于doublewrite文件中。 本文基于MySQL 5.7编写。</p></blockquote><p>操作系统写文件是以4KB为单位的,那么每写一个InnoDB的page到磁盘上,操作系统需要写4个块。如果写入4个块的过程中出现系统崩溃,那么会导致16K的数据只有一部分写是成功的,这种情况下就是<code>partial page write</code> 部分页写入 问题。</p><p>InnoDB这个时候是没法通过redo log来恢复的,因为这个时候页面的<code>Fil Trailer</code> Fil Trailer 主要存放<code>FIL_PAGE_END_LSN</code>,主要包含页面校验和以及最后的事务 中的数据是有问题的。</p><p>为此,每当InnoDB将页面写入到数据文件中的适当位置之前,都会首先将其写入双写缓冲区。只有将缓冲区安全地刷新到磁盘后,InnoDB才会将页面写入最终的数据文件。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img33.avif"></p><p>如果在页面写入过程中发生操作系统或者mysqld进程崩溃,则InnoDB可以在崩溃恢复期间从双写缓冲区中找到页面的完好副本用于恢复。恢复时,InnoDB扫描双写缓冲区,并为缓冲区中的每个有效页面检查数据文件中的页面是否完整。</p><p>如果系统表空间文件 “ ibdata文件 ” 位于支持原子写的Fusion-io设备上,则自动禁用双写缓冲,并且将Fusion-io原子写用于所有数据文件。</p><h3 id="3-10、Redo-Log"><a href="#3-10、Redo-Log" class="headerlink" title="3.10、Redo Log"></a>3.10、Redo Log</h3><p>重做日志(Redo Log)主要适用于数据库的崩溃恢复,用于实现数据的完整性。</p><p>重做日志由两部分组成:</p><ul><li>重做日志缓冲区 Log Buffer;</li><li>重做日志文件,重做日志文件在磁盘上由两个名为<code>ib_logfile0</code>和<code>ib_logfile1</code>的物理文件表示。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img34.avif"></p><p><strong>为了实现数据完整性,在脏页刷新到磁盘之前,必须先把重做日志写入到磁盘。除了数据页,聚集索引、辅助索引以及Undo Log都需要记录重做日志。</strong></p><h4 id="3-10-1、Redo-Log在事务中的写入时机"><a href="#3-10-1、Redo-Log在事务中的写入时机" class="headerlink" title="3.10.1、Redo Log在事务中的写入时机"></a><em>3.10.1、Redo Log在事务中的写入时机</em></h4><p>在事务中,除了写Redo log,还需要写binlog,为此,我们先来简单介绍下binlog。</p><h5 id="3-10-1-1、binlog"><a href="#3-10-1-1、binlog" class="headerlink" title="3.10.1.1、binlog"></a>3.10.1.1、binlog</h5><p>全写:Binary Log,二进制log。二进制日志是一组日志文件。其中包含有关对MySQL服务器实例进行的数据修改的信息。</p><p><strong>Redo Log是InnoDB引擎特有的,而binlog是MySQL的Server层实现的,所有引擎都可以使用。</strong></p><p><strong>Redo Log的文件是循环写的,空间会用完,binlog日志是追加写的,不会覆盖以前的日志。</strong></p><p><strong>binlog主要的目的:</strong></p><ul><li>主从同步,主服务器将二进制日志中包含的事件发送到从服务器,从服务器执行这些事件,以保持和主服务器相同的数据更改;</li><li>某些数据恢复操作需要使用二进制日志,还原到某一个备份点。</li></ul><p><strong>binlog主要是用于主从同步和数据恢复,Redo Log主要是用于实现事务数据的完整性,让InnoDB具有不会丢失数据的能力,又称为crash-safe。</strong></p><p><strong>binlog日志的两种记录形式:</strong></p><ul><li>基于SQL的日志记录:事件包含产生数据更改(插入,新增,删除)的SQL语句;</li><li>基于行的日志记录:时间描述对单个行的更改。</li></ul><p>混合日志记录默认情况下使用基于语句的日志记录,但根据需要自动切换到基于行的日志记录。</p><h5 id="3-10-1-2、Redo-Log在事务中的写入时机"><a href="#3-10-1-2、Redo-Log在事务中的写入时机" class="headerlink" title="3.10.1.2、Redo Log在事务中的写入时机"></a>3.10.1.2、Redo Log在事务中的写入时机</h5><p>简单的介绍完binlog,我们再来看看Redo Log的写入流程。</p><p>假设我们这里执行一条sql</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">update</span> t20 <span class="keyword">set</span> a <span class="number">10</span> <span class="keyword">where</span> id <span class="number">1</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>执行流程如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img35.avif"></p><h4 id="3-10-2、如何保证数据不丢失"><a href="#3-10-2、如何保证数据不丢失" class="headerlink" title="3.10.2、如何保证数据不丢失"></a><em>3.10.2、如何保证数据不丢失</em></h4><p>前面我们介绍<code>Log Buffer</code>的时候,提到过,为了保证数据不丢失,我们需要执行以下操作:</p><ul><li>如果启用了binlog,则设置:sync_binlog 1;</li><li>innodb_flush_log_at_trx_commit 1;</li></ul><blockquote></blockquote><ul><li>sync_binlog 0:表示每次提交事务都只 write,不 fsync;</li><li>sync_binlog 1:表示每次提交事务都会执行 fsync;</li><li>sync_binlog N(N&gt;1) :表示每次提交事务都 write,但累积 N 个事务后才 fsync。</li></ul><p>这两个的作用相当于在上面的流程最后一步,提交事务接口返回Server层之前,把binlog cache和log buffer都fsync到磁盘中了,这样就保证了数据的落盘,不会丢失,即使奔溃了,也可以通过binlog和redo log恢复数据相关流程如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img36.avif"></p><p>在磁盘和内存中的处理流程如下面编号所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img37.avif"></p><p><strong>其中第四步log buffer持久化到磁盘的时机为:</strong></p><ul><li>log buffer占用的空间即将达到<code>innodb_log_buffer_size</code>一半的时候,后台线程主动写盘;</li><li>InnoDB后台有个线程,每隔1秒会把log buffer刷到磁盘;</li><li>由于log buffer是所有线程共享的,当其他事务线程提交时也会导致已写入log buffer但还未提交的事务的redo log一起刷新到磁盘</li></ul><p><strong>其中第五步:脏页刷新到磁盘的时机为:</strong></p><ul><li>系统内存不足,需要淘汰脏页的时候,要把脏页同步回磁盘;</li><li>MySQL空闲的时候;</li><li>MySQL正常关闭的时候,会把脏页flush到磁盘。</li></ul><blockquote><p>参数<code>innodb_max_dirty_pages_pct</code>是脏页比例上限,默认值是 75%。</p></blockquote><p><strong>为什么第二步 redo log prepare状态也要写磁盘?</strong></p><p>因为这里先写了,才能确保在把binlog写到磁盘后崩溃,能够恢复数据:如果判断到redo log是prepare状态,那么查看是否存XID对应的binlog,如果存在,则表示事务成功提交,需要用prepare状态的redo log进行恢复。</p><p><strong>这样即使崩溃了,也可以通过redo log来进行恢复了,恢复流程如下:</strong></p><p>Redo Log是循环写的,如下图:</p><ul><li>writepos记录了当前写的位置,一边写位置一边往前推进,当writepos与checkpoint重叠的时候就表示logfile写满了,绿色部分表示是空闲的空间,红色部分是写了redo log的空间;</li><li>checkpoint处标识了当前的<code>LSN</code>,每当系统崩溃重启,都会从当前checkpoint这个位置执行重做日志,根据重做日志逐个确认数据页是否没问题,有问题就通过redo log进行修复。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img38.avif"></p><blockquote><p>LSN Log Sequence Number的缩写。代表日志序列号。在InnoDB中,LSN占用8个字节,单调递增,LSN的含义:</p></blockquote><ul><li>重做日志写入的总量;</li><li>checkpoint的位置;</li><li>页的版本;</li></ul><p>除了重做日志中有LSN,每个页的头部也是有存储了该页的LSN,我们前面介绍页面格式的时候有介绍过。 在页中LSN表示该页最后刷新时LSN的大小。[8]</p><h3 id="3-11、Undo-Logs"><a href="#3-11、Undo-Logs" class="headerlink" title="3.11、Undo Logs"></a>3.11、Undo Logs</h3><p>上面说的<strong>redo log记录了事务的行为,可以通过其对页进行重做操作,但是食物有时候需要进行回滚,这时候就需要undo log了</strong>。[15]</p><p>**关于Undo Log的存储:**InnoDB中有回滚段(rollback segment),每个回滚段记录1024个undo log segment,在每个undo log segment段中进行申请undo页。系统表空间偏移量为5的页记录了所有的rollback segment header所在的页。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img39.avif"></p><h4 id="3-11-1、undo-log的格式"><a href="#3-11-1、undo-log的格式" class="headerlink" title="3.11.1、undo log的格式"></a><em>3.11.1、undo log的格式</em></h4><p>根据行为不同分为两种:</p><p><strong>insert undo log</strong></p><p><code>insert undo log</code>:只对事务本身可见,所以insert undo log在事务提交后可直接删除,无需执行purge操作;</p><p>insert undo log主要记录了:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img40.avif"></p><p>假设在事务1001中,执行以下sql,t20的table_id为10:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">insert into</span> t20(id, a, b, c, d) <span class="keyword">values</span>(<span class="number">12</span>, <span class="number">2</span>, <span class="number">3</span>, <span class="number">1</span>, init )</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>那么对应会生成一条undo log:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img41.avif"></p><p><strong>update undo log</strong></p><p><code>update undo log</code>:执行update或者delete会产生undo log,会影响已存在的记录,为了实现MVCC(后边介绍),update undo log不能再事务提交时立刻删除,<strong>需要将事务提交时放入到history list上,等待purge线程进行最后的删除操作。</strong></p><p>update undo log主要记录了:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img42.avif"></p><p>假设在事务1002中,执行以下sql,t20的table_id为10:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">update</span> t20 <span class="keyword">set</span> d update1 <span class="keyword">where</span> id <span class="number">60</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>那么对应会生成一条undo log:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img43.avif"></p><p>如上图,<strong>每回退应用一个undo log,就回退一个版本,这就是MVCC(Multi versioning concurrency control)的实现原理。</strong></p><p>下面我们在执行一个delete sql:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">delete</span> <span class="keyword">from</span> t20 <span class="keyword">where</span> id <span class="number">60</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>复制</p><p>对应的undo log变为如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img44.avif"></p><p>如上图,实际的行记录不会立刻删除,而是在行记录头信息记录了一个<code>deleted_flag</code>标志位。最终会在purge线程purge undo log的时候进行实际的删除操作,这个时候undo log也会清理掉。</p><h4 id="3-11-2、MVCC实现原理"><a href="#3-11-2、MVCC实现原理" class="headerlink" title="3.11.2、MVCC实现原理"></a><em>3.11.2、MVCC实现原理</em></h4><p>如上图所示,MySQL只会有一个行记录,但是会把每次执行的sql导致行记录的变动,通过undo log的形式记录起来,undo log通过回滚指针连接在一起,这样我们想回溯某一个版本的时候,就可以应用undo log,回到对应的版本视图了。</p><p>我们知道InnoDB是支持<code>RC</code>(Read Commit)和<code>RR</code>(Repeatable Read)事务隔离级别的,而这个是通过<code>一致性视图</code>(consistent read view)实现的。</p><p>一个事务开启瞬间,所有活跃的事务(未提交)构成了一个视图数组,InnoDB就是通过这个视图数组来判断行数据是否需要undo到指定的版本:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img45.avif"></p><h6 id="RR事务隔离级别"><a href="#RR事务隔离级别" class="headerlink" title="RR事务隔离级别"></a><strong>RR事务隔离级别</strong></h6><p>假设我们使用了<strong>RR事务隔离级别</strong>。我们看个例子:</p><p>如下图,假设id 60的记录a 1</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img46.avif"></p><p>事务C启动的瞬间,活跃的事务如下图黄色部分所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img47.avif"></p><p>也就是对于事务A、事务B、事务C,他们能够看到的数据只有是行记录中的最大事务ID<code>DATA_TRX_ID</code>&lt; 11的,如果大于,那么只能通过undo进行回滚了。如果TRX_ID 当前事务id,也可以看到,即看到自己的改动。</p><p>另外有一个需要注意的:</p><ul><li><strong>在RR隔离级别下,当事务更新事务的时候,只能用当前读来获取最新的版本数据来更新,如果当前记录的行锁被其他事务占用,就需要进入所等待;</strong></li><li><strong>在RC隔离级别下,每个语句执行都会计算出新的一致性视图。</strong></li></ul><p>所以我们分析上面的例子的执行流程:</p><ul><li>事务C执行update,执行当前读,拿到的a 1,然后 1,最终a 2,同时添加一个TRX_ID 11的undo log;</li><li></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img48.avif"></p><ul><li>事务B执行select,使用快照读,记录的DATA_TRX_ID &gt; 11,所以需要通过undo log回滚到DATA_TRX_ID 11的版本,所以拿到的a是1;</li><li>事务B执行update,需要使用当前读,拿到最新的记录,a 2,然后加1,最终a 3;</li><li></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img49.avif"></p><ul><li>事务B执行select,拿到当前最新的版本,为自己的事务id,所以得到a 3;</li><li>事务A执行select,使用快照读,记录的DATA_TRX_ID &gt; 11,所以需要通过undo log回滚到DATA_TRX_ID 11的版本,所以拿到的a是1。</li><li>如果是RC隔离级别,执行select的时候会计算出新的视图,新的视图能够看到的最大事务ID 14,由于事务B还没提交,事务C提交了,所以可以得到a 2:</li><li></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img50.avif"></p><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><ul><li>数据完整性依靠:redo log</li><li>事务隔离级别的实现依靠MVCC,MVCC依靠undo log实现</li><li>IO性能提升方式:buffer pool加快查询效率和普通索引更新的效率,log buffer对日志写的性能提升</li><li>查询性能提升依赖于索引,底层用页存储,字段越小页存储越多行记录,查询效率越快;自增字段作为聚集索引可以加快插入操作;</li><li>故障恢复:双写缓冲区、redo log</li><li>主从同步:binlog</li></ul><p>本文内容比较多,看完之后需要多梳理,最后大家可以对照着这个思维导图回忆一下,这些内容是否都记住了:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img51.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img52.avif"></p><blockquote><p> 这篇文章的内容就差不多介绍到这里了,能够阅读到这里的朋友真的是很有耐心,为你点个赞。</p></blockquote>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/02/ac6408c4/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>一篇文章让你了解MySQL中的索引</title>
      <link>https://blog.eucalyptus.cc/2023/11/02/34360ed9/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/02/34360ed9/</guid>
      <pubDate>Thu, 02 Nov 2023 05:51:40 GMT</pubDate>
      
        
        
          
          
      <description>&lt;ul&gt;
&lt;li&gt;索引是怎么提高查询效率的?可以为了提高查询效率增加索引么?&lt;/li&gt;
&lt;li&gt;mysql索引系统采用的数据结构是什么?&lt;/li&gt;
&lt;li&gt;为什么要使用B</description>
          
        
      
      
      
      <content:encoded><![CDATA[<ul><li>索引是怎么提高查询效率的?可以为了提高查询效率增加索引么?</li><li>mysql索引系统采用的数据结构是什么?</li><li>为什么要使用B 树?</li><li>聚集索引相对于非聚集索引的区别?</li><li>什么是回表?</li><li>什么是索引覆盖?</li><li>什么是最左匹配原则?</li><li>索引失效场景有哪些,如何避免?</li></ul><h2 id="索引原理探究"><a href="#索引原理探究" class="headerlink" title="索引原理探究"></a>索引原理探究</h2><p>什么是数据库索引?先来个官方一些的定义吧。</p><p><strong>官方解释</strong>:在关系数据库中,索引是一种<strong>单独的、物理的</strong>对数据库表中一列或多列的值进行<strong>排序</strong>的一种<strong>存储结构</strong>,它是某个表中一列或若干列值的集合和相应的指向表中物理标识这些值的数据页的<strong>逻辑指针</strong>清单。索引的作用相当于图书的目录,可以根据目录中的页码<strong>快速找到所需的内容</strong>。</p><p>索引不是mysql特有的,涉及到任何文件、数据查找的系统都有,比如windows操作系统也有索引的存在,帮助我们更加快速的找到对应的文件。</p><p>为了可以让查找的速度提升,那<strong>树</strong>就是一种很好数据结构。mysql在索引的设计上采用的就是采用B 树的结构来对数据进行排序存储,不管是聚簇索引 辅助索引 联合索引,本质上都是在b 树的结构上进行查找。</p><p><strong>既然提到了B 树,还是要拓展一下</strong>,为啥B 树会作为主流数据结构。树的类型有这么多,为啥用B 树呢?那下面列举几种常见的 树 。</p><h2 id="数据结构"><a href="#数据结构" class="headerlink" title="数据结构"></a>数据结构</h2><h3 id="普通二叉树"><a href="#普通二叉树" class="headerlink" title="普通二叉树"></a>普通二叉树</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img1.avif"></p><p>​</p><p>它是一颗普普通通的树,特点:</p><ul><li>左边的字节点一定小于右边的子节点;</li><li>每个节点最多有2个叶子结点。</li></ul><p>用了这种结构,再也不用顺序io了,可以通过<strong>折半查找</strong>来查询我们想要的数据,插入和查找的时间复杂度变成了O(log(N)),确实一定程度上减缓了io次数。 缺点:但是<strong>容易失衡</strong>,就像这样。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img2.avif"></p><p>​</p><p>随着数据量越来越大,树阶越来越高,查询次数和io大幅提升啊。所以这种 肯定不适合mysql。那就需要优化一下,来个平衡二叉树,每次写入的时候判断左右两个节点的层级差不能超过1层不就行了,否则就左旋或者右旋自动平衡。</p><h3 id="平衡二叉树"><a href="#平衡二叉树" class="headerlink" title="平衡二叉树"></a>平衡二叉树</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img3.avif"></p><p>​</p><p>这样看起来是平衡了,但是如果节点增多了,树阶还是会增多,io次数又要上去了。所以这也不适合mysql。 缺点:每个节点下的子节点只能有两个,树阶还是高。​</p><h3 id="B树"><a href="#B树" class="headerlink" title="B树"></a>B树</h3><p>基于平衡二叉树继续优化一下,让每个节点下可以放的叶子节点多一些,树高降低,io也就降下来了。</p><p>这个时候就需要B树(也叫平衡多路查找树),这里要注意这个(多路),我们在描述一个B书的时候,一般需要指定树阶,也就是一个节点下最多能存在几个孩子节点,下面看一下三阶的。 如下图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img4.avif"></p><p>​</p><p>这样看来树已经平衡,而且多路也可以降低树的高度。你可能有个大胆的想法,把数据都存在一个叶子节点上,是不是1亿数据最多也只要io三次就够了。</p><p>这时候要先引出一下<strong>mysql是如何于磁盘交互</strong>来读取数据的。</p><p>上面提到的存储引擎(innodb、myIsam),<strong>它的基础存储单位是页</strong>。 当我们发送查询指令,mysql会从磁盘读取数据,但是磁盘io效率极差,所以这里有一些小的优化措施,mysql在做一次读取的时候除了会加载需要读取数据,还会将地址附近的数据一起加载出来,这个动作叫<strong>预读</strong>。而mysql<strong>一次可以加载出来的数据就是</strong>16KB**,所以一页的大小就是16K(注意看我上图画的,每一个大方块代表一页,一页里面的内容就是一次io读取出来的数据),这样就可以根据你每个key的大小推算出来一个节点能放多少路的数据了。 但是除了key,<strong>B树的行数据也是存在每节点上的</strong>,看看一条行数据的大小,就能推算出一个节点的数据有多大了,数据大了,那一页上能存放的数据就少了,那节点就会多,节点多了,树又高了(套娃警告)。</p><p>​</p><h3 id="B-树"><a href="#B-树" class="headerlink" title="B 树"></a>B 树</h3><p>所以为了让每个节点上尽可能的多存放数据,就要<strong>缩衣节食</strong>。B 树就在节点的数据存储上继续优化,他们唯一的区别就是,B 树在非叶子节点上不再存在数据,只存放指针地址。如下图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img5.avif"></p><p>​</p><p>从B树和B 树的结构图可以看出,两者在树结构上的差别不大,都是多路平衡查找树,区别在于以下两点:</p><ul><li>B 树所有的非叶子节点上就只有key了,而data只存放在叶子节点,每个非页子节点上的数据占用的空间就少了,再算下16KB能放多少数据了。<strong>B 树三层的高度就可以存放2000万的数据,每条数据如果在1kb左右</strong>。</li></ul><p>首先我们算出非叶子节点能放多少指针,一个指针的大小是6bit,id如果是integer类型是8bit,一共14bit,一页是16kb,也就是16384bit,当 B 树的高度为 1 时,即树只有一个非叶子节点 根节点 ,它可以存储 1170 个指针,每个指针指向一个叶子节点,每个叶子节点可以存储 16 行数据,因此总共可以存储 1170 * 16 18720 行数据,当 B 树的高度为 2 时,根节点可以存储 1170 个指针,每个指针指向一个非叶子节点,每个非叶子节点又可以存储 1170 个指针指向叶子节点。因此,总共可以存储的行数是 1170 * 1170 * 16 18720 * 1170 21902400 行数据。也就是说在一棵三阶的B 树就可以放2000万的数据量级以内,3次io即可查询到。B树同理,只不过B树非叶子节点不止有id,还有数据,一页就不止是8 6 14了,可能会更大,所以相同树高存的东西也就少了。 拓展点: 如果超过这个数量,io次数又会增加,所以我们在设计表的时候需要清楚的知道每一行的数据有多大,来保证每张表在三层树高的情况下最多能存放多少数据,超过这个量级,可能就需要引入一些分表、或者数据迁移的工作,这也是大表优化的一些手段。</p><ul><li>同时B树还存在一个缺点,范围查询效率不高,因为当你查到子节点的时候发现没路了,那需要重新返回根节点再次遍历,而在B 树中,可以看到每个叶子节点之间用双向指针连接,这样当进行范围查询,就可以通过叶子节点的双向指针来进行快速的查找了。</li></ul><p>索引的基础结构B 树以及B 树的好处介绍完了,索引快(利用树形结构和折半查找)的原因就大致清楚了吧。接下来再来看看具体的索引类型。</p><p><strong>拓展点</strong>:除了树形结构,索引比较常见的还有hash表结构,和java中的hashMap类似,以键值对的方式存储数据,key存放索引字段,value就存储行数据或地址。hash结构通过index获取地址的查询效率是非常之高的,时间复杂度是O(1),但是缺点就是无法支持范围查询,所以适用的场景不了,了解一下就好了。</p><h2 id="索引类型"><a href="#索引类型" class="headerlink" title="索引类型"></a>索引类型</h2><p>首先索引分为两大块</p><ul><li>聚集索引(也叫主键索引或聚簇索引)</li><li>非聚集索引(辅助索引、联合索引、全文索引等都是非聚集索引)</li></ul><p>为啥这么这么分,且往下看</p><h3 id="InnoDB的索引"><a href="#InnoDB的索引" class="headerlink" title="InnoDB的索引"></a>InnoDB的索引</h3><h4 id="聚簇索引"><a href="#聚簇索引" class="headerlink" title="聚簇索引"></a>聚簇索引</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#查看一张表中的索引情况</span><br><span class="line"><span class="keyword">SHOW</span> INDEX <span class="keyword">FROM</span> table_name;</span><br></pre></td></tr></table></figure><p>聚集索引就是我们所说的主键索引,如果没有主键,innodb就会自动创建一个rowId来构建聚簇索引,平时也许我们都知道主键索引查询效率最高,但是这又是为啥呢?首先innodb才有聚集索引(myisam没有真正意义上的聚集索引,具体后面会说到)。看这张图。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img6.avif"></p><p>​</p><p>当我们要查询36的时候,首先进行两次io,查找到了这个id所在的位置,B 树的叶子节点可以直接存放数据,所以就直接定位到id所对应的行数据。</p><p>IO总次数:3次</p><h4 id="辅助索引"><a href="#辅助索引" class="headerlink" title="辅助索引"></a>辅助索引</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#创建辅助索引</span><br><span class="line"><span class="keyword">ALTER TABLE</span> table_name <span class="keyword">ADD</span> INDEX index_name (<span class="keyword">column</span>);</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img7.avif"></p><p>​</p><p>这次用非主键字段来查,可以看到辅助索引的叶子节点只会存放id,然后根据指针再去主键索引中查到对应的行数据(这里的步骤和上面的主键索引查询步骤一样了)。 IO次数:最多6次</p><p><strong>拓展点</strong>: 这个重新根据主键id去查询行数据的行为被称为<strong>回表查询</strong>。所以知道为啥叫辅助了,辅助就是先找到大哥(主键),再根据主键去查到最终想要的数据。(不准抢人头)。当然这个也有优化的方案,后面会说。</p><p><strong>说到这里可以再点一下题</strong>,上面这样分的原因。方便大家记住,innodb下主键索引和非主键索引的主要区别就在于这里,主键索引直接可以拿到行数据,<strong>而非主键索引都需要回表</strong>,所以会增加Io次数,这就说明了为什么主键索引的速度最快。</p><h4 id="联合索引"><a href="#联合索引" class="headerlink" title="联合索引"></a>联合索引</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">#创建联合索引</span><br><span class="line"><span class="keyword">ALTER TABLE</span> table_name <span class="keyword">ADD</span> INDEX index_name(column1,column2, column3);</span><br></pre></td></tr></table></figure><p>当我们的where语句后面跟着的条件有多个的时候,就要用到联合索引了,多个查询字段组合在一起的索引被称为联合索引,先看下联合索引的结构和查询路径</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img8.avif"></p><p>​</p><p>IO次数:最多6次。</p><p><strong>拓展点:最左匹配原则。</strong> 联合索引是怎么进行排序的呢?根据你联合索引的数量,比如abc三个索引,先根据a排序,在a相等的情况下,再根据b排序,a、b都相等的情况下,再根据c排序,<strong>当你建立联合索引(a、b、c)的同时,等价于建立了(a)(a、b)(a、b、c)三个索引</strong>,所以当where后面的条件要使联合索引生效,条件必须根据这个顺序来,即必须要有a,再有b,再有c,如果哪个索引漏了,那后面的条件就都失效了。<strong>为什么直接来个b、c就不生效了呢?你想啊,我的排序是要从a开始的,只有保障了a的有序才能查b,单看b的排序是杂乱无章</strong>,那你直接给我塞个我应该从哪里走?只能全表扫描了呀。所以索引也就失效了。 <strong>但是你说我a、b换下位置可不可以</strong>,比如select * from table where a xx and b xx或者select * from table where b xx and a xx,这样是可以的,mysql没这么傻这样就认不出来了,<strong>查询优化器会帮你把位置调整过来的</strong>.</p><h4 id="覆盖索引"><a href="#覆盖索引" class="headerlink" title="覆盖索引"></a>覆盖索引</h4><p>上面说到,非主键索引的查询都会有一次回表,那有办法让他不回表吗,可以,那就是查询的同时将索引的值带入select后面的字段中,这样你查询的行数据就直接再你的条件中了呀,还回啥表。</p><p>注意,这种场景其实不常用,很多查询场景下其实我们需要很多字段的,不可能将所有的字段都设置索引,所以还是要分场景,不要为了覆盖而搞了一大堆索引,索引也是有成本的,有写入成本,存储成本。只有所需字段比较少且是热点数据的情况下,才可能需要这么设置。</p><p>以上,索引的基本内容就介绍完了,下面再说一下和索引有密切关系的一个内容。</p><h3 id="myisam的索引"><a href="#myisam的索引" class="headerlink" title="myisam的索引"></a>myisam的索引</h3><p>刚刚在说主键索引的时候,提到了innodb和myiSam。 它们的索引区别就在于myIsam可以理解为只有辅助索引,因为它的叶子节点是不存放数据的,而是只存放数据的指针。 看图:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img9.avif"></p><p>​</p><p>IO次数:4次。 这里和innodb的辅助索引还是有一丢丢区别!<strong>它拿到指针后直接去磁盘拿到对应的数据,没有回表了</strong>,但是还是多一次io。所以查询的时候效率会相对来说低一些。(但是他们都是B 树,有些人会搞混,觉得myiSam不存在数据就不是B 树,是不是B 树取决于你的叶子节点是否只存放指针)。</p><p>它的其他索引就不画了,因为不管是主键索引还是辅助索引。查询路径和这个一样,都是找到地址后再去查一遍。</p><p>myisam不支持主键索引不代表它就不能设置主键索引了 myisam的也有主键索引,但是主要是用来标示字段唯一,刚刚也提到,它没有真正意义上的聚集索引,是因为它除了唯一性以外查询路径和结构基本一样,不要搞浑说它没主键索。</p><h3 id="存储引擎"><a href="#存储引擎" class="headerlink" title="存储引擎"></a>存储引擎</h3><p>本期内容我们只关注存储文件区别,这和我们的上面说到的他们的索引区别有关系</p><p>先说myIsam和innodb索引文件上的区别。 myIsam的表有三个文件: - tableName.frm:表结构文件 - tableName.MYD:数据文件 MyISAM Data - tableName.MYI:索引文件 MyISAM Index</p><p>Innodb的表有两个文件: - tableName.frm:表结构文件 - tableName.ibd:索引和数据文件 InnoDB Data 。</p><p>从这个物理文件的区别也就可以看出为什么myIsam的没有主键索引,因为它的索引和数据物理文件就是分开的,拿到地址必须再去数据文件中获取具体的行数据内容。</p><h2 id="索引的管理"><a href="#索引的管理" class="headerlink" title="索引的管理"></a>索引的管理</h2><p>索引的原理探究到此结束,这部分内容堪称最难啃的骨头。不过,能坚持读下来的朋友,你的收获也一定良多。接下来的内容就轻松愉悦多了。​</p><h3 id="索引的优化"><a href="#索引的优化" class="headerlink" title="索引的优化"></a>索引的优化</h3><p>上面的索引基本都介绍完了,那是不是无脑上索引就可以了,万事大吉。万万不可 首先索引会带来两个缺陷:</p><ul><li>刚刚提到不同存储引擎的索引文件不一样的,但是他们都是需要占用物磁盘理空间的,每一条数据的增加都是增加一个索引,随意的添加索引导致磁盘空间的过度占用。</li><li>因为每次的写入和删除都会调整索引,所以在删写频繁的时候也会影响到吞吐量,提升db的负荷。</li></ul><p>其次:索引也会存在很多建立了之后不生效的情况,除了上述说到的最左匹配,还有诸如以下</p><ul><li>隐式转换-查询条件的数据类型和字段的数据类型不匹配。</li><li>查询条件有is null、is not null 不走索引。</li><li>查询条件是用函数或计算操作。比如concat(‘jingxi’,1)不走索引;</li><li>or条件,任意一个or连接的条件没有索引,就会失效。</li><li>查询优化器的成本计算导致不走索引。</li><li>这些原因有部分通过上面的分析应该可以推断出原因,这里就不细说了比较固定,可以通过explan去查看这条sql是否走了索引,走了什么索引。</li></ul><p>下面是关于索引优化的几条建议</p><ul><li>避免过度索引:过多的索引会增加数据库的存储和维护成本,同时也会影响数据库的性能。因此,在建立索引时,应该根据实际查询场景进行决定,尽量避免过度索引。</li><li>建立复合索引:对于经常需要同时查询多个列的语句,建立复合索引可以有效地提高查询效率。需要注意的是,复合索引的建立顺序需要根据实际查询场景进行决定。</li><li>使用覆盖索引:覆盖索引是指查询语句只需要使用索引就可以获取需要的数据,而不需要回表操作。覆盖索引可以减少MySQL的I&#x2F;O操作,从而提高查询效率。</li><li>避免使用函数在索引列上进行计算:在查询语句中,应尽量避免在索引列上使用函数进行计算,因为这样会使MySQL无法使用索引,而需要进行全表扫描。</li><li>定期维护索引:定期维护索引可以清理无用的索引,以保证数据库的正常运行。例如,可以使用OPTIMIZE TABLE语句来对表进行优化,以清理无用的索引和碎片。</li></ul><p>索引优化案例</p><p>下面,我将通过一个具体案例来说明如何优化MySQL索引。</p><p>假设我们有一个用户表,包含用户的ID、姓名、年龄、性别、所在城市、注册时间等信息。现在,我们需要查询年龄大于20岁、所在城市为北京、注册时间在2019年以后的用户。</p><p>首先,我们可以通过以下语句来查询这些用户:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> users <span class="keyword">WHERE</span> age <span class="operator">&gt;</span> <span class="number">20</span> <span class="keyword">AND</span> city <span class="string">&#x27;北京&#x27;</span> <span class="keyword">AND</span> reg_time <span class="operator">&gt;</span> <span class="string">&#x27;2019-01-01&#x27;</span>;</span><br></pre></td></tr></table></figure><p>接下来,我们需要对这个查询语句进行优化。首先,我们可以对age和city列建立复合索引,以避免回表操作。同时,由于我们需要查询注册时间在2019年以后的用户,因此我们还需要对reg_time列建立单独的索引。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> users <span class="keyword">ADD</span> INDEX idx_age_city (age, city);</span><br><span class="line"><span class="keyword">ALTER TABLE</span> users <span class="keyword">ADD</span> INDEX idx_reg_time (reg_time);</span><br></pre></td></tr></table></figure><p>建立完索引后,我们可以再次执行查询语句,查看查询性能的提升情况:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> users <span class="keyword">WHERE</span> age <span class="operator">&gt;</span> <span class="number">20</span> <span class="keyword">AND</span> city <span class="string">&#x27;北京&#x27;</span> <span class="keyword">AND</span> reg_time <span class="operator">&gt;</span> <span class="string">&#x27;2019-01-01&#x27;</span>;</span><br></pre></td></tr></table></figure><p>在执行上述查询语句时,MySQL将使用idx_age_city和idx_reg_time索引进行查询,并避免回表操作,从而大大提高查询效率。希望这个具体案例能够帮助你更好地理解MySQL索引优化。</p><h3 id="索引的查看"><a href="#索引的查看" class="headerlink" title="索引的查看"></a>索引的查看</h3><p>查看索引的语法格式如下:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> INDEX <span class="keyword">FROM</span> <span class="operator">&lt;</span>表名<span class="operator">&gt;</span></span><br></pre></td></tr></table></figure><p>创建索引的方式有三种:</p><h4 id="create-index直接创建"><a href="#create-index直接创建" class="headerlink" title="create index直接创建"></a>create index直接创建</h4><p>可以使用专门用于创建索引的 CREATE INDEX 语句在一个已有的表上创建索引,但该语句不能创建主键。</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="operator">&lt;</span>索引名<span class="operator">&gt;</span> <span class="keyword">ON</span> <span class="operator">&lt;</span>表名<span class="operator">&gt;</span> (<span class="operator">&lt;</span>列名<span class="operator">&gt;</span> [<span class="operator">&lt;</span>长度<span class="operator">&gt;</span>] [ <span class="keyword">ASC</span> <span class="operator">|</span> <span class="keyword">DESC</span>])</span><br></pre></td></tr></table></figure><p>语法说明如下:</p><ul><li>&lt;索引名&gt;:指定索引名。一个表可以创建多个索引,但每个索引在该表中的名称是唯一的。</li><li>&lt;表名&gt;:指定要创建索引的表名。</li><li>&lt;列名&gt;:指定要创建索引的列名。通常可以考虑将查询语句中在 JOIN 子句和 WHERE 子句里经常出现的列作为索引列。</li><li>&lt;长度&gt;:可选项。指定使用列前的 length 个字符来创建索引。使用列的一部分创建索引有利于减小索引文件的大小,节省索引列所占的空间。在某些情况下,只能对列的前缀进行索引。索引列的长度有一个最大上限 255 个字节 MyISAM 和 InnoDB 表的最大上限为 1000 个字节 ,如果索引列的长度超过了这个上限,就只能用列的前缀进行索引。另外,BLOB 或 TEXT 类型的列也必须使用前缀索引。</li><li>ASC|DESC:可选项。ASC指定索引按照升序来排列,DESC指定索引按照降序来排列,默认为ASC。</li></ul><p>例如,在student表name字段上创建索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#普通索引</span><br><span class="line"><span class="keyword">CREATE</span> INDEX index_name <span class="keyword">ON</span> student (name);</span><br><span class="line">#唯一索引</span><br><span class="line"><span class="keyword">CREATE</span> <span class="keyword">UNIQUE</span> index_name <span class="keyword">ON</span> student (name);</span><br></pre></td></tr></table></figure><p>创建普通索引使用的关键字,例如在student表name字段上创建一个普通索引index_name</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">#建表创建</span><br><span class="line"><span class="keyword">CREATE TABLE</span> student(id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,name <span class="type">CHAR</span>(<span class="number">45</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,INDEX(name));</span><br><span class="line">#<span class="keyword">ALTER TABLE</span></span><br><span class="line"><span class="keyword">ALTER</span> student <span class="keyword">ADD</span> INDEX index_name (name)</span><br></pre></td></tr></table></figure><h4 id="CREATE-TABLE时创建"><a href="#CREATE-TABLE时创建" class="headerlink" title="CREATE TABLE时创建"></a><strong>CREATE TABLE时创建</strong></h4><p>索引也可以在创建表 CREATE TABLE 的同时创建。在 CREATE TABLE 语句中添加以下语句。例如创建student表时在name字段添加索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">#主键索引</span><br><span class="line"><span class="keyword">CREATE TABLE</span> student(name <span class="type">CHAR</span>(<span class="number">45</span>) <span class="keyword">PRIMARY KEY</span>);</span><br><span class="line">#唯一索引</span><br><span class="line"><span class="keyword">CREATE TABLE</span> student(id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,name <span class="type">CHAR</span>(<span class="number">45</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,<span class="keyword">UNIQUE</span> INDEX(name));</span><br><span class="line">#普通索引</span><br><span class="line"><span class="keyword">CREATE TABLE</span> student(id <span class="type">INT</span> <span class="keyword">NOT NULL</span>,name <span class="type">CHAR</span>(<span class="number">45</span>) <span class="keyword">DEFAULT</span> <span class="keyword">NULL</span>,INDEX(name));</span><br></pre></td></tr></table></figure><h4 id="ALTER-TABLE时创建"><a href="#ALTER-TABLE时创建" class="headerlink" title="ALTER TABLE时创建"></a><strong>ALTER TABLE时创建</strong></h4><p>ALTER TABLE 语句也可以在一个已有的表上创建索引。例如在student表name字段上创建一个普通索引index_name:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">#主键索引</span><br><span class="line"><span class="keyword">ALTER TABLE</span> student <span class="keyword">ADD</span> <span class="keyword">PRIMARY KEY</span> (name);</span><br><span class="line">#唯一索引</span><br><span class="line"><span class="keyword">ALTER TABLE</span> student <span class="keyword">ADD</span> <span class="keyword">UNIQUE</span> INDEX index_name(name);</span><br><span class="line">#普通索引</span><br><span class="line"><span class="keyword">ALTER TABLE</span> student <span class="keyword">ADD</span> INDEX index_name(name);</span><br></pre></td></tr></table></figure><h4 id="索引的删除"><a href="#索引的删除" class="headerlink" title="索引的删除"></a>索引的删除</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">drop</span> index indexname <span class="keyword">on</span> tablename;</span><br></pre></td></tr></table></figure><h2 id="补充说明"><a href="#补充说明" class="headerlink" title="补充说明"></a>补充说明</h2><p>那当我们执行了一条查询语句的时候是怎么判断它到底有没有使用索引呐?</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line">mysql<span class="operator">&gt;</span> explain <span class="keyword">select</span> name,age,sex,mail <span class="keyword">from</span> <span class="keyword">user</span> <span class="keyword">where</span> name <span class="string">&#x27;lisi&#x27;</span>;</span><br><span class="line"><span class="comment">---- ------------- ------- ------------ ------ ------------------- ------------------- --------- ------- ------ ---------- -------------</span></span><br><span class="line"><span class="operator">|</span> id <span class="operator">|</span> select_type <span class="operator">|</span> <span class="keyword">table</span> <span class="operator">|</span> partitions <span class="operator">|</span> type <span class="operator">|</span> possible_keys <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> key <span class="operator">|</span> key_len <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> <span class="keyword">rows</span> <span class="operator">|</span> filtered <span class="operator">|</span> Extra <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="number">1</span> <span class="operator">|</span> SIMPLE <span class="operator">|</span> <span class="keyword">user</span> <span class="operator">|</span> <span class="keyword">NULL</span> <span class="operator">|</span> <span class="keyword">ref</span> <span class="operator">|</span> name_age_sex_mail <span class="operator">|</span></span><br><span class="line"><span class="operator">|</span> <span class="comment">--- | --- | --- | --- | --- | --- |</span></span><br><span class="line"><span class="operator">|</span> name_age_sex_mail <span class="operator">|</span> <span class="number">43</span> <span class="operator">|</span> const <span class="operator">|</span> <span class="number">3</span> <span class="operator">|</span> <span class="number">100.00</span> <span class="operator">|</span> <span class="keyword">Using</span> index <span class="operator">|</span></span><br><span class="line"><span class="number">1</span> <span class="type">row</span> <span class="keyword">in</span> <span class="keyword">set</span>, <span class="number">1</span> warning (<span class="number">0.01</span> sec)</span><br></pre></td></tr></table></figure><p>返回结果说明:</p><ul><li>id: 查询中每个子查询或表访问的唯一标识符。</li><li>select_type: 查询的类型,例如简单查询、联合查询、子查询等。</li><li>table: 显示了哪个表正在被访问。</li><li>partitions: 显示查询中涉及的分区。</li><li>type: 表示 MySQL 在表中找到所需行的方式,常见的取值有:ALL, index, range, ref, eq_ref, const, system等。</li><li>possible_keys: 显示可能应用在这张表中的索引,一个或多个可以显示在该字段中。</li><li>key: MySQL 实际决定使用的索引。</li><li>key_len: 表示索引中使用的字节数。</li><li>ref: 显示索引的哪一列被使用了,如果可能的话。</li><li>rows: 表示 MySQL 从表中读取的行数。</li><li>filtered: 表示此查询条件下返回的行占需要读取的行的百分比。</li><li>Extra: 包含了关于查询优化过程的额外信息,例如是否使用了覆盖索引,是否使用了临时表等。</li></ul><p>主要关注一下 key 和 Extra 这两列的内容</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-02/img10.avif"></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/02/34360ed9/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>理解ACID原则：数据库事务处理的关键特性</title>
      <link>https://blog.eucalyptus.cc/2023/11/01/027ffda2/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/01/027ffda2/</guid>
      <pubDate>Wed, 01 Nov 2023 10:25:21 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;p&gt;ACID 是数据库管理系统 DBMS 中用来确保事务处理正确性和可靠性的四个特性的首字母缩写。ACID 是指原子性 Atomicity 、一致性 Consistency 、隔离性 Isolation 和持久性 Durability</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote><p>ACID 是数据库管理系统 DBMS 中用来确保事务处理正确性和可靠性的四个特性的首字母缩写。ACID 是指原子性 Atomicity 、一致性 Consistency 、隔离性 Isolation 和持久性 Durability 。</p></blockquote><ul><li>原子性 Atomicity :原子性要求一个事务被视为一个不可分割的最小操作单元,要么全部执行成功,要么全部回滚到事务开始前的状态。即使在发生错误或异常的情况下,也不能只执行部分操作。原子性保证了事务的完整性,如果任何操作失败,所有已经执行的操作都将被撤销,数据库状态会回滚到事务开始前的一致状态。</li><li>一致性 Consistency :一致性指的是在事务开始和结束时,数据库必须保持一致状态。这意味着事务必须遵循预定义的规则和约束条件,不会破坏数据库的完整性。一致性确保了数据的有效性和正确性。</li><li>隔离性 Isolation :隔离性规定了同时执行的多个事务之间应该是相互隔离的,每个事务应该感觉不到其他事务的存在。隔离性主要关注并发事务之间可能产生的问题,如脏读 Dirty Read 、不可重复读 Non-repeatable Read 、幻读 Phantom Read 等。通过隔离级别的设置,可以控制事务之间的隔离程度,确保事务并发执行时的数据一致性。</li><li>持久性 Durability :持久性要求一旦事务提交成功,对数据库的修改就是永久性的,即使在系统故障或崩溃的情况下也不会丢失。为了实现持久性,DBMS 将事务的日志记录到非易失性的存储介质 如磁盘 上,确保在系统恢复后可以将数据还原到提交事务的状态。<blockquote><p>ACID 事务的特性保证了数据库中的事务处理是可靠和可靠的。通过将一系列操作组装成一个事务,并遵循 ACID 特性,可以确保数据库在并发环境下能够正确处理数据,并保持数据的一致性和完整性。</p></blockquote></li></ul><h2 id="隔离性"><a href="#隔离性" class="headerlink" title="隔离性"></a>隔离性</h2><p>说到隔离性首先是四种隔离级别</p><ul><li>READ UNCOMMITTED 未提交读RU :一个事务还没提交时,它做的变更就能被别的事务看到</li><li>READ COMMITTED 已提交读RC :一个事务提交之后,它做的变更才会被其他事务看到</li><li>REPEATABLE READ 可重复读RR :一个事务中,对同一份数据的读取结果总是相同的,无论是否有其他事务对这份数据进行操作,以及这个事务是否提交。 InnoDB默认级别 。</li><li>SERIALIZABLE 串行化 :事务串行化执行,每次读都需要获得表级共享锁,读写相互都会阻塞,隔离级别最高,牺牲系统并发性。<br><strong>这四大等级从上到下,隔离的效果是逐渐增强,但是性能却是越来越差。</strong></li></ul><p>不同的隔离级别是为了解决不同的问题</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img1.avif"></p><p>那么不同的隔离级别,隔离性是如何实现的,为什么不同事物间能够互不干扰? 答案是 <strong>锁 和 MVCC。</strong></p><h3 id="隔离级别的设置"><a href="#隔离级别的设置" class="headerlink" title="隔离级别的设置"></a>隔离级别的设置</h3><h4 id="查看当前的隔离级别"><a href="#查看当前的隔离级别" class="headerlink" title="查看当前的隔离级别"></a>查看当前的隔离级别</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> transaction_isolation;</span><br></pre></td></tr></table></figure><h4 id="临时设置隔离级别"><a href="#临时设置隔离级别" class="headerlink" title="临时设置隔离级别"></a>临时设置隔离级别</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SET</span> TRANSACTION ISOLATION LEVEL <span class="operator">&lt;</span>隔离级别<span class="operator">&gt;</span>;</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img2.avif"></p><h4 id="永久设置隔离级别"><a href="#永久设置隔离级别" class="headerlink" title="永久设置隔离级别"></a>永久设置隔离级别</h4><figure class="highlight xml"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">transaction_isolation <span class="tag">&lt;<span class="name">隔离级别</span>&gt;</span></span><br></pre></td></tr></table></figure><h3 id="事务的管理"><a href="#事务的管理" class="headerlink" title="事务的管理"></a>事务的管理</h3><h4 id="开启事务"><a href="#开启事务" class="headerlink" title="开启事务"></a>开启事务</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">begin</span><span class="operator">/</span><span class="keyword">start</span> transaction</span><br></pre></td></tr></table></figure><h4 id="提交事务"><a href="#提交事务" class="headerlink" title="提交事务"></a>提交事务</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">commit</span><br></pre></td></tr></table></figure><h4 id="回滚事务"><a href="#回滚事务" class="headerlink" title="回滚事务"></a>回滚事务</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">rollback</span><br></pre></td></tr></table></figure><h2 id="原子性"><a href="#原子性" class="headerlink" title="原子性"></a>原子性</h2><p>接着说说原子性。前文有提到 undo log ,回滚日志。隔离性的MVCC其实就是依靠它来实现的,原子性也是。 实现原子性的关键,是当事务回滚时能够撤销所有已经成功执行的sql语句。 当事务对数据库进行修改时,InnoDB会生成对应的 undo log;如果事务执行失败或调用了 rollback,导致事务需要回滚,便可以利用 undo log 中的信息将数据回滚到修改之前的样子。 undo log 属于逻辑日志,它记录的是sql执行相关的信息。当发生回滚时,InnoDB 会根据 undo log 的内容做与之前相反的工作:</p><ul><li>对于每个 insert,回滚时会执行 delete;</li><li>对于每个 delete,回滚时会执行insert;</li><li>对于每个 update,回滚时会执行一个相反的 update,把数据改回去。<br>以update操作为例:当事务执行update时,其生成的undo log中会包含被修改行的主键(以便知道修改了哪些行)、修改了哪些列、这些列在修改前后的值等信息,回滚时便可以使用这些信息将数据还原到update之前的状态。</li></ul><h2 id="一致性"><a href="#一致性" class="headerlink" title="一致性"></a>一致性</h2><p>一致性是事务追求的最终目标,前文所诉的原子性、持久性和隔离性,其实都是为了保证数据库状态的一致性。 当然,上文都是数据库层面的保障,一致性的实现也需要应用层面进行保障。 也就是你的业务,比如购买操作只扣除用户的余额,不减库存,肯定无法保证状态的一致。</p><h2 id="持久性"><a href="#持久性" class="headerlink" title="持久性"></a>持久性</h2><p>Innnodb有很多 log,持久性靠的是 redo log。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/01/027ffda2/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MVCC详解</title>
      <link>https://blog.eucalyptus.cc/2023/11/01/d5c50ebd/</link>
      <guid>https://blog.eucalyptus.cc/2023/11/01/d5c50ebd/</guid>
      <pubDate>Wed, 01 Nov 2023 10:20:19 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是MVCC&quot;&gt;&lt;a href=&quot;#什么是MVCC&quot; class=&quot;headerlink&quot; title=&quot;什么是MVCC?&quot;&gt;&lt;/a&gt;什么是MVCC?&lt;/h2&gt;&lt;p&gt;MVCC,即**Multi-Version Concurrency Control</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是MVCC"><a href="#什么是MVCC" class="headerlink" title="什么是MVCC?"></a>什么是MVCC?</h2><p>MVCC,即**Multi-Version Concurrency Control 多版本并发控制 **。它是一种并发控制的方法,一般在数据库管理系统中,实现对数据库的并发访问,在编程语言中实现事务内存。</p><p>通俗的讲,数据库中同时存在多个版本的数据,并不是整个数据库的多个版本,而是某一条记录的多个版本同时存在,在某个事务对其进行操作的时候,需要查看这一条记录的隐藏列事务版本id,比对事务id并根据事物隔离级别去判断读取哪个版本的数据。</p><p>数据库隔离级别读<strong>已提交、可重复读</strong> 都是基于MVCC实现的,相对于加锁简单粗暴的方式,它用更好的方式去处理读写冲突,能有效提高数据库并发性能。</p><h2 id="MVCC实现的关键知识点"><a href="#MVCC实现的关键知识点" class="headerlink" title="MVCC实现的关键知识点"></a>MVCC实现的关键知识点</h2><h3 id="事务版本号"><a href="#事务版本号" class="headerlink" title="事务版本号"></a>事务版本号</h3><p>事务每次开启前,都会从数据库获得一个<strong>自增</strong>长的事务ID,可以从事务ID判断事务的执行先后顺序。这就是事务版本号。</p><h3 id="隐式字段"><a href="#隐式字段" class="headerlink" title="隐式字段"></a>隐式字段</h3><p>对于InnoDB存储引擎,每一行记录都有两个隐藏列<strong>trx_id</strong>、<strong>roll_pointer</strong>,如果表中没有主键和非NULL唯一键时,则还会有第三个隐藏的主键列<strong>row_id</strong>。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img1.avif"></p><h3 id="undo-log"><a href="#undo-log" class="headerlink" title="undo log"></a>undo log</h3><p>undo log,<strong>回滚日志</strong>,用于记录数据被修改前的信息。在表记录修改之前,会先把数据拷贝到undo log里,如果事务回滚,即可以通过undo log来还原数据。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img2.avif"></p><p>可以这样认为,当delete一条记录时,undo log 中会记录一条对应的insert记录,当update一条记录时,它记录一条对应相反的update记录。</p><p>undo log有什么<strong>用途</strong>呢?</p><ul><li>事务回滚时,保证原子性和一致性</li><li>用于MVCC<strong>快照读</strong></li></ul><h3 id="版本链"><a href="#版本链" class="headerlink" title="版本链"></a>版本链</h3><p>多个事务并行操作某一行数据时,不同事务对该行数据的修改会产生多个版本,然后通过回滚指针 roll_pointer ,连成一个链表,这个链表就称为<strong>版本链</strong>。如下:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img3.avif"></p><p>其实,通过版本链,我们就可以看出<strong>事务版本号、表格隐藏的列和undo log</strong>它们之间的关系。我们再来小分析一下。</p><p>        1.假设现在有一张core_user表,表里面有一条数据,id为1,名字为孙权:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img4.avif"></p><p>        2.现在开启一个事务A: 对core_user表执行update core_user set name 曹操 where id 1,会进行如下流程操作</p><ul><li>首先获得一个事务ID 100</li><li>把core_user表修改前的数据,拷贝到undo log</li><li>修改core_user表中,id 1的数据,名字改为曹操</li><li>把修改后的数据事务Id 101改成当前事务版本号,并把<strong>roll_pointer</strong>指向undo log数据地址。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-11-01/img5.avif"></p><h3 id="快照读和当前读"><a href="#快照读和当前读" class="headerlink" title="快照读和当前读"></a>快照读和当前读</h3><h4 id="快照读"><a href="#快照读" class="headerlink" title="快照读"></a>快照读</h4><p>读取的是记录数据的可见版本 有旧的版本 。不加锁,普通的select语句都是快照读,如:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> core_user <span class="keyword">where</span> id <span class="operator">&gt;</span> <span class="number">2</span>;</span><br></pre></td></tr></table></figure><h4 id="当前读"><a href="#当前读" class="headerlink" title="当前读"></a>当前读</h4><p>读取的是记录数据的最新版本,显式加锁的都是当前读</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> core_user <span class="keyword">where</span> id <span class="operator">&gt;</span> <span class="number">2</span> <span class="keyword">for</span> <span class="keyword">update</span>;</span><br><span class="line"><span class="keyword">select</span> <span class="operator">*</span> <span class="keyword">from</span> account <span class="keyword">where</span> id<span class="operator">&gt;</span><span class="number">2</span> lock <span class="keyword">in</span> share mode;</span><br></pre></td></tr></table></figure><h3 id="Read-View"><a href="#Read-View" class="headerlink" title="Read View"></a>Read View</h3><ul><li><p><strong>Read View是什么呢?</strong> 它就是事务执行SQL语句时,产生的读视图。实际上在innodb中,每个SQL语句执行前都会得到一个Read View。</p></li><li><p><strong>Read View有什么用呢?</strong> 它主要是用来做可见性判断的,即判断当前事务可见哪个版本的数据~<br>Read View是如何保证可见性判断的呢?我们先看看Read view 的几个重要属性</p></li><li><p>m_ids:当前系统中那些活跃(未提交)的读写事务ID, 它数据结构为一个List。</p></li><li><p>min_limit_id:表示在生成ReadView时,当前系统中活跃的读写事务中最小的事务id,即m_ids中的最小值。</p></li><li><p>max_limit_id:表示生成ReadView时,系统中应该分配给下一个事务的id值。</p></li><li><p>creator_trx_id: 创建当前read view的事务ID<br><strong>Read view 匹配条件规则</strong>如下:</p></li><li><p>如果数据事务ID trx_id &lt; min_limit_id,表明生成该版本的事务在生成Read View前,已经提交(因为事务ID是递增的),所以该版本可以被当前事务访问。</p></li><li><p>如果trx_id&gt; max_limit_id,表明生成该版本的事务在生成ReadView后才生成,所以该版本不可以被当前事务访问。</p></li><li><p>如果 min_limit_id &lt;trx_id&lt; max_limit_id,需腰分3种情况讨论</p></li><li><p>1 .如果m_ids包含trx_id,则代表Read View生成时刻,这个事务还未提交,但是如果数据的trx_id等于creator_trx_id的话,表明数据是自己生成的,因此是<strong>可见</strong>的。</p></li><li><p>2 如果m_ids包含trx_id,并且trx_id不等于creator_trx_id,则Read View生成时,事务未提交,并且不是自己生产的,所以当前事务也是<strong>看不见</strong>的;</p></li><li><p>3 .如果m_ids不包含trx_id,则说明你这个事务在Read View生成之前就已经提交了,修改的结果,当前事务是能看见的。</p></li></ul><h2 id="MVCC实现原理分析"><a href="#MVCC实现原理分析" class="headerlink" title="MVCC实现原理分析"></a>MVCC实现原理分析</h2><h3 id="查询一条记录-基于MVCC是怎样的流程"><a href="#查询一条记录-基于MVCC是怎样的流程" class="headerlink" title="查询一条记录,基于MVCC是怎样的流程"></a>查询一条记录,基于MVCC是怎样的流程</h3><ul><li>获取事务自己的版本号,即事务ID</li><li>获取Read View</li><li>查询得到的数据,然后Read View中的事务版本号进行比较。</li><li>如果不符合Read View的可见性规则, 即就需要Undo log中历史快照;</li><li>最后返回符合规则的数据<br>InnoDB 实现MVCC,是通过 <strong>Read View Undo Log</strong> 实现的,Undo Log 保存了历史快照,Read View可见性规则帮助判断当前版本的数据是否可见。</li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/11/01/d5c50ebd/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>InnoDB存储引擎详解：架构、内存管理与性能优化</title>
      <link>https://blog.eucalyptus.cc/2023/10/30/0cbdc98c/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/30/0cbdc98c/</guid>
      <pubDate>Mon, 30 Oct 2023 08:15:57 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;其实存储引擎也很简单,我认为就是一种存储解决方案,实现了新增数据、更新数据和建立索引等等功能。&lt;/p&gt;
&lt;p&gt;有哪些已有的存储引擎可以让我们选择呢?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;InnoDB、MyISAM、Memory、CSV、Archive、Blackhole</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>其实存储引擎也很简单,我认为就是一种存储解决方案,实现了新增数据、更新数据和建立索引等等功能。</p><p>有哪些已有的存储引擎可以让我们选择呢?</p><blockquote><p>InnoDB、MyISAM、Memory、CSV、Archive、Blackhole、Merge、Federated、Example</p></blockquote><p>种类很多,但是常用的存储引擎目前就只有InnoDB和MyISAM,下面将会介绍到InnoDB存储引擎。</p><h2 id="InnoDB体系架构"><a href="#InnoDB体系架构" class="headerlink" title="InnoDB体系架构"></a>InnoDB体系架构</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img1.avif"></p><h2 id="后台线程"><a href="#后台线程" class="headerlink" title="后台线程"></a>后台线程</h2><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img2.avif"></p><p>InnoDB后台有多个不同的线程,用来负责不同的任务。主要有如下:</p><ul><li>Master Thread<br>这是最核心的一个线程,主要负责将缓冲池中的数据异步刷新到磁盘,保证数据的一致性,包括赃页的刷新、合并插入缓冲、UNDO 页的回收等.</li><li>IO Thread<br>在 InnoDB 存储引擎中大量使用了异步 IO 来处理写 IO 请求, IO Thread 的工作主要是负责这些 IO 请求的回调处理。</li><li>Purge Thread<br>事务被提交之后, undo log 可能不再需要,因此需要 Purge Thread 来回收已经使用并分配的 undo页. InnoDB 支持多个 Purge Thread, 这样做可以加快 undo 页的回收。</li><li>Page Cleaner Thread<br>Page Cleaner Thread 是在InnoDB 1.2.x版本新引入的,其作用是将之前版本中脏页的刷新操作都放入单独的线程中来完成,这样减轻了 Master Thread 的工作及对于用户查询线程的阻塞。</li></ul><blockquote><p>–innodb-page-cleaner参数可以控制Page Cleaner Thread的数量。一个Buffer Pool实例同时只能有一个Page Cleaner进行刷脏操作。因此Page Cleaner的数量最多和Buffer Pool实例的数量相同(–innodb-buffer-pool-instances)。</p><p>innodb-buffer-pool-size参数可以控制BP的大小,innodb-buffer-pool-instances参数可以控制BP实例的数量,也就是BP的数量,但是需要注意的是innodb-buffer-pool-instances 参数的值不能超过 CPU 核心的数量。当设置为大于 CPU 核心数的值时,MySQL 会自动将其调整为合理的值。</p></blockquote><h2 id="内存"><a href="#内存" class="headerlink" title="内存"></a>内存</h2><p>InnoDB的内存架构主要分为三大块:</p><ul><li><strong>缓冲池</strong> Buffer Pool</li><li><strong>重做缓冲池</strong> Redo Log Buffer</li><li><strong>额外内存池</strong></li></ul><h3 id="缓冲池"><a href="#缓冲池" class="headerlink" title="缓冲池"></a>缓冲池</h3><p><a href="https://dev.mysql.com/doc/refman/5.7/en/innodb-buffer-pool.html">MySQL官方文档Buffer Pool</a></p><p>缓冲池列表</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img3.avif"></p><p>InnoDB为了做数据的持久化,会将数据存储到磁盘上。但是面对大量的请求时,CPU的处理速度和磁盘的IO速度之间差距太大,为了提高整体的效率, InnoDB引入了<strong>缓冲池</strong>。</p><p>当有请求来查询数据时,如果缓存池中没有,就会去磁盘中查找,将匹配到的数据放入缓存池中。同样的,如果有请求来修改数据,MySQL并不会直接去修改磁盘,而是会修改已经在缓冲池的页中的数据,然后再将数据刷回磁盘,这就是缓冲池的作用,加速读,加速写,减少与磁盘的IO交互。</p><p>缓冲池说白了就是把磁盘中的数据丢到内存,那既然是内存就会存在没有内存空间可以分配的情况。所以缓冲池采用了<strong>LRU</strong>算法,在缓冲池中没有空闲的页时,来进行页的淘汰。但是采用这种算法会带来一个问题叫做<strong>缓冲池污染</strong>。</p><blockquote><p><strong>LUR算法</strong></p><p>在 MySQL 中,LRU 指的是 Least Recently Used 缓存淘汰算法。该算法用于在缓存空间不足时,通过淘汰最近最少使用的数据来腾出空间,以便让新的数据进入缓存。</p><p>MySQL 中常用 LRU 算法来管理缓存,例如 InnoDB 存储引擎就使用了 LRU 算法来管理其缓冲池 Buffer Pool 。InnoDB 的缓冲池是一个内存区域,用于缓存数据库中的数据页,通过缓存页,可以避免频繁读取磁盘,从而提高数据库的性能。当需要获取一个数据页时,InnoDB 会首先在缓冲池中查找,如果找到了就直接返回,否则会从磁盘中读取并放入缓冲池中。</p><p>当缓冲池空间不足时,InnoDB 就需要根据 LRU 算法来淘汰一些数据页。具体来说,InnoDB 会维护一个“最近使用列表” Recently Used List 和一个“最近未使用列表” Recently Unused List ,最近使用的数据页会被移到最前面,最近未使用的数据页则会移到后面。当需要淘汰数据页时,InnoDB 会选择最近未使用的数据页进行淘汰,以便让更常用的数据页留在缓冲池中,从而提高缓存命中率。</p><p>需要注意的是,LRU 算法是一种基于历史访问模式的淘汰算法,它假设未来的访问模式会和过去的访问模式相似,因此会尽可能地保留最近使用的数据。但是,在实际应用中,访问模式并不一定会保持不变,因此 LRU 算法也有其局限性。针对这个问题,还有其他缓存淘汰算法,如 MRU Most Recently Used 、LFU Least Frequently Used 等,可以根据具体场景来选择合适的算法。</p><p><strong>LUR算法运行方式</strong></p><ul><li>缓冲池的 3&#x2F;8 专用于旧的子列表。</li><li>列表的中点是 新子列表与旧子列表的头部相遇。</li><li>将页面读入缓冲区时 池,它最初将其插入中点 头部 旧子列表 。可以读取页面,因为它是 用户启动的操作,例如 SQL 查询,或作为<a href="https://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_read_ahead">预读</a>操作的一部分 由 自动执行。InnoDBInnoDB</li><li>访问旧子列表中的页面会使其“年轻”,将其移动到新子列表的头部 子列表。如果该页面被阅读是因为 用户启动的操作,首次访问立即发生 并且页面变得年轻。如果由于 预读操作,不会发生第一次访问 立即发生,并且可能根本不会在页面之前发生 驱逐。</li><li>当数据库运行时,缓冲池中 无法通过向尾部移动来访问“年龄” 列表。新旧子列表中的页面与其他页面一样老化 页面是新的。旧子列表中的页面也会作为页面老化 插入到中点。最终,留下一个页面 未使用到达旧子列表的尾部并被逐出。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img4.avif"></p><h4 id="缓冲池污染"><a href="#缓冲池污染" class="headerlink" title="缓冲池污染"></a>缓冲池污染</h4><p>缓冲池污染 Buffer Pool Contention 是数据库系统中的一个性能问题,指的是多个事务同时访问和争用缓冲池中的同一数据页,从而导致了事务之间的等待和竞争,以及数据库性能下降。缓冲池污染通常发生在高负载的数据库系统中,它可能会导致系统响应变慢,甚至服务不可用。</p><p>在一个并发访问的环境中,当多个事务同时需要访问或修改同一个数据页时,它们都需要先将该数据页读入到缓冲池中,再进行读取或修改操作。由于缓冲池的大小有限,当缓冲池中的数据页被占满后,新的事务需要等待已有事务归还缓冲池中的数据页才能继续执行,这就是缓冲池的竞争现象。</p><p>缓冲池污染的另一个原因是缓冲池管理算法的问题,常见的缓冲池管理算法包括最近最少使用 LRU 、先进先出 FIFO 等,它们都是基于一些策略来选择要从缓冲池中淘汰的数据页。如果选择的策略不够优秀,就会导致缓冲池中的热点数据页被频繁淘汰,从而影响系统性能。</p></blockquote><p>当你在进行批量扫描甚至全表扫描时,可能会将缓冲池中的热点页全部替换出去。这样以来可能会导致MySQL的性能断崖式下降。所以InnoDB对LRU做了一些优化,规避了这个问题。</p><p>MySQL采用<strong>日志先行</strong>,在真正写数据之前,会首先记录一个日志,叫<strong>Redo Log</strong>,会定期的使用CheckPoint技术将新的Redo Log刷入磁盘,这个后面会讲。</p><p>除了数据之外,里面还存储了索引页、Undo页、插入缓冲、自适应哈希索引、InnoDB锁信息和数据字典。下面选几个比较重要的来简单聊一聊。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img5.avif"></p><h4 id="插入缓存"><a href="#插入缓存" class="headerlink" title="插入缓存"></a>插入缓存</h4><p><strong>非唯一辅助索引的插入操作</strong></p><p>插入缓冲针对的操作是更新或者插入,我们考虑最坏的情况,那就是需要更新的数据都不在缓冲池中。那么此时会有下面两种方案。</p><ul><li>来一条数据就直接写入磁盘</li><li>等数据达到某个阈值 例如50条 才批量的写入磁盘</li></ul><p>很明显,第二种方案要好一点,减少了与磁盘IO的交互。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img6.avif"></p><h3 id="两次写"><a href="#两次写" class="headerlink" title="两次写"></a><strong>两次写</strong></h3><p>鉴于都聊到了插入缓冲,我就不得不需要提一嘴<strong>两次写</strong>,因为我认为这两个InnoDB的特性是相辅相成的。</p><p><strong>插入缓冲</strong>提高了MySQL的性能,而<strong>两次写</strong>则在此基础上提高了数据的可靠性。我们知道,当数据还在缓冲池中的时候,当机器宕机了,发生了<strong>写失效</strong>,有Redo Log来进行恢复。但是如果是在从缓冲池中将数据刷回磁盘的时候宕机了呢?</p><p>这种情况叫做部分写失效,此时重做日志就无法解决问题。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img7.avif"></p><p>在刷脏页时,并不是直接刷入磁盘,而是copy到内存中的Doublewrite Buffer中,然后再拷贝至磁盘共享表空间 你可以就理解为磁盘 中,每次写入1M,等copy完成后,再将Doublewrite Buffer中的页写入磁盘文件。</p><p>有了两次写机制,即使在刷脏页时宕机了,在实例恢复的时候也可以从共享表空间中找到Doublewrite Buffer的页副本,直接将其覆盖原来的数据页即可。</p><h4 id="自适应哈希索引"><a href="#自适应哈希索引" class="headerlink" title="自适应哈希索引"></a>自适应哈希索引</h4><p>自适应索引就跟JVM在运行过程中,会动态的把某些热点代码编译成Machine Code一样,InnoDB会监控对所有索引的查询,对热点访问的页建立哈希索引,以此来提升访问速度。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img8.avif"></p><h4 id="异步IO-AIO"><a href="#异步IO-AIO" class="headerlink" title="异步IO(AIO)"></a><strong>异步IO(AIO)</strong></h4><p>为了提高磁盘操作性能,当前的数据库系统都采用异步IO的方式来处理磁盘操作。InnoDB也是如此。</p><p>与AIO对应的是Sync IO,即每进行一次IO操作,需要等待此次操作结束才能继续接下来的操作。但是如果用户发出的是一条索引扫描的查询,那么这条SQL语句可能需要扫描多个索引页,也就是需要进行多次IO操作。在每扫描一个页并等待其完成再进行下一次扫描,这是没有必要的。用户可以在发出一个IO请求后立即再发出另外一个IO请求,当全部IO请求发送完毕后,等待所有IO操作完成,这就是AIO。</p><p>AIO的另外一个优势是进行IO Merge操作,也就是将多个IO合并为一个IO操作,这样可以提高IOPS的性能。</p><p>在InnoDB 1.1.x之前,AIO的实现是通过InnoDB存储引擎中的代码来模拟的。但是从这之后,提供了内核级别的AIO的支持,称为Native AIO。Native AIO需要操作系统提供支持。Windows和Linux都支持,而Mac则未提供。在选择MySQL数据库服务器的操作系统时,需要考虑这方面的因素。</p><p>MySQL可以通过参数innodb_use_native_aio来决定是否启用Native AIO。在InnoDB存储引擎中,read ahead方式的读取都是通过AIO完成,脏页的刷新,也是通过AIO完成。</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img9.avif"></p><h4 id="刷新邻接页"><a href="#刷新邻接页" class="headerlink" title="刷新邻接页"></a><strong>刷新邻接页</strong></h4><p>InnoDB存储引擎在刷新一个脏页时,会检测该页所在区(extent)的所有页,如果是脏页,那么一起刷新。这样做的好处是通过AIO可以将多个IO写操作合并为一个IO操作。该工作机制在传统机械磁盘下有显著优势。但是需要考虑下吧两个问题:</p><p>是不是将不怎么脏的页进行写入,而该页之后又会很快变成脏页?<br>固态硬盘有很高IOPS,是否还需要这个特性?<br>为此InnoDB存储引擎1.2.x版本开始提供参数innodb_flush_neighbors来决定是否启用。对于传统机械硬盘建议使用,而对于固态硬盘可以关闭。</p><h3 id="重做缓冲池"><a href="#重做缓冲池" class="headerlink" title="重做缓冲池"></a>重做缓冲池</h3><p>上面聊过,InnoDB中缓冲池中的页数据更新会先于磁盘数据更新的,InnoDB也会采用日志先行 Write Ahead Log 策略来刷新数据,什么意思呢?当事务开始时,会先记录Redo Log到Redo Log Buffer中,然后再更新缓冲池页数据。</p><p>Redo Log Buffer中的数据会按照一定的频率写到重做日志中去。被更改过的页就会被标记成<strong>脏页</strong>,InnoDB会根据CheckPoint机制来将脏页刷到磁盘。</p><h3 id="额外缓冲池"><a href="#额外缓冲池" class="headerlink" title="额外缓冲池"></a>额外缓冲池</h3><p>InnoDB在对一些数据结构本身的内存分配时,需要从额外的内存池中进行申请。例如缓冲池中的中的一些对象记录了锁、等待、LUR等消息,这些对象需要从额外的内存池中申请内存。</p><h2 id="数据文件"><a href="#数据文件" class="headerlink" title="数据文件"></a>数据文件</h2><p>数据文件中主要包括了:db.opt文件、frm文件、MYD文件、MYI文件、ibd文件、ibdata文件、ibdata1文件、ib_logfile0和ib_logfile1文件等。</p><h3 id="db-opt文件"><a href="#db-opt文件" class="headerlink" title="db.opt文件"></a>db.opt文件</h3><p>主要记录当前数据库使用的字符集和检验规则等信息。</p><h3 id="frm文件"><a href="#frm文件" class="headerlink" title="frm文件"></a>frm文件</h3><p>存储数据表的结构信息,主要是数据表相关的元数据信息,包括数据表的表结构定义信息,每张表都会有一个frm文件。</p><p><strong>值得注意的是:MySQL8版本中的innodb存储引擎的表没有frm文件。</strong></p><h3 id="MYD文件"><a href="#MYD文件" class="headerlink" title="MYD文件"></a>MYD文件</h3><p>MyISAM存储引擎专用的文件格式,主要存放MyISAM存储引擎数据表中的数据,每张MyISAM存储引擎表对应一个.MYD文件。</p><h3 id="MYI文件"><a href="#MYI文件" class="headerlink" title="MYI文件"></a>MYI文件</h3><p>MyISAM存储引擎专用的文件格式,主要存放与MyISAM存储引擎数据表相关的索引信息,每张MyISAM存储引擎表对应一个.MYI文件。</p><h3 id="ibd文件"><a href="#ibd文件" class="headerlink" title="ibd文件"></a>ibd文件</h3><p>存放Innodb存储引擎的数据文件和索引文件,主要存放的是独享表空间的数据和索引,每张表对应一个.ibd文件。</p><h3 id="ibdata文件"><a href="#ibdata文件" class="headerlink" title="ibdata文件"></a>ibdata文件</h3><p>存放Innodb存储引擎的数据文件和索引文件,主要存放的是共享表空间的数据和索引,所有表共用一个 或者多个 .ibdata文件,可以根据配置来指定共用的.ibdata文件个数。</p><h3 id="ibdata1文件"><a href="#ibdata1文件" class="headerlink" title="ibdata1文件"></a>ibdata1文件</h3><p>MySQL的系统表空间数据文件,主要存储MySQL的数据表元数据、Undo日志等信息。</p><h3 id="ib-logfile0和ib-logfile1文件"><a href="#ib-logfile0和ib-logfile1文件" class="headerlink" title="ib_logfile0和ib_logfile1文件"></a>ib_logfile0和ib_logfile1文件</h3><p>MySQL数据库中的Redo log文件,主要用于MySQL实现事务的持久性。如果在某个时间点MySQL发生了故障,此时如果有脏页没有写入到数据库的ibd文件中,在重启MySQL的时候,MySQL会根据Redo Log信息进行重做,将写入Redo Log并且尚未写入数据表的数据进行持久化操作。</p><h2 id="ChectPoint技术"><a href="#ChectPoint技术" class="headerlink" title="ChectPoint技术"></a>ChectPoint技术</h2><p>说完缓冲池,下面说CheckPoint技术。<br>CheckPoint技术是用来解决如下几个问题:</p><ul><li>缩短数据库恢复时间</li><li>缓冲池不够用时,将脏页刷新到磁盘</li><li>重做日志不可用时,刷新脏页</li></ul><h3 id="缩短数据库恢复时间"><a href="#缩短数据库恢复时间" class="headerlink" title="缩短数据库恢复时间"></a>缩短数据库恢复时间</h3><p>缩短数据库恢复时间,重做日志中记录了的checkpoint的位置,这个点之前的页已经刷新回磁盘,只需要对checkpoint之后的重做日志进行恢复。这样就大大缩短了恢复时间。</p><h3 id="缓冲池不够用"><a href="#缓冲池不够用" class="headerlink" title="缓冲池不够用"></a>缓冲池不够用</h3><p>缓冲池不够用时,根据LRU算法,溢出最近最少使用的页,如果页为脏页,强制执行checkpoint,将脏页刷新回磁盘。</p><h3 id="重做日志不可用"><a href="#重做日志不可用" class="headerlink" title="重做日志不可用"></a>重做日志不可用</h3><p>重做日志不可用,是指重做日志的这部分不可以被覆盖,为什么?因为:由于重做日志的设计是循环使用的。这部分对应的数据还未刷新到磁盘上。数据库恢复时,如果不需要这部分日志,即可被覆盖;如果需要,必须强制执行checkpoint,将缓冲池中的页至少刷新到当前重做日志的位置。</p><blockquote><p>checkpoint每次刷新多少页到磁盘?每次从哪里取脏页?什么时间触发checkpoint?</p><p>InnoDB存储引擎内部,两种checkpoint,分别为:</p><ul><li>Sharp Checkpoint</li><li>Fuzzy Checkpoint</li></ul><h4 id="Sharp-Checkpoint"><a href="#Sharp-Checkpoint" class="headerlink" title="Sharp Checkpoint"></a>Sharp Checkpoint</h4><p>Sharp Checkpoint发生在数据库关闭时,将所有的脏页都刷新回磁盘,这是默认的工作方式,即参数:innodb_fast_shutdown 1。<br>不适用于数据库运行时的刷新。</p><h4 id="Fuzzy-Checkpoint"><a href="#Fuzzy-Checkpoint" class="headerlink" title="Fuzzy Checkpoint"></a>Fuzzy Checkpoint</h4><p>在数据库运行时,InnoDB存储引擎内部采用Fuzzy Checkpoint,只刷新一部分脏页。</p><p>几种发生Fuzzy Checkpoint的情况:<br>①MasterThread Checkpoint<br>异步刷新,每秒或每10秒从缓冲池脏页列表刷新一定比例的页回磁盘。异步刷新,即此时InnoDB存储引擎可以进行其他操作,用户查询线程不会受阻。<br>②FLUSH_LRU_LIST Checkpoint<br>InnoDB存储引擎需要保证LRU列表中差不多有100个空闲页可供使用。在InnoDB 1.1.x版本之前,用户查询线程会检查LRU列表是否有足够的空间操作。如果没有,根据LRU算法,溢出LRU列表尾端的页,如果这些页有脏页,需要进行checkpoint。因此叫:flush_lru_list checkpoint。<br>InnoDB 1.2.x开始,这个检查放在了单独的进程 Page Cleaner 中进行。好处:1.减少master Thread的压力 2.减轻用户线程阻塞。<br>设置参数:innodb_lru_scan_dept:控制LRU列表中可用页的数量,该值默认1024<br>③Async&#x2F;Sync Flush Checkpoint<br>指重做日志不可用的情况,需要强制刷新页回磁盘,此时的页时脏页列表选取的。<br>这种情况是保证重做日志的可用性,说白了就是,重做日志中可以循环覆盖的部分空间太少了,换种说法,就是极短时间内产生了大量的redo log。<br>接下来会有几个变量,图解也不难,仔细看看。<br>InnoDB存储引擎,通过LSN Log Sequence Number 来标记版本,LSN是8字节的数字。每个页有LSN,重做日志有LSN,checkpoint有LSN。<br><strong>写入日志的LSN:redo_lsn</strong><br><strong>刷新回磁盘的最新页LSN:checkpoint_lsn</strong><br>有如下定义:<br>checkpoint_age redo_lsn - checkpoint_lsn<br>async_water_mark 75% * total_redo_file_size<br>sync_water_mark 90% * total_redo_file_size<br>刷新过程如下图所示:</p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img10.avif"></p><p>④Dirty Page too much Checkpoint<br>即脏页太多,强制checkpoint.保证缓冲池有足够可用的页。<br>参数设置:innodb_max_dirty_pages_pct 75 表示:当缓冲池中脏页的数量占75%时,强制checkpoint。1.0.x之后默认75</p></blockquote>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/30/0cbdc98c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL主从复制延时</title>
      <link>https://blog.eucalyptus.cc/2023/10/30/1030f229/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/30/1030f229/</guid>
      <pubDate>Mon, 30 Oct 2023 08:11:47 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;主从复制原理&quot;&gt;&lt;a href=&quot;#主从复制原理&quot; class=&quot;headerlink&quot; title=&quot;主从复制原理&quot;&gt;&lt;/a&gt;主从复制原理&lt;/h2&gt;&lt;p&gt;MySQL主从复制是MySQL数据库中一种数据备份和数据同步的方式。它将一台MySQL服务器 主服务器</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="主从复制原理"><a href="#主从复制原理" class="headerlink" title="主从复制原理"></a>主从复制原理</h2><p>MySQL主从复制是MySQL数据库中一种数据备份和数据同步的方式。它将一台MySQL服务器 主服务器 的数据同步到另外一台MySQL服务器 从服务器 。主服务器是数据的提供者,而从服务器是数据的接收者。主从复制可以用于数据备份和读写分离等场景。</p><p>MySQL主从复制的原理如下:</p><ul><li>主服务器将更新的日志写入二进制日志文件 binary log 。</li><li>从服务器连接主服务器,通过读取主服务器的二进制日志文件并解析其中的更新记录,将这些记录应用到自己的数据库中,从而实现数据的同步。</li><li>从服务器会定期向主服务器发送心跳包,以确保主服务器的可用性。当主服务器宕机或网络不通时,从服务器会自动切换为主服务器,继续提供服务。</li><li></li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-10-30/img1.avif"></p><p>详细的主从同步主要有三种形式 binlog格式 :statement、row、mixed</p><ul><li><strong>语句复制</strong> Statement-based replication,SBR : 会将对数据库操作的sql语句写道binlog中</li><li><strong>行复制</strong> Row-based replication,RBR : 会将每一条数据的变化写道binlog中。</li><li><strong>混合复制</strong> Mixed-based replication,MBR : statement与row的混合。Mysql决定何时写statement格式的binlog, 何时写row格式的binlog。</li></ul><p>在 MySQL 中,可以通过配置参数 binlog_format 来选择使用的复制格式,包括 STATEMENT、ROW 和 MIXED。</p><h2 id="主从复制延时问题"><a href="#主从复制延时问题" class="headerlink" title="主从复制延时问题"></a>主从复制延时问题</h2><h3 id="I-O线程存在延迟"><a href="#I-O线程存在延迟" class="headerlink" title="I&#x2F;O线程存在延迟"></a>I&#x2F;O线程存在延迟</h3><ul><li>网络延迟</li><li>磁盘I&#x2F;O存在瓶颈</li><li>网卡存在问题</li></ul><h3 id="SQL线程存在延迟"><a href="#SQL线程存在延迟" class="headerlink" title="SQL线程存在延迟"></a>SQL线程存在延迟</h3><ul><li>高并发:主库写入量过大,sql线程单线程重放</li><li>大事务:如果从库执行的二进制日志中包含一个较长时间的事务,而且该事务尚未完成,则SQL线程会一直等待这个事务完成。这会导致SQL线程在处理其他的更新操作时被阻塞,表现为卡顿。</li></ul><h2 id="解决主从复制延时的方案"><a href="#解决主从复制延时的方案" class="headerlink" title="解决主从复制延时的方案"></a>解决主从复制延时的方案</h2><ul><li>网络优化</li><li>事务优化</li><li>数据库性能优化</li><li>MySQL配置优化</li></ul><h3 id="网络优化"><a href="#网络优化" class="headerlink" title="网络优化"></a>网络优化</h3><h4 id="使用高速网络连接"><a href="#使用高速网络连接" class="headerlink" title="使用高速网络连接"></a>使用高速网络连接</h4><p>尽可能使用高速网络连接,例如千兆以太网连接或更高速的连接,以确保快速传输数据。</p><h4 id="优化网络带宽"><a href="#优化网络带宽" class="headerlink" title="优化网络带宽"></a>优化网络带宽</h4><p>通过调整网络带宽分配,可以确保主从数据库之间的网络连接稳定并且带宽充足。</p><h4 id="减少跨数据中心的复制"><a href="#减少跨数据中心的复制" class="headerlink" title="减少跨数据中心的复制"></a>减少跨数据中心的复制</h4><p>如果数据中心之间的网络延迟比较大,则可以考虑将主从数据库部署在同一数据中心或就近的数据中心。</p><h3 id="事务优化"><a href="#事务优化" class="headerlink" title="事务优化"></a>事务优化</h3><h4 id="将大事务拆分成多个小事务"><a href="#将大事务拆分成多个小事务" class="headerlink" title="将大事务拆分成多个小事务"></a>将大事务拆分成多个小事务</h4><p>将大事务拆分成多个小事务,可以减少主从复制延迟,同时减少锁定资源的时间。</p><h4 id="减少并发事务的数量"><a href="#减少并发事务的数量" class="headerlink" title="减少并发事务的数量"></a>减少并发事务的数量</h4><p>减少并发事务的数量,可以避免过多的锁定资源和占用资源,从而减少主从复制延迟。</p><h4 id="使用InnoDB存储引擎"><a href="#使用InnoDB存储引擎" class="headerlink" title="使用InnoDB存储引擎"></a>使用InnoDB存储引擎</h4><p>在使用InnoDB存储引擎时,可以通过设置事务隔离级别,来避免锁定资源的时间。</p><h3 id="数据库性能优化"><a href="#数据库性能优化" class="headerlink" title="数据库性能优化"></a>数据库性能优化</h3><h4 id="提升硬件性能"><a href="#提升硬件性能" class="headerlink" title="提升硬件性能"></a>提升硬件性能</h4><p>通过升级硬件配置,例如增加内存、硬盘容量等,可以提升从数据库性能。</p><h4 id="调整服务器负载"><a href="#调整服务器负载" class="headerlink" title="调整服务器负载"></a>调整服务器负载</h4><p>通过调整服务器负载,例如减少并发连接数、优化查询语句等,可以减轻从数据库的负载,从而提升性能。</p><h4 id="使用缓存技术"><a href="#使用缓存技术" class="headerlink" title="使用缓存技术"></a>使用缓存技术</h4><p>在从数据库中使用缓存技术,例如Memcached或Redis等,可以减少从数据库的查询次数,从而提升性能。</p><h3 id="MySQL配置优化"><a href="#MySQL配置优化" class="headerlink" title="MySQL配置优化"></a>MySQL配置优化</h3><h4 id="调整主从服务器时间"><a href="#调整主从服务器时间" class="headerlink" title="调整主从服务器时间"></a><strong>调整主从服务器时间</strong></h4><p>如果主从服务器之间的时间存在偏差,则可以通过调整时间来减少主从复制延迟。可以使用ntpdate命令来同步时间。</p><p><strong>修改binlog格式</strong></p><p>在MySQL中,有三种binlog格式:STATEMENT、ROW和MIXED。可以通过修改binlog格式来减少主从复制延迟。</p><p>STATEMENT格式适用于执行简单的SQL语句,但可能会出现一些不一致的情况。ROW格式记录了每一行数据的修改,但是可能会产生大量的日志,增加复制的负担。MIXED格式将根据具体情况自动选择STATEMENT或ROW格式。</p><p>如果使用的是STATEMENT格式,则可以考虑切换到ROW格式,以减少主从复制延迟。如果使用的是ROW格式,则可以考虑切换到MIXED格式,以避免大量的日志。</p><h4 id="调整binlog缓存大小"><a href="#调整binlog缓存大小" class="headerlink" title="调整binlog缓存大小"></a><strong>调整binlog缓存大小</strong></h4><p>binlog缓存大小是指MySQL服务器用来缓存二进制日志的内存大小。如果binlog缓存大小过小,则可能会导致主从复制延迟。可以通过修改my.cnf文件来调整binlog缓存大小。</p><h4 id="调整复制线程数"><a href="#调整复制线程数" class="headerlink" title="调整复制线程数"></a><strong>调整复制线程数</strong></h4><p><strong>slave_parallel_workers</strong> n 开启多线程复制</p><p>复制线程是指用于复制二进制日志的MySQL线程。如果复制线程数量过少,则可能会导致主从复制延迟。可以通过修改my.cnf文件来调整复制线程数。</p><h4 id="使用半同步复制"><a href="#使用半同步复制" class="headerlink" title="使用半同步复制"></a><strong>使用半同步复制</strong></h4><p>半同步复制是一种MySQL复制模式,它可以提高主从复制的可靠性,并减少主从复制延迟。在半同步复制模式下,当从服务器收到主服务器发送的日志时,它会向主服务器发送一个确认消息,以确保数据已经正确地复制到从服务器上。</p><p>可以通过在my.cnf文件中启用半同步复制来减少主从复制延迟。</p><p>开发板推荐：天空星STM32F407VET6开发板</p><p>超高性价比 STM32主控 | 超高主频 | 一板兼容百芯 | 比赛神器 | 沉金彩色丝印</p><p>点击查看</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/30/1030f229/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL语言分类</title>
      <link>https://blog.eucalyptus.cc/2023/10/24/469c6a44/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/24/469c6a44/</guid>
      <pubDate>Tue, 24 Oct 2023 02:58:23 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;#1.%E5%88%9B%E5%BB%BA%E8%A1%A8%EF%BC%9A&quot;&gt;1.创建表:&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p><strong><a href="#1.%E5%88%9B%E5%BB%BA%E8%A1%A8%EF%BC%9A">1.创建表:</a></strong></p><p><strong><a href="#2.%E4%BF%AE%E6%94%B9%E8%A1%A8%E7%BB%93%E6%9E%84%EF%BC%8C%E6%B7%BB%E5%8A%A0%E5%88%97%EF%BC%9A">2.修改表结构,添加列:</a></strong></p><p><strong><a href="#%C2%A03.%E5%88%A0%E9%99%A4%E8%A1%A8%EF%BC%9A">3.删除表:</a></strong></p><p><strong><a href="#4.%E5%88%9B%E5%BB%BA%E7%B4%A2%E5%BC%95%EF%BC%9A">4.创建索引:</a></strong></p><p><strong><a href="#5.%E5%88%9B%E5%BB%BA%E8%A7%86%E5%9B%BE%EF%BC%9A">5.创建视图:</a></strong></p><p><strong><a href="#6.%E4%BF%AE%E6%94%B9%E8%A1%A8%E5%90%8D%EF%BC%9A">6.修改表名:</a></strong></p><p><strong><a href="#7.%E4%BF%AE%E6%94%B9%E5%88%97%E5%90%8D%EF%BC%9A">7.修改列名:</a></strong></p><p><strong><a href="#8.%E5%88%A0%E9%99%A4%E7%B4%A2%E5%BC%95%EF%BC%9A">8.删除索引:</a></strong></p><p><strong><a href="#1.%E6%8F%92%E5%85%A5%E6%95%B0%E6%8D%AE%EF%BC%9A">1.插入数据:</a></strong></p><p><strong><a href="#2.%E6%9B%B4%E6%96%B0%E6%95%B0%E6%8D%AE%EF%BC%9A">2.更新数据:</a></strong></p><p><strong><a href="#3.%E5%88%A0%E9%99%A4%E6%95%B0%E6%8D%AE%EF%BC%9A">3.删除数据:</a></strong></p><p><strong><a href="#4.%E6%9F%A5%E8%AF%A2%E6%95%B0%E6%8D%AE%EF%BC%9A">4.查询数据:</a></strong></p><p><strong><a href="#5.%E6%9D%A1%E4%BB%B6%E6%9F%A5%E8%AF%A2%EF%BC%9A">5.条件查询:</a></strong></p><p><strong><a href="#6.%E6%8E%92%E5%BA%8F%E6%9F%A5%E8%AF%A2%EF%BC%9A">6.排序查询:</a></strong></p><p><strong><a href="#7.%E8%81%9A%E5%90%88%E5%87%BD%E6%95%B0%E6%9F%A5%E8%AF%A2%EF%BC%9A">7.聚合函数查询:</a></strong></p><p><strong><a href="#8.%E8%BF%9E%E6%8E%A5%E6%9F%A5%E8%AF%A2%EF%BC%9A">8.连接查询:</a></strong></p><p><strong><a href="#1.%E6%9F%A5%E8%AF%A2%E6%89%80%E6%9C%89%E6%95%B0%E6%8D%AE%EF%BC%9A">1.查询所有数据:</a></strong></p><p><strong><a href="#2.%E6%8C%87%E5%AE%9A%E5%88%97%E6%9F%A5%E8%AF%A2%EF%BC%9A">2.指定列查询:</a></strong></p><p><strong><a href="#3.%E6%9D%A1%E4%BB%B6%E6%9F%A5%E8%AF%A2%EF%BC%9A">3.条件查询:</a></strong></p><p><strong><a href="#4.%E6%8E%92%E5%BA%8F%E6%9F%A5%E8%AF%A2%EF%BC%9A">4.排序查询:</a></strong></p><p><strong><a href="#5.%E5%88%86%E7%BB%84%E6%9F%A5%E8%AF%A2%EF%BC%9A">5.分组查询:</a></strong></p><p><strong><a href="#6.%E8%81%9A%E5%90%88%E5%87%BD%E6%95%B0%E6%9F%A5%E8%AF%A2%EF%BC%9A">6.聚合函数查询:</a></strong></p><p><strong><a href="#7.%E8%BF%9E%E6%8E%A5%E6%9F%A5%E8%AF%A2%EF%BC%9A">7.连接查询:</a></strong></p><p><strong><a href="#8.%E5%AD%90%E6%9F%A5%E8%AF%A2%EF%BC%9A">8.子查询:</a></strong></p><p><strong><a href="#1.%E6%8E%88%E6%9D%83%E7%94%A8%E6%88%B7%EF%BC%9A">1.授权用户:</a></strong></p><p><strong><a href="#2.%E6%92%A4%E9%94%80%E7%94%A8%E6%88%B7%E6%9D%83%E9%99%90%EF%BC%9A">2.撤销用户权限:</a></strong></p><p><strong><a href="#3.%E5%88%9B%E5%BB%BA%E8%A7%92%E8%89%B2%EF%BC%9A">3.创建角色:</a></strong></p><p><strong><a href="#4.%E6%8E%88%E6%9D%83%E8%A7%92%E8%89%B2%EF%BC%9A">4.授权角色:</a></strong></p><p><strong><a href="#5.%E5%B0%86%E7%94%A8%E6%88%B7%E6%B7%BB%E5%8A%A0%E5%88%B0%E8%A7%92%E8%89%B2%EF%BC%9A">5.将用户添加到角色:</a></strong></p><p><strong><a href="#6.%E6%92%A4%E9%94%80%E8%A7%92%E8%89%B2%E6%9D%83%E9%99%90%EF%BC%9A">6.撤销角色权限:</a></strong></p><p><strong><a href="#7.%E5%88%A0%E9%99%A4%E8%A7%92%E8%89%B2%EF%BC%9A">7.删除角色:</a></strong></p><p><strong><a href="#8.%E5%88%9B%E5%BB%BA%E8%A7%86%E5%9B%BE%EF%BC%9A">8.创建视图:</a></strong></p><p><strong><a href="#9.%E4%BF%AE%E6%94%B9%E8%A7%86%E5%9B%BE%EF%BC%9A">9.修改视图:</a></strong></p><p><strong><a href="#10.%E5%88%A0%E9%99%A4%E8%A7%86%E5%9B%BE%EF%BC%9A">10.删除视图:</a></strong></p><p><strong><a href="#%E6%80%BB%E7%BB%93">总结</a></strong></p><p>当谈到MySQL数据库时,你会想到什么?索引、键、表、视图、触发器还是开源性。那么你知道MySQL中SQL语言的分类吗?下面我们将会介绍到SQL语言。当谈到MySQL中的四种语言 DDL、DML、DQL、DCL 时,可以使用表格进行简洁的介绍:</p><table><thead><tr><th>语言类型</th><th>全称</th><th>作用</th><th>DDL</th><th>Data Definition Language 数据定义语言</th><th>用于定义数据库结构和模式的操作,包括创建、修改和删除数据库对象。常见命令有CREATE、ALTER和DROP。</th><th>DML</th><th>Data Manipulation Language 数据操作语言</th><th>用于对数据库中的数据进行操作,如插入、更新和删除数据。允许用户对表中的数据进行增删改操作。常见命令有INSERT、UPDATE和DELETE。</th><th>DQL</th><th>Data Query Language 数据查询语言</th><th>用于从数据库中检索数据,执行查询操作。允许用户根据条件查询数据库中的数据,并返回满足条件的结果集。常见命令是SELECT。</th><th>DCL</th><th>Data Control Language 数据控制语言</th><th>用于控制数据库的访问权限和安全性。包括授权用户对数据库对象的访问权限以及撤销权限。常见命令有GRANT和REVOKE。</th></tr></thead></table><p>这个表格简明扼要地列出了每种语言的全称和作用。通过使用这些语言,可以在MySQL中定义数据库结构、操作数据、查询数据以及控制数据库的访问权限和安全性。</p><h2 id="DDL"><a href="#DDL" class="headerlink" title="DDL"></a>DDL</h2><p>DDL是数据定义语言 Data Definition Language 的缩写,它是SQL语言的一部分,用于定义数据库的结构和模式。DDL命令可以创建、修改和删除数据库对象,如表、索引、视图、存储过程等。</p><p>下面是一些常用的DDL命令:</p><ul><li><p>CREATE:用于创建数据库对象,如表、索引、视图等。CREATE TABLE语句用于创建表,CREATE INDEX语句用于创建索引,CREATE VIEW语句用于创建视图。</p></li><li><p>ALTER:用于修改数据库对象的结构,如添加、删除、修改列、约束、索引等。ALTER TABLE语句用于修改表结构,ALTER INDEX语句用于修改索引结构。</p></li><li><p>DROP:用于删除数据库对象,如表、索引、视图等。DROP TABLE语句用于删除表,DROP INDEX语句用于删除索引,DROP VIEW语句用于删除视图。</p></li><li><p>TRUNCATE:用于删除表中的所有数据,但保留表的结构。TRUNCATE TABLE语句用于删除表中的所有数据。</p></li><li><p>RENAME:用于重命名数据库对象,如表、列、索引等。RENAME TABLE语句用于重命名表,RENAME COLUMN语句用于重命名列。</p></li></ul><p>DDL命令对数据库结构和模式进行操作,因此需要谨慎使用。在执行DDL命令之前,应该先备份数据,以免误操作导致数据丢失。同时,DDL命令也需要满足数据库的安全性要求,只有授权用户才能执行DDL命令。</p><p>以下是一些使用SQL代码表示的DDL示例:</p><h3 id="1-创建表"><a href="#1-创建表" class="headerlink" title="1.创建表:"></a>1.创建表:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> students (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">age <span class="type">INT</span>,</span><br><span class="line">grade <span class="type">VARCHAR</span>(<span class="number">10</span>)</span><br><span class="line">);</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="2-修改表结构-添加列"><a href="#2-修改表结构-添加列" class="headerlink" title="2.修改表结构,添加列:"></a>2.修改表结构,添加列:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> students</span><br><span class="line"><span class="keyword">ADD</span> <span class="keyword">COLUMN</span> email <span class="type">VARCHAR</span>(<span class="number">100</span>);</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-删除表"><a href="#3-删除表" class="headerlink" title="3.删除表:"></a>3.删除表:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">DROP</span> <span class="keyword">TABLE</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="4-创建索引"><a href="#4-创建索引" class="headerlink" title="4.创建索引:"></a>4.创建索引:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> INDEX idx_students_name <span class="keyword">ON</span> students (name);</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="5-创建视图"><a href="#5-创建视图" class="headerlink" title="5.创建视图:"></a>5.创建视图:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">VIEW</span> student_details <span class="keyword">AS</span></span><br><span class="line"><span class="keyword">SELECT</span> id, name, age, grade <span class="keyword">FROM</span> students <span class="keyword">WHERE</span> grade <span class="string">&#x27;A&#x27;</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="6-修改表名"><a href="#6-修改表名" class="headerlink" title="6.修改表名:"></a>6.修改表名:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> students RENAME <span class="keyword">TO</span> new_students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="7-修改列名"><a href="#7-修改列名" class="headerlink" title="7.修改列名:"></a>7.修改列名:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER TABLE</span> students RENAME <span class="keyword">COLUMN</span> grade <span class="keyword">TO</span> class;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="8-删除索引"><a href="#8-删除索引" class="headerlink" title="8.删除索引:"></a>8.删除索引:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">DROP</span> INDEX idx_students_name;</span><br></pre></td></tr></table></figure><h2 id="DML"><a href="#DML" class="headerlink" title="DML"></a>DML</h2><p>DML Data Manipulation Language 是SQL语言的一部分,用于对数据库中的数据进行操作。DML命令用于插入、更新、删除和查询数据,它是数据库应用中最常用的一类命令。</p><p>以下是DML的一些主要操作:</p><ul><li><p>插入数据 INSERT :通过INSERT语句将新的数据行插入到数据库表中。可以指定要插入的列和对应的值,也可以使用SELECT语句从其他表中选择数据插入。</p></li><li><p>更新数据 UPDATE :使用UPDATE语句修改表中的现有数据行。可以指定要更新的列和对应的新值,并使用WHERE子句指定要更新的数据行。</p></li><li><p>删除数据 DELETE :使用DELETE语句从表中删除数据行。可以使用WHERE子句指定要删除的数据行。</p></li><li><p>查询数据 SELECT :使用SELECT语句从表中检索数据。可以指定要检索的列,使用FROM子句指定要检索的表,使用WHERE子句指定检索条件。</p></li><li><p>排序数据 ORDER BY :使用ORDER BY子句对查询结果进行排序,可以按照一个或多个列进行升序或降序排序。</p></li><li><p>聚合函数 Aggregate Functions :DML支持一些聚合函数,如COUNT、SUM、AVG、MIN和MAX等,用于计算数据的总数、总和、平均值、最小值和最大值。</p></li><li><p>连接查询 JOIN :通过连接多个表,可以根据关联条件从多个表中检索相关的数据。</p></li></ul><p>DML命令允许开发人员对数据库中的数据进行灵活的操作和处理。通过组合不同的DML命令,可以实现复杂的数据操作和查询需求。在使用DML命令时,需要注意数据的完整性和安全性,并根据具体的业务需求编写正确的DML语句。</p><p>以下是一些使用SQL代码表示的DML 数据操作语言 示例:</p><h3 id="1-插入数据"><a href="#1-插入数据" class="headerlink" title="1.插入数据:"></a>1.插入数据:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">INSERT INTO</span> students (id, name, age, grade)</span><br><span class="line"><span class="keyword">VALUES</span> (<span class="number">1</span>, <span class="string">&#x27;Alice&#x27;</span>, <span class="number">18</span>, <span class="string">&#x27;A&#x27;</span>);</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="2-更新数据"><a href="#2-更新数据" class="headerlink" title="2.更新数据:"></a>2.更新数据:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">UPDATE</span> students</span><br><span class="line"><span class="keyword">SET</span> age <span class="number">19</span></span><br><span class="line"><span class="keyword">WHERE</span> id <span class="number">1</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-删除数据"><a href="#3-删除数据" class="headerlink" title="3.删除数据:"></a>3.删除数据:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">DELETE</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">WHERE</span> id <span class="number">1</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="4-查询数据"><a href="#4-查询数据" class="headerlink" title="4.查询数据:"></a>4.查询数据:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="5-条件查询"><a href="#5-条件查询" class="headerlink" title="5.条件查询:"></a>5.条件查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">WHERE</span> grade <span class="string">&#x27;A&#x27;</span> <span class="keyword">AND</span> age <span class="operator">&gt;</span> <span class="number">18</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="6-排序查询"><a href="#6-排序查询" class="headerlink" title="6.排序查询:"></a>6.排序查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">ORDER</span> <span class="keyword">BY</span> age <span class="keyword">DESC</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="7-聚合函数查询"><a href="#7-聚合函数查询" class="headerlink" title="7.聚合函数查询:"></a>7.聚合函数查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="built_in">COUNT</span>(<span class="operator">*</span>) <span class="keyword">FROM</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="8-连接查询"><a href="#8-连接查询" class="headerlink" title="8.连接查询:"></a>8.连接查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> students.name, grades.grade</span><br><span class="line"><span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">JOIN</span> grades <span class="keyword">ON</span> students.id grades.student_id;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="DQL"><a href="#DQL" class="headerlink" title="DQL"></a>DQL</h2><p>DQL Data Query Language 是SQL语言的一部分,用于从数据库中检索数据。DQL命令主要用于查询和获取数据,而不是对数据进行修改。</p><p>以下是DQL的一些主要操作:</p><ul><li><p>基本查询 SELECT :使用SELECT语句从数据库表中检索数据。可以指定要检索的列,使用FROM子句指定要检索的表,使用WHERE子句指定检索条件。</p></li><li><p>条件查询:使用WHERE子句过滤查询结果,根据指定的条件筛选出符合要求的数据行。可以使用比较运算符 如等于、大于、小于等 、逻辑运算符 如AND、OR、NOT 和通配符 如LIKE 来构建条件。</p></li><li><p>排序查询 ORDER BY :使用ORDER BY子句对查询结果进行排序,可以按照一个或多个列进行升序或降序排序。</p></li><li><p>分组查询 GROUP BY :使用GROUP BY子句对查询结果进行分组,可以根据指定的列将数据分组,并使用聚合函数 如COUNT、SUM、AVG、MIN和MAX 对每个组进行计算。</p></li><li><p>连接查询 JOIN :通过连接多个表,可以根据关联条件从多个表中检索相关的数据。常见的连接类型包括内连接 INNER JOIN 、左连接 LEFT JOIN 和右连接 RIGHT JOIN 等。</p></li><li><p>子查询:在查询中嵌套使用子查询,子查询是一个嵌套在主查询中的查询语句,可以用来获取更复杂的查询结果。</p></li></ul><p>DQL命令允许开发人员根据需求灵活地从数据库中检索数据。通过组合不同的DQL命令和使用各种查询条件,可以实现复杂的数据查询和过滤需求。在编写DQL查询时,需要注意查询的效率和性能,并根据具体的业务需求编写正确的查询语句。</p><p>以下是一些使用SQL代码表示的DQL Data Query Language 示例:</p><h3 id="1-查询所有数据"><a href="#1-查询所有数据" class="headerlink" title="1.查询所有数据:"></a>1.查询所有数据:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="2-指定列查询"><a href="#2-指定列查询" class="headerlink" title="2.指定列查询:"></a>2.指定列查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> name, age <span class="keyword">FROM</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-条件查询"><a href="#3-条件查询" class="headerlink" title="3.条件查询:"></a>3.条件查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">WHERE</span> grade <span class="string">&#x27;A&#x27;</span> <span class="keyword">AND</span> age <span class="operator">&gt;</span> <span class="number">18</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="4-排序查询"><a href="#4-排序查询" class="headerlink" title="4.排序查询:"></a>4.排序查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">ORDER</span> <span class="keyword">BY</span> age <span class="keyword">DESC</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="5-分组查询"><a href="#5-分组查询" class="headerlink" title="5.分组查询:"></a>5.分组查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> grade, <span class="built_in">COUNT</span>(<span class="operator">*</span>) <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">GROUP</span> <span class="keyword">BY</span> grade;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="6-聚合函数查询"><a href="#6-聚合函数查询" class="headerlink" title="6.聚合函数查询:"></a>6.聚合函数查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="built_in">COUNT</span>(<span class="operator">*</span>) <span class="keyword">FROM</span> students;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="7-连接查询"><a href="#7-连接查询" class="headerlink" title="7.连接查询:"></a>7.连接查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> students.name, grades.grade</span><br><span class="line"><span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">JOIN</span> grades <span class="keyword">ON</span> students.id grades.student_id;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="8-子查询"><a href="#8-子查询" class="headerlink" title="8.子查询:"></a>8.子查询:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> students</span><br><span class="line"><span class="keyword">WHERE</span> age <span class="operator">&gt;</span> (<span class="keyword">SELECT</span> <span class="built_in">AVG</span>(age) <span class="keyword">FROM</span> students);</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="DCL"><a href="#DCL" class="headerlink" title="DCL"></a>DCL</h2><p>DCL Data Control Language 是SQL语言的一部分,用于控制数据库中的数据访问和权限管理。DCL命令允许开发人员授权和撤销用户对表、视图和其他数据库对象的操作权限,创建和管理角色以及定义访问控制策略。</p><p>以下是一些常见的DCL命令:</p><ul><li><p>GRANT:授权用户或角色对指定的数据库对象进行操作。可以授予SELECT、INSERT、UPDATE、DELETE等操作权限,也可以授予管理权限 如CREATE、ALTER、DROP等 。</p></li><li><p>REVOKE:撤销用户或角色对指定数据库对象的操作权限。</p></li><li><p>CREATE ROLE:创建角色,角色是一组权限的集合,可以将多个用户添加到同一个角色中,从而方便地管理用户权限。</p></li><li><p>DROP ROLE:删除角色。</p></li><li><p>ALTER ROLE:修改角色的属性,如名称、描述等。</p></li><li><p>GRANT ROLE:将角色授予给用户。</p></li><li><p>REVOKE ROLE:从用户中撤销角色。</p></li><li><p>CREATE VIEW:创建视图,视图是一种虚拟表,可以通过查询其他表或视图来创建,提供了一种更高层次的数据抽象。</p></li><li><p>ALTER VIEW:修改视图的定义。</p></li><li><p>DROP VIEW:删除视图。</p></li></ul><p>DCL命令对数据库的结构和安全性具有重要影响,因此在使用DCL命令时需要谨慎操作,以确保数据的完整性和安全性。需要注意的是,只有具有足够权限的用户才能执行DCL操作。数据库管理员通常拥有最高权限,可以执行所有DCL命令。</p><p>以下是一些使用SQL代码表示的DCL Data Control Language 示例:</p><h3 id="1-授权用户"><a href="#1-授权用户" class="headerlink" title="1.授权用户:"></a>1.授权用户:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span>, <span class="keyword">INSERT</span>, <span class="keyword">UPDATE</span> <span class="keyword">ON</span> employees <span class="keyword">TO</span> user1;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="2-撤销用户权限"><a href="#2-撤销用户权限" class="headerlink" title="2.撤销用户权限:"></a>2.撤销用户权限:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">REVOKE</span> <span class="keyword">INSERT</span>, <span class="keyword">UPDATE</span> <span class="keyword">ON</span> employees <span class="keyword">FROM</span> user1;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="3-创建角色"><a href="#3-创建角色" class="headerlink" title="3.创建角色:"></a>3.创建角色:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> ROLE manager;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="4-授权角色"><a href="#4-授权角色" class="headerlink" title="4.授权角色:"></a>4.授权角色:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> <span class="keyword">SELECT</span>, <span class="keyword">UPDATE</span> <span class="keyword">ON</span> employees <span class="keyword">TO</span> manager;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="5-将用户添加到角色"><a href="#5-将用户添加到角色" class="headerlink" title="5.将用户添加到角色:"></a>5.将用户添加到角色:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">GRANT</span> manager <span class="keyword">TO</span> user1;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="6-撤销角色权限"><a href="#6-撤销角色权限" class="headerlink" title="6.撤销角色权限:"></a>6.撤销角色权限:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">REVOKE</span> <span class="keyword">SELECT</span>, <span class="keyword">UPDATE</span> <span class="keyword">ON</span> employees <span class="keyword">FROM</span> manager;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="7-删除角色"><a href="#7-删除角色" class="headerlink" title="7.删除角色:"></a>7.删除角色:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">DROP</span> ROLE manager;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="8-创建视图"><a href="#8-创建视图" class="headerlink" title="8.创建视图:"></a>8.创建视图:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE</span> <span class="keyword">VIEW</span> employee_view <span class="keyword">AS</span></span><br><span class="line"><span class="keyword">SELECT</span> name, age, salary</span><br><span class="line"><span class="keyword">FROM</span> employees</span><br><span class="line"><span class="keyword">WHERE</span> department <span class="string">&#x27;IT&#x27;</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="9-修改视图"><a href="#9-修改视图" class="headerlink" title="9.修改视图:"></a>9.修改视图:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">ALTER</span> <span class="keyword">VIEW</span> employee_view</span><br><span class="line"><span class="keyword">AS</span></span><br><span class="line"><span class="keyword">SELECT</span> name, age, salary</span><br><span class="line"><span class="keyword">FROM</span> employees</span><br><span class="line"><span class="keyword">WHERE</span> department <span class="string">&#x27;HR&#x27;</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="10-删除视图"><a href="#10-删除视图" class="headerlink" title="10.删除视图:"></a>10.删除视图:</h3><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">DROP</span> <span class="keyword">VIEW</span> employee_view;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><ul><li><p>DDL操作可能会对数据库产生重大影响,请在操作之前务必进行充分的备份和谨慎评估。</p></li><li><p>DML操作时要小心,确保对数据的操作符合预期,并且遵循数据库的安全性和完整性要求。</p></li><li><p>DQL查询时要小心,确保查询结果符合预期,并且遵循数据库的安全性和完整性要求。</p></li><li><p>DCL命令执行时需要谨慎操作,以确保数据的完整性和安全性。</p></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/24/469c6a44/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>数据库演进：关系型与NoSQL的比较与选择,</title>
      <link>https://blog.eucalyptus.cc/2023/10/23/794e167c/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/23/794e167c/</guid>
      <pubDate>Mon, 23 Oct 2023 08:14:09 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;数据库的发展经历了从简单的文件系统到层次结构、网状结构、关系型结构以及现在的NoSQL、NewSQL等多种类型的演化,同时也伴随着计算机技术和互联网的发展而不断地发展和改进。数据库的出现和发展让数据的存储、管理和应用变得更加高效和便捷,成为现代信息化社会中不可或缺的一部分。</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>数据库的发展经历了从简单的文件系统到层次结构、网状结构、关系型结构以及现在的NoSQL、NewSQL等多种类型的演化,同时也伴随着计算机技术和互联网的发展而不断地发展和改进。数据库的出现和发展让数据的存储、管理和应用变得更加高效和便捷,成为现代信息化社会中不可或缺的一部分。</p><h2 id="数据库分类"><a href="#数据库分类" class="headerlink" title="数据库分类"></a>数据库分类</h2><h3 id="关系型数据库"><a href="#关系型数据库" class="headerlink" title="关系型数据库"></a>关系型数据库</h3><ul><li>MySQL</li><li>PostgreSQL</li><li>Oracle</li><li>SQL Server</li><li>MariaDB</li></ul><h4 id="MySQL"><a href="#MySQL" class="headerlink" title="MySQL"></a>MySQL</h4><p>MySQL是一种常用的开源关系型数据库管理系统 RDBMS 。它是一个可靠、高性能且易于使用的数据库解决方案,广泛用于Web应用程序的后端数据存储。</p><p>以下是MySQL的一些特点和功能:</p><ul><li><p>开源性:MySQL以GPL 通用公共许可证 开源许可证发布,允许用户自由地使用、修改和分发。</p></li><li><p>可靠性和稳定性:MySQL经过广泛测试,并被大量的企业和机构在生产环境中使用。它具有出色的稳定性和容错能力。</p></li><li><p>高性能:MySQL通过多种优化技术和索引结构提供高效的数据访问和查询性能。它可以处理大规模的数据集和高并发请求。</p></li><li><p>简单易用:MySQL提供了直观的命令行工具和图形界面工具,使用户能够轻松管理和操作数据库。</p></li><li><p>跨平台支持:MySQL可在多个操作系统上运行,包括Windows、Linux、macOS等,便于开发人员根据需要进行部署。</p></li><li><p>数据安全性:MySQL提供了各种安全功能,如用户认证、数据加密、访问控制和审计日志等,以确保数据的安全性和完整性。</p></li><li><p>复制和高可用性:MySQL支持主从复制和主主复制等复制方式,使数据可以在多个节点间进行同步,以提高可用性和容错能力。</p></li><li><p>扩展性:MySQL可以根据需求进行水平和垂直扩展,通过添加更多的服务器节点或增加硬件资源来满足不断增长的数据处理需求。</p></li><li><p>多种编程语言支持:MySQL提供了多种编程语言的API和驱动程序,如Java、Python、PHP等,方便开发人员在不同的应用程序中使用MySQL。</p></li></ul><p>总的来说,MySQL是一个成熟、稳定且功能丰富的关系型数据库管理系统。它在广泛的应用场景中得到了验证,并且具有庞大的用户社区和活跃的开发者社区,提供了丰富的资源和支持。</p><h4 id="PostgreSQL"><a href="#PostgreSQL" class="headerlink" title="PostgreSQL"></a>PostgreSQL</h4><p>PostgreSQL是一种高级的开源关系型数据库管理系统(RDBMS),广泛用于Web应用程序、日志处理、地理信息系统(GIS)等场景。</p><p>以下是PostgreSQL的一些特点和功能:</p><ul><li><p>开源性:PostgreSQL以PostgreSQL许可证 类似于MIT许可证 的形式发布,允许用户自由使用、修改和分发。</p></li><li><p>数据安全性:PostgreSQL在数据安全方面提供了丰富的功能,如SSL支持、访问控制、加密扩展、行级别安全等,以确保数据的安全性和完整性。</p></li><li><p>可靠性和稳定性:PostgreSQL经过广泛测试,并被大量的企业和机构在生产环境中使用。它具有出色的稳定性和容错能力。</p></li><li><p>高性能:PostgreSQL通过多种优化技术和索引结构提供高效的数据访问和查询性能。它可以处理大规模的数据集和高并发请求。</p></li><li><p>复制和高可用性:PostgreSQL支持主从复制和流式复制等复制方式,使数据可以在多个节点间进行同步,以提高可用性和容错能力。</p></li><li><p>扩展性:PostgreSQL可以根据需求进行水平和垂直扩展,通过添加更多的服务器节点或增加硬件资源来满足不断增长的数据处理需求。</p></li><li><p>多种编程语言支持:PostgreSQL提供了多种编程语言的API和驱动程序,如Java、Python、PHP等,方便开发人员在不同的应用程序中使用PostgreSQL。</p></li><li><p>强大的功能和扩展性:PostgreSQL具有丰富的功能和扩展性,如SQL完整度、事务、触发器、存储过程、插件架构等。</p></li><li><p>出色的GIS支持:PostgreSQL具有出色的地理信息系统(GIS)支持,包括空间索引、查询函数、可视化等,使开发人员能够轻松处理空间数据。</p></li></ul><p>总体来说,PostgreSQL是一个功能强大而稳定的关系型数据库管理系统,广泛用于企业级应用、Web应用程序、数据分析等场景。它具有出色的性能、安全性和可扩展性,并且得到了活跃的开发者社区的支持和发展。</p><h4 id="Oracle"><a href="#Oracle" class="headerlink" title="Oracle"></a>Oracle</h4><p>Oracle是一种领先的商业关系型数据库管理系统 RDBMS ,由Oracle Corporation开发和销售。它是业界广泛使用的数据库解决方案之一,用于企业级应用、大规模数据处理、数据仓库等场景。</p><p>以下是Oracle数据库的一些主要特点和功能:</p><ul><li><p>高性能:Oracle数据库通过多种技术和优化策略提供卓越的性能。它具有高效的查询处理、并行执行能力以及强大的索引和缓存机制,能够处理大规模的数据和高并发请求。</p></li><li><p>可靠性和稳定性:Oracle数据库以其出色的可靠性而闻名。它具有事务处理的ACID特性,支持强大的错误恢复和故障转移机制,能够保证数据的完整性和可用性。</p></li><li><p>安全性:Oracle数据库提供了多层次的安全功能,如用户认证、细粒度的访问控制、数据加密、审计等。这些功能保护了敏感数据免受未经授权的访问和恶意攻击。</p></li><li><p>扩展性:Oracle数据库支持水平和垂直扩展,可以根据需求进行横向扩展 添加更多的服务器节点 或纵向扩展 增加硬件资源 。这使得它能够满足不断增长的数据处理需求。</p></li><li><p>复制和高可用性:Oracle数据库支持多种复制和高可用性方案,如物理备份、逻辑备份、数据集群等。这些方案确保了数据的冗余存储和故障切换,提高了系统的可用性和容错能力。</p></li><li><p>强大的开发工具和生态系统:Oracle提供了丰富的开发工具和API,如SQL Developer、PL&#x2F;SQL、JDBC等,方便开发人员进行数据库设计、查询和编程。此外,Oracle拥有庞大的第三方开发者社区和广泛的支持资源。</p></li><li><p>数据管理和分析功能:Oracle数据库提供了强大的数据管理和分析功能,包括分区表、索引、查询优化器、数据挖掘、报表生成等。这些功能有助于开发人员更高效地组织和处理数据,并从中获取有价值的信息。</p></li></ul><p>总的来说,Oracle数据库是一种功能强大、可靠性高的商业关系型数据库管理系统。它在企业级应用和大型数据处理领域具有广泛的应用,通过提供高性能、可靠性和安全性,满足了复杂的数据管理和分析需求。</p><h4 id="SQL-Server"><a href="#SQL-Server" class="headerlink" title="SQL Server"></a>SQL Server</h4><p>SQL Server是由微软公司开发和销售的关系型数据库管理系统 RDBMS 。它是业界广泛使用的数据库解决方案之一,适用于各种规模和类型的应用程序。</p><p>以下是SQL Server的一些主要特点和功能:</p><ul><li><p>可靠性和稳定性:SQL Server以其高度可靠的性能而闻名。它具有事务处理的ACID特性,支持故障转移和数据冗余机制,确保数据的完整性和可用性。</p></li><li><p>安全性:SQL Server提供了多层次的安全功能,包括数据加密、访问控制、身份验证和授权等。它支持角色和权限管理,以及审计功能,保护敏感数据免受未经授权的访问和攻击。</p></li><li><p>高性能:SQL Server通过优化器和索引机制提供卓越的查询处理性能。它还具有并行处理、查询优化和内存管理等功能,可处理大规模的数据和高并发请求。</p></li><li><p>可扩展性:SQL Server支持水平和垂直扩展,可以根据需求添加更多的服务器节点或增加硬件资源。这使得它能够适应不断增长的数据处理需求。</p></li><li><p>商业智能和数据分析:SQL Server提供了丰富的商业智能和数据分析功能。它具备强大的数据仓库和报表生成能力,支持数据挖掘、OLAP分析和大数据集成等,帮助用户从数据中获得有价值的信息。</p></li><li><p>开发工具和集成环境:SQL Server提供了多种开发工具和集成环境,如SQL Server Management Studio SSMS 、Visual Studio等。这些工具简化了数据库的管理和开发任务,并提供了丰富的调试和性能分析功能。</p></li><li><p>平台兼容性:SQL Server可在Windows操作系统上运行,并与Windows Server、Azure云服务等无缝集成。此外,SQL Server还提供了Linux版,增加了在其他操作系统上部署和运行的灵活性。</p></li></ul><p>总的来说,SQL Server是一种功能强大、可靠性高的关系型数据库管理系统。它通过提供可靠性、安全性和高性能,满足了各种规模和类型的应用程序的数据库需求,并提供了丰富的商业智能和数据分析功能。</p><h4 id="MariaDB"><a href="#MariaDB" class="headerlink" title="MariaDB"></a>MariaDB</h4><p>MariaDB是一个开源的关系型数据库管理系统 RDBMS ,它是MySQL数据库的一个分支。它由MySQL的创始人之一Michael Widenius在Oracle收购Sun Microsystems后创建,并以他女儿的名字命名。</p><p>以下是MariaDB的一些主要特点和功能:</p><ul><li><p>兼容性:MariaDB与MySQL高度兼容,可以无缝地迁移和替换MySQL数据库。它使用与MySQL相同的客户端和驱动程序,并支持大多数MySQL的语法和功能。</p></li><li><p>开源和社区驱动:MariaDB采用开源模式,基于GNU通用公共许可证发布。它由一个庞大的全球社区支持和贡献,不断进行改进和优化。</p></li><li><p>高性能:MariaDB通过使用更快的查询优化器、查询缓存和多线程处理等技术,提供了卓越的性能。它还支持并行复制和多源复制等特性,提高了数据处理的效率。</p></li><li><p>可靠性和稳定性:MariaDB具有良好的稳定性和可靠性。它通过支持事务处理和ACID属性,确保数据的完整性和一致性。此外,它还提供了故障转移和数据冗余机制,增加了系统的可用性。</p></li><li><p>安全性:MariaDB提供了多层次的安全功能,包括用户认证、访问控制和数据加密等。它支持角色和权限管理,并具有审计和日志功能,保护敏感数据免受未经授权的访问和攻击。</p></li><li><p>数据管理和扩展性:MariaDB支持广泛的数据管理功能,如分区表、索引、视图和存储过程等。它还支持水平和垂直扩展,可以根据需求增加服务器节点或增加硬件资源。</p></li><li><p>其他特性:MariaDB还提供了一些额外的功能,如动态列、数据类型扩展、JSON支持和GIS 地理信息系统 功能等。这些功能增强了数据库的灵活性和适用性。</p></li></ul><p>总的来说,MariaDB是一个功能强大、高性能的开源关系型数据库管理系统。它以与MySQL的高度兼容性、稳定性和可靠性而著称,并通过社区驱动的开发模式不断改进和创新。无论是小型应用还是大型企业级应用,MariaDB都是一个可靠的数据库选择。</p><h3 id="NoSQL数据库"><a href="#NoSQL数据库" class="headerlink" title="NoSQL数据库"></a>NoSQL数据库</h3><ul><li>Redis</li><li>MongoDB</li></ul><h4 id="Redis"><a href="#Redis" class="headerlink" title="Redis"></a>Redis</h4><p>Redis Remote Dictionary Server 是一个开源的内存数据结构存储系统,也被称为数据结构服务器。它提供了一个键值对存储模型,支持多种数据结构,如字符串、哈希表、列表、集合、有序集合等。</p><p>以下是Redis的一些主要特点和功能:</p><ul><li><p>内存存储:Redis将数据存储在内存中,因此读取和写入速度非常快。它适用于需要快速访问和响应时间的应用程序,并可通过持久化机制将数据保存到磁盘上,以实现数据的持久化存储。</p></li><li><p>数据结构支持:Redis支持多种数据结构,如字符串、哈希表、列表、集合、有序集合等。这些数据结构具有丰富的操作命令,如插入、删除、更新、查找、排序等,使得开发人员能够更方便地处理和操作数据。</p></li><li><p>发布&#x2F;订阅模式:Redis支持发布&#x2F;订阅模式,即可以发布消息和订阅消息。这使得不同的应用程序和服务可以通过消息传递进行解耦和通信,实现高效的消息发布和实时通知。</p></li><li><p>缓存机制:由于Redis的快速读写性能和灵活的数据结构,它经常被用作缓存服务器。通过将频繁访问的数据存储在内存中,可以大大提高应用程序的性能和响应能力。</p></li><li><p>分布式支持:Redis可通过主从复制和分片两种方式实现数据的分布式存储和负载均衡。主从复制可以提高系统的可用性和容错性,分片可以扩展系统的处理能力和存储容量。</p></li><li><p>事务支持:Redis支持事务,在一次请求中执行多个命令,保证了这些命令的原子性,即要么全部成功执行,要么全部失败。这使得开发人员能够对一系列相关操作进行批处理和管理。</p></li><li><p>持久化支持:Redis提供了两种持久化机制,分别是快照 snapshotting 和日志 append-only file 。快照可以周期性地将数据保存到磁盘上,而日志则记录了每个写操作,确保数据不会丢失。</p></li></ul><p>总的来说,Redis是一个快速、灵活和可靠的键值数据库系统,适用于缓存、消息队列、实时应用等各种场景。它具有多种数据结构的支持、发布&#x2F;订阅功能、分布式支持和事务支持等特性,使得开发人员能够高效地处理和管理数据。</p><h4 id="MongoDB"><a href="#MongoDB" class="headerlink" title="MongoDB"></a>MongoDB</h4><p>MongoDB是一个开源的分布式文档数据库,它以可扩展性、灵活性和高性能而闻名。作为一种面向文档的数据库管理系统 DBMS ,MongoDB以JSON样式的文档作为数据存储的基本单位。</p><p>以下是MongoDB的一些主要特点和功能:</p><ul><li><p>文档存储模型:MongoDB使用文档 Document 来组织和存储数据,文档是由键值对组成的类似于JSON格式的数据结构。这种存储方式非常灵活,可以存储不同结构的文档,而不需要预定义表结构。</p></li><li><p>分布式数据库:MongoDB支持水平扩展,可以将数据分布在多个服务器节点上,实现负载均衡和数据的高可用性。它提供了内建的复制机制和分片功能,使得数据的分布式管理变得简单且可靠。</p></li><li><p>高性能:MongoDB使用内存映射文件技术,将磁盘上的数据映射到内存中,以实现高效的读写操作。它还支持索引和查询优化,可以快速地检索和操作大规模数据集。</p></li><li><p>强大的查询语言:MongoDB提供了丰富的查询语法和表达式,可以进行复杂的查询和数据聚合操作。它支持查询嵌套文档、范围查询、正则表达式查询、地理空间查询等多种查询方式,满足不同场景的数据需求。</p></li><li><p>数据复制和容错性:MongoDB通过复制机制实现了数据的冗余备份和故障恢复。它可以将数据复制到多个节点上,当主节点出现故障时,自动选举新的主节点,并保证数据的一致性和可用性。</p></li><li><p>数据安全和权限控制:MongoDB提供了安全性功能,如访问控制、身份验证和数据加密等。它支持基于角色的访问控制,可以对用户进行细粒度的权限管理,确保数据的安全性和隐私性。</p></li><li><p>可扩展性和灵活性:MongoDB具有良好的扩展性,可以根据应用程序的需求进行水平扩展或垂直扩展。它还支持动态更新文档结构,可以轻松地适应数据模型的变化。</p></li></ul><p>总的来说,MongoDB是一个高性能、可扩展和灵活的分布式文档数据库。它以面向文档的存储模型、分布式数据库、强大的查询语言和数据安全性而受到广泛使用。无论是开发Web应用、移动应用还是大规模数据分析,MongoDB都是一个强大的数据库选择。</p><h2 id="数据库对比"><a href="#数据库对比" class="headerlink" title="数据库对比"></a>数据库对比</h2><p>下面是MySQL、PostgreSQL、Oracle、SQL Server、MongoDB、Redis和MariaDB这些数据库的一些主要区别:</p><p>| MySQL | PostgreSQL | Oracle | SQL Server | MongoDB | Redis | MariaDB |</p><table><thead><tr><th>序号</th><th>表名</th><th>描述</th></tr></thead><tbody><tr><td>类型</td><td>关系型数据库</td><td>关系型数据库</td></tr><tr><td>关系型数据库</td><td>NoSQL数据库</td><td>NoSQL数据库</td></tr><tr><td>开源</td><td>是</td><td>是</td></tr><tr><td>否</td><td>是</td><td>是</td></tr><tr><td>事务支持</td><td>是</td><td>是</td></tr><tr><td>是</td><td>部分支持</td><td>部分支持</td></tr><tr><td>数据安全性</td><td>高</td><td>高</td></tr><tr><td>高</td><td>较低</td><td>较低</td></tr><tr><td>扩展性</td><td>中等</td><td>高</td></tr><tr><td>高</td><td>高</td><td>中等</td></tr><tr><td>查询语言</td><td>SQL</td><td>SQL</td></tr><tr><td>SQL</td><td>无</td><td>无</td></tr><tr><td>主要特点</td><td>简单易用,广泛应用于Web领域,性能较高</td><td>强大的功能和扩展性,支持复杂查询</td></tr><tr><td>完善的集成环境,与Microsoft产品紧密结合</td><td>面向文档的数据模型,灵活且可扩展</td><td>内存数据库,用于缓存和快速数据访问</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>这些数据库在类型、开源性质、事务支持、数据安全性、扩展性、查询语言以及主要特点等方面存在差异。选择适合自己需求的数据库时,需要根据项目的规模、性能要求、数据结构以及开发团队的熟悉程度进行综合考虑。</td><td></td><td></td></tr></tbody></table><h2 id=""><a href="#" class="headerlink" title=""></a></h2>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/23/794e167c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>数据库索引与键详解：MySQL中的优化策略</title>
      <link>https://blog.eucalyptus.cc/2023/10/16/3b031886/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/16/3b031886/</guid>
      <pubDate>Mon, 16 Oct 2023 08:19:48 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是索引&quot;&gt;&lt;a href=&quot;#什么是索引&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是索引"><a href="#什么是索引" class="headerlink" title="什么是索引"></a>什么是索引</h2><p>索引是数据库中的一种数据结构,用于加快对表中数据的访问速度。它类似于书籍的目录,可以帮助数据库快速定位和检索符合某个条件的数据。</p><p>索引通过按照某种规则 如升序或降序 对列的值进行排序,并创建一个索引文件,提供快速的查找路径。当执行查询时,数据库可以利用索引定位到符合条件的行,而无需扫描整个表,从而提高查询效率。</p><p>索引可以应用于单个列或多个列的组合,根据不同的需求可以选择不同的索引类型,如B-Tree索引、哈希索引、全文索引等。常见的索引类型具有不同的特点和适用场景,例如,B-Tree索引适用于范围查询和排序操作,哈希索引适用于精确查找,全文索引适用于文本搜索。</p><p>在使用索引时需要权衡存储空间和性能之间的平衡。索引虽然能提高查询速度,但也会占用额外的存储空间,并在插入、更新和删除数据时增加额外的开销。因此,在设计数据库时,需要根据实际情况和查询需求来合理选择索引的列和类型,以达到最佳的性能和存储效果。</p><h2 id="什么是键-Key"><a href="#什么是键-Key" class="headerlink" title="什么是键 Key"></a>什么是键 Key</h2><p>在MySQL中,键 Key 是用于唯一标识表中的每一行记录的概念。键可以分为三种类型:主键 Primary Key 、唯一键 Unique Key 和普通键 Normal Key 。</p><ul><li>主键 Primary Key : 主键是被选定为表中每一行记录唯一标识的列或列组合。主键必须是唯一且非空的,确保了表中的每一行记录都能被唯一地标识。一个表只能有一个主键,并且主键的值在整个表中必须是唯一的。</li><li>唯一键 Unique Key : 唯一键保证了被选择作为键的列或列组合具有唯一性,不允许重复值。与主键不同的是,唯一键可以包含空值 NULL ,即允许至多一个表中的记录不具有唯一键值。一个表可以有多个唯一键。</li><li>普通键 Normal Key : 普通键即非主键和非唯一键的键。它们可以包含重复值和空值,不会强制保持唯一性。普通键的目的是为了提高数据的查询效率,但不要求列或列组合的值是唯一的。<br>在设计数据库时,选择合适的键非常重要。主键用于唯一标识表中的每一行,是表中最基本的唯一标识符。唯一键用于确保某一列或列组合的值在表中是唯一的。普通键用于提高查询效率,但并不要求值的唯一性。通过合理选择和使用不同类型的键,可以确保数据库的数据完整性、一致性和高效性。</li></ul><h2 id="MySQL中常见的索引"><a href="#MySQL中常见的索引" class="headerlink" title="MySQL中常见的索引"></a>MySQL中常见的索引</h2><p>在MySQL中,常见的索引类型包括以下几种:</p><p>1.B-Tree索引</p><p>B-Tree索引是MySQL中最常用和默认的索引类型,它可以应用于单列或多列,可以包括NULL值或不包括NULL值,可以是唯一的或非唯一的。B-Tree索引可以加速等值查询、范围查询和ORDER BY等操作,但对于模糊匹配 如LIKE ‘%XXX%’ 等操作效果不佳。</p><p>2.哈希索引</p><p>哈希索引适用于等值查询,它可以把查询条件和索引值进行哈希计算,快速定位需要的数据。哈希索引对于范围查询、ORDER BY等操作效果不好,而且不能使用在唯一性约束上。</p><p>3.全文索引</p><p>全文索引适用于文本数据的模糊查询,它可以对文本进行分词和索引,提供强大的文本搜索功能。全文索引相对于B-Tree索引需要更大的存储空间,而且只能应用于MyISAM表和InnoDB表的特定字符集。</p><p>4.空间索引</p><p>空间索引适用于地理信息数据等具有空间属性的数据,它可以加速空间查询、距离计算和空间关系判断等操作。空间索引需要使用特定的数据类型和索引算法,如POINT、LINESTRING、POLYGON、RTREE等。</p><p>除了以上几种常见的索引类型外,MySQL还支持其他一些较少使用的索引类型,如全文索引的n-gram索引、B-Tree索引的前缀索引、哈希索引的in-memory哈希索引等。在实际应用中,需要根据查询需求和数据特点来选择合适的索引类型和优化策略。</p><h2 id="常见索引举例"><a href="#常见索引举例" class="headerlink" title="常见索引举例"></a>常见索引举例</h2><p>MySQL中常见的索引包括主键索引、唯一索引和普通索引。以下是一些常见索引的示例:</p><p>1.主键索引 Primary Key Index :用于唯一标识表中的每一行记录。例如,可以在users表的id字段上创建主键索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> users (</span><br><span class="line">id <span class="type">INT</span> <span class="keyword">PRIMARY KEY</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">50</span>)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>2.唯一索引 Unique Index :确保列或列组合的值在表中是唯一的。例如,可以在users表的email字段上创建唯一索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> users (</span><br><span class="line">id <span class="type">INT</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">50</span>) <span class="keyword">UNIQUE</span></span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>3.普通索引 Index :用于加速列的查询和排序操作。例如,在users表的name字段上创建普通索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> users (</span><br><span class="line">id <span class="type">INT</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">INDEX idx_name (name)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>4.复合索引 Composite Index :基于多个列创建的索引,用于支持多列的查询条件。例如,在users表的name和email字段上创建复合索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> users (</span><br><span class="line">id <span class="type">INT</span>,</span><br><span class="line">name <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">email <span class="type">VARCHAR</span>(<span class="number">50</span>),</span><br><span class="line">INDEX idx_name_email (name, email)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>5.全文索引 Full-Text Index :用于对文本进行全文搜索,支持模糊匹配和关键词搜索等。例如,在articles表的content字段上创建全文索引:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">CREATE TABLE</span> articles (</span><br><span class="line">id <span class="type">INT</span>,</span><br><span class="line">title <span class="type">VARCHAR</span>(<span class="number">100</span>),</span><br><span class="line">content TEXT,</span><br><span class="line">FULLTEXT idx_content (content)</span><br><span class="line">);</span><br></pre></td></tr></table></figure><p>请注意,以上示例仅供参考,实际应用中需要根据具体需求和数据特点来选择合适的索引类型和列。另外,索引的创建语法可能会因MySQL的版本和存储引擎而有所差异,建议参考相应版本的MySQL文档进行使用。</p><h2 id="键和索引的区别"><a href="#键和索引的区别" class="headerlink" title="键和索引的区别"></a>键和索引的区别</h2><p>在MySQL中,索引 Index 和键 Key 是两个相关但不完全相同的概念。</p><ul><li>索引 Index :索引是一种用于提高数据库查询效率的数据结构,它可以加速对表中数据的查找和排序操作。索引可以应用于单个列或多个列的组合,并根据索引类型 如B-Tree索引、哈希索引、全文索引等 进行构建。索引会按照特定的排序规则 如升序或降序 存储列值,并创建一个索引文件。当进行查询时,数据库可以利用索引快速定位符合条件的行,避免扫描整个表来查找数据。</li><li>键 Key :键是一种逻辑概念,表示表中某一列或列组合的标识符,用于唯一标识表中的每一行记录。键可以是主键、唯一键或普通键。在MySQL中,主键 Primary Key 是一种特殊的键,用于唯一标识表中的每一行记录,并且不允许重复值或空值。唯一键 Unique Key 是一种键,用于确保某一列或列组合的值在表中是唯一的,允许空值。普通键 Normal Key 是指除主键和唯一键之外的一般键,它可以有重复值和空值。<br>总结来说,索引是用于提高数据库查询效率的数据结构,键是用于唯一标识表中的每一行记录的逻辑概念。索引可以应用于键或一组列,它们的目的是不同的,但它们经常在数据库中结合使用以提供高效的数据操作。</li></ul><p>当使用表格来表示键 Key 和索引 Index 的区别时,可以使用以下表格进行对比:</p><table><thead><tr><th>键 Key</th><th>索引 Index</th><th>特点</th></tr></thead><tbody><tr><td>数据类型</td><td>逻辑概念</td><td>物理数据结构</td></tr><tr><td>唯一性</td><td>可能唯一</td><td>可以重复</td></tr><tr><td>空值处理</td><td>允许空值</td><td>不包含空值</td></tr><tr><td>主键约束</td><td>是</td><td>否</td></tr><tr><td>唯一约束</td><td>是</td><td>否</td></tr><tr><td>数据查询速度</td><td>快速查找</td><td>提高查询效率</td></tr><tr><td>数据修改速度</td><td>幂等操作</td><td>需要维护索引</td></tr><tr><td>使用限制</td><td>表中只能有一个主键,多个唯一键</td><td>可以根据需求创建多个索引</td></tr><tr><td>这个表格可以帮助你更好地理解键和索引之间的区别。键是逻辑概念,用于唯一标识表中的每一行记录,可以是主键、唯一键或普通键,具有唯一性和空值处理的特点。而索引是物理数据结构,用于提高数据查询的效率,可以包含重复值但不含空值,并需要维护索引来保持数据的一致性。同时,键可以包含主键和唯一约束,而索引则可以根据需求创建多个。</td><td></td><td></td></tr></tbody></table><p>请注意,这只是一种对比键和索引的方式,表格中的特点可能不是完全准确或全面的,但可以帮助你理解二者之间的基本区别。</p><h3 id="在生活中举例说明"><a href="#在生活中举例说明" class="headerlink" title="在生活中举例说明"></a>在生活中举例说明</h3><p>当我们购买商品时,可以将商品的条形码看作是一个键,用来唯一标识每一件商品。这个键是由商品生产商定义的,用来确保商品在销售和库存管理时能被正确追踪和管理。</p><p>而当超市或商场需要对商品进行管理时,它们可能会创建一些索引,例如按照商品类别、品牌、价格等进行分类和排序。这些索引可以帮助商家更快地定位和查询特定的商品,提高商品管理的效率。</p><p>在这个例子中,条形码就是商品的键,用来唯一标识每一件商品。而商品分类、品牌、价格等信息则是商家创建的索引,它们并不是用来唯一标识每一件商品的,而是用来加快商品管理和查询的速度。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/16/3b031886/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>优化MySQL查询：Hint的作用、使用场景与注意事项</title>
      <link>https://blog.eucalyptus.cc/2023/10/16/2a190962/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/16/2a190962/</guid>
      <pubDate>Mon, 16 Oct 2023 07:39:04 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是MySQL-Hint&quot;&gt;&lt;a href=&quot;#什么是MySQL-Hint&quot; class=&quot;headerlink&quot; title=&quot;什么是MySQL Hint&quot;&gt;&lt;/a&gt;什么是MySQL Hint&lt;/h2&gt;&lt;p&gt;MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是MySQL-Hint"><a href="#什么是MySQL-Hint" class="headerlink" title="什么是MySQL Hint"></a>什么是MySQL Hint</h2><p>MySQL Hint是一种能优化MySQL数据库查询性能的提示指令,也称为SQL注释或SQL提示。通过在SQL查询语句中添加hint,用户可以指导MySQL数据库选择最合适的查询执行路径。这种提示通常是以注释的形式添加到SQL查询语句中,以便优化MySQL的执行计划。当MySQL数据库优化器进行查询优化时,会考虑hint提供的信息,以生成更有效的查询执行计划。</p><h2 id="在什么情况下适用Hint"><a href="#在什么情况下适用Hint" class="headerlink" title="在什么情况下适用Hint"></a>在什么情况下适用Hint</h2><p>在一些特定情况下,可以考虑使用提示 hint 来指导MySQL的查询优化器生成更好的查询计划。以下是一些可能需要使用提示的情况:</p><ul><li>查询性能问题:当某个查询的性能较差,并且经过分析确定问题出现在查询计划选择上时,可以尝试使用提示来指导优化器选择更合适的计划。</li><li>强制索引使用:在某些情况下,MySQL的查询优化器可能没有选择最优的索引,或者无法正确识别应使用的索引。这时可以使用FORCE INDEX提示来强制指定使用特定的索引,以获得更好的查询性能。</li><li>去除不必要的连接:在多表连接查询中,优化器可能根据统计信息和规则自动选择连接的顺序。但在特定场景下,可能需要指定连接的顺序,使用STRAIGHT_JOIN提示来强制选择连接的顺序。</li><li>子查询优化:对于复杂的子查询结构,优化器有时可能无法生成最优的查询计划。可以使用UNNEST或MATERIALIZED等提示来控制子查询的优化方式。</li><li>控制查询执行方式:有时候希望限制查询的执行时间、内存消耗或其它资源使用。可以使用相应的提示来设置查询的最大执行时间、最大内存等。<br>需要注意的是,使用提示并不总是能够带来性能提升,有时反而可能导致性能下降。因此,在使用提示之前应该进行仔细评估和测试,并考虑是否有其他优化手段可以解决问题。此外,不同版本的MySQL可能支持不同的提示选项,应注意查阅相应版本的文档以了解可用的提示语法和选项。</li></ul><h2 id="MySQL中常用的Hint"><a href="#MySQL中常用的Hint" class="headerlink" title="MySQL中常用的Hint"></a>MySQL中常用的Hint</h2><p>MySQL中常用的几种hint包括:</p><ul><li>使用查询提示 Query Hints :例如使用STRAIGHT_JOIN提示强制使用连接的顺序,或使用USE INDEX提示指定索引的使用方式等。这些提示可以影响查询计划生成器的选择,但也可能导致性能问题,需要谨慎使用。</li><li>使用表提示 Table Hints :例如使用FORCE INDEX提示强制使用指定的索引,或使用IGNORE INDEX提示忽略指定的索引等。这些提示可以直接应用于特定的表,用于干预查询计划生成和执行过程中的索引选择。</li><li>使用优化器提示 Optimizer Hints :例如使用&#x2F;* MAX_EXECUTION_TIME(n)<em>&#x2F;提示设置查询的最大执行时间,或使用&#x2F;</em> NO_MERGE(t1) *&#x2F;提示禁止合并指定的子查询等。这些提示主要用于控制查询的执行或优化器的行为,但同样需要小心使用,以避免不良影响或错误。<br>请注意,提示在MySQL中是可选的,并不是必需的,因为MySQL的查询优化器通常会自动选择最优的查询计划。但在某些情况下,使用提示可以强制MySQL使用特定的查询计划或索引,从而达到性能优化的目的。</li></ul><p>值得注意的是,不同版本的MySQL可能支持不同的提示语法和选项,因此在使用提示时应参考相应的MySQL版本文档以确保正确使用。此外,过度使用或错误使用提示可能产生负面影响,因此在使用时应谨慎评估和测试其效果。</p><h2 id="使用Hint举例"><a href="#使用Hint举例" class="headerlink" title="使用Hint举例"></a>使用Hint举例</h2><p>当需要使用提示时,以下是一些常见的示例:</p><p>1.强制索引使用:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> table_name FORCE INDEX (index_name) <span class="keyword">WHERE</span> <span class="keyword">condition</span>;</span><br></pre></td></tr></table></figure><p>在上述语句中,通过使用FORCE INDEX提示,可以强制查询优化器使用指定的索引 index_name ,而不是根据统计信息和规则自动选择索引。</p><p>2.控制连接顺序:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> table1 STRAIGHT_JOIN table2 <span class="keyword">ON</span> <span class="keyword">condition</span>;</span><br></pre></td></tr></table></figure><p>在上述语句中,使用STRAIGHT_JOIN提示可以强制查询优化器按照指定的连接顺序 先表1再表2 执行连接操作,而不是根据自动选择的连接顺序执行。</p><p>3.控制子查询优化方式:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="operator">*</span> <span class="keyword">FROM</span> table1 <span class="keyword">WHERE</span> column1 <span class="keyword">IN</span> (<span class="keyword">SELECT</span> <span class="comment">/* UNNEST */</span> column2 <span class="keyword">FROM</span> table2 <span class="keyword">WHERE</span> <span class="keyword">condition</span>);</span><br></pre></td></tr></table></figure><p>在上述语句中,使用UNNEST提示可以告诉查询优化器将子查询展开为普通的JOIN操作,而不是作为独立的子查询执行。</p><p>4.控制查询执行方式:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> <span class="comment">/*! MAX_EXECUTION_TIME(1000) */</span> <span class="operator">*</span> <span class="keyword">FROM</span> table_name <span class="keyword">WHERE</span> <span class="keyword">condition</span>;</span><br></pre></td></tr></table></figure><p>在上述语句中,通过使用MAX_EXECUTION_TIME提示,可以限制查询的最大执行时间 单位:毫秒 ,防止执行时间过长。</p><p>需要注意的是,以上示例只是一些常见的情况,实际使用时需要根据具体的查询场景和需求来决定是否使用提示,并选择适合的提示类型和选项。使用提示需要谨慎评估和测试,确保其对性能有真正的改进效果。</p><h2 id="使用Hint需要注意的地方"><a href="#使用Hint需要注意的地方" class="headerlink" title="使用Hint需要注意的地方"></a>使用Hint需要注意的地方</h2><p>在使用提示 hint 时,需要注意以下几点:</p><ul><li>谨慎使用:提示是一种手动干预查询优化器的方式,需要谨慎使用。过度使用提示或错误使用提示可能导致查询性能下降或产生错误的结果。</li><li>版本兼容性:不同版本的MySQL可能支持不同的提示语法和选项。在使用提示之前,应查阅相应版本的文档,了解支持的提示类型、语法和选项。</li><li>持续评估和测试:使用提示后,应进行评估和测试,确保它们真正改善了查询性能。有时,优化器自动选择的查询计划可能比手动指定的计划更好,所以要不断监控和评估性能差异。</li><li>更新统计信息:提示可能会避开MySQL的统计信息,因此在使用提示后,应考虑及时更新相关表的统计信息,以便优化器能够基于准确的信息做出决策。</li><li>不可靠的提示:有些提示可能在未来版本中被废弃或移除,或者在某些情况下可能不起作用。因此,在使用提示之前,应对其稳定性和可靠性有所了解,并选择那些经过验证和经过时间检验的提示。</li><li>维护成本:在使用提示后,如果数据库结构、查询逻辑或查询负载发生变化,可能需要不断调整和更新提示。因此,使用提示可能会增加维护成本,需要在性能改进和维护成本之间进行权衡。<br>总之,使用提示是一种有风险的手动干预方式,需要谨慎评估和测试,并且在真正需要时使用。优化器通常会自动选择最优的查询计划,只有在特定情况下,使用提示才能带来额外的性能提升。</li></ul><p>本文章已经生成可运行项目 一键运行**</p><p>生成项目</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/16/2a190962/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL存储引擎详解</title>
      <link>https://blog.eucalyptus.cc/2023/10/16/2b5ada03/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/16/2b5ada03/</guid>
      <pubDate>Mon, 16 Oct 2023 04:01:38 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;什么是引擎&quot;&gt;&lt;a href=&quot;#什么是引擎&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="什么是引擎"><a href="#什么是引擎" class="headerlink" title="什么是引擎"></a>什么是引擎</h2><p>在关系型数据库中,存储引擎是负责管理数据的方式和方法的组件或模块。它定义了数据如何被存储、访问和操作,决定了数据库的性能、可靠性和功能。</p><p>存储引擎实现了数据库的核心功能,包括数据存储、索引管理、数据查询、事务处理、并发控制等。不同的存储引擎具有不同的特性和优势,可以根据应用需求选择最适合的引擎。</p><p>总结来说,存储引擎是数据库中负责管理数据存储和操作的组件,它定义了如何存储、访问和处理数据。选择合适的存储引擎对于数据库的性能和功能至关重要。</p><h2 id="引擎分类"><a href="#引擎分类" class="headerlink" title="引擎分类"></a>引擎分类</h2><p>MySQL中常见的存储引擎有以下几种:</p><ul><li>InnoDB引擎:默认的事务性存储引擎,支持ACID特性 原子性、一致性、隔离性、持久性 和行级锁定,并提供了高并发读写的能力。</li><li>MyISAM引擎:不支持事务处理和行级锁定,适合于读操作较多、写操作较少的应用场景。它不会占用过多的内存,并且支持全文本索引。</li><li>Memory引擎 也称为Heap引擎 :将数据存储在内存中,读写速度非常快,适用于临时数据存储和高速缓存。但是,该引擎不支持持久化存储,即服务重启后数据会丢失。</li><li>Archive引擎:专门用于存储归档数据的引擎,适用于大量历史数据或日志信息的存储。它具有高度压缩和快速插入的特点,但不支持更新和删除操作。</li><li>CSV引擎 用于存储以逗号分隔的值 。</li><li>Blackhole引擎 将所有写入操作转发到&#x2F;dev&#x2F;null设备,用于复制和日志测试 。</li><li>NDB Cluster引擎 适用于MySQL集群)。</li><li>X-Engine 引擎<br>根据应用需求和性能特点,选择合适的存储引擎对于数据库的性能和功能有着重要的影响。</li></ul><h3 id="InnoDB引擎"><a href="#InnoDB引擎" class="headerlink" title="InnoDB引擎"></a>InnoDB引擎</h3><p>InnoDB是MySQL的一种存储引擎,它被设计用于支持事务处理和高并发读写操作。</p><p>InnoDB存储引擎最初由Innobase Oy AB公司开发,随后被Oracle收购并成为MySQL AB的一部分。在MySQL 5.5版本以后,InnoDB成为MySQL默认的存储引擎。</p><p>相较于其他存储引擎,InnoDB具有以下几个特点:</p><ul><li>支持事务处理和崩溃恢复:InnoDB采用了ACID 原子性、一致性、隔离性和持久性 特性,保证数据的一致性和可靠性。它还具有崩溃恢复功能,可以在意外断电或故障时恢复未完成的事务。</li><li>支持行级锁定:InnoDB支持行级锁定,避免了对整个表或大部分表的加锁,从而使得多个用户可以同时访问同一张表而不会互相干扰。</li><li>支持外键约束:InnoDB支持外键约束,确保数据的完整性和一致性。当父表更新或删除时,子表中相关的行也会被更新或删除。</li><li>支持多版本控制:InnoDB实现了多版本控制 MVCC 机制,可以处理并发事务,允许读取未提交的数据,可防止死锁。</li><li>支持高并发读写操作:InnoDB使用自适应哈希索引和缓冲池,对热点数据进行缓存,减少物理读写操作的次数,提高了查询和写入速度。<br>因此,InnoDB存储引擎在支持高并发读写操作和事务处理方面表现出色,是MySQL最常用的存储引擎之一。</li></ul><h3 id="MyISAM引擎"><a href="#MyISAM引擎" class="headerlink" title="MyISAM引擎"></a>MyISAM引擎</h3><p>MyISAM是MySQL的一种存储引擎,是MySQL中最早的一种存储引擎,在早期版本的MySQL中被广泛使用。</p><p>与InnoDB不同,MyISAM不支持事务处理和崩溃恢复功能,也不支持行级锁定和外键约束。因此,在高并发读写和数据完整性方面,MyISAM的表现不如InnoDB。</p><p>不过,MyISAM有几个优点:</p><ul><li>快速查询:MyISAM采用了一种基于B树的索引机制,可以很快地进行单条记录的查找和精确匹配。</li><li>低的存储空间占用:MyISAM存储引擎对数据的压缩和文件大小的管理相对简单,因此在数据管理方面能够占用较小的存储空间。</li><li>适合用于大型的只读表:由于MyISAM采用了表级锁定,因此在读操作比较频繁、写操作相对较少、需要支持高并发访问的情况下,MyISAM比InnoDB要更加适用。<br>因此,如果需要进行大量的只读查询和具有节省存储空间的需求时,MyISAM可能是一个不错的选择。但是,由于其不支持事务处理和崩溃恢复等特性,不适合用于需要强数据完整性和一致性的应用程序,特别是对于在线交易、银行、金融等领域。</li></ul><h3 id="Memory引擎"><a href="#Memory引擎" class="headerlink" title="Memory引擎"></a>Memory引擎</h3><p>Memory引擎 也称为Heap引擎 是MySQL的一种存储引擎,它将数据存储在内存中而不是硬盘上。它是MySQL中最快的一种存储引擎,适用于对速度和临时性要求较高的场景。</p><p>Memory引擎的特点如下:</p><ul><li>数据存储在内存中:与其他引擎将数据存储在硬盘上不同,Memory引擎将数据完全存储在内存中,因此读取和写入数据的速度非常快。</li><li>不支持持久化功能:当MySQL服务器关闭或重启时,Memory引擎中的数据将丢失,因为数据只存在于内存中,所以它并不适合需要长期保存数据的应用场景。</li><li>表级锁定:Memory引擎使用表级锁定,这意味着在同一时刻只能有一个进程对表进行读写操作。这可能会导致并发性能问题,特别是在多线程环境下。</li><li>支持哈希索引和B树索引:Memory引擎支持哈希索引和B树索引,这两种索引都可以加快查询速度。</li><li>适用于临时数据和缓存:由于Memory引擎的数据存储在内存中且不支持持久化,它适合用于存储临时数据和缓存数据,例如会话数据、临时计算结果等。<br>尽管Memory引擎在性能方面具有优势,但也有一些限制。由于数据存储在内存中,因此受限于可用的内存大小。此外,数据写入过程中的故障或意外断电可能导致数据丢失。</li></ul><p>因此,在选择使用Memory引擎时,需要进行权衡考虑,根据实际需求判断是否适合使用,避免数据丢失和性能瓶颈等问题。</p><h3 id="Archive引擎"><a href="#Archive引擎" class="headerlink" title="Archive引擎"></a>Archive引擎</h3><p>023&#x2F;10&#x2F;16 上午11:54:22</p><p>Archive引擎是MySQL的一种存储引擎,它专门用于高度压缩和归档数据。它的设计目标是在保持较低的存储空间占用的同时,提供对归档数据的快速查询和检索。</p><p>Archive引擎的特点如下:</p><ul><li>高度压缩:Archive引擎使用非常高效的压缩算法,可以将数据以非常紧凑的方式进行存储,从而显著减小数据文件的大小。</li><li>只支持插入和查询:Archive引擎专注于数据归档,并且仅支持插入和查询操作。它不支持更新和删除操作,也不支持索引。</li><li>适合静态和历史数据:由于Archive引擎的主要目的是存储归档数据,它适用于存储那些不经常变动但需要保留的静态数据或历史数据。</li><li>查询性能较低:尽管Archive引擎可以提供高度压缩的存储,但其查询性能通常较低。因为在使用Archive引擎时,数据需要解压缩才能进行查询和检索操作。</li><li>不支持索引:为了实现高度的数据压缩,Archive引擎不支持任何索引。这意味着所有的查询都必须进行全表扫描,因此在对大量数据进行复杂查询时,性能可能会受到影响。<br>总结来说,Archive引擎适用于那些需要高度压缩和存档数据的场景,特别是对于静态和历史数据。它可以帮助节省存储空间,并提供基本的查询功能。然而,在需要频繁进行更新、删除操作或需要快速查询性能的情况下,建议选择其他更适合的存储引擎。</li></ul><h3 id="CSV引擎"><a href="#CSV引擎" class="headerlink" title="CSV引擎"></a>CSV引擎</h3><p>MySQL并没有内置的CSV引擎。但可以使用MySQL的CSV存储格式来处理CSV文件。CSV 逗号分隔值 是一种常见的文本文件格式,用于存储表格数据。</p><p>在MySQL中,你可以创建一个表,并将其存储为CSV格式。以下是使用MySQL的CSV存储格式的一些特点:</p><ul><li><p>存储为纯文本:CSV存储格式将数据以纯文本的方式存储,每条记录使用逗号进行分隔。</p></li><li><p>不支持索引和约束:由于CSV存储格式仅是将数据以文本形式存储,它不支持任何索引、主键或外键约束。</p></li><li><p>快速导入和导出:由于CSV存储格式是基于文本的,因此可以快速导入和导出数据,这对于从其他系统导入数据或生成报表非常有用。</p></li><li><p>数据类型推断:在导入CSV数据时,MySQL会尝试根据数据内容推断每列的数据类型。<br>要使用CSV存储格式,可以按照以下步骤操作:</p></li><li><p>创建表:创建一个MySQL表,定义各列的名称和数据类型。</p></li><li><p>使用CSV存储格式:在创建表时,使用 ENGINE CSV 语句指定表的存储引擎为CSV。</p></li><li><p>导入数据:将CSV文件导入到MySQL表中,可使用LOAD DATA INFILE语句。</p></li><li><p>导出数据:将表中的数据导出为CSV文件,可使用SELECT INTO OUTFILE语句。<br>请注意,MySQL的CSV存储格式适用于处理中间结果、临时数据或非常简单的数据存储需求。如果需要更复杂的查询和事务支持,请考虑使用其他MySQL存储引擎,如InnoDB或MyISAM。</p></li></ul><h3 id="Blackhole引擎"><a href="#Blackhole引擎" class="headerlink" title="Blackhole引擎"></a>Blackhole引擎</h3><p>Blackhole是MySQL的一种存储引擎,它实际上不存储任何数据。当你使用Blackhole引擎时,所有的数据都将被丢弃。</p><p>Blackhole引擎对于测试、复制和日志记录非常有用。例如,你可以将一个表从InnoDB或MyISAM等其他存储引擎转换为Blackhole引擎,以便作为复制或日志记录目标,而不会影响原始数据表的性能。</p><p>以下是使用Blackhole引擎的一些注意事项:</p><ul><li>不存储数据:Blackhole引擎不存储任何数据,因此你不能从中检索数据。</li><li>支持索引和约束:尽管Blackhole引擎不存储数据,但它可以支持和维护索引和约束。</li><li>用于数据复制:你可以使用Blackhole引擎作为MySQL复制的目标,这有利于在不影响主服务器性能的同时,快速地将数据同步到备用服务器。</li><li>用于日志记录:你可以使用Blackhole引擎作为日志记录表,以便记录操作历史、审计信息、错误日志等。</li><li>无需配置:你无需进行任何配置即可使用Blackhole引擎。它与其他MySQL存储引擎具有相同的语法和特性。<br>总之,Blackhole引擎对于测试、数据复制和日志记录等场景非常有用。由于它不存储数据,因此它可以提供很快的查询速度,并且不会占用太多的磁盘空间。</li></ul><h3 id="NDB-Cluster引擎"><a href="#NDB-Cluster引擎" class="headerlink" title="NDB Cluster引擎"></a>NDB Cluster引擎</h3><p>NDB Cluster引擎是MySQL的一种分布式存储引擎,也称作MySQL Cluster。它是一个完全分布式的、实时的、高可用的数据库解决方案,能够处理海量的数据以及高并发的读写请求。</p><p>NDB Cluster是基于共享磁盘并使用共享存储技术的传统数据库架构的严格分布式替代品。它支持多个MySQL节点之间的数据同步和负载均衡,因此在负载均衡和高可用性方面非常强大和可靠。NDB Cluster还支持故障切换和容错,并提供原子性操作和事务支持。</p><p>以下是NDB Cluster的一些主要特点:</p><ul><li>全部内存数据:NDB Cluster所有数据都存储在内存中,因此具有非常快的读写速度。</li><li>数据分区:NDB Cluster支持数据分区,可以将数据分布在多个节点上,使查询效率更高。</li><li>数据副本:每个数据分区可以有多个副本,以保证数据的可靠性和高可用性。</li><li>分布式查询:NDB Cluster具有分布式查询功能,可以在多个节点上同时执行查询,并将结果合并返回给客户端。</li><li>支持SQL接口:NDB Cluster支持标准的SQL接口,因此与MySQL的其他存储引擎兼容。<br>NDB Cluster引擎适用于需要高可用性、高并发读写和大规模数据存储的应用程序,例如电信和网络运营商、在线游戏、金融交易等领域。使用NDB Cluster需要对MySQL和分布式数据库架构有一定的了解,并进行了解MySQL Cluster的详细配置与部署。</li></ul><h3 id="X-Engine引擎"><a href="#X-Engine引擎" class="headerlink" title="X-Engine引擎"></a>X-Engine引擎</h3><p>X-Engine 引擎是阿里云自主研发的一种高性能、可扩展、分布式 MySQL 存储引擎,它主要用于大规模互联网应用程序的数据存储和处理。相对于传统的 InnoDB 存储引擎,X-Engine 引擎在以下方面进行了优化:</p><ul><li>高效的存储结构:X-Engine 引擎采用了 LSM-KV 存储引擎模型,可以实现更高效的写入和读取性能,特别是对于大量更新巨型表等 OLTP 场景,能够减少锁竞争和 I&#x2F;O 操作,提升性能和可靠性。</li><li>精细的资源管理:X-Engine 引擎实现了多级缓存,精细控制内存和磁盘使用,大幅降低了 I&#x2F;O 操作和处理延迟,提升了响应速度和吞吐量。此外,它还为大规模的集群和数据处理提供了优秀的可扩展性和高可用性。</li><li>全面的安全防护:X-Engine 引擎提供了完善的数据备份和恢复功能、事务和隔离级别、权限管理等安全特性,能够满足企业级数据存储和处理的需求。<br>但需要注意的是,X-Engine 是阿里云的专有技术,并未在开源社区中发布,因此无法在非阿里云环境中使用。如果你是在使用阿里云的 MySQL 服务 如 RDS ,那么你可以选择 X-Engine 作为存储引擎来获得更好的性能和稳定性。但如果你是在其他环境中使用 MySQL,目前是无法直接使用 X-Engine 引擎的。</li></ul><h2 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h2><table><thead><tr><th>存储引擎</th><th>主要特点与区别</th></tr></thead><tbody><tr><td>InnoDB</td><td>- 支持事务处理和外键约束<br>- 提供行级锁定和高并发性能<br>- 支持崩溃恢复和故障容错<br>- 默认的事务性存储引擎</td></tr><tr><td>MyISAM</td><td>- 不支持事务处理和外键约束<br>- 提供表级锁定和较好的读取性能<br>- 适用于大量读取操作的场景<br>- 不支持崩溃恢复和故障容错</td></tr><tr><td>Memory</td><td>- 数据存储在内存中，读写速度非常快<br>- 不支持事务处理、外键约束和持久性存储，重启后数据丢失<br>- 适用于缓存和临时数据存储</td></tr><tr><td>Archive</td><td>- 高度压缩存储，适用于存储大量归档数据<br>- 不支持索引和事务处理<br>- 适用于存储稀疏的历史数据，不经常进行读写操作</td></tr><tr><td>CSV</td><td>- 以逗号分隔 CSV 格式存储数据<br>- 不支持索引、事务处理和外键约束<br>- 适用于存储简单的数据集，如日志文件等</td></tr><tr><td>Blackhole</td><td>- 黑洞存储引擎，写入数据后直接丢弃，不进行实际存储和读取操作<br>- 适用于测试和性能评估，或实现主从同步时作为备用引擎</td></tr><tr><td>NDB Cluster</td><td>- 集群存储引擎，支持水平扩展和高可用性<br>- 提供多主复制、自动分片和故障恢复能力<br>- 适用于大规模分布式数据库环境</td></tr><tr><td>X-Engine</td><td>- 阿里云自主研发的高性能存储引擎，专为云原生场景下的MySQL设计<br>- 在InnoDB基础上进行优化和改进，提供更高的读写性能和可靠性<br>- 仅限于阿里云环境使用</td></tr></tbody></table><p>需要注意的是，不同的存储引擎适用于不同的场景和应用程序，选择合适的存储引擎取决于你的应用程序的需求和特性。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/16/2b5ada03/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL 5和MySQL 8的区别</title>
      <link>https://blog.eucalyptus.cc/2023/10/12/ee006171/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/12/ee006171/</guid>
      <pubDate>Thu, 12 Oct 2023 09:27:15 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;引言&quot;&gt;&lt;a href=&quot;#引言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="引言"><a href="#引言" class="headerlink" title="引言"></a>引言</h2><p>在数据库管理系统中,MySQL是一个广泛使用、开源的解决方案。它提供了强大的功能,同时具有优秀的性能和可扩展性。到目前为止,MySQL经历了两个重要的版本升级,从MySQL 5到MySQL 8。这两个版本在功能、性能和可扩展性方面都有一些显著的差异。本文将详细讨论这两个版本的差异以及MySQL 8的新功能。</p><h2 id="MySQL-5"><a href="#MySQL-5" class="headerlink" title="MySQL 5"></a>MySQL 5</h2><p>MySQL 5是MySQL数据库管理系统的一个主要版本,在MySQL数据库的发展历史中具有重要的里程碑意义。MySQL 5的</p><p>以下是MySQL 5的一些主要特点和功能:</p><ul><li><p>InnoDB存储引擎:MySQL 5引入了InnoDB存储引擎作为默认的事务引擎,提供了ACID 原子性、一致性、隔离性和持久性 事务支持,以及行级锁定和多版本并发控制 MVCC 等高级特性。</p></li><li><p>存储过程和触发器:MySQL 5引入了存储过程和触发器的支持,使得可以在数据库中使用更复杂的业务逻辑和数据处理操作。</p></li><li><p>视图:MySQL 5引入了视图的支持,允许用户创建虚拟表,从而简化查询和数据访问。</p></li><li><p>增强的查询优化器:MySQL 5对查询优化器进行了改进,提供了更好的查询执行计划生成和查询性能。</p></li><li><p>增强的索引支持:MySQL 5引入了更多类型的索引,包括全文索引、B-Tree索引和哈希索引,以提高查询效率。</p></li><li><p>外键支持:MySQL 5开始支持外键约束,使得在多表关联查询和数据完整性方面更加灵活和方便。</p></li><li><p>分区表和分布式查询:MySQL 5引入了分区表的支持,可以将大型表分割成若干个子表,以提高查询和维护的效率。此外,MySQL 5还引入了分布式查询的功能,允许在多个MySQL实例之间进行查询操作。</p></li></ul><p>需要注意的是,MySQL 5是一个大版本,包含了多个小版本 如MySQL 5.0、MySQL 5.1、MySQL 5.5等 ,每个小版本都对功能和性能进行了不同程度的改进和优化。因此,具体使用的MySQL 5版本可能会有一些差异。</p><h2 id="MySQL-8"><a href="#MySQL-8" class="headerlink" title="MySQL 8"></a>MySQL 8</h2><p>MySQL 8是MySQL数据库管理系统的一个主要版本,在MySQL数据库的发展历史中代表了重要的进步和改进。MySQL 8于2018年发布,引入了众多新功能和改进,以提供更高性能、更强安全性和更丰富的功能。</p><p>以下是MySQL 8的一些主要特点和功能:</p><ul><li><p>JSON支持:MySQL 8引入了更强大的JSON功能,包括对JSON文档的索引和查询功能,使得存储和检索JSON数据变得更加便捷和高效。</p></li><li><p>插件化存储引擎:MySQL 8采用了插件化存储引擎架构,使得用户可以根据需求选择不同的存储引擎,如InnoDB、MyISAM等,并支持自定义存储引擎。</p></li><li><p>性能优化:MySQL 8进行了许多性能方面的改进,包括更好的查询优化器、索引算法的改进、并行查询等,从而提供更高的查询速度和吞吐量。</p></li><li><p>安全增强:MySQL 8引入了多项安全增强功能,如更加严格的密码策略、默认启用的SSL&#x2F;TLS支持、资源组和权限控制的增强等,以提供更高的数据安全性。</p></li><li><p>支持的SQL语法:MySQL 8增加了对一些新的SQL语法的支持,如窗口函数和CTE 公共表达式,即WITH语句 ,使得复杂查询更加方便和灵活。</p></li><li><p>Unicode支持:MySQL 8默认使用utf8mb4字符集,支持存储更广泛的Unicode字符,包括表情符号和特殊字符等。</p></li><li><p>索引算法改进:MySQL 8引入了更高效的索引算法 R-tree和B-tree索引的改进 ,从而提升空间数据类型和文本数据类型的查询性能。</p></li></ul><p>除上述功能外,MySQL 8还提供了许多其他的改进和优化,包括故障恢复、查询缓存的改进、在线DDL操作的支持等。这些功能使得MySQL 8成为一个更强大、更稳定和更可扩展的数据库管理系统。</p><h2 id="MySQL-5和MySQL-8的区别"><a href="#MySQL-5和MySQL-8的区别" class="headerlink" title="MySQL 5和MySQL 8的区别"></a>MySQL 5和MySQL 8的区别</h2><p>MySQL 5和MySQL 8是两个不同版本的MySQL数据库管理系统,它们之间存在一些重要的区别。以下是MySQL 5和MySQL 8之间的一些主要区别:</p><ul><li><p>JSON支持:MySQL 5对JSON支持较弱,只能存储和查询JSON字符串,而MySQL 8引入了更强大的JSON功能,包括对JSON文档的索引和查询功能。</p></li><li><p>插件化架构:MySQL 8引入了插件式存储引擎架构,使得用户可以根据具体需求选择不同的存储引擎,比如InnoDB、MyISAM等。而MySQL 5则相对较为有限,大多数情况下使用的是InnoDB引擎。</p></li><li><p>性能提升:MySQL 8在性能方面进行了许多改进,包括更好的查询优化器、索引算法的改进、并行查询等,从而提供更高的查询速度和吞吐量。</p></li><li><p>安全增强:MySQL 8引入了许多安全增强功能,如更加严格的密码策略、默认启用的SSL&#x2F;TLS支持、资源组和权限控制的增强等,以提供更高的数据安全性。</p></li><li><p>支持的SQL语法:MySQL 8增加了对一些新的SQL语法的支持,如窗口函数和CTE 公共表达式,即WITH语句 ,使得复杂查询更加方便和灵活。</p></li><li><p>Unicode支持:MySQL 8默认使用utf8mb4字符集,支持存储更广泛的Unicode字符,包括表情符号和特殊字符等。</p></li><li><p>索引算法改进:MySQL 8引入了更高效的索引算法 R-tree和B-tree索引的改进 ,从而提升空间数据类型和文本数据类型的查询性能。</p></li></ul><p>以下是MySQL 5和MySQL 8的一些主要功能和特点的对比:</p><table><thead><tr><th>序号</th><th>表名</th><th>描述</th></tr></thead><tbody><tr><td>功能&#x2F;特点</td><td>MySQL 5</td><td>MySQL 8</td></tr><tr><td>存储引擎</td><td>InnoDB、MyISAM等</td><td>InnoDB、MyISAM、NDB Cluster等 支持插件化存储引擎</td></tr><tr><td>ACID事务</td><td>InnoDB存储引擎支持</td><td>InnoDB存储引擎支持</td></tr><tr><td>触发器、存储过程</td><td>支持</td><td>支持</td></tr><tr><td>视图</td><td>支持</td><td>支持</td></tr><tr><td>索引算法</td><td>B-Tree索引、哈希索引、全文索引</td><td>B-Tree索引、哈希索引、全文索引、R-tree索引</td></tr><tr><td>JSON支持</td><td>不支持</td><td>支持</td></tr><tr><td>Unicode支持</td><td>utf8字符集</td><td>utf8mb4字符集</td></tr><tr><td>分区表</td><td>支持</td><td>支持</td></tr><tr><td>外键约束</td><td>支持</td><td>支持</td></tr><tr><td>查询优化</td><td>优化器改进</td><td>优化器改进、并行查询</td></tr><tr><td>安全性</td><td>较弱的密码策略</td><td>更严格的密码策略、默认启用SSL&#x2F;TLS支持</td></tr><tr><td>新SQL语法支持</td><td>不支持CTE和窗口函数</td><td>支持CTE和窗口函数</td></tr><tr><td>空间数据类型查询</td><td>R-tree索引不支持</td><td>R-tree索引支持</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr><tr><td>—</td><td>—</td><td>—</td></tr></tbody></table><p>需要注意的是这些区别仅是MySQL 5和MySQL 8之间的一部分,实际上,两个版本之间还存在其他一些差异和改进。在选择具体版本时,需要考虑自身的业务需求、性能要求和安全性等因素,并进行综合权衡。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/12/ee006171/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL连接方式详解</title>
      <link>https://blog.eucalyptus.cc/2023/10/12/d91efe0c/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/12/d91efe0c/</guid>
      <pubDate>Thu, 12 Oct 2023 07:44:34 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;在 MySQL 中,客户端与服务器之间的通信可以通过多种方式实现,包括 TCP&amp;#x2F;IP、套接字 Socket 、命名管道 Named Pipe 和共享内存 Shared Memory</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>在 MySQL 中,客户端与服务器之间的通信可以通过多种方式实现,包括 TCP&#x2F;IP、套接字 Socket 、命名管道 Named Pipe 和共享内存 Shared Memory 。每种连接方式都有其特点和适用场景。以下是对这四种连接方式的详细介绍:</p><h4 id="TCP-IP-连接"><a href="#TCP-IP-连接" class="headerlink" title="TCP&#x2F;IP 连接"></a><strong>TCP&#x2F;IP 连接</strong></h4><h5 id="原理"><a href="#原理" class="headerlink" title="原理"></a><strong>原理</strong></h5><p>TCP&#x2F;IP 是一种基于网络的通信协议,允许客户端和服务器通过网络进行通信。MySQL 默认使用 TCP&#x2F;IP 协议进行连接,端口号为 <strong>3306</strong> 默认值 。</p><h5 id="特点"><a href="#特点" class="headerlink" title="特点"></a><strong>特点</strong></h5><ul><li><strong>适用范围</strong>:适用于本地和远程连接。</li><li><strong>灵活性</strong>:可以通过网络防火墙和路由器进行通信。</li><li><strong>安全性</strong>:可以通过 SSL&#x2F;TLS 加密数据传输,确保通信安全。</li></ul><h5 id="配置"><a href="#配置" class="headerlink" title="配置"></a><strong>配置</strong></h5><ul><li><strong>服务器端</strong>:在 MySQL 配置文件 <code>my.cnf</code> 或 <code>my.ini</code> 中,确保以下参数未被禁用:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">[mysqld]</span><br><span class="line">bind-address 0.0.0.0 # 允许远程连接</span><br><span class="line">port 3306</span><br></pre></td></tr></table></figure><ul><li><strong>客户端</strong>:使用以下命令连接:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u username -p -h hostname -P port</span><br></pre></td></tr></table></figure><h5 id="示例"><a href="#示例" class="headerlink" title="示例"></a><strong>示例</strong></h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u root -p -h 127.0.0.1 -P 3306</span><br></pre></td></tr></table></figure><h4 id="套接字-Socket-连接"><a href="#套接字-Socket-连接" class="headerlink" title="套接字 Socket 连接"></a><strong>套接字 Socket 连接</strong></h4><h5 id="原理-1"><a href="#原理-1" class="headerlink" title="原理"></a><strong>原理</strong></h5><p>套接字是一种在本地主机上实现进程间通信 IPC 的机制。MySQL 使用 Unix 套接字文件 在 Linux 和 macOS 上 进行本地通信。</p><h5 id="特点-1"><a href="#特点-1" class="headerlink" title="特点"></a><strong>特点</strong></h5><ul><li><strong>适用范围</strong>:仅适用于本地连接。</li><li><strong>性能</strong>:比 TCP&#x2F;IP 更高效,因为不需要通过网络协议栈。</li><li><strong>安全性</strong>:由于仅限于本地主机,相对更安全。</li></ul><h5 id="配置-1"><a href="#配置-1" class="headerlink" title="配置"></a><strong>配置</strong></h5><ul><li><strong>服务器端</strong>:在 MySQL 配置文件中,确保以下参数已正确设置:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">[mysqld]</span><br><span class="line">socket /var/run/mysqld/mysqld.sock</span><br></pre></td></tr></table></figure><ul><li><strong>客户端</strong>:使用以下命令连接:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u username -p -S /var/run/mysqld/mysqld.sock</span><br></pre></td></tr></table></figure><h5 id="示例-1"><a href="#示例-1" class="headerlink" title="示例"></a><strong>示例</strong></h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u root -p -S /var/run/mysqld/mysqld.sock</span><br></pre></td></tr></table></figure><h4 id="命名管道-Named-Pipe-连接"><a href="#命名管道-Named-Pipe-连接" class="headerlink" title="命名管道 Named Pipe 连接"></a><strong>命名管道 Named Pipe 连接</strong></h4><h5 id="原理-2"><a href="#原理-2" class="headerlink" title="原理"></a><strong>原理</strong></h5><p>命名管道是一种特殊类型的文件,它实际上是一个命名通道。客户端可以通过读取该文件来创建管道,然后将管道连接到服务器端的数据源。服务器端的数据源可以读取管道中的数据,并将数据发送给客户端。客户端可以读取管道中的数据,但无法立即向服务器端发送数据。</p><h5 id="特点-2"><a href="#特点-2" class="headerlink" title="特点"></a><strong>特点</strong></h5><ul><li><strong>适用范围</strong>:仅适用于 Windows 系统上的本地连接。</li><li><strong>性能</strong>:比 TCP&#x2F;IP 更高效,但不如套接字。</li><li><strong>安全性</strong>:由于仅限于本地主机,相对更安全。</li></ul><h5 id="配置-2"><a href="#配置-2" class="headerlink" title="配置"></a><strong>配置</strong></h5><ul><li><strong>服务器端</strong>:在 MySQL 配置文件中,确保以下参数已启用:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">[mysqld]</span><br><span class="line">named-pipe</span><br></pre></td></tr></table></figure><ul><li><strong>客户端</strong>:使用以下命令连接:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u username -p --pipe</span><br></pre></td></tr></table></figure><h5 id="示例-2"><a href="#示例-2" class="headerlink" title="示例"></a><strong>示例</strong></h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u root -p --pipe</span><br></pre></td></tr></table></figure><h4 id="共享内存-Shared-Memory-连接"><a href="#共享内存-Shared-Memory-连接" class="headerlink" title="共享内存 Shared Memory 连接"></a><strong>共享内存 Shared Memory 连接</strong></h4><h5 id="原理-3"><a href="#原理-3" class="headerlink" title="原理"></a><strong>原理</strong></h5><p>共享内存是一种特殊类型的内存,它允许多个进程同时访问同一块内存区域。在MySQL中,服务器端可以创建一个共享内存区域,并将该区域分配给客户端。客户端可以通过读取共享内存区域来获取数据,并将数据发送给服务器端。服务器端可以读取共享内存区域中的数据,并将数据发送给客户端。</p><h5 id="特点-3"><a href="#特点-3" class="headerlink" title="特点"></a><strong>特点</strong></h5><ul><li><strong>适用范围</strong>:仅适用于 Windows 系统上的本地连接。</li><li><strong>性能</strong>:非常高效,因为数据直接在内存中传递,无需通过文件系统或网络协议栈。</li><li><strong>安全性</strong>:由于仅限于本地主机,相对更安全。</li></ul><h5 id="配置-3"><a href="#配置-3" class="headerlink" title="配置"></a><strong>配置</strong></h5><ul><li><strong>服务器端</strong>:在 MySQL 配置文件中,确保以下参数已启用:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">[mysqld]</span><br><span class="line">shared-memory</span><br><span class="line">shared-memory-base-name MYSQL</span><br></pre></td></tr></table></figure><ul><li><strong>客户端</strong>:使用以下命令连接:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u username -p --protocol MEMORY</span><br></pre></td></tr></table></figure><h5 id="示例-3"><a href="#示例-3" class="headerlink" title="示例"></a><strong>示例</strong></h5><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -u root -p --protocol MEMORY</span><br></pre></td></tr></table></figure><h4 id="总结"><a href="#总结" class="headerlink" title="总结"></a><strong>总结</strong></h4><ul><li><strong>TCP&#x2F;IP</strong>:适用于本地和远程连接,灵活性高,可通过网络防火墙和路由器。</li><li><strong>套接字</strong>:适用于本地连接,性能高,安全性好。</li><li><strong>命名管道</strong>:适用于 Windows 系统上的本地连接,性能较好。</li><li><strong>共享内存</strong>:适用于 Windows 系统上的本地连接,性能最高。</li></ul><p>选择哪种连接方式取决于你的具体需求,包括是否需要远程访问、对性能的要求以及操作系统的限制。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/12/d91efe0c/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL数据库日志详解</title>
      <link>https://blog.eucalyptus.cc/2023/10/12/7cf647ed/</link>
      <guid>https://blog.eucalyptus.cc/2023/10/12/7cf647ed/</guid>
      <pubDate>Thu, 12 Oct 2023 02:55:19 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;MySQL数据库日志是一种记录数据库活动的机制。它可以记录执行的查询、更新、删除、插入等操作以及其他服务器相关的事件。MySQL数据库日志对于数据库管理者来说非常重要,以下是MySQL数据库日志的几个重要性方面:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;p&gt;调试和故障排除:当MySQL</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>MySQL数据库日志是一种记录数据库活动的机制。它可以记录执行的查询、更新、删除、插入等操作以及其他服务器相关的事件。MySQL数据库日志对于数据库管理者来说非常重要,以下是MySQL数据库日志的几个重要性方面:</p><ul><li><p>调试和故障排除:当MySQL数据库发生故障时,数据库日志是调试和故障排除的关键工具之一。通过分析数据库日志,管理员可以确定发生故障的时间和原因,从而更快地解决问题。</p></li><li><p>性能优化:数据库日志不仅记录了数据库发生过的事件,还提供了有关这些事件的详细信息,如执行时间,查询执行计划以及查询所使用的索引等。通过分析数据库日志,管理员可以识别查询性能瓶颈并进行进一步的调整,以提高数据库性能。</p></li><li><p>安全审计:数据库日志是安全审计的重要部分。通过数据库日志,管理员可以跟踪谁访问了数据库、何时访问以及执行了哪些操作。这对于保护敏感信息以及满足法规要求非常重要。</p></li><li><p>数据恢复:在某些情况下,数据丢失或损坏是无法避免的。在这种情况下,数据库日志可以帮助管理员通过回放日志操作来恢复数据库以前的状态。</p></li><li><p>数据库备份:数据库日志可以用来确定在某个时间点之后更改了哪些数据。这对于增量备份或差异备份非常重要,因为只需要备份从上次备份以来更改的部分就好了。</p></li></ul><p>综上所述,MySQL数据库日志对于数据库管理者来说非常重要。管理员可以使用数据库日志来调试和故障排除、性能优化、安全审计、数据恢复以及数据库备份。</p><h2 id="MySQL数据库中的日志"><a href="#MySQL数据库中的日志" class="headerlink" title="MySQL数据库中的日志"></a>MySQL数据库中的日志</h2><ul><li>redo log 重做日志</li><li>undo log 回滚日志</li><li>bin log 二进制日志</li><li>error log 错误日志</li><li>slow query log 慢查询日志</li><li>general query log 一般查询日志</li><li>relay log 中继日志</li></ul><hr><h3 id="1-redo-log-重做日志"><a href="#1-redo-log-重做日志" class="headerlink" title="1.redo log(重做日志)"></a>1.redo log(重做日志)</h3><ul><li>redo log属于MySQL存储引擎InnoDB的事务日志</li><li>MySQL的数据是存放在磁盘中的,每次读写数据都需做磁盘IO操作,如果并发场景下性能就会很差。为此MySQL提供了一个优化手段,引入缓存<strong>Buffer Pool</strong>。这个缓存中包含了磁盘中<strong>部分</strong>数据页 <strong>page</strong> 的映射,以此来缓解数据库的磁盘压力。</li><li>当从数据库读数据时,首先从缓存中读取,如果缓存中没有,则从磁盘读取后放入缓存;当向数据库写入数据时,先向缓存写入,此时缓存中的数据页数据变更,这个数据页称为<strong>脏页</strong>,<strong>Buffer Pool</strong>中修改完数据后会按照设定的更新策略,定期刷到磁盘中,这个过程称为<strong>刷脏页</strong>。</li></ul><h4 id="1-1开启方式"><a href="#1-1开启方式" class="headerlink" title="1.1开启方式"></a>1.1开启方式</h4><p>在MySQL中,redo log是用于保证事务的持久性和原子性的一种机制。默认情况下,MySQL会自动开启redo log,并进行管理。然而,你也可以通过修改配置文件来调整redo log的相关参数。</p><p>下面是一些关于redo log的常用配置参数:</p><ul><li>innodb_log_file_size:设置每个redo log文件的大小,默认值为 48MB。可以根据实际需求调整该参数的值。</li><li>innodb_log_files_in_group:设置每组redo log文件的数量,默认值为 2。通常不需要修改此参数,除非你有特殊需求。</li></ul><p>如果你希望修改redo log的大小或数量,可以按照以下步骤进行操作:</p><ul><li>打开MySQL的配置文件 如my.cnf 。</li><li>在[mysqld]模块下添加或修改以下参数:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">innodb_log_file_size 新的文件大小</span><br><span class="line">innodb_log_files_in_group 新的文件数量</span><br></pre></td></tr></table></figure><p>确保新的文件大小和文件数量合理,并与已有的redo log文件兼容。</p><ul><li>保存并退出配置文件。</li><li>停止MySQL服务。</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl stop mysql</span><br></pre></td></tr></table></figure><ul><li>移动或删除旧的redo log文件。在MySQL的数据目录中,通常有以 ib_logfile 开头的文件,这些就是redo log文件。移动或删除这些文件,确保MySQL能够使用新的参数创建新的redo log文件。</li><li>启动MySQL服务。</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl <span class="keyword">start</span> mysql</span><br></pre></td></tr></table></figure><p>现在,MySQL将使用新的redo log参数进行运行。请注意,在修改redo log参数之后,可能需要重新执行备份和恢复操作,以确保数据的一致性和完整性。</p><h4 id="1-2管理命令"><a href="#1-2管理命令" class="headerlink" title="1.2管理命令"></a>1.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理redo log:</p><ul><li>查看redo log的信息和配置:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;innodb_log_%&#x27;</span>;</span><br></pre></td></tr></table></figure><p>上述命令将显示与redo log相关的配置参数和信息。</p><ul><li>修改redo log文件的大小和数量:</li></ul><p>在MySQL的配置文件 如my.cnf或my.ini 中,可以修改以下参数来调整redo log的大小和数量:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">innodb_log_file_size X</span><br><span class="line">innodb_log_files_in_group Y</span><br></pre></td></tr></table></figure><p>其中,innodb_log_file_size用于指定每个redo log文件的大小,单位为字节。innodb_log_files_in_group用于指定redo log文件的数量。修改这些参数后,需要重启MySQL服务才能使其生效。</p><p>注意:修改redo log的大小和数量是一个敏感且高风险的操作,建议在深入了解相关知识和风险的情况下进行操作,并备份数据库以防止数据丢失。</p><ul><li>刷新 清空 redo log:</li></ul><p>在某些情况下,你可能需要刷新 清空 redo log以释放磁盘空间或使某些操作生效。可以使用以下命令执行这个操作:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">FLUSH LOGS;</span><br></pre></td></tr></table></figure><p>上述命令将刷新所有的日志文件并创建一个新的redo log文件。</p><p>注意:刷新redo log将导致当前的redo log文件关闭并创建一个新的日志文件,这可能会影响数据库的正常运行和恢复能力。请在必要时谨慎使用此命令,并确保已经备份了数据库。</p><p>以上是常用的管理redo log的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="2-undo-log-回滚日志"><a href="#2-undo-log-回滚日志" class="headerlink" title="2.undo log(回滚日志)"></a>2.undo log(回滚日志)</h3><ul><li><strong>undo log</strong>也是属于MySQL存储引擎InnoDB的事务日志。</li><li><strong>undo log</strong>属于逻辑日志,如其名主要起到回滚的作用,它是保证事务原子性的关键。记录的是数据修改前的状态,在数据修改的流程中,同时会记录一条修改之前的逻辑日志到<strong>undo log</strong>中。</li><li>我们举个栗子:假如更新ID 1记录的name字段,name原始数据为小富,现改name为程序员内点事</li><li>事务执行<strong>update X set name 程序员内点事 where id 1</strong>语句时,先会在<strong>undo log</strong>中记录一条相反逻辑的<strong>update X set name 小富 where id 1</strong>记录,这样当某些原因导致服务异常事务失败,就可以借助<strong>undo log</strong>将数据回滚到事务执行前的状态,保证事务的完整性。</li></ul><h4 id="2-1开启方式"><a href="#2-1开启方式" class="headerlink" title="2.1开启方式"></a>2.1开启方式</h4><p>在MySQL中,undo log是用于支持事务的回滚和 MVCC 多版本并发控制 实现的重要组件。默认情况下,MySQL会自动开启undo log,并进行管理。不需要额外的配置来启用undo log。</p><p>然而,你可以通过调整特定配置参数来优化undo log的性能和管理。下面是一些与undo log相关的常用配置参数:</p><ul><li>innodb_undo_log_truncate:当事务提交后,是否立即截断 truncate undo log。默认值为ON,表示立即截断。如果设置为OFF,MySQL将在后台线程中定期截断undo log。</li><li>innodb_undo_logs:指定undo log的数量,默认值为128。这个参数决定了可以并行执行的事务数量。增加undo log的数量可以提高并发性能,但也会增加系统资源的消耗。</li><li>innodb_undo_tablespaces:指定undo log的表空间数量,默认值为0 自动确定 。可以根据数据库的负载和需求来调整此参数。</li></ul><p>如果你希望修改以上参数或其他与undo log相关的参数,可以按照以下步骤进行操作:</p><ul><li>打开MySQL的配置文件 如my.cnf 。</li><li>在[mysqld]模块下添加或修改需要调整的参数。</li><li>保存并退出配置文件。</li><li>重启MySQL服务。</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl restart mysql</span><br></pre></td></tr></table></figure><p>这样,MySQL将使用新的配置参数来管理undo log。请注意,修改undo log的参数可能会对数据库的性能和资源消耗产生影响。在进行任何更改之前,请确保了解其潜在的影响,并进行充分的测试和评估。</p><h4 id="2-2管理命令"><a href="#2-2管理命令" class="headerlink" title="2.2管理命令"></a>2.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理undo log:</p><ul><li>查看undo log的信息和配置:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;innodb_undo_%&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示与undo log相关的配置参数和信息。</p><ul><li>修改undo log的大小:</li></ul><p>在MySQL的配置文件 如my.cnf或my.ini 中,可以修改以下参数来调整undo log的大小:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">innodb_undo_tablespaces 2</span><br></pre></td></tr></table></figure><p>其中,innodb_undo_tablespaces用于指定undo log的大小。每个undo tablespace的默认大小为10MB。可以根据需要增加或减少undo tablespace的数量以调整undo log的总大小。</p><p>修改这些参数后,需要重启MySQL服务才能使其生效。</p><p>注意:修改undo log的大小是一个敏感且高风险的操作,建议在深入了解相关知识和风险的情况下进行操作,并备份数据库以防止数据丢失。</p><ul><li>清除当前活动事务的undo log:</li></ul><p>如果你想强制终止当前正在运行的事务并清除其相关的undo log,则可以使用以下命令:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ROLLBACK;</span><br></pre></td></tr></table></figure><p>这个命令将回滚当前的事务并清除其生成的undo log。</p><p>注意:使用ROLLBACK命令将会导致当前事务的所有更改都被撤销,请谨慎使用。</p><p>以上是常用的管理undo log的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="3-bin-log-二进制日志"><a href="#3-bin-log-二进制日志" class="headerlink" title="3.bin log(二进制日志)"></a>3.bin log(二进制日志)</h3><ul><li>bin log是一种数据库Server层 和存储引擎无关 ,以二进制形式存储在磁盘中的逻辑日志。bin log记录了数据库所有的DDL和DML操作 不包括SELECT 和 SHOW</li><li>bin log也叫做归档日志,因为他不像redo log一样循环写擦除之前的记录,而是会一直记录日志。如果单个日志文件大小超过 max_binlog_size,就会创建新的文件继续写入。</li><li>bin log日志的内容格式其实就是执行SQL命令的反向逻辑, 和undo log有点类似 。</li><li>一般来说,开启bin log都会给日志文件设置过期时间 expire_logs_days变量,单位是天</li></ul><h4 id="3-1开启方式"><a href="#3-1开启方式" class="headerlink" title="3.1开启方式"></a>3.1开启方式</h4><p>在MySQL中,开启二进制日志 binlog 功能可以实现数据备份、主从复制以及恢复等功能。下面是在MySQL中开启binlog日志的步骤:</p><ul><li>修改my.cnf配置文件,找到[mysqld]模块,在其中加入如下配置:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">server-id 1</span><br><span class="line">log-bin /var/lib/mysql/mysql-bin</span><br></pre></td></tr></table></figure><p>其中,server-id为服务器唯一标识,可以设置为任何非0数字,需要确保与其他服务器不重复。log-bin表示binlog日志存放的路径和文件名,可以根据实际需求修改。</p><ul><li>保存并退出配置文件,重启MySQL服务,使其读取新的配置。可以使用以下命令重启MySQL服务:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl restart mysql</span><br></pre></td></tr></table></figure><ul><li>验证binlog是否已经开启。可以在MySQL客户端输入以下命令:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> MASTER STATUS;</span><br></pre></td></tr></table></figure><p>如果输出了类似于 mysql-bin.000001 和 x 的信息,则说明binlog已经开启成功,其中 mysql-bin.000001 为当前的binlog文件名, x 为binlog日志中最后一个事件的位置。</p><p>注意:开启binlog会影响MySQL服务器的性能,因此建议在生产环境中进行仔细测试再决定是否开启。</p><h4 id="3-2管理命令"><a href="#3-2管理命令" class="headerlink" title="3.2管理命令"></a>3.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理二进制日志 binlog :</p><ul><li>查看binlog的信息和配置:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;log_bin%&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示与binlog相关的配置参数和信息,包括是否启用了binlog、binlog文件名等。</p><ul><li>启用或禁用binlog:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以启用或禁用binlog。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">log_bin ON</span><br></pre></td></tr></table></figure><p>将log_bin设置为ON表示启用binlog,将其设置为OFF表示禁用binlog。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看当前正在使用的binlog文件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> MASTER STATUS;</span><br></pre></td></tr></table></figure><p>这个命令将显示当前正在使用的binlog文件名以及相关的位置信息。</p><ul><li>刷新 关闭当前binlog文件并创建新文件 :</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">FLUSH LOGS;</span><br></pre></td></tr></table></figure><p>执行上述命令后,MySQL将关闭当前的binlog文件,并创建一个新的binlog文件开始记录。</p><ul><li>查看已经写入的binlog文件列表:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> <span class="type">BINARY</span> LOGS;</span><br></pre></td></tr></table></figure><p>这个命令将显示已经写入的binlog文件列表,包括文件名、大小和创建时间等信息。</p><ul><li>清除旧的binlog文件:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">PURGE BINARY LOGS TO &#x27;binlog文件名&#x27;;</span><br></pre></td></tr></table></figure><p>这个命令将删除指定binlog文件名之前的所有binlog文件。使用PURGE BINARY LOGS BEFORE ‘日期时间’可以删除指定日期时间之前创建的所有binlog文件。</p><p>注意:删除旧的binlog文件将无法恢复被删除的事务,所以在执行此命令之前,请谨慎备份数据库。</p><p>以上是一些常用的管理binlog的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="4-relay-log-中继日志"><a href="#4-relay-log-中继日志" class="headerlink" title="4.relay log 中继日志"></a>4.relay log 中继日志</h3><p><strong>relay log</strong>日志文件和<strong>bin log</strong>日志文件格式相同,从上边的MySQL主从复制流程可以看到,<strong>relay log</strong>起到一个中转作用,<strong>slave</strong>先从主库<strong>master</strong>中读取二进制日志数据,写入从库本地,后续再一户由<strong>SQL线程</strong>读取解析relay log成对应的SQL命令。</p><h4 id="4-1开启方式"><a href="#4-1开启方式" class="headerlink" title="4.1开启方式"></a>4.1开启方式</h4><p>在MySQL中,Relay Log是用于复制和同步主从服务器之间的数据更新操作的日志文件。它记录了从主服务器接收到的binlog事件。默认情况下,当你启用MySQL的复制功能时,Relay Log会自动开启。以下是启用Relay Log的一般步骤:</p><ul><li>首先,确保你已经启用了MySQL的复制功能,并且主服务器和从服务器已经建立了正确的复制关系。</li><li>在主服务器上修改配置文件 如my.cnf或my.ini ,找到并编辑[mysqld]模块。</li><li>添加或修改以下参数以启用Relay Log:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">relay_log relay<span class="operator">-</span>log<span class="operator">-</span>name</span><br><span class="line">relay_log_index relay<span class="operator">-</span>log<span class="operator">-</span>index<span class="operator">-</span>name</span><br></pre></td></tr></table></figure><p>其中,relay-log-name和relay-log-index-name是存储Relay Log日志文件和索引文件的路径和名称。你可以根据自己的需求指定它们的具体值。</p><p>示例:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">relay_log <span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span>relay<span class="operator">-</span>bin</span><br><span class="line">relay_log_index <span class="operator">/</span>var<span class="operator">/</span>lib<span class="operator">/</span>mysql<span class="operator">/</span>relay<span class="operator">-</span>bin.index</span><br></pre></td></tr></table></figure><ul><li>保存并关闭配置文件。</li><li>在从服务器上停止MySQL服务。</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl stop mysql</span><br></pre></td></tr></table></figure><ul><li>删除从服务器上的旧的Relay Log文件和索引文件 如果存在 。</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> <span class="built_in">rm</span> /var/lib/mysql/relay-bin*</span><br></pre></td></tr></table></figure><ul><li>启动从服务器上的MySQL服务。</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">sudo systemctl <span class="keyword">start</span> mysql</span><br></pre></td></tr></table></figure><p>现在,从服务器将开始使用新配置的Relay Log来接收和处理来自主服务器的binlog事件。请注意,在设置Relay Log之前,请确保主从服务器之间的复制已经正确配置,并在进行修改之前进行备份。</p><p>同时,如果你使用的是MySQL 8.0版本或更高版本,并且启用了基于GTID 全局事务标识 的复制,你可以设置以下参数来控制Relay Log的保留和自动清理:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">relay_log_purge ON</span><br><span class="line">relay_log_recovery ON</span><br></pre></td></tr></table></figure><p>这些参数将在复制过程中自动管理Relay Log的清理和恢复操作。</p><h4 id="4-2管理命令"><a href="#4-2管理命令" class="headerlink" title="4.2管理命令"></a>4.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理中继日志 relay log :</p><ul><li>查看relay log的信息和配置:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;relay_log%&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示与relay log相关的配置参数和信息,包括是否启用了relay log、relay log文件名等。</p><ul><li>启用或禁用relay log:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以启用或禁用relay log。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">relay_log ON</span><br></pre></td></tr></table></figure><p>将relay_log设置为ON表示启用relay log,将其设置为OFF表示禁用relay log。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看当前正在使用的relay log文件:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> MASTER STATUS;</span><br></pre></td></tr></table></figure><p>这个命令将显示当前正在使用的relay log文件名以及相关的位置信息。</p><ul><li>刷新 关闭当前relay log文件并创建新文件 :</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">FLUSH LOGS;</span><br></pre></td></tr></table></figure><p>执行上述命令后,MySQL将关闭当前的relay log文件,并创建一个新的relay log文件开始记录。</p><ul><li>查看已经写入的relay log文件列表:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> RELAYLOGS;</span><br></pre></td></tr></table></figure><p>这个命令将显示已经写入的relay log文件列表,包括文件名、大小和创建时间等信息。</p><ul><li>清除旧的relay log文件:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">PURGE RELAYLOGS TO &#x27;relaylog文件名&#x27;;</span><br></pre></td></tr></table></figure><p>这个命令将删除指定relay log文件名之前的所有relay log文件。使用PURGE RELAYLOGS BEFORE ‘日期时间’可以删除指定日期时间之前创建的所有relay log文件。</p><p>注意:删除旧的relay log文件将可能导致数据丢失或同步延迟,请在执行此命令之前谨慎备份数据库,并确保主从复制状态正常。</p><p>以上是一些常用的管理relay log的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="5-error-log-错误日志"><a href="#5-error-log-错误日志" class="headerlink" title="5.error log(错误日志)"></a>5.error log(错误日志)</h3><ul><li>错误日志主要记录MySQL服务器每次启动和停止的时间以及诊断和出错信息。</li><li>错误日志中记录的并非全部错误信息,也包括MySQL如何启动InnoDB的表空间文件、如何初始化自己的存储引擎,初始化buffer pool等,这些也记录在错误日志中。</li></ul><h4 id="5-1开启方式"><a href="#5-1开启方式" class="headerlink" title="5.1开启方式"></a>5.1开启方式</h4><p>在MySQL中,Error Log是一种记录MySQL服务器运行过程中产生的错误和警告信息的日志文件。通过启用Error Log,你可以方便地记录和跟踪MySQL服务器活动中出现的各种问题,有助于诊断和解决系统故障。以下是启用Error Log的一般步骤:</p><ul><li>找到MySQL的配置文件 如my.cnf或my.ini 并打开它。</li><li>找到[mysqld]模块,并添加或修改以下参数:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">log_error /path/to/error.log</span><br></pre></td></tr></table></figure><p>其中,&#x2F;path&#x2F;to&#x2F;error.log是存储Error Log的目录和文件名称。你可以根据需要修改它们的名称和路径。</p><p>示例:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">log_error /var/log/mysql/error.log</span><br></pre></td></tr></table></figure><ul><li>添加或修改以下参数来限制Error Log文件的大小和数量:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">log_error_verbosity 2</span><br><span class="line">log_error_suppression_list 1270</span><br><span class="line">max_error_count 1000</span><br></pre></td></tr></table></figure><ul><li>log_error_verbosity 2: 指定Error Log记录的详细程度,值为2时记录错误和警告信息。</li><li>log_error_suppression_list 1270 : 指定一个逗号分隔的错误号列表,在Error Log中删除这些错误的记录。例如,这里指定了 1270 ,表示忽略称为“1364 Field ‘xx’ doesn’t have a default value”的错误。</li><li>max_error_count 1000: 指定Error Log文件最大记录的条目数,默认值是1000。</li><li>保存并关闭配置文件。</li><li>重启MySQL服务以使配置生效。通过以下命令重启服务:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl restart mysql</span><br></pre></td></tr></table></figure><ul><li>现在,当MySQL服务器运行时产生错误和警告信息时,这些信息将被写入指定的Error Log文件中。</li></ul><p>请注意,在生产环境中,开启Error Log可以帮助你及时发现和解决系统异常,但也需要定期查看和维护Error Log文件,以确保其不会因为过大或其他问题而占用过多磁盘空间或导致其他性能问题。同时,请保护好Error Log文件,防止未授权的用户访问敏感信息。</p><h4 id="5-2管理命令"><a href="#5-2管理命令" class="headerlink" title="5.2管理命令"></a>5.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理错误日志 error log :</p><ul><li>查看错误日志的路径和文件名:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;log_error&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示错误日志文件的路径和文件名。</p><ul><li>查看错误日志内容:</li></ul><p>你可以直接查看错误日志文件的内容。例如,在Linux系统上可以使用cat命令:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> /path/to/error.log</span><br></pre></td></tr></table></figure><ul><li>刷新 关闭当前错误日志并创建新文件 :</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">FLUSH ERROR LOGS;</span><br></pre></td></tr></table></figure><p>执行上述命令后,MySQL将关闭当前的错误日志文件,并创建一个新的错误日志文件开始记录。</p><ul><li>手动写入错误日志:</li></ul><p>你可以使用SELECT语句结合sys.format_error()函数手动将错误信息写入错误日志文件:</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SELECT</span> sys.format_error(错误码, <span class="string">&#x27;错误消息&#x27;</span>) <span class="keyword">INTO</span> OUTFILE <span class="string">&#x27;/path/to/error.log&#x27;</span>;</span><br></pre></td></tr></table></figure><p>将错误码替换为实际的错误码,将错误消息替换为实际的错误消息,将&#x2F;path&#x2F;to&#x2F;error.log替换为实际的错误日志文件路径。</p><ul><li>修改错误日志的路径和文件名:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以修改错误日志文件的路径和文件名。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">log_error /path/to/new_error.log</span><br></pre></td></tr></table></figure><p>将&#x2F;path&#x2F;to&#x2F;new_error.log替换为你想要设置的新的错误日志文件路径和文件名。修改后,需要重启MySQL服务才能使其生效。</p><p>注意:在进行任何更改之前,请谨慎备份错误日志文件,并确保对日志文件的写入权限和路径的合法性。</p><p>以上是一些常用的管理错误日志的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="6-slow-query-log-慢查询日志"><a href="#6-slow-query-log-慢查询日志" class="headerlink" title="6.slow query log 慢查询日志"></a>6.slow query log 慢查询日志</h3><ul><li>慢查询日志 <strong>slow query log</strong> : 用来记录在 MySQL 中执行时间超过指定时间的查询语句,在 SQL 优化过程中会经常使用到。通过慢查询日志,我们可以查找出哪些查询语句的执行效率低,耗时严重。</li><li>出于性能方面的考虑,一般只有在排查慢SQL、调试参数时才会开启,默认情况下,慢查询日志功能是关闭的。</li></ul><h4 id="6-1开启方式"><a href="#6-1开启方式" class="headerlink" title="6.1开启方式"></a>6.1开启方式</h4><p>在MySQL中,Slow Query Log 慢查询日志 可以记录执行时间超过设定阈值的SQL查询语句。启用Slow Query Log可以帮助你发现并优化执行时间较长的查询,从而提高数据库性能。以下是启用Slow Query Log的一般步骤:</p><ul><li>找到MySQL的配置文件 如my.cnf或my.ini 并打开它。</li><li>找到[mysqld]模块,并添加或修改以下参数:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">slow_query_log 1</span><br><span class="line">slow_query_log_file /path/to/slow-query.log</span><br><span class="line">long_query_time X</span><br></pre></td></tr></table></figure><p>其中:</p><ul><li>slow_query_log参数用于启用&#x2F;禁用Slow Query Log,将其设置为1表示启用,设置为0表示禁用。</li><li>slow_query_log_file参数用于指定Slow Query Log文件的路径和文件名。</li><li>long_query_time参数用于设定执行时间超过多少秒的查询被认为是慢查询。X请根据自己的需求来设置,例如设置为2表示执行时间超过2秒的查询会被记录在Slow Query Log中。</li></ul><p>示例:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">slow_query_log 1</span><br><span class="line">slow_query_log_file /var/log/mysql/slow-query.log</span><br><span class="line">long_query_time 2</span><br></pre></td></tr></table></figure><ul><li>保存并关闭配置文件。</li><li>重启MySQL服务以使配置生效。可以通过以下命令重启服务:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl restart mysql</span><br></pre></td></tr></table></figure><ul><li>现在,当执行时间超过设定阈值的查询语句被执行时,它们的详细信息将被记录在指定的Slow Query Log文件中。</li></ul><p>注意事项:</p><ul><li>启用Slow Query Log会对系统性能产生一定影响,因此在生产环境中应谨慎使用,并根据需要进行定期的日志文件维护和清理。</li><li>为了获得更准确的慢查询日志,你可以使用其他参数进行进一步设置,如min_examined_row_limit 最小扫描行数限制 等。</li><li>Slow Query Log记录的是执行时间超过阈值的查询语句,因此该日志文件可能包含敏感信息。请妥善保护好该文件,防止未授权的访问。</li></ul><p>通过启用Slow Query Log,你可以在数据库中识别和优化执行慢查询的操作,从而提高数据库的性能和效率。</p><h4 id="6-2管理命令"><a href="#6-2管理命令" class="headerlink" title="6.2管理命令"></a>6.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理慢查询日志 slow query log :</p><ul><li>查看当前慢查询日志的状态:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;slow_query_log&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示当前慢查询日志的状态,包括是否启用了慢查询日志和慢查询的阈值等。</p><ul><li>启用或禁用慢查询日志:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以启用或禁用慢查询日志。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">slow_query_log ON</span><br></pre></td></tr></table></figure><p>将slow_query_log设置为ON表示启用慢查询日志,将其设置为OFF表示禁用慢查询日志。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看慢查询日志文件的路径和文件名:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;slow_query_log_file&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示慢查询日志文件的路径和文件名。</p><ul><li>修改慢查询日志的路径和文件名:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以修改慢查询日志文件的路径和文件名。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">slow_query_log_file /path/to/new_slow_query.log</span><br></pre></td></tr></table></figure><p>将&#x2F;path&#x2F;to&#x2F;new_slow_query.log替换为你想要设置的新的慢查询日志文件路径和文件名。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>修改慢查询阈值:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以修改慢查询的阈值。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">long_query_time 10</span><br></pre></td></tr></table></figure><p>将10替换为实际的慢查询阈值,单位为秒。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看慢查询日志内容:</li></ul><p>你可以直接查看慢查询日志文件的内容。例如,在Linux系统上可以使用cat命令:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> /path/to/slow_query.log</span><br></pre></td></tr></table></figure><ul><li>使用mysqldumpslow工具分析慢查询日志:</li></ul><p>mysqldumpslow是一个用于分析慢查询日志的工具,它可以根据查询时间、锁定时间、扫描行数等几个维度来排序和统计查询。例如,以下命令将统计并按执行次数降序排列前10条最慢的查询:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysqldumpslow -s t -t 10 /path/to/slow_query.log</span><br></pre></td></tr></table></figure><p>其中,-s t表示以查询时间为排序依据,-t 10表示显示前10条结果。</p><p>注意:在进行任何更改之前,请谨慎备份慢查询日志文件,并确保对日志文件的写入权限和路径的合法性。</p><p>以上是一些常用的管理慢查询日志的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p><hr><h3 id="7-general-query-log-一般查询日志"><a href="#7-general-query-log-一般查询日志" class="headerlink" title="7.general query log(一般查询日志)"></a>7.general query log(一般查询日志)</h3><ul><li>一般查询日志 general query log :用来记录用户的<strong>所有</strong>操作,包括客户端何时连接了服务器、客户端发送的所有SQL以及其他事件,比如 MySQL 服务启动和关闭等等。MySQL服务器会按照它接收到语句的先后顺序写入日志文件。</li><li>由于一般查询日志记录的内容过于详细,开启后 Log 文件的体量会非常庞大,所以出于对性能的考虑,默认情况下,该日志功能是关闭的,通常会在排查故障需获得详细日志的时候才会临时开启。</li></ul><h4 id="7-1开启方式"><a href="#7-1开启方式" class="headerlink" title="7.1开启方式"></a>7.1开启方式</h4><p>在MySQL中,General Query Log 通用查询日志 可以记录所有经过MySQL服务器的查询语句,包括</p><ul><li>找到MySQL的配置文件 如my.cnf或my.ini 并打开它。</li><li>找到[mysqld]模块,并添加或修改以下参数:</li></ul><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">general_log 1</span><br><span class="line">general_log_file /path/to/general-query.log</span><br></pre></td></tr></table></figure><p>其中:</p><ul><li>general_log参数用于启用&#x2F;禁用General Query Log,将其设置为1表示启用,设置为0表示禁用。</li><li>general_log_file参数用于指定General Query Log文件的路径和文件名。</li></ul><p>示例:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">general_log 1</span><br><span class="line">general_log_file /var/log/mysql/general-query.log</span><br></pre></td></tr></table></figure><ul><li>保存并关闭配置文件。</li><li>重启MySQL服务以使配置生效。可以通过以下命令重启服务:</li></ul><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">sudo</span> systemctl restart mysql</span><br></pre></td></tr></table></figure><ul><li><p>现在,所有经过MySQL服务器的查询语句,包括<br>注意事项:</p></li><li><p>启用General Query Log会生成大量的日志信息,可能对系统性能和磁盘空间产生负面影响。在生产环境中,应避免长时间启用General Query Log,可以根据需要进行临时性的开启和关闭。</p></li><li><p>General Query Log记录的是所有经过MySQL服务器的查询操作,因此该日志文件可能包含敏感信息。请妥善保护好该文件,防止未授权的访问。</p></li></ul><p>通过启用General Query Log,你可以详细了解MySQL服务器上执行的所有查询操作,从而帮助你进行调试和分析数据库的行为。但请注意,由于General Query Log产生的大量日志数据,建议在必要时才启用,并定期对日志文件进行维护和清理。</p><h4 id="7-2管理命令"><a href="#7-2管理命令" class="headerlink" title="7.2管理命令"></a>7.2管理命令</h4><p>在MySQL中,你可以使用以下命令来管理常规查询日志 general query log :</p><ul><li>查看当前常规查询日志的状态:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;general_log&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示当前常规查询日志的状态,包括是否启用了常规查询日志。</p><ul><li>启用或禁用常规查询日志:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以启用或禁用常规查询日志。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">general_log ON</span><br></pre></td></tr></table></figure><p>将general_log设置为ON表示启用常规查询日志,将其设置为OFF表示禁用常规查询日志。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看常规查询日志文件的路径和文件名:</li></ul><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">SHOW</span> VARIABLES <span class="keyword">LIKE</span> <span class="string">&#x27;general_log_file&#x27;</span>;</span><br></pre></td></tr></table></figure><p>这个命令将显示常规查询日志文件的路径和文件名。</p><ul><li>修改常规查询日志的路径和文件名:</li></ul><p>通过修改MySQL的配置文件 如my.cnf或my.ini ,可以修改常规查询日志文件的路径和文件名。找到以下参数并进行修改:</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">general_log_file /path/to/new_general_query.log</span><br></pre></td></tr></table></figure><p>将&#x2F;path&#x2F;to&#x2F;new_general_query.log替换为你想要设置的新的常规查询日志文件路径和文件名。修改后,需要重启MySQL服务才能使其生效。</p><ul><li>查看常规查询日志内容:</li></ul><p>你可以直接查看常规查询日志文件的内容。例如,在Linux系统上可以使用cat命令:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> /path/to/general_query.log</span><br></pre></td></tr></table></figure><p>注意:启用常规查询日志会记录每个查询的详细信息,包括敏感数据 如密码 ,因此请务必保护好生成的日志文件,避免泄露敏感信息。</p><ul><li>分析常规查询日志:</li></ul><p>你可以使用各种日志分析工具来分析常规查询日志,例如使用pt-query-digest工具。这个工具可以帮助你分析查询的性能瓶颈和优化建议,以及识别慢查询等。</p><p>以上是一些常用的管理常规查询日志的命令和操作,但在实际操作中,请务必谨慎处理并了解相关风险。如果不确定,请在进行任何更改之前备份数据库并咨询专业人士的意见。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/10/12/7cf647ed/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>MySQL5.7.43 GTID主从复制配置</title>
      <link>https://blog.eucalyptus.cc/2023/09/17/f20bfe69/</link>
      <guid>https://blog.eucalyptus.cc/2023/09/17/f20bfe69/</guid>
      <pubDate>Sun, 17 Sep 2023 09:09:54 GMT</pubDate>
      
        
        
          
          
      <description>&lt;blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href=&quot;#%E5%BC%95%E8%A8%80&quot;&gt;引言&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<blockquote></blockquote><p><strong><a href="#%E5%BC%95%E8%A8%80">引言</a></strong></p><p><strong><a href="#%E7%8E%AF%E5%A2%83%E9%85%8D%E7%BD%AE">环境配置</a></strong></p><p><strong><a href="#%E4%B8%BB%E5%BA%93%EF%BC%88master1%EF%BC%89%E9%85%8D%E7%BD%AE">主库 master1 配置</a></strong></p><p><strong><a href="#%E8%AE%BE%E7%BD%AE%E4%B8%BB%E5%BA%93%E4%B8%BB%E9%85%8D%E7%BD%AE%E6%96%87%E4%BB%B6">设置主库主配置文件</a></strong></p><p><strong><a href="#%E9%87%8D%E5%90%AFMySQL">重启MySQL</a></strong></p><p>**[</p><p><strong><a href="#%E5%88%9B%E5%BB%BA%E7%94%A8%E6%88%B7%E5%92%8C%E6%8E%88%E6%9D%83%E5%B9%B6%E5%88%B7%E6%96%B0">创建用户和授权并刷新</a></strong></p><p><strong><a href="#%E4%BB%8E%E5%BA%93%EF%BC%88slave2%EF%BC%89%E9%85%8D%E7%BD%AE">从库 slave2 配置</a></strong></p><p><strong><a href="#%E6%B5%8B%E8%AF%95master1%E6%98%AF%E5%90%A6%E5%8F%AF%E4%BB%A5%E8%BF%9E%E6%8E%A5">测试master1是否可以连接</a></strong></p><p><strong><a href="#%E8%AE%BE%E7%BD%AE%E4%BB%8E%E5%BA%93%E4%B8%BB%E9%85%8D%E7%BD%AE%E6%96%87%E4%BB%B6">设置从库主配置文件</a></strong></p><p><strong><a href="#%E9%87%8D%E5%90%AFMySQL">重启MySQL</a></strong></p><p>**[重启MySQL后</p><p><strong><a href="#%E5%88%A0%E9%99%A4%E4%BB%8E%E5%BA%93%E6%97%A5%E5%BF%97">删除从库日志</a></strong></p><p><strong><a href="#%E9%85%8D%E7%BD%AE%E8%BF%9E%E6%8E%A5%E4%B8%BB%E5%BA%93">配置连接主库</a></strong></p><p><strong><a href="#%E5%90%AF%E5%8A%A8slave%E5%92%8C%E6%9F%A5%E7%9C%8Bslave">启动slave和查看slave</a></strong></p><p><strong><a href="#%E9%AA%8C%E8%AF%81%E4%B8%BB%E4%BB%8E%E5%A4%8D%E5%88%B6">验证主从复制</a></strong></p><p><strong><a href="#%E6%80%BB%E7%BB%93">总结</a></strong></p><h3 id="引言"><a href="#引言" class="headerlink" title="引言"></a>引言</h3><p>为什么需要主从复制</p><ul><li>在业务复杂的系统中,有这么一个情景,有一句sql语句需要锁表,导致暂时不能使用读的服务,那么就很影响运行中的业务,使用主从复制,让主库负责写,从库负责读,这样,即使主库出现了锁表的情景,通过读从库也可以保证业务的正常运作。</li><li>做数据的热备</li><li>架构的扩展。业务量越来越大,I&#x2F;O访问频率过高,单机无法满足,此时做多库的存储,降低磁盘I&#x2F;O访问的频率,提高单个机器的I&#x2F;O性能。</li></ul><p>什么是主从复制</p><p>​ MySQL 主从复制是指数据可以从一个MySQL数据库服务器主节点复制到一个或多个从节点。MySQL 默认采用异步复制方式,这样从节点不用一直访问主服务器来更新自己的数据,数据的更新可以在远程连接上进行,从节点可以复制主数据库中的所有数据库或者特定的数据库,或者特定的表。</p><p>主从复制原理</p><ul><li>在主库上把数据更改(DDL DML DCL)记录到二进制日志(Binary Log)中。</li><li>备库I&#x2F;O线程将主库上的日志复制到自己的中继日志(Re’lay Log)中。</li><li>备库SQL线程读取中继日志的事件,将其重放到备库的数据库上。</li></ul><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-17/img1.avif"></p><p>主从复制方式,M是master主库,S是slave从库</p><ul><li>M-S</li><li>M-M</li><li>M-S-S</li><li>M-M-S-S</li></ul><p>接下来文章中主要介绍的是M-S GTID ,除了M-M-S-S和其他复制方式的时候有点区别,其他的的复制方式大同小异</p><p>GTID是一个基于原始mysql服务器生成的一个已经被成功执行的全局事务ID,它由服务器ID以及事务ID组合而成。这个全局事务ID不仅仅在原始服务器器上唯一,在所有存在主从关系 的mysql服务器上也是唯一的。正是因为这样一个特性使得mysql的主从复制变得更加简单,以及数据库一致性更可靠。</p><blockquote><p>GTID复制模式原理参考文章:<a href="https://blog.51cto.com/u_6215974/4938532">MySQL 基于GTID复制模式-运维小结 (完整篇)</a></p></blockquote><h3 id="环境配置"><a href="#环境配置" class="headerlink" title="环境配置"></a>环境配置</h3><ul><li>准备好2台在Centos7中安装了MySQL 5.7.43的操作系统</li><li>2台操作系统提前关闭防火墙和SElinux</li><li>提前配置好&#x2F;etc&#x2F;hosts文件</li><li>修改Centos7的主机名</li></ul><p>参考文章</p><ul><li>MySQL的安装<a href="https://blog.eucalyptus.cc/index.php/2023/09/15/mysql%E5%AE%89%E8%A3%85%E4%BF%9D%E5%A7%86%E7%BA%A7%E6%95%99%E7%A8%8B/">Linux中MySQL的安装 - Eucalyptus</a></li><li>防火墙的管理<a href="https://blog.eucalyptus.cc/index.php/2023/07/17/%E9%98%B2%E7%81%AB%E5%A2%99%E7%9A%84%E7%AE%A1%E7%90%86/">防火墙的管理 - Eucalyptus</a></li><li>hosts文件配置<a href="https://blog.eucalyptus.cc/index.php/2023/09/08/linux%E4%B8%AD%E8%AE%BE%E7%BD%AE%E4%B8%BB%E6%9C%BA%E5%90%8D%E5%92%8Chosts%E6%98%A0%E5%B0%84/">Linux中设置主机名和hosts映射 - Eucalyptus</a></li><li>Centos7主机名的修改<a href="https://blog.eucalyptus.cc/index.php/2023/09/08/linux%E4%B8%AD%E8%AE%BE%E7%BD%AE%E4%B8%BB%E6%9C%BA%E5%90%8D%E5%92%8Chosts%E6%98%A0%E5%B0%84/">Linux中设置主机名和hosts映射 - Eucalyptus</a></li></ul><h3 id="主库-master1-配置"><a href="#主库-master1-配置" class="headerlink" title="主库 master1 配置"></a>主库 master1 配置</h3><h4 id="设置主库主配置文件"><a href="#设置主库主配置文件" class="headerlink" title="设置主库主配置文件"></a>设置主库主配置文件</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">vim <span class="operator">/</span>etc<span class="operator">/</span>my.cnf</span><br><span class="line">在文件的末尾加入下面设置</span><br><span class="line">log<span class="operator">-</span>bin</span><br><span class="line">server<span class="operator">-</span>id <span class="number">1</span></span><br><span class="line">gtid_mode <span class="keyword">ON</span></span><br><span class="line">enforce_gtid_consistency <span class="number">1</span></span><br></pre></td></tr></table></figure><h4 id="重启MySQL"><a href="#重启MySQL" class="headerlink" title="重启MySQL"></a>重启MySQL</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">systemctl restart mysqld</span><br><span class="line">重启失败的话就是上面配置文件的修改出错了,好好检查</span><br></pre></td></tr></table></figure><h4 id=""><a href="#" class="headerlink" title=""></a></h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -uroot -p<span class="string">&#x27;密码&#x27;</span></span><br></pre></td></tr></table></figure><h4 id="创建用户和授权并刷新"><a href="#创建用户和授权并刷新" class="headerlink" title="创建用户和授权并刷新"></a>创建用户和授权并刷新</h4><blockquote><p>这里的授权语句在MySQL5和MySQL8不同版本中会有变化,大家根据自己的MySQL版本选择正确的sql语句去授权</p></blockquote><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">create</span> <span class="keyword">user</span> <span class="string">&#x27;rep&#x27;</span> <span class="string">&#x27;192.168.159.%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;密码&#x27;</span>;</span><br><span class="line"><span class="keyword">grant</span> replication slave <span class="keyword">on</span> <span class="operator">*</span>.<span class="operator">*</span> <span class="keyword">to</span> ‘rep’ <span class="string">&#x27;192.168.159.%&#x27;</span> identified <span class="keyword">by</span> <span class="string">&#x27;密码&#x27;</span>;</span><br><span class="line">flush privileges;</span><br></pre></td></tr></table></figure><h3 id="从库-slave2-配置"><a href="#从库-slave2-配置" class="headerlink" title="从库 slave2 配置"></a>从库 slave2 配置</h3><h4 id="测试master1是否可以连接"><a href="#测试master1是否可以连接" class="headerlink" title="测试master1是否可以连接"></a>测试master1是否可以连接</h4><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">mysql -hmaster1 -urep -p&#x27;123456&#x27;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>连接失败的话可能是防火墙和selinux没有关闭,关闭后重新连接</p><h4 id="设置从库主配置文件"><a href="#设置从库主配置文件" class="headerlink" title="设置从库主配置文件"></a>设置从库主配置文件</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">vim <span class="operator">/</span>etc<span class="operator">/</span>my.cnf</span><br><span class="line">将下面设置添加到文件末尾</span><br><span class="line">log<span class="operator">-</span>bin</span><br><span class="line">server<span class="operator">-</span>id <span class="number">2</span></span><br><span class="line">gtid_mode <span class="keyword">ON</span></span><br><span class="line">enforce_gtid_consistency <span class="number">1</span></span><br></pre></td></tr></table></figure><h4 id="重启MySQL-1"><a href="#重启MySQL-1" class="headerlink" title="重启MySQL"></a>重启MySQL</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl restart mysqld</span><br></pre></td></tr></table></figure><h4 id="重启MySQL后"><a href="#重启MySQL后" class="headerlink" title="重启MySQL后"></a>重启MySQL后</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">systemctl restart mysqld</span><br><span class="line">mysql -uroot -p<span class="string">&#x27;123456&#x27;</span></span><br><span class="line"></span><br></pre></td></tr></table></figure><h4 id="删除从库日志"><a href="#删除从库日志" class="headerlink" title="删除从库日志"></a>删除从库日志</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">reset slave <span class="keyword">all</span>;</span><br></pre></td></tr></table></figure><h4 id="配置连接主库"><a href="#配置连接主库" class="headerlink" title="配置连接主库"></a>配置连接主库</h4><blockquote><p>当然通常在完成change master to命令初始化后是复制配置是自动管理的,会有自动恢复复制机制。在开源的低版本的MySQL中,从服务器在启动时,会检查 <code>master.info</code> 用于存储复制配置 和 <code>relay-log.info</code> 用于存储当前的复制状态 文件。如果此前配置过主从复制,并且还未执行 <code>RESET SLAVE</code>,从服务器就会根据这些信息自动尝试恢复复制。</p><p>但是在高版本的MySQL中例如MySQL8.0.36中,主从复制的状态信息默认存储在两个系统表中,而不再是之前版本里的文件 <code>master.info</code> 和 <code>relay-log.info</code> 。</p><p>这两个系统表分别是:</p><ul><li><p><strong>slave_master_info</strong>: 用于存储有关主服务器的连接信息。这些信息通常会在执行了 <code>CHANGE MASTER TO</code> 命令以定义主服务器的连接参数后被填写到此表中。</p></li><li><p><strong>slave_relay_log_info</strong>: 存储从服务器当前复制状态的信息,包括当前正在应用的relay日志文件的名称和位置。</p></li></ul><figure class="highlight plaintext"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">`-- 查询有关主服务器连接的信息</span><br><span class="line">SELECT * FROM mysql.slave_master_info;</span><br><span class="line"></span><br><span class="line">-- 查询有关当前从服务器复制状态的信息</span><br><span class="line">SELECT * FROM mysql.slave_relay_log_info;</span><br><span class="line">`</span><br></pre></td></tr></table></figure><p>重要的是,这些表是内部维护的,通常你不需要直接操作或修改它们,因为这可能会导致复制的配置和状态不一致。如果复制出现问题,MySQL 提供了包括 <code>SHOW SLAVE STATUS</code> 在内的多个诊断命令,以及用于修复和配置复制环境的 <code>CHANGE MASTER TO</code>、<code>START SLAVE</code>、<code>STOP SLAVE</code> 等命令。</p><p>另外,了解存储复制信息对预防灾难发生是很重要的,这意味着如果你要迁移或备份从服务器的状态,你也需要考虑备份 <code>mysql</code> 数据库中的这些表。不过一般情况下,全数据库备份 例如使用 <code>mysqldump --all-databases</code> 会包含 <code>mysql</code> 数据库和相应的系统表。</p></blockquote><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line"> change master <span class="keyword">to</span></span><br><span class="line">master_host <span class="string">&#x27;master1&#x27;</span>,</span><br><span class="line">master_user <span class="string">&#x27;rep&#x27;</span>,</span><br><span class="line">master_password <span class="string">&#x27;密码&#x27;</span>,</span><br><span class="line">master_auto_position <span class="number">1</span>;</span><br></pre></td></tr></table></figure><h4 id="启动slave和查看slave"><a href="#启动slave和查看slave" class="headerlink" title="启动slave和查看slave"></a>启动slave和查看slave</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">start</span> slave;</span><br><span class="line"><span class="keyword">show</span> slave status\G</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-17/img2.avif"></p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br><span class="line">26</span><br><span class="line">27</span><br><span class="line">28</span><br><span class="line">29</span><br><span class="line">30</span><br><span class="line">31</span><br><span class="line">32</span><br><span class="line">33</span><br><span class="line">34</span><br><span class="line">35</span><br><span class="line">36</span><br><span class="line">37</span><br><span class="line">38</span><br><span class="line">39</span><br><span class="line">40</span><br><span class="line">41</span><br><span class="line">42</span><br><span class="line">43</span><br><span class="line">44</span><br><span class="line">45</span><br><span class="line">46</span><br><span class="line">47</span><br><span class="line">48</span><br><span class="line">49</span><br><span class="line">50</span><br><span class="line">51</span><br><span class="line">52</span><br><span class="line">53</span><br><span class="line">54</span><br><span class="line">55</span><br><span class="line">56</span><br><span class="line">57</span><br><span class="line">58</span><br><span class="line">59</span><br><span class="line">60</span><br><span class="line">61</span><br></pre></td><td class="code"><pre><span class="line">Replica_IO_State: Waiting <span class="keyword">for</span> source <span class="keyword">to</span> send event # 复制状态:等待主库发送事件</span><br><span class="line">Source_Host: <span class="number">192.168</span><span class="number">.0</span><span class="number">.104</span> # 主库地址</span><br><span class="line">Source_User: repl # 主库复制用户</span><br><span class="line">Source_Port: <span class="number">3306</span> # 主库端口</span><br><span class="line">Connect_Retry: <span class="number">60</span> # 连接重试次数</span><br><span class="line">Source_Log_File: <span class="number">87503</span>f057dd8<span class="operator">-</span>bin<span class="number">.000004</span> # 主库当前正在读取的日志文件</span><br><span class="line">Read_Source_Log_Pos: <span class="number">157</span> # 主库当前正在读取的日志位置</span><br><span class="line">Relay_Log_File: e7df40b28cde<span class="operator">-</span>relay<span class="operator">-</span>bin<span class="number">.000005</span> # 从库当前正在写入的中继日志文件</span><br><span class="line">Relay_Log_Pos: <span class="number">387</span> # 从库当前正在写入的中继日志位置</span><br><span class="line">Relay_Source_Log_File: <span class="number">87503</span>f057dd8<span class="operator">-</span>bin<span class="number">.000004</span> # 从库中继的主库日志文件名</span><br><span class="line">Replica_IO_Running: Yes # 复制 I<span class="operator">/</span>O 进程是否正在运行</span><br><span class="line">Replica_SQL_Running: Yes # 复制 <span class="keyword">SQL</span> 进程是否正在运行</span><br><span class="line">Replicate_Do_DB: # 需要复制的数据库</span><br><span class="line">Replicate_Ignore_DB: # 需要忽略复制的数据库</span><br><span class="line">Replicate_Do_Table: # 需要复制的表</span><br><span class="line">Replicate_Ignore_Table: # 需要忽略复制的表</span><br><span class="line">Replicate_Wild_Do_Table: # 需要通配符匹配复制的表</span><br><span class="line">Replicate_Wild_Ignore_Table: # 需要通配符匹配忽略复制的表</span><br><span class="line">Last_Errno: <span class="number">0</span> # 最后一个错误编号</span><br><span class="line">Last_Error: # 最后一个错误信息</span><br><span class="line">Skip_Counter: <span class="number">0</span> # 跳过的事件数量</span><br><span class="line">Exec_Source_Log_Pos: <span class="number">157</span> # 执行主库日志的位置</span><br><span class="line">Relay_Log_Space: <span class="number">1014</span> # 中继日志占用空间</span><br><span class="line">Until_Condition: <span class="keyword">None</span> # 复制停止条件</span><br><span class="line">Until_Log_File: # 复制停止的日志文件</span><br><span class="line">Until_Log_Pos: <span class="number">0</span> # 复制停止的日志位置</span><br><span class="line">Source_SSL_Allowed: <span class="keyword">No</span> # 主库是否允许 SSL 连接</span><br><span class="line">Source_SSL_CA_File: # 主库 SSL CA 文件路径</span><br><span class="line">Source_SSL_CA_Path: # 主库 SSL CA 路径</span><br><span class="line">Source_SSL_Cert: # 主库 SSL 证书</span><br><span class="line">Source_SSL_Cipher: # 主库 SSL 加密方式</span><br><span class="line">Source_SSL_Key: # 主库 SSL 密钥</span><br><span class="line">Seconds_Behind_Source: <span class="number">0</span> # 从库与主库之间的延迟</span><br><span class="line">Source_SSL_Verify_Server_Cert: <span class="keyword">No</span> # 主库 SSL 服务器证书验证方式</span><br><span class="line">Last_IO_Errno: <span class="number">0</span> # 最后一个 I<span class="operator">/</span>O 错误编号</span><br><span class="line">Last_IO_Error: # 最后一个 I<span class="operator">/</span>O 错误信息</span><br><span class="line">Last_SQL_Errno: <span class="number">0</span> # 最后一个 <span class="keyword">SQL</span> 错误编号</span><br><span class="line">Last_SQL_Error: # 最后一个 <span class="keyword">SQL</span> 错误信息</span><br><span class="line">Replicate_Ignore_Server_Ids: # 忽略的主库 ID</span><br><span class="line">Source_Server_Id: <span class="number">1</span> # 主库服务器 ID</span><br><span class="line">Source_UUID: <span class="number">254752</span>fe<span class="operator">-</span>eff5<span class="number">-11</span>ee<span class="number">-92</span>a5<span class="number">-0242</span>c0a80068 # 主库 UUID</span><br><span class="line">Source_Info_File: mysql.slave_master_info # 主库信息文件</span><br><span class="line">SQL_Delay: <span class="number">0</span> # <span class="keyword">SQL</span> 延迟</span><br><span class="line">SQL_Remaining_Delay: <span class="keyword">NULL</span> # 剩余的 <span class="keyword">SQL</span> 延迟</span><br><span class="line">Replica_SQL_Running_State: Replica has read <span class="keyword">all</span> relay log; waiting <span class="keyword">for</span> more updates # 复制 <span class="keyword">SQL</span> 进程状态</span><br><span class="line">Source_Retry_Count: <span class="number">86400</span> # 重试计数</span><br><span class="line">Source_Bind: # 主库绑定地址</span><br><span class="line">Last_IO_Error_Timestamp: # 最后一个 I<span class="operator">/</span>O 错误时间戳</span><br><span class="line">Last_SQL_Error_Timestamp: # 最后一个 <span class="keyword">SQL</span> 错误时间戳</span><br><span class="line">Source_SSL_Crl: # 主库 SSL CRL 文件路径</span><br><span class="line">Source_SSL_Crlpath: # 主库 SSL CRL 路径</span><br><span class="line">Retrieved_Gtid_Set: # 检索到的 GTID 集合</span><br><span class="line">Executed_Gtid_Set: # 执行的 GTID 集合</span><br><span class="line">Auto_Position: <span class="number">1</span> # 是否启用自动位置定位</span><br><span class="line">Replicate_Rewrite_DB: # 重写复制数据库</span><br><span class="line">Channel_Name: # 通道名称</span><br><span class="line">Source_TLS_Version: # 主库 TLS 版本</span><br><span class="line">Source_public_key_path: # 主库公钥路径</span><br><span class="line">Get_Source_public_key: <span class="number">1</span> # 获取主库公钥</span><br><span class="line">Network_Namespace: # 网络命名空间</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="验证主从复制"><a href="#验证主从复制" class="headerlink" title="验证主从复制"></a>验证主从复制</h3><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-17/img3.avif"></p><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><ul><li>主库和从库的主配置文件中2个server-id “不同的数字“</li><li>做主从架构的时候若是使用克隆虚拟机需要在&#x2F;var&#x2F;lib&#x2F;mysql&#x2F;auto.cnf下面修改uuid,在MySQL中查看uuid show variables like ‘%server_uuid%’;</li><li>MySQL数据库的版本不同也会有问题,MySQL 8 的版本安全性相对较高,在做主从复制的时候要去修改一个表的数据,这里就不作过多介绍了</li><li>Centos7的防火墙和SELinux一定要关闭</li></ul><p>更多关于MySQL主从复制的教程可以去从看看这篇文章<a href="https://blog.eucalyptus.cc/index.php/2023/09/17/mysql%E4%B8%BB%E4%BB%8E%E5%A4%8D%E5%88%B6%E9%85%8D%E7%BD%AE/">MySQL主从复制保姆级教程</a></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/09/17/f20bfe69/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>CentOS7中MySQLRPM包安装教程,</title>
      <link>https://blog.eucalyptus.cc/2023/09/16/ab3291b4/</link>
      <guid>https://blog.eucalyptus.cc/2023/09/16/ab3291b4/</guid>
      <pubDate>Fri, 15 Sep 2023 16:13:33 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;[&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;#%E5%9C%A8%E6%97%A5%E5%BF%97%E4%B8%AD%E6%9F%A5%E7%9C%8B%E5%AF%86%E7%A0%81&quot;&gt;在日志中查看密码&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;[复制密码&lt;/p&gt;
&lt;p&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>[</p><p><a href="#%E5%9C%A8%E6%97%A5%E5%BF%97%E4%B8%AD%E6%9F%A5%E7%9C%8B%E5%AF%86%E7%A0%81">在日志中查看密码</a></p><p>[复制密码</p><p><a href="#%E4%BF%AE%E6%94%B9MySQL%E5%AF%86%E7%A0%81">修改MySQL密码</a></p><p><a href="#%E6%96%B9%E6%B3%95%E4%B8%80">方法一</a></p><p><a href="#%E6%96%B9%E6%B3%95%E4%BA%8C">方法二</a></p><p><a href="#%E6%96%B9%E6%B3%95%E4%B8%89">方法三</a></p><p><a href="#%E4%BF%AE%E6%94%B9%E5%AF%86%E7%A0%81%E5%A4%8D%E6%9D%82%E5%BA%A6">修改密码复杂度</a></p><p><a href="#%E6%80%BB%E7%BB%93">总结</a></p><h3 id="引言"><a href="#引言" class="headerlink" title="引言"></a>引言</h3><p><a href="https://blog.eucalyptus.cc/index.php/2023/09/15/mysql%E5%AE%89%E8%A3%85%E4%BF%9D%E5%A7%86%E7%BA%A7%E6%95%99%E7%A8%8B/">MySQL</a>是一种开放源代码的关系型数据库管理系 RDBMS ,使用最常用的数据库管理语言–结构化查询语言 SQL 进行数据库管理,于1998年一月发行第一个版本。而MySQL数据库是作为程序员来说必备的一个组件,但是安装相对来说又是非常繁琐的,所以本文就给大家整理下MySQL的三种安装方法:</p><ul><li>二进制安装</li><li>源码编译安装</li><li>RPM包安装</li></ul><p>今天文章中主要介绍的是centos7中MySQL的RPM包安装</p><h3 id="检查安装环境"><a href="#检查安装环境" class="headerlink" title="检查安装环境"></a>检查安装环境</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br></pre></td><td class="code"><pre><span class="line">检查系统自带mariadb</span><br><span class="line">rpm -qa | grep -i mariadb</span><br><span class="line">卸载自带的mariadb</span><br><span class="line">rpm -evh mariadb-libs-5.5.60-1.el7-5.x86_64</span><br><span class="line">查看mariadb依赖</span><br><span class="line">yum list | grep -i mariadb</span><br><span class="line">卸载依赖</span><br><span class="line">yum remove -y mariadb-*</span><br></pre></td></tr></table></figure><h3 id="下载压缩包"><a href="#下载压缩包" class="headerlink" title="下载压缩包"></a>下载压缩包</h3><p>在官网下载tar包<a href="https://dev.mysql.com/">MySQL 官网</a></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img1.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img2.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img3.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img4.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img5.avif"></p><p>这里下载压缩包的方法有俩种:</p><ul><li>在windows中下载后上传到linux中</li><li>直接用wget命令在linux中下载</li></ul><p>我们这里选择wget下载tar包:</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">wget https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.43-1.el7.x86_64.rpm-bundle.tar</span><br><span class="line"></span><br></pre></td></tr></table></figure><p>若是下载很慢的话可以去看看这篇文章更换yum源<a href="https://blog.eucalyptus.cc/index.php/2023/07/13/%E9%85%8D%E7%BD%AEyum%E6%BA%90/">配置YUM源</a></p><p>也可以去百度网盘提取tar包[链接:<a href="https://pan.baidu.com/s/1ewuRkAvkQ2VrQ2gEohBaYg?pwd">https://pan.baidu.com/s/1ewuRkAvkQ2VrQ2gEohBaYg?pwd</a> ig2p](<a href="http://xn--https-bl8js66z7n7i//pan.baidu.com/s/1ewuRkAvkQ2VrQ2gEohBaYg?pwd">http://xn--https-bl8js66z7n7i//pan.baidu.com/s/1ewuRkAvkQ2VrQ2gEohBaYg?pwd</a> ig2p)<br>提取码:ig2p</p><h3 id="解压tar包"><a href="#解压tar包" class="headerlink" title="解压tar包"></a>解压tar包</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">tar -xvf mysql-5.7.43-1.el7.x86_64.rpm-bundle.tar</span><br></pre></td></tr></table></figure><p>解压后的rpm包</p><p>mysql-community-client-5.7.43-1.el7.x86_64.rpm<br>mysql-community-common-5.7.43-1.el7.x86_64.rpm<br>mysql-community-devel-5.7.43-1.el7.x86_64.rpm<br>mysql-community-embedded-5.7.43-1.el7.x86_64.rpm<br>mysql-community-embedded-compat-5.7.43-1.el7.x86_64.rpm<br>mysql-community-embedded-devel-5.7.43-1.el7.x86_64.rpm<br>mysql-community-libs-5.7.43-1.el7.x86_64.rpm<br>mysql-community-libs-compat-5.7.43-1.el7.x86_64.rpm<br>mysql-community-server-5.7.43-1.el7.x86_64.rpm<br>mysql-community-test-5.7.43-1.el7.x86_64.rpm</p><h3 id="RPM安装"><a href="#RPM安装" class="headerlink" title="RPM安装"></a>RPM安装</h3><p>选择需要的rpm包按下面顺序进行安装</p><p><strong>注意事项:这里安装rpm包的时候可能会缺少某些依赖,若是报错的话可以查看报错信息安装缺少的依赖即可,尤其是安装MySQL.8.0 以上版本的时候</strong></p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br></pre></td><td class="code"><pre><span class="line">rpm -ivh mysql-community-common-5.7.43-1.el7.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-libs-5.7.43-1.el7.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-client-5.7.43-1.el7.x86_64.rpm</span><br><span class="line">rpm -ivh mysql-community-server-5.7.43-1.el7.x86_64.rpm</span><br><span class="line"></span><br></pre></td></tr></table></figure><h3 id="MySQL配置"><a href="#MySQL配置" class="headerlink" title="MySQL配置"></a>MySQL配置</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br></pre></td><td class="code"><pre><span class="line">启动mysql</span><br><span class="line">systemctl start mysqld</span><br><span class="line">查看mysql状态</span><br><span class="line">systemctl status mysqld</span><br><span class="line">查看端口3306</span><br><span class="line">netstat -nltp</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img6.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img7.avif"></p><p>上述可以成功查看的到就证明MySQL启动成功,若是启动失败清理&#x2F;var&#x2F;lib&#x2F;mysql&#x2F;下的数据在启动</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">rm</span> -rf /var/lib/msyql/*</span><br></pre></td></tr></table></figure><h3 id=""><a href="#" class="headerlink" title=""></a></h3><h4 id="在日志中查看密码"><a href="#在日志中查看密码" class="headerlink" title="在日志中查看密码"></a>在日志中查看密码</h4><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">tail</span> /var/log/mysqld.log | grep password</span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img8.avif"></p><h4 id="复制密码"><a href="#复制密码" class="headerlink" title="复制密码"></a>复制密码</h4><p><strong>注意事项:这里的密码可能需要上一个反引号,因为有些特殊字符需要转义,例如 !</strong></p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">mysql -uroot -p<span class="string">&#x27;k.&lt;COpgI?6l7&#x27;</span></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img9.avif"></p><p>看到下面页面证明</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">systemctl stop mysqld</span><br><span class="line">systemctl start mysqld</span><br><span class="line"><span class="built_in">rm</span> -rf /var/lib/mysql/*</span><br><span class="line"><span class="built_in">tail</span> /var/log/mysqld.log | grep password</span><br></pre></td></tr></table></figure><h3 id="修改MySQL密码"><a href="#修改MySQL密码" class="headerlink" title="修改MySQL密码"></a>修改MySQL密码</h3><h4 id="方法一"><a href="#方法一" class="headerlink" title="方法一"></a>方法一</h4><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line"><span class="keyword">set</span> password <span class="string">&#x27;123 qaz&#x27;</span>;</span><br><span class="line">单引号中的是修改后的密码,密码要复杂一点</span><br><span class="line"></span><br></pre></td></tr></table></figure><h4 id="方法二"><a href="#方法二" class="headerlink" title="方法二"></a>方法二</h4><p>直接在命令行中修改</p><figure class="highlight text"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">\q退出数据库</span><br><span class="line">mysqladmin -uroot -p&#x27;123 qaz&#x27; password &#x27;123 qaz!&#x27;</span><br><span class="line"></span><br></pre></td></tr></table></figure><h4 id="方法三"><a href="#方法三" class="headerlink" title="方法三"></a>方法三</h4><h2 id="修改密码复杂度"><a href="#修改密码复杂度" class="headerlink" title="修改密码复杂度"></a>修改密码复杂度</h2><p>下面这个只是临时的修改,当数据库重启之后,就会恢复,需要永久生效则需要配置&#x2F;etc&#x2F;my.cnf文件</p><figure class="highlight sql"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br></pre></td><td class="code"><pre><span class="line">#查看密码复杂度策略</span><br><span class="line"><span class="keyword">show</span> variables <span class="keyword">like</span> <span class="string">&#x27;validate_password%&#x27;</span>;</span><br><span class="line">#设置密码验证的强度等级</span><br><span class="line"><span class="keyword">set</span> <span class="keyword">global</span> validate_password.policy LOW;</span><br><span class="line">#设置密码的长度</span><br><span class="line"><span class="keyword">set</span> <span class="keyword">global</span> validate_password.length <span class="number">4</span>;</span><br><span class="line"></span><br></pre></td></tr></table></figure><p><img src="https://img.eucalyptus.cc/blog-img/MYSQL/2023-09-16/img10.avif"></p><h3 id="总结"><a href="#总结" class="headerlink" title="总结"></a>总结</h3><ul><li>安装数据库需要的四个rpm包</li><li>安装mysql之前清理mariadb的依赖</li><li>若是启动和密码<br>若是想用其他的2种方法安装MySQL数据库可以参考<a href="https://blog.eucalyptus.cc/index.php/2023/09/15/mysql%E5%AE%89%E8%A3%85%E4%BF%9D%E5%A7%86%E7%BA%A7%E6%95%99%E7%A8%8B/">MySQL安装保姆级教程</a></li></ul>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/09/16/ab3291b4/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>关系型数据库和非关系型数据库的区别</title>
      <link>https://blog.eucalyptus.cc/2023/09/12/1ab8a930/</link>
      <guid>https://blog.eucalyptus.cc/2023/09/12/1ab8a930/</guid>
      <pubDate>Tue, 12 Sep 2023 10:24:39 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h3 id=&quot;什么是数据库&quot;&gt;&lt;a href=&quot;#什么是数据库&quot; class=&quot;headerlink&quot; title=&quot;什么是数据库&quot;&gt;&lt;/a&gt;什么是数据库&lt;/h3&gt;&lt;p&gt;数据库是结构化信息或数据的有序集合,一般以电子形式存储在计算机系统中。通常由&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h3 id="什么是数据库"><a href="#什么是数据库" class="headerlink" title="什么是数据库"></a>什么是数据库</h3><p>数据库是结构化信息或数据的有序集合,一般以电子形式存储在计算机系统中。通常由<a href="https://www.oracle.com/cn/database/what-is-database/#WhatIsDBMS">数据库管理系统 (DBMS)</a> 来控制。在现实中,数据、DBMS 及关联应用一起被称为数据库系统,通常简称为数据库。</p><p>为了提高数据处理和查询效率,当今最常见的数据库通常以行和列的形式将数据存储在一系列的表中,支持用户便捷地访问、管理、修改、更新、控制和组织数据。另外,大多数数据库都使用结构化查询语言 (SQL) 来编写和查询数据。</p><p>而数据库又可以分为关系型数据库和非关系型数据库。</p><h3 id="关系型数据库"><a href="#关系型数据库" class="headerlink" title="关系型数据库"></a>关系型数据库</h3><h4 id="概念"><a href="#概念" class="headerlink" title="概念"></a>概念</h4><p>关系型数据库是指采用了关系模型来组织数据的数据库。简单来说,关系模式就是二维表格模型。</p><p>主要代表:SQL Server,Oracle,Mysql,PostgreSQL。</p><h4 id="优点"><a href="#优点" class="headerlink" title="优点"></a>优点</h4><ul><li>容易理解,二维表的结构非常贴近现实世界,二维表格,容易理解。</li><li>使用方便,通用的sql语句使得操作关系型数据库非常方便。</li><li>易于维护,数据库的ACID属性,大大降低了数据冗余和数据不一致的概率。</li></ul><h4 id="瓶颈"><a href="#瓶颈" class="headerlink" title="瓶颈"></a>瓶颈</h4><ul><li>海量数据的读写效率。对于网站的并发量高,往往达到每秒上万次的请求,对于传统关系型数据库来说,硬盘I&#x2F;o是一个很大的挑战。</li><li>高扩展性和可用性。在基于web的结构中,数据库是最难以横向拓展的,当一个应用系统的用户量和访问量与日俱增的时候,数据库没有办法像web Server那样简单的通过添加更多的硬件和服务节点来拓展性能和负载能力。</li></ul><h3 id="非关系型数据库"><a href="#非关系型数据库" class="headerlink" title="非关系型数据库"></a>非关系型数据库</h3><h4 id="概念-1"><a href="#概念-1" class="headerlink" title="概念"></a>概念</h4><p>NoSQL非关系型数据库,主要指那些非关系型的、分布式的,且一般不保证ACID的数据存储系统,主要代表MongoDB,Redis、CouchDB。</p><p>NoSQL提出了另一种理念,以键值来存储,且结构不稳定,每一个元组都可以有不一样的字段,这种就不会局限于固定的结构,可以减少一些时间和空间的开销。使用这种方式,为了获取用户的不同信息,不需要像关系型数据库中,需要进行多表查询。仅仅需要根据key来取出对应的value值即可。</p><h4 id="缺点"><a href="#缺点" class="headerlink" title="缺点"></a>缺点</h4><p>但是由于Nosql约束少,所以也不能够像sql那样提供where字段属性的查询。因此适合存储较为简单的数据。有一些不能够持久化数据,所以需要和关系型数据库结合。</p><h4 id="分类"><a href="#分类" class="headerlink" title="分类"></a>分类</h4><p>非关系数据库大部分是开源的,实现比较简单,大都是针对一些特性的应用需求出现的。根据结构化方法和应用场景的不同,分为以下几类。</p><ul><li>面向高性能并发读写的key-value数据库,主要特点是具有极高的并发读写性能,例如Redis、Tokyo Cabint等。</li><li>面向海量数据访问的面向文档数据库,特点是,可以在海量的数据库快速的查询数据。例如MongoDB以及CouchDB.</li><li>面向可拓展的分布式数据库,解决的主要问题是传统数据库的扩展性上的缺陷。</li></ul><h3 id="区别"><a href="#区别" class="headerlink" title="区别"></a>区别</h3><h4 id="数据存储方式不同"><a href="#数据存储方式不同" class="headerlink" title="数据存储方式不同"></a>数据存储方式不同</h4><ul><li>主要差异在于数据存储的方式,关系型数据库是表格形式存储数据的,存储在鼠标的行和列中。数据表可以彼此关联写作存储,也容易提取数据</li><li>非关系型数据不适合存储在数据表的行和列中,而是大块组合在一起。通常存储在数据集中,就像文档、键值对或者图结构。数据及其特性是选择数据存储和提取方式的首要影响因素</li></ul><h4 id="扩展方式不同"><a href="#扩展方式不同" class="headerlink" title="扩展方式不同"></a>扩展方式不同</h4><ul><li>SQL和NoSQL数据库最大的差别可能是在扩展方式上,要支持日益增长的需求当然要扩展</li><li>要支持更多并发量,SQL数据库是纵向扩展,也就是说提高处理能力,使用速度更快速的计算机,这样处理相同的数据集就更快了。因为数据存储在关系表中,操作的性能瓶颈可能涉及很多个表,这都需要通过提高计算机性能来客服。虽然SQL数据库有很大扩展空间,但最终肯定会达到纵向扩展的上限</li><li>NoSQL数据库是横向扩展的。因为非关系型数据存储天然就是分布式的,NoSQL数据库的扩展可以通过给资源池添加更多普通的数据库服务器(节点)来分担负载</li></ul><h4 id="对事务性的支持不同"><a href="#对事务性的支持不同" class="headerlink" title="对事务性的支持不同"></a>对事务性的支持不同</h4><ul><li>如果数据操作需要高事务性或者复杂数据查询需要控制执行计划,那么传统的SQL数据库从性能和稳定性方面考虑是你的最佳选择。SQL数据库支持对事务原子性细粒度控制,并且易于回滚事务</li><li>虽然NoSQL数据库也可以使用事务操作,但稳定性方面没法和关系型数据库比较,所以它们真正闪亮的价值是在操作的扩展性和大数据量处理方面</li></ul><p>下面是一个简化的表格,以表格形式表示关系型数据库和非关系型数据库之间的区别:</p><table><thead><tr><th>特征</th><th>关系型数据库</th><th>非关系型数据库</th></tr></thead><tbody><tr><td>数据结构</td><td>表格 表 ,行,列</td><td>键值对,文档,列族,图形等</td></tr><tr><td>可扩展性</td><td>垂直扩展</td><td>水平扩展</td></tr><tr><td>灵活性</td><td>预定义模式和架构,需要修改表结构进行数据迁移</td><td>动态调整数据模型和结构</td></tr><tr><td>查询语言</td><td>结构化查询语言 SQL</td><td>不同的查询语言或API,如键值查询,文档查询等</td></tr><tr><td>数据一致性</td><td>ACID事务,强调数据一致性</td><td>最终一致性,强调可用性和分区容忍性</td></tr><tr><td>适用场景</td><td>强调数据一致性和复杂查询,事务处理</td><td>大数据量、高并发和灵活性要求较高的场景</td></tr></tbody></table><p>请注意,这只是一个概述,并不能完全涵盖所有数据库类型和特性。实际上,关系型数据库和非关系型数据库之间的差异更加复杂和多样化,具体的数据库产品可能具有不同的特性和功能。因此,在选择数据库时,最好根据实际需求和具体场景进行评估和比较。</p><p>当涉及到生活中的例子时,我们可以使用以下两个示例来说明关系型数据库和非关系型数据库之间的区别:</p><h3 id="示例1"><a href="#示例1" class="headerlink" title="示例1"></a>示例1</h3><p>        1.关系型数据库 RDBMS 示例:图书馆管理系统 在一个图书馆管理系统中,我们可以使用关系型数据库来存储和管理图书馆的数据。以下是数据库中可能包含的几个表:</p><ul><li>书籍表 Books table :包含书籍的信息,如书名、作者、出版社等。</li><li>借阅者表 Borrowers table :包含借阅者的信息,如姓名、借书卡号等。</li><li>借书记录表 Borrowing records table :用于跟踪借书记录,包含书籍ID、借阅者ID、借书日期、还书日期等。</li></ul><p>这些表之间通过主键和外键建立关联,例如,借书记录表中的书籍ID和借阅者ID可以与书籍表和借阅者表中的对应字段进行关联,形成关系。我们可以使用SQL查询语言进行各种查询操作,如查找某位借阅者借了哪些书籍、某本书的借阅历史等。</p><p>        2.非关系型数据库 NoSQL 示例:社交媒体用户数据 当涉及到社交媒体平台的用户数据时,非关系型数据库更适合处理动态和半结构化的数据。例如,假设我们有一个社交媒体平台,需要存储和管理用户的个人资料、好友关系和发布的帖子。</p><p>使用非关系型数据库,我们可以采用文档模型来存储用户数据。每个用户的个人资料可以表示为一个文档,其中包含各种字段,如用户名、年龄、兴趣爱好等。好友关系可以使用键值对存储,其中键表示用户ID,值表示其好友的列表。用户发布的帖子可以作为文档存储,其中包含帖子内容、发布时间、</p><p>在非关系型数据库中,我们可以使用特定的API或查询语言来搜索用户个人资料、查找某个用户的好友、获取帖子数据等。非关系型数据库的灵活性使其能够快速适应不断变化的数据结构和查询需求。</p><h3 id="示例2"><a href="#示例2" class="headerlink" title="示例2"></a>示例2</h3><p>以下是另外两个生活中的例子:</p><p>        1.关系型数据库 RDBMS 示例:学生课程管理系统 假设有一个学生课程管理系统,需要存储和管理学生的选课信息。在关系型数据库中,可以使用以下表来表示数据:</p><ul><li>学生表 Students table :包含学生的信息,如学号、姓名、年龄等字段。</li><li>课程表 Courses table :包含课程的信息,如课程编号、课程名称、学分等字段。</li><li>选课记录表 Course enrollment table :用于跟踪学生的选课记录,包含学生ID、课程ID、成绩等字段。</li></ul><p>这些表之间通过主键和外键进行关联,例如,选课记录表中的学生ID和课程ID可以与学生表和课程表中对应字段建立关系。使用SQL查询语言,可以进行各种查询操作,如查找某位学生的选课情况、某门课程的学生成绩等。</p><p>        2.非关系型数据库 NoSQL 示例:物联网传感器数据 考虑一个物联网应用场景,其中存在大量传感器设备收集实时数据,并需要将这些数据存储和处理。非关系型数据库更适合处理此类动态、半结构化的数据。</p><p>例如,假设有一个温度监测系统,每秒收集来自不同传感器的温度数据。非关系型数据库可以使用时间序列数据库来存储这些数据,其中每个数据点可以作为一个文档存储,包含时间戳、传感器ID、温度值等字段。</p><p>使用非关系型数据库,可以轻松地添加新的传感器数据点,而无需预先定义表结构。通过特定的API或查询语言,可以进行实时分析、聚合查询和数据可视化等操作。非关系型数据库的高可扩展性和灵活性使其适用于处理大规模的物联网数据。</p><p>通过这些例子,我们可以深入了解关系型数据库和非关系型数据库的不同之处。关系型数据库适用于结构化数据和复杂查询,而非关系型数据库则适用于半结构化和非结构化数据,并具备灵活性和可扩展性。选择适当的数据库类型取决于特定应用场景和数据需求。</p><p>参考文章:</p><p><a href="https://blog.eucalyptus.cc/index.php/2023/09/12/%E5%85%B3%E7%B3%BB%E5%9E%8B%E6%95%B0%E6%8D%AE%E5%BA%93%E5%92%8C%E9%9D%9E%E5%85%B3%E7%B3%BB%E5%9E%8B%E6%95%B0%E6%8D%AE%E5%BA%93%E7%9A%84%E5%8C%BA%E5%88%AB/">关系型数据库和非关系型数据库的区别 - Eucalyptus (blog.eucalyptus.cc)</a></p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/MYSQL/">MYSQL</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/MySQL/">MySQL</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E6%95%B0%E6%8D%AE%E5%BA%93/">数据库</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/09/12/1ab8a930/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>七牛云网站图床保姆级教程</title>
      <link>https://blog.eucalyptus.cc/2023/08/29/3d5e9a2f/</link>
      <guid>https://blog.eucalyptus.cc/2023/08/29/3d5e9a2f/</guid>
      <pubDate>Tue, 29 Aug 2023 00:25:27 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;引言&quot;&gt;&lt;a href=&quot;#引言&quot; class=&quot;headerlink&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="引言"><a href="#引言" class="headerlink" title="引言"></a>引言</h2><p>一个网站有图床（图片托管服务）可以带来以下好处：</p><ul><li><strong>节省存储空间</strong>：通过使用图床，您可以将网站上的图片存储在第三方服务器上，减少了您网站所需的存储空间。这对于需要大量图片的网站特别有用，尤其是当存储空间有限或成本较高时。</li><li><strong>提升网站加载速度</strong>：通过使用图床，您可以分散图片资源的加载压力，减轻了网站服务器的负担。第三方图床服务器通常具有更大的带宽和更高的资源利用率，可以更快地传输图片，改善用户访问网站时的加载速度和体验。</li><li><strong>防止图片盗链</strong>：图床提供防止图片盗链的功能，可以控制只有您的网站才能使用和显示托管在图床上的图片。这有助于防止其他网站未经授权地使用和消耗您的图片资源。</li><li><strong>精简备份和迁移过程</strong>：如果您需要备份或迁移整个网站，使用图床会更加方便。您只需备份或迁移网站的内容和链接，而不必单独处理和迁移所有图片文件。</li><li><strong>方便的管理和分享</strong>：图床通常提供用户友好的界面和管理工具，让您可以轻松上传、管理和分享图片。您可以根据需要对图片进行分类、标签和权限设置，并轻松地与其他人共享图片。</li></ul><p>总体而言，使用图床可以提供更高效、可靠和方便的图片托管服务，节省资源并提升用户体验。但请记住，选择一个可信赖和稳定的图床服务提供商非常重要，确保您的图片能够安全地存储和传输，而下面介绍的这款七牛云图床就可以完全实现上面的功能。</p><h2 id="创建存储空间"><a href="#创建存储空间" class="headerlink" title="创建存储空间"></a>创建存储空间</h2><p>打开官网<a href="https://www.qiniu.com/">七牛云 | 一站式场景化智能音视频 APaaS (qiniu.com)</a>登录后点击控制台，当然前提是你得完成七牛云的实名注册。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/01.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/02.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/03.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/04.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/05.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/06.avif"></p><h2 id="CDN配置"><a href="#CDN配置" class="headerlink" title="CDN配置"></a>CDN配置</h2><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/07.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/08.avif"></p><p>点击域名管理后按照下图设置，其他设置默认即可；这里的二级域名相当于在一级域名之前加了一个标识，例如你的一级域名是 baidu.com, 那么你在这里的二级域名可以设置为 lanan.baidu.com, 这里的 lanan 就相当于一个标识，可以随便设置，但在后面的设置中必须给这个标识进行解析。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/09.avif"></p><p>因为我的是配置过的，所以下面的 CNAME 和协议会和你们的不一样。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/10.avif"></p><h2 id="CNAME解析"><a href="#CNAME解析" class="headerlink" title="CNAME解析"></a>CNAME解析</h2><p>创建完成之后你可以看到域名生成对应的 CNAME，复制下来准备解析。这是官网的方法：<a href="https://developer.qiniu.com/fusion/kb/1322/how-to-configure-cname-domain-name">CNAME解析</a>。这里我们以阿里云为例子，其他平台也大同小异。</p><p>复制 CNAME 的值：</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/11.avif"></p><p>添加解析：</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/12.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/13.avif"></p><h2 id="配置HTTPS"><a href="#配置HTTPS" class="headerlink" title="配置HTTPS"></a>配置HTTPS</h2><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/14.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/15.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/16.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/17.avif"></p><p>这里的订单状态目前不是已签发，需要点击已签发这个位置进行设置，里面的验证选择下载验证文件进行验证，将下载的文件传输到自己网站的根目录下，然后点击验证即可。这里需要等待 15 分钟左右，最后看到这个位置显示已签发就证明配置成功。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/18.avif"></p><h2 id="验证"><a href="#验证" class="headerlink" title="验证"></a>验证</h2><p>点击到下面这个页面：</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/19.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/20.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/21.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/22.avif"></p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/23.avif"></p><p>复制外链后在浏览器打开看到上传的图片，证明配置成功。</p><p><img src="https://img.eucalyptus.cc/blog-img/%E5%9B%BE%E5%BA%8A/2023-08-29/24.avif"></p><p>到这里就已经算是完成了配制了，有什么问题可以联系博主，希望能够帮助到你。</p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/%E5%9B%BE%E5%BA%8A/">图床</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E4%B8%83%E7%89%9B%E4%BA%91/">七牛云</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%9B%BE%E5%BA%8A/">图床</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/CDN/">CDN</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/08/29/3d5e9a2f/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Docker生命周期和原理</title>
      <link>https://blog.eucalyptus.cc/2023/07/03/8b360202/</link>
      <guid>https://blog.eucalyptus.cc/2023/07/03/8b360202/</guid>
      <pubDate>Sun, 02 Jul 2023 17:57:43 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;1-Docker生命周期&quot;&gt;&lt;a href=&quot;#1-Docker生命周期&quot; class=&quot;headerlink&quot; title=&quot;1.Docker生命周期&quot;&gt;&lt;/a&gt;1.Docker生命周期&lt;/h2&gt;&lt;h3 id=&quot;废话少说直接看图&quot;&gt;&lt;a</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="1-Docker生命周期"><a href="#1-Docker生命周期" class="headerlink" title="1.Docker生命周期"></a>1.Docker生命周期</h2><h3 id="废话少说直接看图"><a href="#废话少说直接看图" class="headerlink" title="废话少说直接看图"></a>废话少说直接看图</h3><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2023-07-03/img1.avif" alt="Docker生命周期"></p><h2 id="2-Docker原理"><a href="#2-Docker原理" class="headerlink" title="2.Docker原理"></a>2.Docker原理</h2><h3 id="作为大神或者准架构师-架构师，一定要了解一下docker的底层原理。"><a href="#作为大神或者准架构师-架构师，一定要了解一下docker的底层原理。" class="headerlink" title="作为大神或者准架构师&#x2F;架构师，一定要了解一下docker的底层原理。"></a>作为大神或者准架构师&#x2F;架构师，一定要了解一下docker的底层原理。</h3><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2023-07-03/img2.avif" alt="Docker原理"></p><h3 id="所有对容器的修改动作，都只会发生在容器层里，只有容器层是可写的，其余镜像层都是只读的"><a href="#所有对容器的修改动作，都只会发生在容器层里，只有容器层是可写的，其余镜像层都是只读的" class="headerlink" title="所有对容器的修改动作，都只会发生在容器层里，只有容器层是可写的，其余镜像层都是只读的"></a>所有对容器的修改动作，都只会发生在容器层里，只有容器层是可写的，其余镜像层都是只读的</h3><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2023-07-03/img3.avif" alt="容器层"></p><p><img src="https://img.eucalyptus.cc/blog-img/Docker/2023-07-03/img4.avif" alt="分层结构"></p><h2 id="3-总结"><a href="#3-总结" class="headerlink" title="3. 总结"></a>3. 总结</h2><h3 id="一句话Docker是分层的"><a href="#一句话Docker是分层的" class="headerlink" title="一句话Docker是分层的"></a>一句话Docker是分层的</h3>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/07/03/8b360202/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>Centos7下安装Docker</title>
      <link>https://blog.eucalyptus.cc/2023/07/03/3c836bfe/</link>
      <guid>https://blog.eucalyptus.cc/2023/07/03/3c836bfe/</guid>
      <pubDate>Sun, 02 Jul 2023 17:30:58 GMT</pubDate>
      
        
        
          
          
      <description>&lt;p&gt;百科说：Docker</description>
          
        
      
      
      
      <content:encoded><![CDATA[<p>百科说：Docker 是一个开源的应用容器引擎，让开发者可以打包他们的应用以及依赖包到一个可移植的容器中，然后发布到任何流行的Linux机器上，也可以实现虚拟化，容器是完全使用沙箱机制，相互之间不会有任何接口。</p><p>看起来有点雾，用过虚拟机的应该对虚拟化技术有点印象，不知道也没关系，就把它当成轻量级的虚拟机吧（虽然一个是完全虚拟化，一个是操作系统层虚拟化）</p><p>百科又说：Docker 使用客户端-服务器 (C&#x2F;S) 架构模式 使用远程API来管理和创建Docker容器。Docker 容器（Container）通过 Docker 镜像（Image）来创建，二者之间的关系类似于面向对象编程中的对象与类</p><p>那Docker由什么组成呢， 包括三个基本概念:</p><ul><li>仓库（Repository）</li><li>镜像（Image）</li><li>容器(Container）</li></ul><p>打个比方：你如果想玩英雄联盟中骚气的亚索，你首先得有这个英雄（Docker的镜像），然后你得花金币去英雄商店（Docker的仓库）买，接着进游戏就会看到一个半蹲的发型飘逸的剑客（Docker的容器），所以：</p><p>1，其中Registry是Docker用于存放镜像文件的仓库，Docker 仓库的概念跟Git 类似（就像商店存放所有的英雄，只是更改英雄的权限在某些非程序员手里）。</p><p>2，所谓镜像就是构建容器的源代码，是一个只读的模板，由一层一层的文件系统组成的，类似于虚拟机的镜像（英雄也是只读的，有自己的技能被动，你也不能进行操作）。</p><p>3，那么容器就是由Docker镜像创建的运行实例，类似于虚拟机，容器之间是相互隔离的，包含特定的应用及其所需的依赖文件（好比每个英雄都是隔离的，都有自己的皮肤，技能以及走的路线)。</p><p>注：Docker Hub是Docker公司提供的一个注册服务器（Register）来保存多个仓库，每个仓库又可以包含多个具备不同tag的镜像。</p><h2 id="安装-Docker"><a href="#安装-Docker" class="headerlink" title="安装 Docker"></a>安装 Docker</h2><h3 id="1-开启linux内核流量转发"><a href="#1-开启linux内核流量转发" class="headerlink" title="1.开启linux内核流量转发"></a>1.开启linux内核流量转发</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">cat</span> &gt; /etc/sysctl.d/docker.conf &lt;&lt;<span class="string">EOF</span></span><br><span class="line"><span class="string">net.bridge.bridge-nf-call-ip6tables = 1</span></span><br><span class="line"><span class="string">net.bridge.bridge-nf-call-iptables = 1</span></span><br><span class="line"><span class="string">net.ipv4.conf.default.rp_filter = 0</span></span><br><span class="line"><span class="string">net.ipv4.conf.all.rp_filter = 0</span></span><br><span class="line"><span class="string">net.ipv4.ip_forward=1</span></span><br><span class="line"><span class="string">EOF</span></span><br><span class="line"></span><br><span class="line">modprobe br_netfilter</span><br><span class="line">sysctl -p /etc/sysctl.d/docker.conf</span><br></pre></td></tr></table></figure><h3 id="2-布置yum仓库"><a href="#2-布置yum仓库" class="headerlink" title="2.布置yum仓库"></a>2.布置yum仓库</h3><p>阿里云自带仓库，阿里云提供的docker专属repo仓库</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br></pre></td><td class="code"><pre><span class="line">curl -o /etc/yum.repos.d/docker-ce.repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo</span><br><span class="line">curl -o /etc/yum.repos.d/Centos-7.repo http://mirrors.aliyun.com/repo/Centos-7.repo</span><br></pre></td></tr></table></figure><h3 id="3-更新yum缓存"><a href="#3-更新yum缓存" class="headerlink" title="3.更新yum缓存"></a>3.更新yum缓存</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">yum clean all &amp;&amp; yum makecache</span><br></pre></td></tr></table></figure><h3 id="4-查看源中可用的版本"><a href="#4-查看源中可用的版本" class="headerlink" title="4.查看源中可用的版本"></a>4.查看源中可用的版本</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">yum list docker-ce --showduplicates | <span class="built_in">sort</span> -r</span><br></pre></td></tr></table></figure><h3 id="5-安装docker-ce"><a href="#5-安装docker-ce" class="headerlink" title="5.安装docker-ce"></a>5.安装docker-ce</h3><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">yum install -y docker-ce-20.16.7</span><br></pre></td></tr></table></figure><p>这里的版本可以随意选择</p><h3 id="6-配置docker加速器"><a href="#6-配置docker加速器" class="headerlink" title="6.配置docker加速器"></a>6.配置docker加速器</h3><p>使用docker首要操作就是获取镜像文件，默认下载是从Docker Hub下载，网速较慢，国内很多云服务商都提供了加速器服务，阿里云加速器，Daocloud加速器，灵雀云加速器。</p><p>先创建一个目录存储加速器</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line"><span class="built_in">mkdir</span> -p /etc/docker</span><br></pre></td></tr></table></figure><p>配置加速器文件</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">vim /etc/docker/daemon.json</span><br></pre></td></tr></table></figure><figure class="highlight json"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br><span class="line">21</span><br><span class="line">22</span><br><span class="line">23</span><br><span class="line">24</span><br><span class="line">25</span><br></pre></td><td class="code"><pre><span class="line"><span class="punctuation">&#123;</span></span><br><span class="line">    <span class="attr">&quot;registry-mirrors&quot;</span><span class="punctuation">:</span> <span class="punctuation">[</span></span><br><span class="line">        <span class="string">&quot;https://ghcr.geekery.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://hub.geekery.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.m.daocloud.io&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.rainbond.cc&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.ckyl.me&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.1panelproxy.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://2a6bf1988cb6428c877f723ec7530dbc.mirror.swr.myhuaweicloud.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://hub-mirror.c.163.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://mirror.baidubce.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://dockerhub.icu&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.registry.cyou&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker-cf.registry.cyou&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://dockercf.jsdelivr.fyi&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.jsdelivr.fyi&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://dockertest.jsdelivr.fyi&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://mirror.aliyuncs.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://dockerproxy.com&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.nju.edu.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.mirrors.sjtug.sjtu.edu.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://docker.mirrors.ustc.edu.cn&quot;</span><span class="punctuation">,</span></span><br><span class="line">        <span class="string">&quot;https://mirror.iscas.ac.cn&quot;</span></span><br><span class="line">    <span class="punctuation">]</span></span><br><span class="line"><span class="punctuation">&#125;</span></span><br></pre></td></tr></table></figure><h3 id="7-启动docker"><a href="#7-启动docker" class="headerlink" title="7.启动docker"></a>7.启动docker</h3><p>使刚才配置的加速器生效</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl daemon-reload</span><br></pre></td></tr></table></figure><p>设置开机自启动</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl <span class="built_in">enable</span> docker</span><br></pre></td></tr></table></figure><p>启动</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">systemctl start docker</span><br></pre></td></tr></table></figure><h3 id="8-检验docker是否安装并成功启动"><a href="#8-检验docker是否安装并成功启动" class="headerlink" title="8.检验docker是否安装并成功启动"></a>8.检验docker是否安装并成功启动</h3><p>查看进程</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">ps -ef | grep docker</span><br></pre></td></tr></table></figure><p>查看详细信息</p><figure class="highlight bash"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">docker version</span><br></pre></td></tr></table></figure>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/Docker/">Docker</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/%E8%BF%90%E7%BB%B4/">运维</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/Docker/">Docker</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/%E5%AE%B9%E5%99%A8/">容器</category>
      
      <category domain="https://blog.eucalyptus.cc/tags/CentOS/">CentOS</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/07/03/3c836bfe/#disqus_thread</comments>
      
    </item>
    
    <item>
      <title>网站提交搜索引擎</title>
      <link>https://blog.eucalyptus.cc/2023/05/08/faf925bf/</link>
      <guid>https://blog.eucalyptus.cc/2023/05/08/faf925bf/</guid>
      <pubDate>Mon, 08 May 2023 08:35:26 GMT</pubDate>
      
        
        
          
          
      <description>&lt;h2 id=&quot;一、前言&quot;&gt;&lt;a href=&quot;#一、前言&quot; class=&quot;headerlink&quot; title=&quot;一、前言&quot;&gt;&lt;/a&gt;一、前言&lt;/h2&gt;&lt;p&gt;将&lt;div class=&#39;anzhiyu-tag-link&#39;&gt;&lt;a class=&quot;tag-Link&quot;</description>
          
        
      
      
      
      <content:encoded><![CDATA[<h2 id="一、前言"><a href="#一、前言" class="headerlink" title="一、前言"></a>一、前言</h2><p>将<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://blog.eucalyptus.cc/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://blog.eucalyptus.cc/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://blog.eucalyptus.cc/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">我的网站</div>            <div class="tag-link-sitename">个人网站</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div>提交给搜索引擎是为了让搜索引擎更早地了解、索引和显示您的网站内容。以下是一些提交网站给搜索引擎的理由：</p><p>提高可见性：通过将您的网站提交给搜索引擎，可以提高您的网站在搜索结果中出现的机会。当用户搜索与您的网站相关的关键词时，搜索引擎将更容易找到并显示您的网站。<br>更快索引网页：搜索引擎通过网络爬虫（也称为<strong>蜘蛛</strong>）来发现新的网页内容。尽管搜索引擎蜘蛛会定期自动抓取和索引网页，但对于新建立的网站或刚发布的新内容，手动提交可以加快搜索引擎对您网站的索引速度。<br>更新通知：如果您的网站经常发布新的内容或更新现有内容，手动提交网站给搜索引擎可以让它们意识到您的网站有新的变化，以便更及时地更新索引。<br>修复索引问题：有时候，搜索引擎可能无法正确索引您的网站或内容，导致网站排名下降或无法出现在搜索结果中。在这种情况下，通过重新提交网站可以帮助搜索引擎重新审视和索引您的网站，以解决问题。</p><p>需要注意的是，尽管提交网站给搜索引擎可以加快索引速度和提高可见性，但并不保证搜索引擎会立即或完全索引您的网站。搜索引擎的索引算法是复杂的，排名和显示结果是基于多个因素综合考虑的。因此，除了提交网站给搜索引擎，还应该关注网站内容的质量、结构优化、外部链接等方面，以提高搜索引擎优化（<em><strong>SEO</strong></em>）效果。</p><h2 id="二、sitemap"><a href="#二、sitemap" class="headerlink" title="二、sitemap"></a>二、sitemap</h2><p>什么是网站地图？</p><p><strong>sitemap</strong>是一种视觉指南，它以图形化的形式展示网站的结构和内容布局。它帮助用户轻松导航，提升用户体验，并辅助搜索引擎优化。网站地图可以是规划、设计和维护网站时的关键工具，确保信息架构的清晰和易于访问。</p><h3 id="2-1、插件生成站点地图"><a href="#2-1、插件生成站点地图" class="headerlink" title="2.1、插件生成站点地图"></a>2.1、插件生成站点地图</h3><p>使用<strong>Yoast SEO</strong>插件可以自动生成<strong>sitemap</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/1.avif"></p><h3 id="2-2、工具生成网站地图"><a href="#2-2、工具生成网站地图" class="headerlink" title="2.2、工具生成网站地图"></a>2.2、工具生成网站地图</h3><p>工具链接：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.xml-sitemaps.com/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.xml-sitemaps.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.xml-sitemaps.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">XML Sitemaps Generator</div>            <div class="tag-link-sitename">在线工具</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/2.avif"></p><p>将生成的网站 <strong>sitemap.xml</strong> 文件上传至网站根目录后，搜索引擎就能更高效地抓取和索引页面内容，有助于提升网站在搜索结果中的可见性。确保文件路径正确，一般应为类似<code>https://www.yourdomain.com/sitemap.xml</code>的访问方式。</p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/3.avif"></p><h2 id="三、Bing"><a href="#三、Bing" class="headerlink" title="三、Bing"></a>三、Bing</h2><p><strong>Bing</strong>搜索引擎提交入口：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.bing.com/webmasters">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.bing.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.bing.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Bing Webmaster Tools</div>            <div class="tag-link-sitename">Bing</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></p><p><strong>Bing</strong>网站管理后台提交站点<strong>sitemap</strong></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/4.avif"></p><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://www.szlogic.net/learn/seo/site-submit/">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://www.szlogic.net/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://www.szlogic.net/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">SEO网站提交教程</div>            <div class="tag-link-sitename">SEO教程</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><h2 id="四、百度"><a href="#四、百度" class="headerlink" title="四、百度"></a>四、百度</h2><div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://ziyuan.baidu.com/property/index">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://ziyuan.baidu.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://ziyuan.baidu.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">百度搜索资源平台</div>            <div class="tag-link-sitename">百度SEO</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div><p>百度的平台公告已经发布了“关于回收网站提交配额的通知”该政策是因为需要打击灰产、低质量和未实名认证的网站，官方的完整说明：“由于近期黑产、作弊行为肆虐，大量抢占平台资源，严重影响用户体验，搜索资源平台针对非实名账户内站点、低质站点关停sitemap提交能力并调整API每日推送额度。请各站点做好日常维护和质量管理，资源平台将在节后陆续为合规站点恢复权益、调配额度。</p><h3 id="4-1、sitemap提交"><a href="#4-1、sitemap提交" class="headerlink" title="4.1、sitemap提交"></a>4.1、sitemap提交</h3><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/5.avif"></p><h3 id="4-2、手动提交"><a href="#4-2、手动提交" class="headerlink" title="4.2、手动提交"></a>4.2、手动提交</h3><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/6.avif"></p><h2 id="五、Google"><a href="#五、Google" class="headerlink" title="五、Google"></a>五、Google</h2><p><strong>Google</strong>搜索引擎提交入口：<div class='anzhiyu-tag-link'><a class="tag-Link" target="_blank" rel="noopener external nofollow noreferrer" href="https://search.google.com/search-console/about">    <div class="tag-link-tips">引用站外地址</div>    <div class="tag-link-bottom">        <div class="tag-link-left" data-icon="https://search.google.com/favicon.ico" style="width:60px;height:60px;min-width:60px;min-height:60px;position:relative;border-radius:var(--anzhiyu-border-radius);overflow:hidden;">          <img class="tag-link-favicon" src="https://search.google.com/favicon.ico" onerror="this.style.display='none';this.nextElementSibling.style.display='flex';" style="width:60px;height:60px;object-fit:cover;border-radius:var(--anzhiyu-border-radius);position:absolute;top:0;left:0;" alt="favicon"/>          <i class="fa-solid fa-link" style="display:flex;align-items:center;justify-content:center;width:100%;height:100%;"></i>        </div>        <div class="tag-link-right">            <div class="tag-link-title">Google Search Console</div>            <div class="tag-link-sitename">Google</div>        </div>        <i class="eucalyptus icon-angle-right"></i>    </div>    </a></div></p><p><img src="https://img.eucalyptus.cc/blog-img/WordPress/2023-05-08/7.avif"></p><p>使用<strong>Yoast SEO</strong>插件生成并提交网站的<strong>sitemap</strong>后，有时候可能会遇到<strong>Google</strong>搜索控制台提示<strong>无法检索</strong>的情况，其实这时候不必过于担心，通常过一会儿系统会自动显示成功，或者在你提交第二个网站地图后，问题也会自动解决。</p><p>当然你可以直接使用上面通过在线工具生成的<strong>sitemap.xml</strong>地图，这样能够方便快捷地为网站整理出结构清晰的索引，有助于搜索引擎更好地抓取和识别网页内容。 </p>]]></content:encoded>
      
      
      <category domain="https://blog.eucalyptus.cc/categories/WordPress/">WordPress</category>
      
      
      <category domain="https://blog.eucalyptus.cc/tags/SEO/">SEO</category>
      
      
      <comments>https://blog.eucalyptus.cc/2023/05/08/faf925bf/#disqus_thread</comments>
      
    </item>
    
  </channel>
</rss>
