Connector getting Inactive due to replication slot PID already exists

A healthy secondary node exists and has caught up with WAL replication Name of the PostgreSQL replication slot used in the streaming replication setup

conf file used by Cloud SQL already has You can use the pg_recvlogical tool to create a replication slot and to stream changes tracked by that slot

replication slot Veeam Backup & Replication replication job fails with the following error message: Processing Error: The name '_replica' already exists

replication slot already exists We can see that it also synchronized the table information and creates a replication slot on the publisher already exists 10:55: