What problem does it solve? After an initial bulk data load with molt fetch, source databases keep receiving writes. This Skill guides you through setting up continuous change-data-capture replication so your CockroachDB target stays in sync until cutover, eliminating manual delta-migration guesswork. ## Core Features & Use Cases - Multi-source CDC replication: Configure pglogical for PostgreSQL, mylogical for MySQL, oraclelogminer for Oracle, plus Kafka, object storage, and CockroachDB CDC sources. - Staged apply architecture: Buffer changes in a _replicator staging schema on the target cluster before applying them to target tables, with dead-letter-queue support for failed rows. - Full cutover workflow: Step-by-step guidance from molt fetch bulk load through publication/slot setup, preflight connectivity checks, lag monitoring via Prometheus metrics, and final cutover. - Use Case: You are migrating a production PostgreSQL database to CockroachDB. After running molt fetch for the initial load, use this Skill to start replicator pglogical, monitor replication lag on the metrics endpoint, and execute a low-lag cutover. ## Quick Start Ask the AI to walk you through starting replicator pglogical against your source PostgreSQL and target CockroachDB after a molt fetch load, including staging database creation and lag monitoring.