<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>并发控制 on SILO</title>
    <link>https://silo.pgsty.com/zh/tags/%E5%B9%B6%E5%8F%91%E6%8E%A7%E5%88%B6/</link>
    <description>Recent content in 并发控制 on SILO</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    
    
    
      <lastBuildDate>Thu, 12 Nov 2026 03:50:08 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/zh/tags/%E5%B9%B6%E5%8F%91%E6%8E%A7%E5%88%B6/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>站点复制状态锁：在存储 I/O 与跨站 RPC 之前快照拓扑状态</title>
        <link>https://silo.pgsty.com/zh/blog/design/site-replication-lock-snapshots/</link>
        <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/zh/blog/design/site-replication-lock-snapshots/</guid>
        <description>为什么在 IAM 自愈、桶自愈、状态采集与同步钩子执行期间持有 SiteReplicationSys.RLock() 会在配置写锁排队时触发 Go sync.RWMutex 永久死锁；以及为什么将状态读锁收敛为纯内存叶节点快照是最小且完整的修复。</description>
      </item>
    
  </channel>
</rss>
