How Patroni Addresses the Problem of the Logical Replication Slot

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

In this case, the hint in the first part of the log is misleading You don't need to increase the replication slots, you just need to fix the

replication slot The replication slot basically tells Postgres not to recycle or remove any WAL files that could ultimately prevent it from catching up with the

replication slot postgres In which replication is not working, I am also getting an error 'replication slot does replication slot does not exist' Can anyone please