This article details the process of moving specific tables from one PostgreSQL instance to another using logical replication. It covers granting access, copying schema, setting up publications and subscriptions, and handling sequences and indexes to minimize downtime.

Motion transitioned from CockroachDB to Postgres due to escalating costs and operational challenges, particularly with migrations and ETL processes. The migration revealed better performance with Postgres for many queries, despite some initial advantages of Cockroach’s query planner. The move ultimately streamlined operations and resolved numerous UI and support issues experienced with CockroachDB.