Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists start_replication slot You must configure a replication slot that uses your chosen output plug-in before running the PostgreSQL server The plug-in can be one of the following: start replication slot postgres START_REPLICATION SLOT stolon_7063fb99 16AB000000 TIMELINE 1 T20:27:57Z appkeeper

start replication slot postgres START_REPLICATION SLOT slot_name LOGICAL XXXXXX Instructs server to start streaming WAL for logical replication

sky queen slot demo ** * START_REPLICATION SLOT slot_name LOGICAL XXXXXX * private String createStartLogicalQuery The size of the replication slot is in hundreds of GB, approaching 1 TB PostgreSQL cannot replay the WAL in memory and must write to disk before streaming