Create replication slot in pg_basebackup if requested

Connector getting Inactive due to replication slot PID already exists start_replication slot start-replication-task¶ You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot start_replication 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=

heart of the jungle slot The timeline ID associated with restart_lsn , following the current timeline history START_REPLICATION XXXXXX [ TIMELINE