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

Thread: A proposal to force-drop replication slots to make disabling postgres delete replication slot The slot state state=present implies the slot must be present in the system state=absent implies the groups must be revoked from target_roles postgresql create replication slot We were able to successfully stop the PID on the primary and then drop the replication slot using SELECT pg_drop_replication_slot

postgresql create replication slot My understanding is that the replication slot prevents it from deleting that log, right? Until both the standby and

postgres delete replication slot On the primary site's database node, start a PostgreSQL console session: sudo gitlab-psql · Find the name of the relevant replication slot · Remove the The replication slot used here will be used in combination with pg_logical_slot_get_changes to consume each change of the slot (to compare with