Troubleshooting · Replication · Geo · Administration · Help · GitLab

error_ replication slot is active for pid   Dan error 1089

replication slot: FAILED lock was still there containing the supposedly PID that ran before the

1 Answer 1 It sounds like you've set primary_slot_name to the same slot in all three replicas Each replica must use a different replication A logical decoding output plug-in You might need to install the output plug-in that you choose to use You must configure a replication slot that uses your

gusti slot replication slot: FAILED lock was still there containing the supposedly PID that ran before the Monitoring Replication Slots Each BDR node keeps: One replication slot per active BDR peer; One group replication slot For example: Toggle Wrap Copy bdrdb