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 creation Schema definition considerations; Install Enable a replication slot and configure a user with sufficient privileges to perform the replication all slot sites The server will retain all WAL segments since replication slot creation When Debezium fails to connect, it returns a “Could not obtain

all slot sites Leaving a logical replication slot inactive prevents the vacuum from removing obsolete tuples from tables, so we recommend that you monitor replication slots

40 slot Postgres replication slot size keeps growing even though Debezium is consuming the WAL This consequently causes to run out of disk space The problem is also Failure cause: The specified replication slot already exists in source database Handling suggestion: Delete the replication slot from the