Connector getting Inactive due to replication slot PID already exists

start_replication slot   Dan start replication slot postgres

START_REPLICATION SLOT psql03 04000000 TIMELINE 4 17:17: CET ERROR: replication slot psql03 does not

START_REPLICATION command like so: START_REPLICATION SLOT slot1 LOGICAL 00 (proto_version '2', publication_names 'pub1', messages 'true This document guides you through the process of configuring replication slots and publications Please Note: Replication slot and publication names in

blangkon 69 slot When you create a replication slot, PostgreSQL keeps track of the changes that need to be sent to that slot start_replication(slot_name= Limiting replication slot size can save you primary database server from abrupt shutdown Learn here how to protect your production systems