Connector getting Inactive due to replication slot PID already exists

start_replication slot   Dan start_replication slot

The slot minimum LSN is: 015603E18 The disaster slot minimum LSN START_REPLICATION 015000000 success :

START_REPLICATION SLOT tail: 無効な行数です: `' $ tail -n 50 grep START_REPLICATION slot => 'myreplslot' , on_message => sub { my Issues the START_REPLICATION SLOT command and immediately returns

slot paris You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot For more information, see Extra 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