<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
  <channel>
    <title>数据库内核机制</title>
    <link>https://growdu.github.io/blog/</link>
    <description>数据库内核机制，讲到源码那一行</description>
    <language>zh-cn</language>
    <lastBuildDate>Fri, 20 Nov 2026 12:15:34 +0000</lastBuildDate>
    <atom:link href="https://growdu.github.io/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <itunes:author>growdu</itunes:author>
    <itunes:explicit>false</itunes:explicit>
    <itunes:subtitle>数据库内核机制，讲到源码那一行</itunes:subtitle>
    <itunes:summary>数据库内核机制，讲到源码那一行</itunes:summary>
    <item>
      <title>EP06 · 两个事务改同一行，谁先谁后</title>
      <link>https://growdu.github.io/blog/blog/2026/10/15/source-tracks/postgresql/transaction-mvcc/postgresql-row-lock-deep-dive/</link>
      <guid isPermaLink="false">growdu.cn/podcast/row-lock</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0800</pubDate>
      <description>MVCC 让读不挡写，但两个写会互相覆盖——行锁在它上面加了一层协调</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_row-lock.mp3" length="563526" type="audio/mpeg"/>
    </item>
    <item>
      <title>EP05 · 为什么 DDL 同步不能直接把 SQL 文本发过去</title>
      <link>https://growdu.github.io/blog/blog/2026/08/31/source-tracks/postgresql/logical-replication/postgresql-logical-replication-ddl-dml-ordering/</link>
      <guid isPermaLink="false">growdu.cn/podcast/structured-ddl</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0800</pubDate>
      <description>社区讨论的方向不是「把 DDL 当字符串发过去」，而是拆成带语义的结构化对象</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_structured-ddl.mp3" length="546822" type="audio/mpeg"/>
    </item>
    <item>
      <title>EP04 · 并行接收之后，谁先应用</title>
      <link>https://growdu.github.io/blog/blog/2026/08/24/source-tracks/postgresql/logical-replication/postgresql-logical-replication-ddl-trigger-apply-worker/</link>
      <guid isPermaLink="false">growdu.cn/podcast/parallel-apply</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0800</pubDate>
      <description>发布端并行了，订阅端还在排队；难的不是并行接收，而是判断哪两条事务不能同时应用</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_parallel-apply.mp3" length="567558" type="audio/mpeg"/>
    </item>
    <item>
      <title>EP03 · WAL 里的顺序，不等于事务的顺序</title>
      <link>https://growdu.github.io/blog/blog/2026/08/24/source-tracks/postgresql/logical-replication/postgresql-logical-replication-worker-model/</link>
      <guid isPermaLink="false">growdu.cn/podcast/wal-interleave</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0800</pubDate>
      <description>WAL 是操作级记录，几个事务交错着写；订阅端要的是「一个事务一整组」</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_wal-interleave.mp3" length="554310" type="audio/mpeg"/>
    </item>
    <item>
      <title>EP02 · 一个 64 位计数器，决定所有事务的提交顺序</title>
      <link>https://growdu.github.io/blog/blog/2026/10/19/source-tracks/postgresql/logical-replication/opengauss-csn-total-ordering/</link>
      <guid isPermaLink="false">growdu.cn/podcast/csn-total-ordering</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0800</pubDate>
      <description>并发提交的时间是乱的，但只要给每次 commit 分配一个单调递增的号，订阅端就能自己排好序</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_csn-total-ordering.mp3" length="565830" type="audio/mpeg"/>
    </item>
    <item>
      <title>EP01 · PostgreSQL 18 并行逻辑解码</title>
      <link>https://growdu.github.io/blog/blog/2026/10/10/source-tracks/postgresql/logical-replication/postgresql-logical-replication-end-to-end-flow/</link>
      <guid isPermaLink="false">growdu.cn/podcast/pg-parallel-decode</guid>
      <pubDate>Mon, 09 Nov 2026 00:00:00 +0800</pubDate>
      <description>openGauss 把发布端拆成三层线程：reader 读 WAL，worker 池并行解码，walsender 收口输出</description>
      <enclosure url="https://growdu.github.io/blog/audio/narration_pg-parallel-decode.mp3" length="519750" type="audio/mpeg"/>
    </item>
  </channel>
</rss>
