<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>数据安全 on Answer</title>
    <link>https://answer.freetools.me/tags/%E6%95%B0%E6%8D%AE%E5%AE%89%E5%85%A8/</link>
    <description>Recent content in 数据安全 on Answer</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>zh-cn</language>
    <lastBuildDate>Sat, 07 Mar 2026 07:20:09 +0800</lastBuildDate>
    <atom:link href="https://answer.freetools.me/tags/%E6%95%B0%E6%8D%AE%E5%AE%89%E5%85%A8/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>数据库已提交的事务为何会丢失？从fsync到异步提交的持久性权衡</title>
      <link>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E5%B7%B2%E6%8F%90%E4%BA%A4%E7%9A%84%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E4%BC%9A%E4%B8%A2%E5%A4%B1%E4%BB%8Efsync%E5%88%B0%E5%BC%82%E6%AD%A5%E6%8F%90%E4%BA%A4%E7%9A%84%E6%8C%81%E4%B9%85%E6%80%A7%E6%9D%83%E8%A1%A1/</link>
      <pubDate>Sat, 07 Mar 2026 07:20:09 +0800</pubDate>
      <guid>https://answer.freetools.me/%E6%95%B0%E6%8D%AE%E5%BA%93%E5%B7%B2%E6%8F%90%E4%BA%A4%E7%9A%84%E4%BA%8B%E5%8A%A1%E4%B8%BA%E4%BD%95%E4%BC%9A%E4%B8%A2%E5%A4%B1%E4%BB%8Efsync%E5%88%B0%E5%BC%82%E6%AD%A5%E6%8F%90%E4%BA%A4%E7%9A%84%E6%8C%81%E4%B9%85%E6%80%A7%E6%9D%83%E8%A1%A1/</guid>
      <description>深入解析数据库持久性的技术本质。从事务提交后数据丢失的困惑出发，剖析fsync性能瓶颈、操作系统页面缓存、SSD写入缓存三层缓冲机制；详解MySQL innodb_flush_log_at_trx_commit、PostgreSQL synchronous_commit、Redis appendfsync、MongoDB write concern等配置的实际含义；分析group commit优化与SSD电源故障保护(PLP)的关键作用；提供不同场景下的持久性配置决策框架。</description>
    </item>
  </channel>
</rss>
