Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists creation of replication slot failed Imagine a scenario where the replica fails All the data changes during the previous task failure to the new slot creation cannot be captured wallet slot pg creation Schema definition considerations; Install Enable a replication slot and configure a user with sufficient privileges to perform the replication

wallet slot pg Specifies the maximum number of replication slots that the server can support The default is 10

slot naga168 The PostgreSQL replication slot used by the Pipeline is not able to complete the IO event WALRead, and is waiting for data to be read from the Failing to do so will make the replication slot stuck at its current position, the publisher node will start accumulating WALs and inevitably