<?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>Compatibility on SILO</title>
    <link>https://silo.pgsty.com/tags/compatibility/</link>
    <description>Recent content in Compatibility on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Mon, 24 Aug 2026 21:35:03 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/compatibility/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>CopyObject Checksums Must Cover Logical Object Bytes</title>
        <link>https://silo.pgsty.com/blog/design/copyobject-checksum/</link>
        <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/copyobject-checksum/</guid>
        <description>Destination compression made it possible for SILO to persist a checksum of the S2 storage stream instead of the logical CopyObject result. This design record reconstructs the failure, compares the rejected fixes, defines the plaintext-reader invariant, proves why the selected solution works, and records rollout and remediation boundaries.</description>
      </item>
    <item>
        <title>DSN-Only Database Notifications: A Compatibility Boundary for #53</title>
        <link>https://silo.pgsty.com/blog/design/notify-url/</link>
        <pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/notify-url/</guid>
        <description>SILO will keep PostgreSQL and MySQL notification targets, but standardize their configuration on complete connection strings. Pre-KV discrete database fields are an unsupported migration input and must abort server startup with an explicit error instead of being accepted and silently disabling every bucket notification.</description>
      </item>
    
  </channel>
</rss>
