
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s tech blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, distributed training, and data engineering.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Tue, 16 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/pg-upgrade/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies.en</guid>
    <title>PostgreSQL Version Upgrade Strategies — pg_upgrade and Logical Replication</title>
    <link>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies.en</link>
    <description>A practical comparison of three ways to perform a PostgreSQL major version upgrade: dump/restore, pg_upgrade, and logical replication. We cover downtime trade-offs, the pg_upgrade --link procedure and its caveats, near-zero-downtime upgrades via logical replication, verification and rollback, and managed upgrades on RDS and Aurora.</description>
    <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>postgresql</category><category>database</category><category>upgrade</category><category>pg-upgrade</category><category>logical-replication</category><category>rds</category><category>aurora</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies.ja</guid>
    <title>PostgreSQL バージョンアップグレード戦略 — pg_upgrade と論理レプリケーション</title>
    <link>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies.ja</link>
    <description>PostgreSQL のメジャーバージョンアップグレードを、dump/restore、pg_upgrade、論理レプリケーションの3つの方式で比較します。ダウンタイムのトレードオフ、pg_upgrade --link の手順と注意点、論理レプリケーションによる無停止アップグレードの手順、検証とロールバック、RDS/Aurora のマネージドアップグレードまで、実務の観点で整理します。</description>
    <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>postgresql</category><category>database</category><category>upgrade</category><category>pg-upgrade</category><category>logical-replication</category><category>rds</category><category>aurora</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies</guid>
    <title>PostgreSQL 버전 업그레이드 전략 — pg_upgrade와 논리 복제</title>
    <link>https://www.youngju.dev/blog/database/2026-06-16-postgresql-version-upgrade-strategies</link>
    <description>PostgreSQL 메이저 버전 업그레이드를 dump/restore, pg_upgrade, 논리 복제 세 가지 방식으로 비교합니다. 다운타임 트레이드오프, pg_upgrade --link 절차와 주의사항, 논리 복제 기반 무중단 업그레이드 단계, 검증과 롤백, RDS/Aurora 관리형 업그레이드까지 실무 관점에서 정리합니다.</description>
    <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>postgresql</category><category>database</category><category>upgrade</category><category>pg-upgrade</category><category>logical-replication</category><category>rds</category><category>aurora</category>
  </item>

    </channel>
  </rss>
