Postgresql 11 logical replication - stuck in `catchup` state

Initial Synchronization Worker: Synchronizes initialexisting data from the publisher by creating a temporary replication slot and running a

Postgresql 11 logical replication - stuck in `catchup` state Slot-Based Query Execution Engine · Stable API · System Collections · Legacy The log message verbosity level for components related to replication See

Initial Synchronization Worker: Synchronizes initialexisting data from the publisher by creating a temporary replication slot and running a

replication slot does not exist PID holding the lock , and whether the lock has been globally One replication slot per active BDR peer; One group replication slot For

Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write

replication slot Also, replication slots on a given standby persist the promotion of that standby to a primary This means that in the event of a primary DB instance failover or

Replication slots must be enabled in by setting the parameter max_replication_slots to at least the number of expected standbys (changes to this