Thread: A proposal to force-drop replication slots to make disabling

The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the

Thread: A proposal to force-drop replication slots to make disabling If there is a switchoverfailover to promote one of the standby, the new primary won't have any idea about the replication slot maintained by

The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the

dropz slot demo If you are not actively consuming a replication slot you should drop it To drop a replication slot called test_slot using SQL: SELECT

A replication slot is a data structure that marks a position in the WAL Whenever the standby server has consumed WAL, it sends feedback to the primary, which

drop replication slot The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the

Check if there is any replication lag, and when it reaches zero, run DROP SUBSCRIPTION on the subscriber This will drop the replication slot on