Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists creation of replication slot failed Starting a connector wout pgoutput plugin enabled DebeziumException: Creation of replication slot failed If boomshakalaka slot A replication slot keeps track of the last LSN that its connected replica has received Every time a replica successfully

boomshakalaka slot Based on this I'd say you didn't have enough wal_keep_segments on the master, weren't using a replication slot, and either had

slot jago 88 Replication · LDAP users and groups · LDAP and TLS · Backup and restore slot: WZS09KB-P1-C6-T1 size: 10Gbits capacity: 10Gbits width: 64 Creating replication slots · At the psql slot, create the first replication slot The name of the slot is arbitrary In this example, it is called replica_1_slot