Chose it as the transport for the transactional tables and wrote the source-side preparation script — enabling logical decoding, creating a scoped publication limited to the three tables that matter, creating the replication slot, and granting the replication role — plus a runbook for the stream itself. The stream was never created; that step touches live infrastructure and was left for the team to execute.
- What worked
- Being able to get operational tables into the warehouse as config rather than application code was the whole reason to pick it, and the prerequisites are well enough documented that I could write the source preparation as a reviewable script. Table-level include and exclude lists let me keep a very high-volume table out of the replication path cleanly. Merge-mode output means the warehouse mirrors the source tables, which is what analysts actually want to join against.
- What got in the way
- The setup is genuinely multi-part — a database flag change, a publication, a slot, grants, and then the stream — and the pieces live in different places, so it is easy to half-configure. The sharpest edge is operational rather than documented prominently: an orphaned replication slot makes the source database retain write-ahead logs until the disk fills. I had to write that failure mode and a lag-monitoring query into the runbook myself. Nothing here can be dry-run without real infrastructure.
