How CloudNativePG manages physical replication slots for

ERROR: could not create replication slot sub1: ERROR: all DETAIL: Key = already exists LOG: worker process: logical

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 Caused by: DebeziumException: Creation of replication slot failed; when setting up multiple connectors for the same database host,

replication slot does not exist already exist: CREATE USER rivery WITH replication_role_name>; In case the Rivery user already exists, use the following SQL command to assign the new role