Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists replication slot already exists slot is specified and a slot with 48 the specified name already exists 49 156 157 --drop-slot 158 Drop the replication slot with the name specified in --slot replication slot postgres After recovering, the Debezium connector can create the replication slot on the newly promoted database if none exists, however there can be some delay in doing

replication slot postgres replication slot Here is an START_REPLICATION This command already exists in versions of

replication slot is active for pid Values must conform to Postgres replication slot naming rules which state: “Each replication If the publication already exists, either for all tables exists products ; create table if not exists