<?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>Database on Peter.H's Full-Stack GAME</title><link>https://peter-notes.com/tags/database/</link><description>Recent content in Database on Peter.H's Full-Stack GAME</description><image><title>Peter.H's Full-Stack GAME</title><url>https://peter-notes.com/images/og-image.jpg</url><link>https://peter-notes.com/images/og-image.jpg</link></image><generator>Hugo</generator><language>zh-tw</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://peter-notes.com/tags/database/index.xml" rel="self" type="application/rss+xml"/><item><title>Schema 主表翻轉的 dual-write 過渡:一場不能 stop-the-world 的搬家</title><link>https://peter-notes.com/posts/schema-pivot-dual-write-migration/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://peter-notes.com/posts/schema-pivot-dual-write-migration/</guid><description>外部系統匯入的 customers 表跑了三年,現在想換成 SaaS 自己的 users 表為主。Stop-the-world 風險太高,dual-write 過渡是唯一可行解。本文拆解 3 階段 migration、partial cut-over、DISTINCT ON 去重、永久共存政策的設計考量與實戰踩坑。</description></item><item><title>資料庫同步的隱藏陷阱：Link Table 的重要性</title><link>https://peter-notes.com/posts/database-sync-link-table-pitfall/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://peter-notes.com/posts/database-sync-link-table-pitfall/</guid><description>從一次 401 Unauthorized 錯誤出發，深入探討資料庫同步時容易遺漏的 Link Table 問題，以及如何預防這個常見的陷阱</description></item><item><title>刪了 52 萬筆資料，為什麼硬碟空間沒變小？</title><link>https://peter-notes.com/posts/postgresql-vacuum-disk-space/</link><pubDate>Wed, 31 Dec 2025 00:00:00 +0000</pubDate><guid>https://peter-notes.com/posts/postgresql-vacuum-disk-space/</guid><description>實戰經驗：刪除 52 萬筆通知資料後，資料表從 207MB 完全沒縮小。深入理解 PostgreSQL MVCC 機制，比較 SQLite 的差異，以及為什麼 VACUUM 是每個後端工程師必須知道的知識。</description></item></channel></rss>