replication slot mysub was not created in this database

replication as opposed to physical replication -C: The option allows you to create a replication slot before the backup gets underway

Failure cause: The specified replication slot already exists in source database Handling suggestion: Delete the replication slot from the

replication slot already exists The first reason why Redis Cluster can lose writes is because it uses asynchronous replication We can try to reshard 1000 hash slots, that should already

replication slot postgres my_slot replication slot, with the replication slots, check if the slot already exists or if there's a conflict with slot names