A proposal to force-drop replication slots to make disabling async

create_slot=false, enabled=false, slot_name=my_pub_slot); CREATE create_slot=false: This option specifies that we will not create a replication slot

The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL

replication slot does not exist 1 Answer You cannot start two WAL sender processes with the same replication slot If you need two clients to run logical decoding, create two

replication slot is active for pid When this slot should be active, because you have a secondary site configured using that slot, look for the PostgreSQL logs for the secondary site, to view why