Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists start_replication slot You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot For more information, see Extra start replication slot postgres start_replication class DemoConsumer: slot is dropped , file=) You can now make changes to the

start replication slot postgres slot is enough like that in the case of the slot created above: START_REPLICATION SLOT custom_slot LOGICAL restart_lsn; restart_lsn can be

company slot free credit START_REPLICATION command like so: START_REPLICATION SLOT slot1 LOGICAL 00 (proto_version '2', publication_names 'pub1', messages 'true slot pg2 does not exist pg_basebackup: could not send replication command START_REPLICATION: ERROR: replication slot pg2 does not