<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Luke Dev Notes</title>
    <link>https://lukedevnotes.com</link>
    <description>Software engineer specializing in Python, LLMs, AI agents, multi-agent systems, and agentic workflows; comfortable with ChatGPT, Gemini, and Claude; focused on production-ready AI and automation systems.</description>
    <language>en-us</language>
    <atom:link href="https://lukedevnotes.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL 效能優化（上）：LIKE 和 Regex，哪個比較快？</title>
      <link>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-1</link>
      <description>用白話拆解 LIKE 與 Regex 的差別：為什麼 Regex 可能讓 CPU 輕鬆一點，卻不一定能解決整表掃描帶來的 I/O 壓力。</description>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
      <guid>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-1</guid>
    </item>
    <item>
      <title>PostgreSQL 效能優化（中）：用 EXPLAIN 看見 Seq Scan 的真相</title>
      <link>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-2</link>
      <description>用 EXPLAIN ANALYZE 拆解 LIKE 與 Regex 的真實成本：為什麼 SQL 觸發點會變成多次 Seq Scan、B-tree 為何幫不上忙、Regex 狀態機只能壓 CPU 卻動不到 I/O。</description>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
      <guid>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-2</guid>
    </item>
    <item>
      <title>PostgreSQL 效能優化（下）：用 Array + GIN 把標籤變成索引</title>
      <link>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-3</link>
      <description>把『分號串起來的標籤字串』改成 PostgreSQL 原生 text[]，搭配 GIN 倒排索引，讓查詢從 Seq Scan 換成 Index Scan，附上資料模型遷移與 GIN 建立的實戰指令。</description>
      <pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
      <guid>https://lukedevnotes.com/posts/postgresql-gin-index-optimization-part-3</guid>
    </item>
  </channel>
</rss>