Reference library

Content library

Every guide and procedure on the site, organized into four areas. Start at a section overview, then drill into a topic or a hands-on walkthrough.

How the four reference areas fit together A left-to-right path across the top row of three areas, over a full-width band for the fourth. Area 01, architecture and fundamentals, covers WAL decoding, replication slots, publications and trust boundaries. An arrow leads to area 02, setup and management, which covers creating publications, initializing slots, and running and recovering subscriptions. A second arrow leads to area 03, the CDC pipeline, which parses the pgoutput stream, routes changes to Kafka, and transforms JSON to Avro. Beneath all three sits area 04, replication topologies and failover operations, the resilience layer covering failover and slot recovery, conflict resolution, and online schema change. AREA 01 · FUNDAMENTALS Architecture WAL decoding, replication slots, trust boundaries AREA 02 · OPERATIONS Setup & management Create publications, init slots, run subscriptions AREA 03 · PIPELINES CDC pipeline Parse pgoutput, route to Kafka, transform to Avro AREA 04 · RESILIENCE — RUNS ACROSS ALL THREE Topologies & failover operations Failover & slot recovery · bidirectional conflict resolution · online schema change
The first three areas form one path — architecture fundamentals feed the setup and management workflow, which feeds a Python and Debezium change-data-capture pipeline — while topologies and failover operations run underneath all three to keep them resilient in production.
CDC Pipeline Implementation with Python & Debezium

Change Data Capture pipelines built on PostgreSQL logical replication and Debezium fail in production for structural reasons, not exotic ones: a disconnected consumer pins restartlsn and floods pgwal until the primary...

Section overview
Logical Replication Setup & Management

Running PostgreSQL logical replication in production is less about the initial CREATE PUBLICATION statement and more about governing the Write-Ahead Log (WAL) lifecycle, replication slot retention, and consumer...

Section overview
PostgreSQL Logical Replication Architecture & Fundamentals

PostgreSQL logical replication operates at the row and transaction level, decoding committed changes from the Write-Ahead Log and replaying them as logical INSERT, UPDATE, and DELETE operations on a subscriber — unlike...

Section overview
Replication Topologies & Failover Operations

Running logical replication across more than one node turns a stream you configured once into a system you have to operate, and the sharpest edge is that a PostgreSQL logical replication slot lives only on the node that...

Section overview