Ensure PostgreSQL is configured with wal_level=logical and the Debezium user has REPLICATION and LOGIN privileges plus SELECT on the tables to capture
Set plugin.name to pgoutput in the connector configuration; pgoutput is the recommended decoder shipped with PostgreSQL 10+ and does not require installing a separate plugin
Specify publication.name if you want to use a pre-existing publication, or let Debezium create one automatically; set publication.autocreate.mode to filtered to limit it to the included tables
Set slot.name to a unique replication slot name; the slot must be unique per connector and persists on the PostgreSQL server until dropped
Configure table.include.list and column.exclude.list as needed to scope the CDC capture surface
Monitor replication lag via the pg_replication_slots view and Debezium metrics to detect slot growth that could exhaust WAL storage
Known gotchas
Replication slots retain WAL segments until the slot is consumed; a stopped connector with an unconsumed slot can cause disk exhaustion on the PostgreSQL server
pgoutput requires that all captured tables have a replica identity of FULL or DEFAULT with a primary key; tables with REPLICA IDENTITY NOTHING will not emit before images for updates and deletes
Dropping and recreating the connector does not drop the replication slot automatically; stale slots must be dropped manually with pg_drop_replication_slot
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp