<?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>Locking on SILO</title>
    <link>https://silo.pgsty.com/tags/locking/</link>
    <description>Recent content in Locking on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Mon, 09 Nov 2026 12:30:06 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/locking/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Native Restore in Two Phases</title>
        <link>https://silo.pgsty.com/blog/design/native-restore-two-phase/</link>
        <pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/native-restore-two-phase/</guid>
        <description>Why a native restore held the object lock for its whole tier download, why the first fix of #281 also stranded failed ordinary uploads, and how staging outside the lock and a short, checked commit replace the private upload.</description>
      </item>
    <item>
        <title>Lock Domains of Large Single-Pool Clusters</title>
        <link>https://silo.pgsty.com/blog/design/single-pool-lock-domains/</link>
        <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/single-pool-lock-domains/</guid>
        <description>Why DELETE and CopyObject can fail to exclude PUT on the same key in a distributed single-pool deployment whose erasure sets do not share the same hosts, which layouts that covers, what the race does to xl.meta, and the smallest routing change that closes it.</description>
      </item>
    
  </channel>
</rss>
