<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pglogical on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/pglogical/</link>
    <description>Recent content in Pglogical on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/pglogical/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PostgreSQL Logical Replication: pglogical vs wal2json vs pgoutput</title>
      <link>https://www.pistack.xyz/posts/2026-05-10-postgresql-logical-replication-pglogical-wal2json-pgoutput-guide/</link>
      <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-10-postgresql-logical-replication-pglogical-wal2json-pgoutput-guide/</guid>
      <description>&lt;p&gt;PostgreSQL offers two replication paradigms: &lt;strong&gt;physical (streaming) replication&lt;/strong&gt;, which copies entire database clusters byte-for-byte, and &lt;strong&gt;logical replication&lt;/strong&gt;, which replicates individual tables, rows, and columns at the SQL level. While physical replication is ideal for read scaling and disaster recovery, logical replication enables selective data synchronization, multi-master setups, zero-downtime migrations, and change data capture (CDC) pipelines.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
