EDB Replication Server v7 - Error messages

replication slot geo_secondary_my_domain_com does not exist ? This occurs when PostgreSQL does not have a replication slot for the secondary node by that name

Moving hash slots from a node to another does not require stopping any operations; therefore, adding and removing nodes, or changing the percentage of hash

replication slot does not exist To resolve these errors, remove the used replication slots, or increase the value of the max_replication_slots parameter Resolution Remove used replication

replication slot Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL